gap-analysis Rework the introduction

Points to Script Resources. Moves Contributors out of intro. Condenses Prioritization.

Author: r12a

gap-analysis/java-gap.html

@@ -85,34 +85,34 @@
 
 
 
-<section id="h_introduction">
-<h2>Introduction</h2>
-
-
 <section id="contributors">
 <h2>Contributors</h2>
 
-<p>This document was created by Richard Ishida.</p>
+<p>The framework of this document was created by Richard Ishida. The text for most gap descriptions is automatically pulled from GitHub issues, and that text may have been written or contributed to by others.</p>
+
 <!--
-<p>The following people contributed information to the gap reports in this document (in alphabetic order): This Person, That Person, etc</p>
+<p>Special thanks to the following people who contributed to this document (contributors' names listed in in alphabetic order).</p>
+
+<p class="acknowledgement">This Person, That Person, etc</p>
 -->
-<p data-lang="en">See also the <a href="https://github.com/w3c/sealreq/graphs/contributors">GitHub contributors list</a> for the Southeast Asian Language Enablement project, and the <a href="https://github.com/w3c/sealreq/issues?q=is%3Aissue+label%3As%3Ajava">discussions related to the Javanese script</a>.</p>
+
+<p data-lang="en">See also the <a href="https://github.com/w3c/sealreq/graphs/contributors" target="_blank">GitHub contributors list</a> for the Southeast Asian Language Enablement project, and the <a href="https://github.com/w3c/sealreq/issues?q=is%3Aissue+label%3As%3Ajava" target="_blank">discussions related to the Javanese script</a>.</p>
 </section>
 
 
 
 
 
 
-<section id="about">
+<section id="h_introduction">
 <h2>About this document</h2>
 
+
 <p>The W3C needs to make sure that the  needs of scripts and languages around the world are built in to technologies such as HTML, CSS, SVG, etc. so that Web pages and eBooks can look and behave as people expect around the world.</p>
 
 <p>This page documents difficulties that people encounter when trying to use languages written in the Javanese script on the Web.</p>
 
 <p>Having identified an issue, it investigates the current status with regards to web specifications and implementations by user agents (browsers, e-readers, etc.), and attempts to prioritise the severity of the issue for web users.</p>
-</section>
 
 
 
@@ -137,26 +137,27 @@ <h3>Prioritization</h3>
 
 <p>It is important to note that these colours do not indicate to what extent a particular feature is broken. They indicate the impact of a broken or missing feature on the content author or end user.</p>
 
-<p>Basic styling is the level that would be generally accepted as sufficient for most Web pages. Advanced level support would include additional features one might expect to include in ebooks or other advanced typographic formats. There may be features of a script or language that are not supported on the Web, but that are not generally regarded as necessary (usually archaic or obscure features). In this case, the feature can be described here, but the status should be marked as OK.</p>
+<p>A cell can be scored as OK if the feature in question is specified in an appropriate specification (including Candidate Recommendations), and is supported by at least two major browser engines. </p>
 
-<p>The decision as to what priority level is assigned to a described gap is down to the experts doing the gap analysis. It may not always be straightforward to decide. If a given section in this document refers to more than one feature that is broken, each with different impacts on Web users, the priority for the section should be the lowest denominator.</p>
+<p>Advanced level support includes features that one might expect to include in ebooks or other advanced typographic formats. If a feature of a script or language is not supported on the Web, but is not generally regarded as necessary (usually archaic or obscure features), even if the feature is described here, the status may be marked as OK. The decision as to what priority level is assigned to a described gap is down to the experts doing the gap analysis. It may not always be straightforward to decide.</p>
 
-<p>A cell can be scored as OK if the feature in question is specified in an appropriate specification, and is supported by user agents. A specification that is in CR or later and has two implementations in 'major' browsers will count. This means that the feature may not be supported in all browsers yet. (At some point in the future we may try to distinguish, visually, whether support is available in a specification but still pending in major browsers or applications.) </p>
+<p>If a given section in this document refers to more than one feature that is broken, each with different impacts on Web users, the priority for the section will be the lowest denominator.</p>
 </section>
 
 
 
 
 
 
+
 <section id="related">
-<h2>Related information</h2>
+<h3>Related documents</h3>
 
-<p>A summary of this report and others can be found as part of the <a href="https://www.w3.org/International/typography/gap-analysis/language-matrix.html" target="_blank">Language Matrix</a>.</p>
+<p>A summary of this report and others can be found as part of the <a href="https://www.w3.org/International/typography/gap-analysis/language-matrix.html" target="_blank" style="font-size: 120%;">Language Matrix</a>.</p>
 
-<p>Gap reports are brought to the attention of spec and browser implementers, and are tracked via the <a href="https://github.com/orgs/w3c/projects/95" target="_blank">Gap Analysis Pipeline</a>. (<a href="https://github.com/orgs/w3c/projects/95/views/1?filterQuery=label%3A%22s%3Ajava%22" target="_blank">Filter for Javanese script items</a>)</p>
+<p>Gap reports are brought to the attention of spec and browser implementers, and are tracked via the <a href="https://github.com/orgs/w3c/projects/95" style="font-size: 120%;" target="_blank">Gap Analysis Pipeline</a>. Find the <a href="https://github.com/orgs/w3c/projects/95/views/1?filterQuery=label%3A%22s%3Ajava%22" target="_blank">Javanese items</a>.</p>
 
-<p>See also <a href="https://www.w3.org/TR/java-lreq/" target="_blank">Javanese Script Resources</a> for information about the Javanese script.</p>
+<p>For more information about the Javanese script, including requirements, tests, GitHub discussions, type samples, and more, see <a  style="font-size: 120%;" href="https://www.w3.org/TR/java-lreq/" target="_blank">Javanese Script Resources</a>.</p>
 </section>
 </section>
 
@@ -168,6 +169,10 @@ <h2>Related information</h2>
 
 
 
+
+
+
+
 <section id="direction">
 <h2>Text direction</h2>
 

gap-analysis/khmr-gap.html

@@ -84,34 +84,35 @@
 
 
 
-<section id="h_introduction">
-<h2>Introduction</h2>
-
 
 <section id="contributors">
 <h2>Contributors</h2>
 
-<p>This document was created by Richard Ishida.</p>
+<p>The framework of this document was created by Richard Ishida. The text for most gap descriptions is automatically pulled from GitHub issues, and that text may have been written or contributed to by others.</p>
+
 <!--
-<p>The following people contributed information to the gap reports in this document (in alphabetic order): This Person, That Person, etc</p>
+<p>Special thanks to the following people who contributed to this document (contributors' names listed in in alphabetic order).</p>
+
+<p class="acknowledgement">This Person, That Person, etc</p>
 -->
-<p data-lang="en">See also the <a href="https://github.com/w3c/sealreq/graphs/contributors">GitHub contributors list</a> for the Southeast Asian Language Enablement project, and the <a href="https://github.com/w3c/sealreq/issues?q=is%3Aissue+label%3As%3Akhmr">discussions related to the Khmer script</a>.</p>
+
+<p data-lang="en">See also the <a href="https://github.com/w3c/sealreq/graphs/contributors" target="_blank">GitHub contributors list</a> for the Southeast Asian Language Enablement project, and the <a href="https://github.com/w3c/sealreq/issues?q=is%3Aissue+label%3As%3Akhmr" target="_blank">discussions related to the Khmer script</a>.</p>
 </section>
 
 
 
 
 
 
-<section id="about">
+<section id="h_introduction">
 <h2>About this document</h2>
 
+
 <p>The W3C needs to make sure that the  needs of scripts and languages around the world are built in to technologies such as HTML, CSS, SVG, etc. so that Web pages and eBooks can look and behave as people expect around the world.</p>
 
 <p>This page documents difficulties that people encounter when trying to use languages written in the Khmer script on the Web.</p>
 
 <p>Having identified an issue, it investigates the current status with regards to web specifications and implementations by user agents (browsers, e-readers, etc.), and attempts to prioritise the severity of the issue for web users.</p>
-</section>
 
 
 
@@ -136,26 +137,27 @@ <h3>Prioritization</h3>
 
 <p>It is important to note that these colours do not indicate to what extent a particular feature is broken. They indicate the impact of a broken or missing feature on the content author or end user.</p>
 
-<p>Basic styling is the level that would be generally accepted as sufficient for most Web pages. Advanced level support would include additional features one might expect to include in ebooks or other advanced typographic formats. There may be features of a script or language that are not supported on the Web, but that are not generally regarded as necessary (usually archaic or obscure features). In this case, the feature can be described here, but the status should be marked as OK.</p>
+<p>A cell can be scored as OK if the feature in question is specified in an appropriate specification (including Candidate Recommendations), and is supported by at least two major browser engines. </p>
 
-<p>The decision as to what priority level is assigned to a described gap is down to the experts doing the gap analysis. It may not always be straightforward to decide. If a given section in this document refers to more than one feature that is broken, each with different impacts on Web users, the priority for the section should be the lowest denominator.</p>
+<p>Advanced level support includes features that one might expect to include in ebooks or other advanced typographic formats. If a feature of a script or language is not supported on the Web, but is not generally regarded as necessary (usually archaic or obscure features), even if the feature is described here, the status may be marked as OK. The decision as to what priority level is assigned to a described gap is down to the experts doing the gap analysis. It may not always be straightforward to decide.</p>
 
-<p>A cell can be scored as OK if the feature in question is specified in an appropriate specification, and is supported by user agents. A specification that is in CR or later and has two implementations in 'major' browsers will count. This means that the feature may not be supported in all browsers yet. (At some point in the future we may try to distinguish, visually, whether support is available in a specification but still pending in major browsers or applications.) </p>
+<p>If a given section in this document refers to more than one feature that is broken, each with different impacts on Web users, the priority for the section will be the lowest denominator.</p>
 </section>
 
 
 
 
 
 
+
 <section id="related">
-<h2>Related information</h2>
+<h3>Related documents</h3>
 
-<p>A summary of this report and others can be found as part of the <a href="https://www.w3.org/International/typography/gap-analysis/language-matrix.html" target="_blank">Language Matrix</a>.</p>
+<p>A summary of this report and others can be found as part of the <a href="https://www.w3.org/International/typography/gap-analysis/language-matrix.html" target="_blank" style="font-size: 120%;">Language Matrix</a>.</p>
 
-<p>Gap reports are brought to the attention of spec and browser implementers, and are tracked via the <a href="https://github.com/orgs/w3c/projects/95" target="_blank">Gap Analysis Pipeline</a>. (<a href="https://github.com/orgs/w3c/projects/95/views/1?filterQuery=label%3A%22s%3Akhmr%22" target="_blank">Filter for Khmer script items</a>)</p>
+<p>Gap reports are brought to the attention of spec and browser implementers, and are tracked via the <a href="https://github.com/orgs/w3c/projects/95" style="font-size: 120%;" target="_blank">Gap Analysis Pipeline</a>. Find the <a href="https://github.com/orgs/w3c/projects/95/views/1?filterQuery=label%3A%22s%3Akhmr%22" target="_blank">Khmer items</a>.</p>
 
-<p>See also <a href="https://www.w3.org/TR/khmr-lreq/" target="_blank">Khmer Script Resources</a> for information about the Khmer script.</p>
+<p>For more information about the Khmer script, including requirements, tests, GitHub discussions, type samples, and more, see <a  style="font-size: 120%;" href="https://www.w3.org/TR/khmr-lreq/" target="_blank">Khmer Script Resources</a>.</p>
 </section>
 </section>
 

gap-analysis/laoo-gap.html

@@ -86,34 +86,34 @@
 
 
 
-<section id="h_introduction">
-<h2>Introduction</h2>
-
-
 <section id="contributors">
 <h2>Contributors</h2>
 
-<p>This document was created by Richard Ishida.</p>
+<p>The framework of this document was created by Richard Ishida. The text for most gap descriptions is automatically pulled from GitHub issues, and that text may have been written or contributed to by others.</p>
+
 <!--
-<p>The following people contributed information to the gap reports in this document (in alphabetic order): This Person, That Person, etc</p>
+<p>Special thanks to the following people who contributed to this document (contributors' names listed in in alphabetic order).</p>
+
+<p class="acknowledgement">This Person, That Person, etc</p>
 -->
-<p data-lang="en">See also the <a href="https://github.com/w3c/sealreq/graphs/contributors">GitHub contributors list</a> for the Southeast Asian Language Enablement project, and the <a href="https://github.com/w3c/sealreq/issues?q=is%3Aissue+label%3As%3Alaoo">discussions related to the Lao script</a>.</p>
+
+<p data-lang="en">See also the <a href="https://github.com/w3c/sealreq/graphs/contributors" target="_blank">GitHub contributors list</a> for the Southeast Asian Language Enablement project, and the <a href="https://github.com/w3c/sealreq/issues?q=is%3Aissue+label%3As%3Alaoo" target="_blank">discussions related to the Lao script</a>.</p>
 </section>
 
 
 
 
 
 
-<section id="about">
+<section id="h_introduction">
 <h2>About this document</h2>
 
+
 <p>The W3C needs to make sure that the  needs of scripts and languages around the world are built in to technologies such as HTML, CSS, SVG, etc. so that Web pages and eBooks can look and behave as people expect around the world.</p>
 
 <p>This page documents difficulties that people encounter when trying to use languages written in the Lao script on the Web.</p>
 
 <p>Having identified an issue, it investigates the current status with regards to web specifications and implementations by user agents (browsers, e-readers, etc.), and attempts to prioritise the severity of the issue for web users.</p>
-</section>
 
 
 
@@ -138,26 +138,27 @@ <h3>Prioritization</h3>
 
 <p>It is important to note that these colours do not indicate to what extent a particular feature is broken. They indicate the impact of a broken or missing feature on the content author or end user.</p>
 
-<p>Basic styling is the level that would be generally accepted as sufficient for most Web pages. Advanced level support would include additional features one might expect to include in ebooks or other advanced typographic formats. There may be features of a script or language that are not supported on the Web, but that are not generally regarded as necessary (usually archaic or obscure features). In this case, the feature can be described here, but the status should be marked as OK.</p>
+<p>A cell can be scored as OK if the feature in question is specified in an appropriate specification (including Candidate Recommendations), and is supported by at least two major browser engines. </p>
 
-<p>The decision as to what priority level is assigned to a described gap is down to the experts doing the gap analysis. It may not always be straightforward to decide. If a given section in this document refers to more than one feature that is broken, each with different impacts on Web users, the priority for the section should be the lowest denominator.</p>
+<p>Advanced level support includes features that one might expect to include in ebooks or other advanced typographic formats. If a feature of a script or language is not supported on the Web, but is not generally regarded as necessary (usually archaic or obscure features), even if the feature is described here, the status may be marked as OK. The decision as to what priority level is assigned to a described gap is down to the experts doing the gap analysis. It may not always be straightforward to decide.</p>
 
-<p>A cell can be scored as OK if the feature in question is specified in an appropriate specification, and is supported by user agents. A specification that is in CR or later and has two implementations in 'major' browsers will count. This means that the feature may not be supported in all browsers yet. (At some point in the future we may try to distinguish, visually, whether support is available in a specification but still pending in major browsers or applications.) </p>
+<p>If a given section in this document refers to more than one feature that is broken, each with different impacts on Web users, the priority for the section will be the lowest denominator.</p>
 </section>
 
 
 
 
 
 
+
 <section id="related">
-<h2>Related information</h2>
+<h3>Related documents</h3>
 
-<p>A summary of this report and others can be found as part of the <a href="https://www.w3.org/International/typography/gap-analysis/language-matrix.html" target="_blank">Language Matrix</a>.</p>
+<p>A summary of this report and others can be found as part of the <a href="https://www.w3.org/International/typography/gap-analysis/language-matrix.html" target="_blank" style="font-size: 120%;">Language Matrix</a>.</p>
 
-<p>Gap reports are brought to the attention of spec and browser implementers, and are tracked via the <a href="https://github.com/orgs/w3c/projects/95" target="_blank">Gap Analysis Pipeline</a>. (<a href="https://github.com/orgs/w3c/projects/95/views/1?filterQuery=label%3A%22s%3Alaoo%22" target="_blank">Filter for Lao script items</a>)</p>
+<p>Gap reports are brought to the attention of spec and browser implementers, and are tracked via the <a href="https://github.com/orgs/w3c/projects/95" style="font-size: 120%;" target="_blank">Gap Analysis Pipeline</a>. Find the <a href="https://github.com/orgs/w3c/projects/95/views/1?filterQuery=label%3A%22s%3Alaoo%22" target="_blank">Lao items</a>.</p>
 
-<p>See also <a href="https://www.w3.org/TR/laoo-lreq/" target="_blank">Lao Script Resources</a> for information about the Lao script.</p>
+<p>For more information about the Lao script, including requirements, tests, GitHub discussions, type samples, and more, see <a  style="font-size: 120%;" href="https://www.w3.org/TR/laoo-lreq/" target="_blank">Lao Script Resources</a>.</p>
 </section>
 </section>