- From: Albert Lunde <atlunde@panix.com>
- Date: Wed, 04 Jul 2012 12:31:37 -0500
- CC: www-international@w3.org, public-web-notification@w3.org
On 7/4/2012 11:03 AM, Anne van Kesteren wrote: > On Thu, Jun 28, 2012 at 6:17 PM, Norbert Lindenberg > <w3@norbertlindenberg.com> wrote: >> OK - the spec doesn't actually say that senders must be web applications, >> but you get to pick the target you're designing for. > > Senders? This is just something you invoke from script in a web page, > so naturally it's limited to web pages that execute script. > > >> It is not normal yet for applications to properly identify the language of the >> text they handle, but there's a clear need for it. Just imagine a screen reader >> trying to read that French email to you pronouncing it as if all words were Dutch. >> http://www.w3.org/International/questions/qa-lang-why > > Well yes, if the language is known. That does not seem like the common > case though. E.g. I often switch languages while chatting and I'm not > telling my chat client when I do so. One of the arguments for identifying language for Unicode text that came up in the context of HTML is that the way CJK character unification was done in Unicode it's not possible to display all characters correctly without knowing the language. (As was noted in some comments.) It seems like putting a slot into the API for language now, may save trouble later.
Received on Wednesday, 4 July 2012 17:32:07 UTC