Hi Addison,
On 9/7/10 6:06 PM, ext Phillips, Addison wrote:
Hello Webapps WG,
(This is a personal comment and is not necessarily indicative of the I18N WG's
opinion)
In Section 5 (The Widget Interface), the interface provides for retrieving values such
as 'name', 'shortName', etc. In Widgets P&C, these can be localized in the
configuration document (I assume that the configuration document in this document means
the same document as P&C??). There is no mention of whether or how this value is
localized or if the locale/language is subject to programmatic control (I assume not,
since it is not mentioned).
Could there be an explicit mention of the language/locale and how it interacts
with user-agent? Can/should there be an accessor for language? How about a way
of querying the value by locale?
Support for locale was part of the Widget Interface spec but as we
worked through the localization model for the Packaging and
Configuration spec, we decided to remove it (at least for this version
of the spec). The Packaging spec includes the gist of the
rationalization for this decision:
[[
http://www.w3.org/TR/widgets/#step-5--derive-the-user-agents-locale
As there are numerous ways a user agent can derive the end-user's
preferred languages and regional settings, the means by which those
values are derived are beyond the scope of this specification and left
up to the implementation.
]]
I suppose one could argue the Widget Interface implies the above
indirectly (via the reference to P&C spec). However, I don't see any
harm if the above text were copied into the Interface spec. Would doing
so address your concern?
-Art Barstow
