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

RE: Widgets 1.0 Packaging and Configuration: I18N comments...

From: Phillips, Addison <addison@amazon.com>
Date: Fri, 3 Apr 2009 07:38:09 -0700
To: "marcosc@opera.com" <marcosc@opera.com>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
CC: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA019F18C20C@EX-SEA5-D.ant.amazon.com>
Hello Webapps,

Thanks for the response. Is there is a new draft or editor's copy where these changes are made?

Addison

Addison Phillips
Globalization Architect -- Lab126

Internationalization is not a feature.
It is an architecture.

> -----Original Message-----
> From: public-i18n-core-request@w3.org [mailto:public-i18n-core-
> request@w3.org] On Behalf Of Marcos Caceres
> Sent: Friday, April 03, 2009 2:34 AM
> To: public-i18n-core@w3.org
> Cc: public-webapps@w3.org
> Subject: Re: Widgets 1.0 Packaging and Configuration: I18N
> comments...
> 
> Hi i18n core,
> 
> On Sun, Feb 22, 2009 at 11:28 PM, Marcos Caceres
> <marcosscaceres@gmail.com> wrote:
> > On Thu, Jan 29, 2009 at 10:56 PM, Phillips, Addison
> <addison@amazon.com> wrote:
> >> 2. Section 7.4 (Widget) The various language bearing elements
> such as <name>, <description>, etc. are of the zero-or-one type.
> However, it is typically better to allow any number of these
> elements to occur, provided that none share the same xml:lang. This
> allows for localization (which is part of the point in allowing
> xml:lang on the element).
> >>
> >
> > We followed "Best Practice 12: Working with multilingual
> documents" in
> > Best Practices for XML Internationalization [1], where it says we
> > should have different documents for this kind of localization (to
> > achieve what you propose, we allow multiple configuration
> documents in
> > a widget).
> >
> > Does i18n core recommend we drop allowing multiple configuration
> > documents and use xml:lang in multiple elements in the manner
> > suggested above? We have built a lot infrastructure around the
> current
> > model in the spec, so if it's all the same we would prefer to
> keep it.
> >
> Given your feedback, in the packaging spec, we have moved to only
> using a single config.xml file located at the root of the widget.
> We
> have added the following rules, as per the example below. Assume
> the
> UA's locale is "en-us":
> 
> <widget xmlns="http://www.w3.org/ns/widgets">
>    <description xml:lang="en">
>       This element would be used.
>    </description>
> 
>    <description xml:lang="en">
>       This element would be ignored because it is not
>       the first element of that has an xml:lang attribute
>       with the value "en".
>    </description>
> 
>    <description>
>       This element would be used if the user agent's
>       locale does not match any localized description
>       elements.
>    </description>
> </widget>
> 
> Kind regards,
> Marcos
> 
> --
> Marcos Caceres
> http://datadriven.com.au


Received on Friday, 3 April 2009 14:39:00 GMT

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