- From: <bugzilla@jessica.w3.org>
- Date: Thu, 01 Mar 2012 23:02:56 +0000
- To: public-i18n-core@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16166 Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xn--mlform-iua@xn--mlform-i | |ua.no --- Comment #2 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2012-03-01 23:02:54 UTC --- (In reply to comment #0) > It's a pain in the neck to have to write both lang and > xml:lang attributes on an element in a polyglot document, Per HTML5: "The lang attribute in no namespace may be used on any HTML element." THUS: @lang takes effect even "XHTML5". And XML-supporting Web browsers already implement it. Therefore, the authoring pain related to "have to write both lang and xml:lang", could be solved by updating the Polyglot Markup spec to explicityly say that xml:lang is *optional*. In fact, per HTML5, it is. With regard to polyglot markup, then: 1) Polyglot documents get more polyglot (the XML and HTML DOM becomes more similar) if one simply omits the xml:lang="" and instead only uses @lang. 2) Polyglot documents also become simpler to author, if they only require @lang. 3) XHTML 1.0 does not require xml:lang. XHTML 1.1 was updated 2010 to the effect that @lang was integrated without any requiremtn to simultaneously use xml:lang, see http://www.w3.org/TR/xhtml11/#status You may also check the validator: http://tinyurl.com/6wal8j2 Comments? -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You reported the bug.
Received on Thursday, 1 March 2012 23:02:59 UTC