W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2011

[Bug 10152] [polyglot] i18n comment 5 : Mention lang and xml:lang

From: <bugzilla@jessica.w3.org>
Date: Sat, 19 Mar 2011 04:52:50 +0000
To: public-i18n-core@w3.org
Message-Id: <E1Q0o9i-0002NU-2o@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10152

--- Comment #21 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-03-19 04:52:48 UTC ---
(In reply to comment #20)
Issues:
* Sentence 2 = incorrect: doesn't list HTTP Content-Language
* The HTML5 Reference should be the language determination rules
   http://www.w3.org/TR/html5/elements#language 
   and not the Content Languag state:
  
http://dev.w3.org/html5/spec/semantics.html#attr-meta-http-equiv-content-language
* Second last sentence is incorrect: doesn't mention the crucial 
   condition that the language attributes of the root element are
   lacking ...
* A problem in the paragraph (the 'pretext') *preceding* the NOTE:
   # 'default' is synonymous with 'fallback'. 'fallback/default' is not the
correct word when the language value stems from the language attributes. Only
when it stems from HTML5's fallback mechanism, should we use default/fallback.



        New text, for the 'pretext' paragraph and for the NOTE:


]]
    Polyglot markup avoids that the language of the root element is set by
HTML5's fallback language mechanism as this mechanism is not required to work
in XML.

    [NOTE:] HTML5's fallback language mechanism activates whenever the root
element is lacking language attributes. But for the mechanism to actually set a
fallback language, it has to locate a http-equiv="Content-Language" meta
element or a HTTP Content-Language: header (anyone of them, but meta element is
considered first) whose content value is no more and no less than exactly a one
language tag, see the <a href="http://www.w3.org/TR/html5/elements#language"
>language determination rules</a> of [HTML5].
[[



PS: I said "not required to work in XML", because when I read the language
determination rules of HTML5, then it *does* seem to work in "normal" XHTML
browsers.
PPS: It is fully legal to uppercase the content value of @http-equiv. Hence I
wrote http-equiv="Content-Language", to get it symmetrical with the typical way
to type the HTTP header syntax.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Saturday, 19 March 2011 04:52:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 19 March 2011 04:52:54 GMT