Skip to content

Commit

Permalink
Issue #61: adjusted references to Unicode to make them future-proof. …
Browse files Browse the repository at this point in the history
…Pointed to correct section 2.11 instead of 2.10.
  • Loading branch information
aphillips committed Feb 5, 2016
1 parent 428f196 commit 7c32697
Showing 1 changed file with 7 additions and 4 deletions.
11 changes: 7 additions & 4 deletions index.html
Expand Up @@ -328,8 +328,10 @@ <h3>Terminology and Notation</h3>
this approximation a <dfn>grapheme cluster</dfn>. There are two types
of default grapheme cluster defined. Unless otherwise noted, grapheme
cluster in this document refers to an extended default grapheme
cluster. (A discussion of grapheme clusters is also given at the end
of Section 2.10 of the <cite>Unicode Standard</cite>, [[!Unicode]].)</p>
cluster. (A discussion of grapheme clusters is also given in Section 2
of the <cite>Unicode Standard</cite>, [[!Unicode]]. Cf. near the end of
<a href="http://www.unicode.org/versions/Unicode8.0.0/ch02.pdf">Section 2.11</a>
in version 8.0 of The Unicode Standard)</p>
<p>Because different natural languages have different needs, grapheme clusters
can also sometimes require tailoring. For example, a Slovak user might
wish to treat the default pair of grapheme clusters "ch" as a single
Expand Down Expand Up @@ -485,7 +487,8 @@ <h3>Case Folding</h3>
<p>Case folding might, at first, appear simple. However there are
variations that need to be considered when treating the full range of
Unicode in diverse languages. For more information,
<cite>[[!Unicode]]</cite> Section 5.18 discusses case folding in detail.</p>
<cite>[[!Unicode]]</cite> Chapter 5 (in v8.0, <a href="">Section 5.18</a>)
discusses case mappings in detail.</p>

<p>Unicode defines the default case fold mapping for each Unicode code point.
Since most scripts do not provide a case distinction, most Unicode code
Expand Down Expand Up @@ -1811,7 +1814,7 @@ <h2 id="Acknowledgements" class="informative">Acknowledgements</h2>
<p>The W3C Internationalization Working Group and Interest Group, as well
as others, provided many comments and suggestions. The Working Group
would like to thank: Mati Allouche, Ebrahim Byagowi, John Cowan, Martin Dürst, Behdad Esfahbod, John Klensin,
Amir Sarabadani, and all of the CharMod
Amir Sarabadani, and all of the CharMod
contributors over the many years of this document's development. </p>
<p>The previous version of this document was edited by:</p>
<ul>
Expand Down

0 comments on commit 7c32697

Please sign in to comment.