Well, BCP 47 just updated to the new country codes. Following that, we have just updated Unicode CLDR for them, and now we are missing a mapping from country codes to timezone for the new country codes. That mapping is used in a number of places, including the localizations, so it is not a trivial lack. CLDR's going out at the end of this month (
1.5.1), and is used in ICU (among other places), which is going out in December (3.8.1), and my company (Google) uses ICU and would upgrade thereafter. So it's kind of a domino effect.
Thus we'd appreciate adding the new country codes so that everything's in sync.
Mark
"Mark Davis" <mark.davis@icu-project.org> writes:Hmm, OK, what's the rush? This doesn't affect any time zone data per
> It would be very helpful for us if we could get a release quickly that added
> these to zone.tab (with new IDs and Links). Any possibility of that?
se; it's just auxiliary info. (Are the 7000 people of St Barthelemy
bombarding us with email, demanding that they not be forced to set
TZ='America/Guadeloupe'? :-)I have been leaning towards America/St_Barthelemy and America/Marigot,
> For the IDs, I'd suggest either Saint_Barthelemy or Gustavia for the first,
> and either Saint_Martin or Marigot for the second.
for reasons discussed earlier on this list.Yes, that makes sense.
> These country codes were split off from Guadeloupe, and so had the same
> timezone rules. So they can be initially Linked to Guadeloupe.