<tt><font size=2>>> I'm maintaining a mapping data between the IANA
tzids and Windows <br>
>> time zones in the Unicode CLDR project and review the data about
<br>
>> quarterly basis [</font></tt><a href=http://www.unicode.org/repos/cldr/trunk/common/><tt><font size=2>http://www.unicode.org/repos/cldr/trunk/common/</font></tt></a><tt><font size=2><br>
>> supplemental/windowsZones.xml].<br>
>> <br>
>> -Yoshito </font></tt>
<br><tt><font size=2>> <br>
> I've found a few differences between your mapping table and my tzdata
[<br>
> </font></tt><a href=http://paste.stg.fedoraproject.org/4440/90540445/><tt><font size=2>http://paste.stg.fedoraproject.org/4440/90540445/</font></tt></a><tt><font size=2>].</font></tt>
<br><tt><font size=2>> I would be happy to provide it patch formatted,
just let me know if <br>
> it's of your interest.</font></tt>
<br><tt><font size=2>> <br>
> Moreover, what is the reason to have those kind of differences?</font></tt>
<br><tt><font size=2>> Could it be different from distro to distro?</font></tt>
<br><tt><font size=2>> <br>
</font></tt>
<br><tt><font size=2>These are FAQs. I think CLDR project should provide
a document about this.</font></tt>
<br><tt><font size=2>This document [</font></tt><a href="http://cldr.unicode.org/development/development-process/design-proposals/extended-windows-olson-zid-mapping"><tt><font size=2 color=blue>http://cldr.unicode.org/development/development-process/design-proposals/extended-windows-olson-zid-mapping</font></tt></a><tt><font size=2>]
is a little bit old, but you can see some useful background information
about the mapping data. (Sorry for my crappy English)</font></tt>
<br>
<br><tt><font size=2>CLDR project defines stable set of tzids, because
tzids are used also for locale data for display names. For example -</font></tt>
<br>
<br><tt><font size=2>TZ database: America/Argentina/Buenos_Aires vs. CLDR:
America/Buenos_Aires</font></tt>
<br>
<br><tt><font size=2>In old versions of the tz database only had "America/Burnos_Aires"
and CLDR project uses it as a key for localized display names for the zone.
Later, the tz database reorganized Argentina zones, then "America/Buenos_Aires"
was moved to backward file as below:</font></tt>
<br>
<br><tt><font size=2>Link America/Argentina/Buenos_Aires
America/Buenos_Aires</font></tt>
<br>
<br><tt><font size=2>Because we don't want CLDR locale data files to change
the key identifying the zone, we preserve America/Buenos_Aires as the canonical
name of the zone, America/Argentina/Buenos_Aires is added as an alias.
The mapping is defined in another place [</font></tt><a href=http://www.unicode.org/repos/cldr/trunk/common/bcp47/timezone.xml><tt><font size=2 color=blue>http://www.unicode.org/repos/cldr/trunk/common/bcp47/timezone.xml</font></tt></a><tt><font size=2>]</font></tt>
<br>
<br><tt><font size=2><type name="arbue" description="Buenos
Aires, Argentina" alias="America/Buenos_Aires America/Argentina/Buenos_Aires"/></font></tt>
<br>
<br><tt><font size=2>In this file, first entry of alias is the canonical
'long' id for the zone in CLDR project, and remaining entries in alias
attribute are its alias. That means, the consumer of windowsZones.xml needs
to use this additional mapping data.</font></tt>
<br>
<br>
<br><tt><font size=2>For 'missing' data, such as "Australia/Lord_Howe"
- is really unmappable. In the tz database, this zone is defined as</font></tt>
<br>
<br><tt><font size=2>Zone Australia/Lord_Howe 10:36:20 -
LMT 1895 Feb</font></tt>
<br><tt><font size=2>
10:00
- EST
1981 Mar</font></tt>
<br><tt><font size=2>
10:30
LH LHST</font></tt>
<br>
<br><tt><font size=2>However, Windows does not have any zone using UTC+10:30
offset. I use a small tooling for maintaining the mapping data in the ICU
project and I have exception data for such zones [</font></tt><a href="http://source.icu-project.org/repos/icu/icuapps/trunk/WinTZ/src/com/ibm/icu/dev/tools/wintz/mapper/MapData.java"><tt><font size=2 color=blue>http://source.icu-project.org/repos/icu/icuapps/trunk/WinTZ/src/com/ibm/icu/dev/tools/wintz/mapper/MapData.java</font></tt></a><tt><font size=2>].
I think the comments below explain why these are not included.</font></tt>
<br>
<br><tt><font size=2> /*<br>
* There are some Olson time zones that do not have the same
base UTC offset in<br>
* Windows time zones. These zones are not supported by Windows.<br>
*/<br>
static final String[] NO_BASE_OFFSET_MATCH_ZONES_ARRAY =
{<br>
"Australia/Eucla",
// +8:45<br>
"Australia/Lord_Howe", // +10:30<br>
"Etc/GMT-14",
// +14:00<br>
"Pacific/Chatham",
// +12:45<br>
"Pacific/Kiritimati", // +14:00<br>
"Pacific/Marquesas", //
-9:30<br>
"Pacific/Norfolk",
// +11:30<br>
};</font></tt>
<br>
<br><tt><font size=2> /*<br>
* These Olson time zones are using different DST rules from
Windows zones with<br>
* same base offset.<br>
*/<br>
static final String[] NO_DST_RULE_MATCH_ZONES_ARRAY = {<br>
// UTC-10:00/North American DST rule.<br>
// Closest match - "Hawaiian Standard
Time" (no DST)<br>
"America/Adak",<br>
<br>
// UTC-08:00/no DST.<br>
// Closest match - "Pacific Standard Time"
(observes DST).<br>
"Etc/GMT+8",<br>
"America/Metlakatla",<br>
"Pacific/Pitcairn",<br>
<br>
// UTC-09:00/no DST<br>
// Closest match - "Alaskan Standard Time"
(observes DST).<br>
"Etc/GMT+9",<br>
"Pacific/Gambier",<br>
<br>
// UTC-06:00/Southern Hemisphere style DST
rule.<br>
// Closest match - "Central America Standard
Time" (observes Northern Hemisphere style DST rule).<br>
"Pacific/Easter",<br>
<br>
// UTC-03:00 zone with North American DST rule.<br>
// Closest match - "Greenland Standard
Time" (observes EU DST rule).<br>
"America/Miquelon",<br>
<br>
// UTC+02:00 with DST (Mar - Sep).<br>
// Closest match - "E. Europe Standard
Time", "Israel Standard Time" and some others<br>
"Asia/Gaza",<br>
"Asia/Hebron",<br>
};<br>
</font></tt>
<br><tt><font size=2>There is a request to add 'unmappable' zones included
in the data [</font></tt><a href=http://unicode.org/cldr/trac/ticket/5589><tt><font size=2 color=blue>http://unicode.org/cldr/trac/ticket/5589</font></tt></a><tt><font size=2>]
and I'm planning to work on this in near future.</font></tt>
<br>
<br><tt><font size=2>I don't want to hijack this ML for discussing CLDR
specific implementation. If you have further questions, please post your
question directly to the CLDR project. You can post your questions to CLDR
user mailing list (cldr-users@unicode.org) [</font></tt><a href=http://www.unicode.org/consortium/distlist.html#cldr_list><tt><font size=2 color=blue>http://www.unicode.org/consortium/distlist.html#cldr_list</font></tt></a><tt><font size=2>]
or problem reports/new feature requests to the CLDR trac [</font></tt><a href=http://unicode.org/cldr/trac><tt><font size=2 color=blue>http://unicode.org/cldr/trac</font></tt></a><tt><font size=2>].</font></tt>
<br>
<br><tt><font size=2>Thanks,</font></tt>
<br><tt><font size=2>Yoshito</font></tt>
<br>
<br>
<br><tt><font size=2> </font></tt>
<br>