From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Subject: Re: localtime on native Windows
Date: Mon, 12 Feb 2024 18:02:15 -0800 [thread overview]
Message-ID: <62badb92-dc1a-4935-89fc-5bf1ba32b811@cs.ucla.edu> (raw)
In-Reply-To: <7117573.dE46n4Xy2H@nimes>
On 2024-02-11 04:46, Bruno Haible wrote:
> The first question is how to include tzdata in gnulib.
> - AFAICS, the main data file (without comments) is tzdata.zi and is about
> 100 KB large. It can be upgraded simply by copying the newest tzdata.zi
> from a newer tzdata distribution. Including such a file in gnulib would
> be OK (re copyright, number of files, total size), right?
No problem with copyright; the file is in the public domain.
> - Whereas including all files from /usr/share/zoneinfo is probably not
> acceptable (> 1300 files, ca. 6 MB total size).
That can be automatically generated from tzdata.zi, by using zic, the
source code of which is also in the public domain. This is common in
GNU/Linux systems. If memory serves Android uses another approach: a
single binary file indexed by timezone name.
next prev parent reply other threads:[~2024-02-13 2:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 17:43 MT-unsafe time modules Bruno Haible
2024-02-09 20:22 ` Bruno Haible
2024-02-10 11:10 ` Bruno Haible
2024-02-11 12:46 ` localtime on native Windows Bruno Haible
2024-02-13 2:02 ` Paul Eggert [this message]
2024-02-18 2:38 ` Bruno Haible
2024-02-18 4:50 ` Paul Eggert
2024-02-18 14:38 ` Bruno Haible
2024-02-18 19:05 ` Paul Eggert
2024-02-11 10:43 ` MT-unsafe time modules Bruno Haible
-- strict thread matches above, loose matches on Subject: below --
2024-02-13 18:25 localtime on native Windows Brian Inglis
2024-02-18 2:14 ` Bruno Haible
2024-02-18 5:32 ` Brian.Inglis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=62badb92-dc1a-4935-89fc-5bf1ba32b811@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).