Internationalization proposal: some comments...
cira at google.com
Tue Jul 27 11:56:06 PDT 2010
1. I've added a reference to RFC 4647, and extended constructor to allow
lookup. I'll try to make it more strict.
2,3. Locale.getDefault() is not necessary, since we get the default if
caller passes * for locale. Same for TimeZone - if caller passes empty time
zone parameter we return default zone.
On Tue, Jul 20, 2010 at 2:17 PM, Phillips, Addison <addison at lab126.com>wrote:
> I reviewed the thread at  and wanted to contribute a few comments on the
> strawman proposal at .
> I think this effort is important. Many of us have struggled with the lack
> of ready internationalization support within ECMAScript and server-side or
> custom processing are both unsatisfying as a solution. During the W3C TPAC
> last year, some of us interested in this problem met with TC39 and made a
> number of suggestions  that I hope will be taken up for
> consideration---some of these are covered by this proposal.
> WRT the strawman, I had these comments:
> 1. The Locale class should have a matches() method or methods that permit
> locale/language negotiation to be implemented. RFC 4647 matching (either
> filtering or lookup) are far more common than pure equality checks.
> 2. Should there be a Locale.getDefault?
> 3. Should there be a TimeZone.getDefault()?
> 4. The Collator doesn't include rule-based collation? Is that planned for
> the future?
> 5. I know that other APIs are planned for the future, but message and
> number format are equally (often more) important than dates. I wouldn't want
> them omitted in an initial implementation.
> I hope to see progress on this work in the future.
>  https://mail.mozilla.org/pipermail/es-discuss/2010-June/011380.html
> Addison Phillips
> Internationalization is not a feature.
> It is an architecture.
> es-discuss mailing list
> es-discuss at mozilla.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss