[prev in list] [next in list] [prev in thread] [next in thread]
List: html5-commit-watchers
Subject: [html5] r7607 - [e] (0) Clarify how language codes are passed on to other tools. Fixing https:// [..
From: whatwg () whatwg ! org
Date: 2012-12-30 0:40:09
Message-ID: 20121230004009.802C4805C10B () ps20323 ! dreamhostps ! com
[Download RAW message or body]
Author: ianh
Date: 2012-12-29 16:40:08 -0800 (Sat, 29 Dec 2012)
New Revision: 7607
Modified:
complete.html
index
source
Log:
[e] (0) Clarify how language codes are passed on to other tools.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=17977
Affected topics: HTML
Modified: complete.html
===================================================================
--- complete.html 2012-12-30 00:04:21 UTC (rev 7606)
+++ complete.html 2012-12-30 00:40:08 UTC (rev 7607)
@@ -248,7 +248,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img \
alt=WHATWG height=101 src=/images/logo width=101></a></p> <hgroup><h1 \
class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 29 December \
2012</h2> + <h2 class="no-num no-toc">Living Standard — Last Updated 30 \
December 2012</h2> </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -11055,20 +11055,23 @@
languages, the language of the node is unknown, and the
corresponding language tag is the empty string.</p>
- <p>If the resulting value is not a recognized language tag, then it
- must be treated as an unknown language having the given language
- tag, distinct from all other languages. For the purposes of
- round-tripping or communicating with other services that expect
- language tags, user agents should pass unknown language tags
- through unmodified.</p>
+ <p>If the resulting value is not a recognized language tag, then it must be \
treated as an unknown + language having the given language tag, distinct from all \
other languages. For the purposes of + round-tripping or communicating with other \
services that expect language tags, user agents should + pass unknown language tags \
through unmodified, and tagged as being BCP 47 language tags, so that + subsequent \
services do not interpret the data as another type of language description. <a \
href=#refsBCP47>[BCP47]</a></p>
- <p class=example>Thus, for instance, an element with <code \
title="">lang="xyzzy"</code> would be matched by the selector <code \
title="">:lang(xyzzy)</code> (e.g. in CSS), but it would not be
- matched by <code title="">:lang(abcde)</code>, even though both are
- equally invalid. Similarly, if a Web browser and screen reader
- working in unison communicated about the language of the element,
- the browser would tell the screen reader that the language was
- "xyzzy", even if it knew it was invalid, just in case the screen
- reader actually supported a language with that tag after all.</p>
+ <p class=example>Thus, for instance, an element with <code \
title="">lang="xyzzy"</code> would be + matched by the selector <code \
title="">:lang(xyzzy)</code> (e.g. in CSS), but it would not be + matched by <code \
title="">:lang(abcde)</code>, even though both are equally invalid. Similarly, if + \
a Web browser and screen reader working in unison communicated about the language of \
the element, + the browser would tell the screen reader that the language was \
"xyzzy", even if it knew it was + invalid, just in case the screen reader actually \
supported a language with that tag after all. + Even if the screen reader supported \
both BCP 47 and another syntax for encoding language names, + and in that other \
syntax the string "xyzzy" was a way to denote the Belarusian language, it would + be \
<em>incorrect</em> for the screen reader to then start treating text as Belarusian, \
because + "xyzzy" is not how Belarusian is described in BCP 47 codes (BCP 47 uses \
the code "be" for + Belarusian).</p>
<p>If the resulting value is the empty string, then it must be
interpreted as meaning that the language of the node is explicitly
Modified: index
===================================================================
--- index 2012-12-30 00:04:21 UTC (rev 7606)
+++ index 2012-12-30 00:40:08 UTC (rev 7607)
@@ -248,7 +248,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img \
alt=WHATWG height=101 src=/images/logo width=101></a></p> <hgroup><h1 \
class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 29 December \
2012</h2> + <h2 class="no-num no-toc">Living Standard — Last Updated 30 \
December 2012</h2> </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -11055,20 +11055,23 @@
languages, the language of the node is unknown, and the
corresponding language tag is the empty string.</p>
- <p>If the resulting value is not a recognized language tag, then it
- must be treated as an unknown language having the given language
- tag, distinct from all other languages. For the purposes of
- round-tripping or communicating with other services that expect
- language tags, user agents should pass unknown language tags
- through unmodified.</p>
+ <p>If the resulting value is not a recognized language tag, then it must be \
treated as an unknown + language having the given language tag, distinct from all \
other languages. For the purposes of + round-tripping or communicating with other \
services that expect language tags, user agents should + pass unknown language tags \
through unmodified, and tagged as being BCP 47 language tags, so that + subsequent \
services do not interpret the data as another type of language description. <a \
href=#refsBCP47>[BCP47]</a></p>
- <p class=example>Thus, for instance, an element with <code \
title="">lang="xyzzy"</code> would be matched by the selector <code \
title="">:lang(xyzzy)</code> (e.g. in CSS), but it would not be
- matched by <code title="">:lang(abcde)</code>, even though both are
- equally invalid. Similarly, if a Web browser and screen reader
- working in unison communicated about the language of the element,
- the browser would tell the screen reader that the language was
- "xyzzy", even if it knew it was invalid, just in case the screen
- reader actually supported a language with that tag after all.</p>
+ <p class=example>Thus, for instance, an element with <code \
title="">lang="xyzzy"</code> would be + matched by the selector <code \
title="">:lang(xyzzy)</code> (e.g. in CSS), but it would not be + matched by <code \
title="">:lang(abcde)</code>, even though both are equally invalid. Similarly, if + \
a Web browser and screen reader working in unison communicated about the language of \
the element, + the browser would tell the screen reader that the language was \
"xyzzy", even if it knew it was + invalid, just in case the screen reader actually \
supported a language with that tag after all. + Even if the screen reader supported \
both BCP 47 and another syntax for encoding language names, + and in that other \
syntax the string "xyzzy" was a way to denote the Belarusian language, it would + be \
<em>incorrect</em> for the screen reader to then start treating text as Belarusian, \
because + "xyzzy" is not how Belarusian is described in BCP 47 codes (BCP 47 uses \
the code "be" for + Belarusian).</p>
<p>If the resulting value is the empty string, then it must be
interpreted as meaning that the language of the node is explicitly
Modified: source
===================================================================
--- source 2012-12-30 00:04:21 UTC (rev 7606)
+++ source 2012-12-30 00:40:08 UTC (rev 7607)
@@ -11203,22 +11203,24 @@
languages, the language of the node is unknown, and the
corresponding language tag is the empty string.</p>
- <p>If the resulting value is not a recognized language tag, then it
- must be treated as an unknown language having the given language
- tag, distinct from all other languages. For the purposes of
- round-tripping or communicating with other services that expect
- language tags, user agents should pass unknown language tags
- through unmodified.</p>
+ <p>If the resulting value is not a recognized language tag, then it must be \
treated as an unknown + language having the given language tag, distinct from all \
other languages. For the purposes of + round-tripping or communicating with other \
services that expect language tags, user agents should + pass unknown language tags \
through unmodified, and tagged as being BCP 47 language tags, so that + subsequent \
services do not interpret the data as another type of language description. <a + \
href="#refsBCP47">[BCP47]</a></p>
- <p class="example">Thus, for instance, an element with <code
- title="">lang="xyzzy"</code> would be matched by the selector <code
- title="">:lang(xyzzy)</code> (e.g. in CSS), but it would not be
- matched by <code title="">:lang(abcde)</code>, even though both are
- equally invalid. Similarly, if a Web browser and screen reader
- working in unison communicated about the language of the element,
- the browser would tell the screen reader that the language was
- "xyzzy", even if it knew it was invalid, just in case the screen
- reader actually supported a language with that tag after all.</p>
+ <p class="example">Thus, for instance, an element with <code \
title="">lang="xyzzy"</code> would be + matched by the selector <code \
title="">:lang(xyzzy)</code> (e.g. in CSS), but it would not be + matched by <code \
title="">:lang(abcde)</code>, even though both are equally invalid. Similarly, if + \
a Web browser and screen reader working in unison communicated about the language of \
the element, + the browser would tell the screen reader that the language was \
"xyzzy", even if it knew it was + invalid, just in case the screen reader actually \
supported a language with that tag after all. + Even if the screen reader supported \
both BCP 47 and another syntax for encoding language names, + and in that other \
syntax the string "xyzzy" was a way to denote the Belarusian language, it would + be \
<em>incorrect</em> for the screen reader to then start treating text as Belarusian, \
because + "xyzzy" is not how Belarusian is described in BCP 47 codes (BCP 47 uses \
the code "be" for + Belarusian).</p>
<p>If the resulting value is the empty string, then it must be
interpreted as meaning that the language of the node is explicitly
_______________________________________________
Commit-Watchers mailing list
Commit-Watchers@lists.whatwg.org
http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic