- From: <bugzilla@jessica.w3.org>
- Date: Mon, 15 Aug 2011 12:37:09 +0000
- To: public-i18n-core@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12417 --- Comment #47 from Arle Lommel <fenevad@gmail.com> 2011-08-15 12:37:08 UTC --- (In reply to comment #46) > HTML serialization of HTML5 doesn't support namespaces hence you can't use > its:translate. Need for translatability is enough widespread to justify having > "native" attribute. Just seconding what Jirka has to say. ITS is intended for XML documents, but HTML5 (with the exception of polyglot markup) is not XML and so cannot use ITS. Even polyglot markup runs into trouble when using external namespaces since the resulting document would then be using XML features not required to be supported in HTML5. So while using ITS appears like a good idea at first, it won't work for HTML5. But Jirka's second point—“Need for translatability is enough widespread…”—is also crucial. If translation of web content is enough of a core function on the web (and I would argue that it is), then core web technologies ought to support it. I would agree with Jirka’s assessment of the importance of this feature, but that is ultimately the question to be determined: is translatability important enough to be defined as a native attribute? -- 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 Monday, 15 August 2011 12:37:15 UTC