[tz] Looking for a way to cut down binary zoneinfo size. Does anyone have the way to?

[Bradley White]

Suggestion: Forget about modifying the source data or zic, and just write a
simple zoneinfo->zoneinfo filter that removes any transitions you don't
want.

On Thu, May 18, 2017 at 12:50 PM, Viktor Sergiienko <singalen at gmail.com>
wrote:

> Thanks Paul!
>
> I don't have Android, I have a much smaller vanilla Linux. We do use
> zic in a toolchain.
>
> Update on my progress: immediately after sending the email, I got
> another idea: apparently, Rules need to stay in the source data, they
> shouldn't affect the output size, as long as no zoneline uses them.
> (hope it's correct)
> I've tried cutting zonelines only, but now I get several of:
>
> > can't determine time zone abbreviation to use just after until time
>
> It also appears to me that some zones will be completely empty, and
> thus should turn into Links (question is, to what?)
> The project goes on.
>
> On Thu, May 18, 2017 at 9:44 AM, Paul Eggert <eggert at cs.ucla.edu> wrote:
> > Android uses its own format, which is smaller; you might look into that.
> If
> > memory serves, the default Android tzdata binary file doesn't worry about
> > dates after 2038, which can save space if you know your devices cannot
> > possibly be long-lived. There is an option to go past 2038, though, and
> I'd
> > likely use that myself.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/tz/attachments/20170518/698b0f73/attachment.html>