[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260430182838.GU1827@brightrain.aerifal.cx>
Date: Thu, 30 Apr 2026 14:28:38 -0400
From: Rich Felker <dalias@...c.org>
To: Pablo Correa Gomez <pabloyoyoista@...tmarketos.org>
Cc: musl@...ts.openwall.com
Subject: Re: Start of localedef tool for locales project
On Thu, Apr 30, 2026 at 08:08:43PM +0200, Pablo Correa Gomez wrote:
> El Wed, 29-04-2026 a las 16:08 -0400, Rich Felker escribió:
> > Based on previous proposal & discussion of the new locale source
> > format (subset of POSIX localedef, to be documented, with extensions
> > for error strings) and the concepts for the proposed binary runtime
> > format, I've put together a simple parser that reads localedef-format
> > input and emits what amount to a sequence of insertions into the
> > multi-level binary table format.
>
> Really nice! I've now just tested with a few of the current translations, and
> seems to mostly just work fine. The only thing that called my attention is that
> the parser seemed to miss the semi-colon-separated eras and alt-digits, taking
> just the first one. You can find the source file attached if you want to use it
> for testing.
OK, AFAICT the nl_langinfo documentation is insufficient to determine
what the actual data in ALT_DIGITS and ERA is supposed to look like. I
assumed ALT_DIGITS was a single string with one character per digit,
but perhaps it's supposed to be a multi-string delimited by null bytes
and terminated by an empty string or something to that effect. I think
we'll need to look at what other implementations do here to figure out
the intent.
Thanks for finding this!
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
