gap-analysis/index, ids corrected

gap-analysis/index.html

@@ -167,7 +167,7 @@ <h3><a href="#cursive">Cursive text</a></h3>
 
 <section class="topic" id="transforms">
 <section class="flexContainer">
-<h3><a href="#transforming_characters">Transforming characters</a></h3>
+<h3><a href="#transforms">Transforming characters</a></h3>
 <p class="prompt">Does your script need special text transforms that are not supported? Does your script convert letters to uppercase, capitalised and lowercase alternatives according to your typographic needs? Do you need to to convert between half-width and full-width presentation forms?
 <a href="../index#transforming_characters">See available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Atext-transform%20label%3Atype-info-request">check for currently needed data</a>.</p>
 </section>
@@ -177,7 +177,7 @@ <h3><a href="#transforming_characters">Transforming characters</a></h3>
 
 <section class="topic" id="numbers">
 <section class="flexContainer">
-  <h3><a href="#overview_numbers">Numbers and digits</a></h3>
+  <h3><a href="#numbers">Numbers and digits</a></h3>
 <p class="prompt">If  the script has its own set of number digits, are there any issues in how they are used? Does the script or language use special format patterns that are problematic?
   <a href="../index#numbers">See available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Anumbers%20label%3Atype-info-request">check for currently needed data</a>.</p>
 </section>
@@ -188,7 +188,7 @@ <h3><a href="#overview_numbers">Numbers and digits</a></h3>
 
 <section class="topic" id="boundaries">
 <section class="flexContainer">
-<h3><a href="#graphemes">Text boundaries and selection</a></h3>
+<h3><a href="#boundaries">Text boundaries and selection</a></h3>
 <p class="prompt">When you double- or triple-click on the text, is the expected range of characters highlighted? When you move through the text with the cursor, or backspace, etc. do you see the expected behaviour? Are there issues when applying punctuation than could be fixed by the application?
 <a href="../index#graphemes">See available information</a>  or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Aboundaries%20label%3Atype-info-request">check for currently needed data</a>.</p>
 </section>
@@ -208,7 +208,7 @@ <h3><a href="#quotations">Quotations</a></h3>
 
 <section class="topic" id="spacing">
 <section class="flexContainer">
-<h3><a href="#letter_spacing">Inter-character spacing</a></h3>
+<h3><a href="#spacing">Inter-character spacing</a></h3>
 <p class="prompt">Many scripts create emphasis or other effects by spacing out the letters or syllables in a word. We know there are questions here about how this should work in Indic and SE Asian scripts, and in Arabic-based scripts.  Are there requirements for other scripts that we should add? (For justification related spacing, see below.) See 
 <a href="../index#letter_spacing">available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Ainline-spacing%20label%3Atype-info-request">check for currently needed data</a>.</p>
 </section>
@@ -219,7 +219,7 @@ <h3><a href="#letter_spacing">Inter-character spacing</a></h3>
 
 <section class="topic" id="ruby">
 <section class="flexContainer">
-<h3><a href="#ruby_annotation">Ruby annotation</a></h3>
+<h3><a href="#ruby">Ruby annotation</a></h3>
 <p class="prompt">The ruby spec currently specifies an initial subset of requirements for fine-tuning the typography of phonetic and semantic annotations of East Asian text, including furigana, pinyin and zhuyin fuhao systems.  Is is adequate for what it sets out to do?  What other controls will be needed in the future?
 <a href="../index#ruby_annotation">See available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Aruby%20label%3Atype-info-request">check for currently needed data</a>.</p>
 </section>
@@ -229,7 +229,7 @@ <h3><a href="#ruby_annotation">Ruby annotation</a></h3>
 
 <section class="topic" id="textdecoration">
 <section class="flexContainer">
-<h3><a href="#text_decoration">Text decoration</a></h3>
+<h3><a href="#textdecoration">Text decoration</a></h3>
 <div>
 <p class="prompt">Some aspects related to the drawing of lines alongside or through text involve local typographic considerations. Do underlines need to be broken in special ways for this script? Do you need support for additional line shapes or widths? Does the distance or position of the lines relative to the text need to vary in ways that are not achievable? Are lines correctly drawn relative to vertical text?
 <a href="../index#text_decoration">See available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Atext-decoration%20label%3Atype-info-request">check for currently needed data</a>.</p>
