- From: Mark Foltz via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Nov 2015 17:00:09 +0000
- To: public-secondscreen@w3.org
Thank you for the example. It is clear that simply preserving the Unicode data isn't sufficient, as locale and font selection can also change the meaning of the content. It would be helpful for @r12a or the followup to http://www.w3.org/International/track/issues/506 point to any normative references to how locales should handled by user agents, so we can refer to them in the spec. There is some discussion about the lang= attribute in HTML5 [1], but I feel that this is better handled at the HTTP level, e.g. by setting `Accept-Language` [2] - after all, the server may provide different content depending on the requested locale. [1] http://www.w3.org/TR/html5/dom.html#the-lang-and-xml:lang-attributes [2] http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.4 -- GitHub Notif of comment by mfoltzgoogle See https://github.com/w3c/presentation-api/issues/218#issuecomment-155486509
Received on Tuesday, 10 November 2015 17:00:12 UTC