[tz] Extra transition type is generated by zic with -r specified

Almaz Mingaleev mingaleev at google.com
Tue Oct 26 09:06:17 UTC 2021

I see it now, thanks.
My goal was to generate transitions beyond 2038, not to truncate

On Mon, 25 Oct 2021 at 19:51, Paul Eggert <eggert at cs.ucla.edu> wrote:

> On 10/25/21 11:15, Almaz Mingaleev wrote:
> > How feasible is it to add a flag which does not truncate the file?
> The -r flag causes zic to truncate the file, so you can avoid truncation
> by not using the -r flag.
> Perhaps you meant "truncate the file in some other way"? What way would
> you like?
> > Also, RFC [1] says the following about TZ string:
> > "the string MUST be
> > consistent with the last version 2+ transition". Doesn't
> > truncation violate that?
> It's not an RFC conformance problem because the TZ string is empty in
> the truncated file, so there's nothing to be consistent with. The full
> quote from RFC 8536 is: "If the string is nonempty and one or more
> transitions appear in the version 2+ data, the string MUST be consistent
> with the last version 2+ transition."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mm.icann.org/pipermail/tz/attachments/20211026/a10b15ce/attachment.html>

More information about the tz mailing list