@@ -276,7 +276,7 @@ <h2 id="lines_paragraphs"><a href="#lines_paragraphs">Lines &amp; paragraphs</a>
 
 <section class="topic" id="linebreak">
 <section class="flexContainer">
-<h3><a href="#line_breaking">Line breaking</a></h3>
+<h3><a href="#linebreak">Line breaking</a></h3>
 <div>
 <p class="prompt">Does the browser capture the rules about the way text in your script wraps when it hits the end of a line?  What characters should not appear at the end or start of a line, and what should be done to prevent that? Does line-breaking wrap whole 'words' at a time, or characters, or something else (such as syllables in Tibetan)?
 <a href="../index#line_breaking">See available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Aline-break%20label%3Atype-info-request">check for currently needed data</a>.</p>
@@ -323,7 +323,7 @@ <h3><a href="#counters">Counters, lists, etc</a></h3>
 
 <section class="topic" id="initialletter">
   <section class="flexContainer">
-  <h3><a href="#initial_letter">Initial letter styling</a></h3>
+  <h3><a href="#initialletter">Initial letter styling</a></h3>
 <p class="prompt">Does the browser or ereader correctly handle special styling of the initial letter of a line or paragraph, such as for drop caps or similar?
 <a href="../index#initial_letter">See available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Ainitial-letter%20label%3Atype-info-request">check for currently needed data</a>.<br />
 </p>
@@ -333,7 +333,7 @@ <h3><a href="#initial_letter">Initial letter styling</a></h3>
 
 <section class="topic" id="baselines">
 <section class="flexContainer">
-  <h3><a href="#baselines_inline_alignment">Baselines &amp; inline alignment</a></h3>
+  <h3><a href="#baselines">Baselines &amp; inline alignment</a></h3>
 <p class="prompt">Does the browser support  requirements for baseline alignment between mixed scripts and in general?
 <a href="../index#baselines_inline_alignment">See available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Abaselines%20label%3Atype-info-request">check for currently needed data</a>.</p>
 </section>
@@ -344,7 +344,7 @@ <h3><a href="#baselines_inline_alignment">Baselines &amp; inline alignment</a></
 
 <section class="topic" id="whitespace">
 <section class="flexContainer">
-<h3><a href="#white_space_wrapping_in_source_code">White space and wrapping in source code</a></h3>
+<h3><a href="#whitespace">White space and wrapping in source code</a></h3>
 <p class="prompt">Do the rules for transforming white space in the source text for display meet the requirements of your script?  
 This is particularly relevant for Far Eastern and South East Asian scripts, that don't use spaces between words.</p>
 </section>
@@ -355,7 +355,7 @@ <h3><a href="#white_space_wrapping_in_source_code">White space and wrapping in s
 
 <section class="topic" id="otherpara">
 <section class="flexContainer">
-<h3><a href="#other_para_features">Other paragraph features</a></h3>
+<h3><a href="#otherpara">Other paragraph features</a></h3>
 <p class="prompt">In your script, is the first line of text typically indented at the start of a paragraph? Are there other features of paragraph design that are peculiar to your script?
 <a href="../index#other_para_features">See available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Aparagraph-features%20label%3Atype-info-request">check for currently needed data</a>.</p>
 </section>
@@ -370,7 +370,7 @@ <h2 id="layout"><a href="#layout">Layout &amp; pages</a></h2>
 
 <section class="topic" id="bidilayout">
 <section class="flexContainer">
-<h3 id="direction_agnostic"><a href="#direction_agnostic">Bidirectional layout</a></h3>
+<h3><a href="#bidilayout">Bidirectional layout</a></h3>
 <p class="prompt">When content can flow vertically and to the left or right, how do you specify the location of objects, text, etc. relative to the flow? For example, keywords 'left' and 'right' are likely to need to be reversed for pages written in English and page written in Arabic. 
 <a href="../index#direction_agnostic">See available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Abidi%20label%3Atype-info-request">check for currently needed data</a>.</p>
 </section>
