W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2008

RE: [widgets] i18n

From: Phillips, Addison <addison@amazon.com>
Date: Mon, 19 May 2008 07:45:14 -0700
To: Marcos Caceres <marcosscaceres@gmail.com>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>, "WAF WG (public)" <public-appformats@w3.org>
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA013A218E4C@EX-SEA5-D.ant.amazon.com>
Hi Marcos,

Thanks for the note. Thanks for making the changes. We'll be glad to take a look and get back to you as soon as possible.

Best Regards,


Addison Phillips
Globalization Architect -- Lab126

Internationalization is not a feature.
It is an architecture.

> -----Original Message-----
> From: Marcos Caceres [mailto:marcosscaceres@gmail.com]
> Sent: Monday, May 19, 2008 12:10 AM
> To: Phillips, Addison; public-i18n-core@w3.org; WAF WG (public)
> Subject: Re: [widgets] i18n
> Hi Addison, All,
> I've attempted to make the widget spec conformant with BCP437. In
> particular, I've deferred searching for localized folders to RFC4647
> using "lookup" against a language priority list composed of a basic
> language range. WAF would be grateful if (i18n) people could take a
> look at the current draft in the spec and make sure that it is ok (so
> we can close issue 23 [1]). The i18n text is fairly short (only about
> 1 page), so it should not take much time to read, and, hopefully,
> respond to.
> In the widget spec, the localization definitions and author
> requirements are described in section:
> http://dev.w3.org/2006/waf/widgets/#localization

> The i18n processing model (which makes use of RFC4647) is described in
> section:
> http://dev.w3.org/2006/waf/widgets/#step-6

> Hope it all makes sense.
> Looking forward to hearing your feedback,
> Marcos
> [1] http://www.w3.org/2005/06/tracker/waf/issues/23

> --
> Marcos Caceres
> http://datadriven.com.au

Received on Monday, 19 May 2008 14:46:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:23:03 UTC