Time Zone Localizations

[Masayoshi Okutsu]

This is a bit off from the proposal, but related to time zone localizations.

It appears that the Locale Data Markup Language spec for <timeZoneNames> 
(http://www.unicode.org/reports/tr35/#%3CtimeZoneNames%3E) assumes that 
a time zone has a single set of long and short names, which assumption 
is not valid if a system supports historical time zone changes. 
Actually, the time zone support in Java has this problem because it 
supports historical changes since 1.4 and always display the "latest" 
time zone names. I planned to fix it in J2SE 1.5 (a.k.a. Tiger), but I 
couldn't due to another commitment.

Is it possible for CLDR to make corrections to the <timeZoneNames> spec 
so that it can represent all historical name changes?

Thanks,
--
Masayoshi Okutsu
Java Internationalization
Sun Microsystems (K.K.)

Mark Davis wrote:

>The common locale data repository project (CLDR) hosted by the Unicode
>consortium (www.unicode.org/cldr/) provides for translations of time zone IDs,
>based on the public domain time zone database at ftp://elsie.nci.nih.gov/pub/. A
>number of issues have come up concerning those translations, and we have put
>together a proposal for changing the way that is done. The goal would be to make
>changes in CLDR 1.1, which would be released around mid-October of this year.
>The current version of the proposal is at:
>
>http://oss.software.ibm.com/cvs/icu/~checkout~/icuhtml/design/formatting/time_zone_localization.html
>
>I'd very much appreciate any feedback on the proposal.
>
>Mark
>__________________________________
>http://www.macchiato.com
>► शिष्यादिच्छेत्पराजयम् ◄
>
>
>  
>