@@ -380,7 +380,7 @@ <h3 id="direction_agnostic"><a href="#direction_agnostic">Bidirectional layout</
 
 <section class="topic" id="vertical">
 <section class="flexContainer">
-<h3 id="vertical_text"><a href="#vertical_text">Vertical text</a></h3>
+<h3><a href="#vertical">Vertical text</a></h3>
 <p class="prompt">Are the script requirements for vertically oriented text met?  What about if you mix vertical text with scripts that are normally only horizontal? Do you need a switch to use different characters in vertical vs. horizontal text? Does the browser support short runs of horizontal text in vertical lines (tate-chu-yoko in Japanese) as expected? Is the orientation of characters and the directional ordering of characters supported as needed?
 <a href="../index#vertical_text">See available information</a>.</p>
 </section>
@@ -389,7 +389,7 @@ <h3 id="vertical_text"><a href="#vertical_text">Vertical text</a></h3>
 
 <section class="topic" id="notes">
 <section class="flexContainer">
-  <h3 id="notes_footnotes"><a href="#notes_footnotes">Notes, footnotes, etc</a></h3>
+<h3><a href="#notes">Notes, footnotes, etc</a></h3>
 <p class="prompt">Does your script have special requirements for notes, footnotes, endnotes or other necessary annotations of this kind in the way needed for your culture?
 <a href="../index#notes_footnotes">See available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Anotes-footnotes%20label%3Atype-info-request">check for currently needed data</a>.</p>
 </section>
@@ -399,7 +399,7 @@ <h3 id="notes_footnotes"><a href="#notes_footnotes">Notes, footnotes, etc</a></h
 
 <section class="topic" id="pageheaders">
 <section class="flexContainer">
-<h3 id="page_numbering_running_headers"><a href="#page_numbering_running_headers">Page numbering, running headers, etc</a></h3>
+<h3><a href="#pageheaders">Page numbering, running headers, etc</a></h3>
 <p class="prompt">Are there special conventions for page numbering, or the way that running headers and the like are handled?
 <a href="../index#page_numbering_running_headers">See available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Apage-numbering%20label%3Atype-info-request">check for currently needed data</a>.</p>
 </section>
@@ -409,7 +409,7 @@ <h3 id="page_numbering_running_headers"><a href="#page_numbering_running_headers
 
 <section class="topic" id="morepage">
 <section class="flexContainer">
-<h3 id="more_page_layout_and_pagination"><a href="#more_page_layout_and_pagination">Other page layout and pagination</a> features</h3>
+<h3><a href="#morepage">Other page layout and pagination</a> features</h3>
 <p class="prompt">Some cultures define page areas and page progression direction very differently from those in the West (eg. kihon hanmen in Japanese). Is this an issue for you? Are widows and orphans relevant? In what order do pages progress, RTL or LTR?
 <a href="../index#more_page_layout_and_pagination">See available information</a> or <a href="https://github.com/w3c/i18n-activity/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Apagination%20label%3Atype-info-request">check for currently needed data</a>.</p>
 </section>
@@ -447,7 +447,7 @@ <h3 id="what_else"><a href="#what_else">What else?</a></h3>
   <section>
     <div class="smallprint">
 	<p>If you have comments about this page, send them to ishida@w3.org.</p>
-      <p id="version">Content last changed <span id="version-info"><!-- #BeginDate format:IS1m -->2017-09-22  11:58<!-- #EndDate --></span> GMT</p>
+      <p id="version">Content last changed <span id="version-info"><!-- #BeginDate format:IS1m -->2017-09-29  18:58<!-- #EndDate --></span> GMT</p>
       <p class="copyright"><a rel="Copyright" href="/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2017 <a href="/"><abbr
 						title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup> (<a href="https://www.csail.mit.edu/"><abbr
 						title="Massachusetts Institute of Technology">MIT</abbr></a>, <a href="https://www.ercim.org/"><abbr