Translate a page into zh-hans

Author: xfq

pages/language_framework_overview.html

@@ -73,7 +73,7 @@ <h2>The Language Matrix</h2>
 <p>The matrix should allow us to get an overall idea of how well the Web is supported for local users around the world, and help identify and prioritise areas where work is needed.</p>
 
 <figure id="fig_lang_matrix">
-<img src="language_framework_overview-data/lang_matrix.png" alt="">
+<img src="language_framework_overview-data/lang_matrix.png" alt="The language matrix">
 <figcaption>Partial view of the language matrix.</figcaption>
 </figure>
 
@@ -112,7 +112,7 @@ <h2>Gap analysis</h2>
 <p>Gap analysis documents are not focused on solutions – only on clarifying barriers to use. They also provide important information for prioritising work on solutions, based on the pain they create for the local community. They contain quite specific information, and parts of that information will hopefully be obsoleted and updated as time goes by and issues are addressed. (See <a href="https://github.com/w3c/typography/wiki/Setting-up-a-Gap-Analysis-Project">Setting up a Gap Analysis Project</a> for more information.)</p>
 
 <figure id="fig_jlreq_gaps">
-<img src="language_framework_overview-data/jlreq_gaps.png" alt="" style="height: 60rem;">
+<img src="language_framework_overview-data/jlreq_gaps.png" alt="An example of a gap report for Devanagari and other scripts" style="height: 60rem;">
 <figcaption>An example of a gap report for Devanagari and various others scripts that has been taken to a successful conclusion.</figcaption>
 </figure>
 
@@ -136,7 +136,7 @@ <h2>Expert networks</h2>
 <p>The <a href="https://github.com/w3c/sealreq/">sealreq</a> (Southeast Asian) task force was the trail blazer here. We started the group without editors, but just focused on discussion on GitHub issue lists. W3C staff capture the information that is coming out of that forum, and we have gap analysis documents in progress for Khmer, Lao, and Javanese.</p>
 
 <figure id="fig_sealreq_repo">
-<img src="language_framework_overview-data/sealreq_repo.jpg" alt="">
+<img src="language_framework_overview-data/sealreq_repo.jpg" alt="The GitHub repository and issue list for the Sealreq group.">
 <figcaption>The GitHub repository and issue list for the Sealreq group.</figcaption>
 </figure>
 </section>
@@ -154,7 +154,7 @@ <h2>Language enablement index</h2>
 <p>The links to GitHub discussions point to threads in the relevant Language Enablement groups, but also point to discussions in W3C repositories used by CSS, SVG, HTML, etc working groups.</p>
 
 <figure id="fig_layout_index">
-<img src="language_framework_overview-data/layout_index.png" alt="" style="height: 30rem;">
+<img src="language_framework_overview-data/layout_index.png" alt="A section in the Chinese Script Resources page." style="height: 30rem;">
 <figcaption>A section in the <a href="https://www.w3.org/TR/hani-lreq/#emphasis">Chinese Script Resources</a> page, which is linked to from the Language Enablement Index.</figcaption>
 </figure>
 </section>
@@ -175,10 +175,10 @@ <h2>Issue tracking</h2>
 <p>Those issues can also be found from the <a href="http://w3c.github.io/i18n-activity/textlayout/" rel="nofollow">Text Layout Issue Tracker</a>, which also allows you to filter the results by type and by language. For example, to see what information is currently needed for chinese, click on <a href="http://w3c.github.io/i18n-activity/textlayout/?filter=type-info-request+han" rel="nofollow">this link</a>. The information is grouped according to the same feature types.</p>-->
 
 
-<p>Various mailing lists belonging to the W3C Internationalization Interest Group receive notifications about GitHub activity.  For example, whenever a GitHub issue is created, raised, added to, or closed in the <a href="https://github.com/w3c/sealreq/issues">Southeast Asian Layout</a> repository, the <a href="https://lists.w3.org/Archives/Public/public-i18n-sea/" rel="nofollow">public-i18n-sealreq</a> mailing list is notified via daily digests. The digest notifications not only capture activity in that repository, but also report changes to issues in the CSS, HTML, etc, repositories that have a <code>sealreq</code> label.</p>
+<p>Various mailing lists belonging to the W3C Internationalization Interest Group receive notifications about GitHub activity.  For example, whenever a GitHub issue is raised, commented, or closed in the <a href="https://github.com/w3c/sealreq/issues">Southeast Asian Layout</a> repository, the <a href="https://lists.w3.org/Archives/Public/public-i18n-sea/" rel="nofollow">public-i18n-sealreq</a> mailing list is notified via daily digests. The digest notifications not only capture activity in that repository, but also report changes to issues in the CSS, HTML, etc, repositories that have a <code>sealreq</code> label.</p>
 
 <figure id="fig_notifications">
-<img src="language_framework_overview-data/notifications.png" alt="">
+<img src="language_framework_overview-data/notifications.png" alt="An example of a daily notification digest">
 <figcaption>An example of how a daily notification digest might look. (The issue titles are links that take you directly to the issue.)</figcaption>
 </figure>
 </section>
@@ -192,7 +192,7 @@ <h2>Type samples</h2>
 <p>Another recently added resource, the <a href="https://w3c.github.io/type-samples/" rel="nofollow">Type Samples Repo</a>, provides a place to store pictures or scans of text layout features in the wild. Again, you can filter the results by the standard feature types, by language, and by medium.</p>
 
 <figure id="fig_type_samples">
-<img src="language_framework_overview-data/type_samples.png" alt="">
+<img src="language_framework_overview-data/type_samples.png" alt="An example of results from the type samples repository search.">
 <figcaption>An example of results from the type samples repository search.</figcaption>
 </figure>
 </section>
@@ -212,7 +212,7 @@ <h2>International issue repository</h2>
 <section id="layout-requirements-groups">
 <h2>Layout requirements groups</h2>
 
-<p>Work on defining gap-analysis and requirements is carried out in a number of 'lreq' groups. See the <a href="https://www.w3.org/International/groups/#mission" rel="nofollow">current list of groups</a>. Some groups are only expert networks, discussing issues on GitHub issue lists.  Others are principally working on gap analysis documents. Yet others are heavily focused on producing layout requirements documents. Groups can move between these categories, depending on the available contributors.</p>
+<p>Work on defining gap-analysis and requirements is carried out in a number of 'lreq' groups. See the <a href="https://www.w3.org/International/i18n-drafts/nav/about#groups" rel="nofollow">current list of groups</a>. Some groups are only expert networks, discussing issues on GitHub issue lists.  Others are principally working on gap analysis documents. Yet others are heavily focused on producing layout requirements documents. Groups can move between these categories, depending on the available contributors.</p>
 <p>A typical group producing documents would have one or more chairs and meet regularly for teleconferences. Key contributors to the group's deliverables form a core. They include document editors, but also those who regularly contribute time for review and discussion.</p>
 <p>Beyond that group lie any number of people who follow the work by subscribing to the notification emails and occasionally contributing comments to issues. The W3C has made participation in these groups as easy as possible. These people can comment on and track developments related to a particular script or group of scripts.</p>
 </section>
@@ -252,7 +252,7 @@ <h2>Related links</h2>
 <li>
 <a href="https://www.w3.org/International/talks/1703-jleq/index.html" rel="nofollow">Next Steps for Japanese Script Support</a> (also available in <a href="https://www.thetype.com/2017/03/11613/" rel="nofollow">Chinese</a>). Talk by r12a at a JEPA seminar in Tokyo, March 2017.</li>
 <li>
-<a href="http://unicodeconference.com/presentations-41/S5T3-Esfahbod.pdf" rel="nofollow">Comparative Analysis of W3C Text Layout Requirements</a>. Talk by Behnam Esfahbod at the Internationalization &amp; Unicode Conference, October 2017.</li>
+<a href="https://www.unicodeconference.org/presentations-41/S5T3-Esfahbod.pdf" rel="nofollow">Comparative Analysis of W3C Text Layout Requirements</a>. Talk by Behnam Esfahbod at the Internationalization &amp; Unicode Conference, October 2017.</li>
 <li>
 <a href="https://www.w3.org/International/talks/1810-paris/" rel="nofollow">Making the World Wide Web worldwide</a> (Paris Web presentation, Paris, France, October 2018)</li>
 </ul>