RE: Client side JavaScript i18n API

Our (I18N activity) experience seems to suggest that a dedicated list is more useful when a project is active. The key thing is to engage in coordination between groups at appropriate times (there exist various means of doing that). 

Addison

Addison Phillips
Globalization Architect (Lab126)
Chair (W3C I18N, IETF IRI WGs)

Internationalization is not a feature.
It is an architecture.

> -----Original Message-----
> From: cira@google.com [mailto:cira@google.com] On Behalf Of Nebojša
> Ciric
> Sent: Thursday, May 13, 2010 5:35 PM
> To: Doug Schepers
> Cc: Robin Berjon; Phillips, Addison; public-webapps WG; public-
> i18n-core@w3.org
> Subject: Re: Client side JavaScript i18n API
> 
> Doug,
>  do you think we should create a new list and move this discussion
> there? Or should we use one of the existing i18n lists?
>  If we do move this discussion off the webapps list, we may lose
> some
> audience/expertise...
> 
>  If nobody objects, we (Google) would like to take this discussion
> to
> webkit-dev list too, and maybe start prototyping the Locale API in
> next couple of weeks (both for JSC and V8).
> 
> Regards,
>  Nebojsa Ciric
> 
> On Tue, May 4, 2010 at 8:46 AM, Doug Schepers <schepers@w3.org>
> wrote:
> > 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
> >
> >
> 
> --
> Nebojša Ćirić

Received on Friday, 14 May 2010 01:03:06 UTC