W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2009

comments on Widgets 1.0 packaging...

From: Phillips, Addison <addison@amazon.com>
Date: Wed, 28 Jan 2009 13:54:31 -0800
To: "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <4D25F22093241741BC1D0EEBC2DBB1DA017D90805B@EX-SEA5-D.ant.amazon.com>
All,

Here are my comments on http://www.w3.org/TR/2008/WD-widgets-20081222/


1. In section 7, starting in 7.3 and encompassing each of the text bearing elements that follow, "xml:lang" is defined as an attribute (good!), but the definition refers to "basic language range". I don't believe this is what is intended. The value of xml:lang is a language tag. Ranges are used for selecting which tagged item to display. For example, an item tagged as <name xml:lang="pt"/> might be selected for display in cases where the default locale is "pt-BR". In that example, "pt-BR" is the range and "pt" is the value (tag) matching it.

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.

3. Section 7.11 (content element). The charset attribute "assumes" UTF-8 if charset is not present. Note that if the encoding isn't UTF-8, this can be detected and an error generated (or some other fallback assumed). Probably the best pattern would be:

  - if charset is present, use that encoding
  - if charset is absent, check if it is UTF-8
  - if not UTF-8, assume Cp437 (or ISO 8859-1 if that's more appropriate)

4. Section 7.15 (ITS tags). Glad to see this.



Addison Phillips
Globalization Architect -- Lab126

Internationalization is not a feature.
It is an architecture.

Received on Wednesday, 28 January 2009 21:58:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 28 January 2009 21:58:21 GMT