W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2010

Re: Client side JavaScript i18n API

From: Doug Schepers <schepers@w3.org>
Date: Tue, 04 May 2010 11:46:55 -0400
Message-ID: <4BE0416F.6090604@w3.org>
To: Robin Berjon <robin@berjon.com>
CC: "Phillips, Addison" <addison@lab126.com>, public-webapps WG <public-webapps@w3.org>, public-i18n-core@w3.org
Hi, Robin-

Robin Berjon wrote (on 4/27/10 12:21 PM):
>
> On Apr 27, 2010, at 18:13 , Phillips, Addison wrote:
>> A project to implement this could go quite fast, I think, but would
>> require agreement by the major browser vendors and a place to do
>> the work. We could do this at W3C, but I think ECMA should be
>> involved from early on.
>
> In general a good place for discussion that involves W3C/TC39
> coordination is public-script-coord@w3.org. It doesn't have an
> attached group and therefore cannot publish specifications, but
> that's a sausage-making detail that can be handled orthogonally (we
> just need to find a WG that can justify having this in its charter).

Actually, public-script-coord is associated with the WebApps WG, and was 
formed to coordinate between TC39 and the WebApps WG, specifically on 
Web IDL issues, but also on other matters of coordination.

If we do decide to bring this i18n work to W3C (which I think would be a 
good idea, though not by necessity in the WebApps WG), we could reuse 
public-script-coord, or we could make a new dedicated list.  I think the 
latter makes more sense, since the i18n folks wouldn't have to drink 
from the public-script-coord hose.

Regards-
-Doug Schepers
W3C Team Contact, SVG and WebApps WGs
Received on Tuesday, 4 May 2010 15:46:59 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:38 GMT