<i18n dev> CLDR Irish time zone name

Mark Davis ☕️ mark at macchiato.com
Wed Feb 14 06:24:23 UTC 2018

I'm pretty annoyed with the TZ group lately; there seems to be little
consideration for compatibility.

I think, if it comes to it, we may need to be prepared to fork the "input
data" in CLDR. My hope is that they will instead at least maintain the
current format AND some new-fangled format that goes off into the weeds as
part of the TZ project.


On Wed, Feb 14, 2018 at 12:25 AM, Martin Buchholz <martinrb at google.com>

> On Tue, Feb 13, 2018 at 3:02 PM, Stephen Colebourne <scolebourne at joda.org>
> wrote:
> >
> > In the short term, I don't think CLDR should change its data, nor do I
> > think OpenJDK should change. ie. for Ireland, standard=winter and
> > daylight=summer should continue to be true in both projects.
> >
> I agree
> > If TZDB insists on continuing with the change, the TZDB compiler in
> > OpenJDK will have to be changed. I've managed to make a change (hack)
> > to the compiler in Joda-Time, so a solution should be possible to some
> > degree in OpenJDK too.
> > https://github.com/JodaOrg/joda-time/commit/
> c5c681c91c74a508e67911e0af4980
> > 846d676ba2
> I was thinking about how to "reverse the polarity".  The advantage of a
> source transformation is that the code can be shared among all downstream
> tzdata consumers.  The advantage of building it into the "compiler" is
> defense against the maintainer/user mistake of simply overwriting the
> tzdata files.

More information about the i18n-dev mailing list