Skip to content
Permalink
Browse files

[] (0) Remove reliance on UTS22, which is apparently too loose. This …

…will be addressed by registering aliases instead. Anne's apparently leading that effort.

git-svn-id: http://svn.whatwg.org/webapps@3679 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
Hixie committed Aug 26, 2009
1 parent eb95f79 commit 1aa47516637cf64534ddb6cdffffdab6a4948658
Showing with 7 additions and 25 deletions.
  1. +3 −11 index
  2. +4 −14 source
14 index
@@ -5075,11 +5075,9 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

<p>When comparing a string specifying a character encoding with the
name or alias of a character encoding to determine if they are
equal, user agents must use the Charset Alias Matching rules defined
in Unicode Technical Standard #22. <a href=#refsUTS22>[UTS22]</a></p>

<p class=example>For instance, "GB_2312-80" and "g.b.2312(80)" are
considered equivalent names.</p>
equal, user agents must remove any leading or trailing <a href=#space-character title="space character">space characters</a> in both names, and
then perform the comparison in an <a href=#ascii-case-insensitive>ASCII
case-insensitive</a> manner.</p>

<!-- this bit will be replaced by actual alias registrations in due course -->

Mail-Safe Transformation Format of Unicode</a></cite>,
D. Goldsmith, M. Davis. IETF, May 1997.</dd>

<dt id=refsUTS22>[UTS22]</dt>
<dd><cite><a href=http://www.unicode.org/reports/tr22/#Charset_Alias_Matching>Charset
Alias Matching</a></cite>. In <cite><a href=http://www.unicode.org/reports/tr22/>UTS #22: Character
Mapping Markup Language (CharMapML)</a></cite>, M. Davis,
M. Scherer. Unicode Consortium, June 2006.</dd>

<dt id=refsWEBADDRESSES>[WEBADDRESSES]</dt>
<dd><cite><a href=http://www.w3.org/html/wg/href/draft>Web
addresses in HTML 5</a></cite>, D. Connolly,
18 source
@@ -4776,12 +4776,10 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

<p>When comparing a string specifying a character encoding with the
name or alias of a character encoding to determine if they are
equal, user agents must use the Charset Alias Matching rules defined
in Unicode Technical Standard #22. <a
href="#refsUTS22">[UTS22]</a></p>

<p class="example">For instance, "GB_2312-80" and "g.b.2312(80)" are
considered equivalent names.</p>
equal, user agents must remove any leading or trailing <span
title="space character">space characters</span> in both names, and
then perform the comparison in an <span>ASCII
case-insensitive</span> manner.</p>

<!-- this bit will be replaced by actual alias registrations in due course -->

Mail-Safe Transformation Format of Unicode</a></cite>,
D. Goldsmith, M. Davis. IETF, May 1997.</dd>

<dt id="refsUTS22">[UTS22]</dt>
<dd><cite><a
href="http://www.unicode.org/reports/tr22/#Charset_Alias_Matching">Charset
Alias Matching</a></cite>. In <cite><a
href="http://www.unicode.org/reports/tr22/">UTS #22: Character
Mapping Markup Language (CharMapML)</a></cite>, M. Davis,
M. Scherer. Unicode Consortium, June 2006.</dd>

<dt id="refsWEBADDRESSES">[WEBADDRESSES]</dt>
<dd><cite><a href="http://www.w3.org/html/wg/href/draft">Web
addresses in HTML 5</a></cite>, D. Connolly,

0 comments on commit 1aa4751

Please sign in to comment.
You can’t perform that action at this time.