W3C home > Mailing lists > Public > www-international@w3.org > July to September 2012

Re: Web Notifications I18N Review: [I18N-ISSUE-161, I18N-ISSUE-162]

From: Anne van Kesteren <annevk@annevk.nl>
Date: Wed, 4 Jul 2012 18:03:34 +0200
Message-ID: <CADnb78iY3w9+=_M7w1uoqAqxQaqNNEcmmZYoNNb7o0Jgj5JQMQ@mail.gmail.com>
To: Norbert Lindenberg <w3@norbertlindenberg.com>
Cc: Doug Turner <dougt@mozilla.com>, Addison Phillips <addison@lab126.com>, www-international@w3.org, public-web-notification@w3.org, "Olli.Pettay" <opettay@mozilla.com>
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.

I think we should wait with language tagging until the case more
clearly has been made. It's no problem to add it in the future. At
this point in time the native notification platforms do not have even
all support text direction, let alone language. And this is something
we can easily add later through titleLang and bodyLang dictionary

Received on Wednesday, 4 July 2012 16:04:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:00 UTC