[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7489170fad0cf568e96d6164a2330f7f45f0cc2b.camel@postmarketos.org>
Date: Wed, 13 May 2026 13:58:58 +0200
From: Pablo Correa Gomez <pabloyoyoista@...tmarketos.org>
To: Rich Felker <dalias@...c.org>, musl@...ts.openwall.com
Subject: Re: Updated dumplocale/source format [Re: Selecting locale
source format]
El Thu, 30-04-2026 a las 19:54 +0200, Pablo Correa Gomez escribió:
> El Mon, 20-04-2026 a las 13:44 +0200, Pablo Correa Gomez escribió:
> > >
> > I have used the provided dumplocale.c file to transform the current locales
> > into
> > the new source format. It can all be found
> > in https://gitlab.postmarketos.org/postmarketOS/musl-locales Generally the
> > whole
> > thing was pretty straight-forward, and clearly it now allowed to fix the
> > infamous "May" bug:
> > https://gitlab.postmarketos.org/postmarketOS/musl-locales/-
> > /commit/374ea7d0164efcf1bc1f14701b1333a943837bd7
> >
> > Of course, the "May" bug is still present in all translations (but Spanish,
> > my
> > native language, that I have manually fixed), and things like the
> > differentiation between H_ and H0 are not there either, since they were not
> > there in the previous translations.
> >
> > I will start poking translators about this, to see if we find any issue that
> > we
> > didn't find earlier.
> >
> > Best,
> > Pablo
> > >
> We've gotten quite some good feedback from the translators already. So far,
> there are 2 questions that have come up as the most salient ones:
>
> First, documentation on the keys to translate. I found good documentation for
> the standard POSIX keys in[1] would be good to know if that's a good
> authoritative source. However, I could not find such documentation for the
> error
> codes in the LC_MESSAGES section. Most specifically, a translator had a
> question
> abuot EAI_OVERFLOW, which in English is just "Overflow". Regardless of whether
> the English string had to be improved, would be nice to have a good
> authorizative source for those. Everything I could find were manual pages for
> getnameinfo
In relation to this, a question just came up about a few errors that seem to be
missing in the documentation in
https://pubs.opengroup.org/onlinepubs/9799919799/functions/V2_chap02.html#tag_16_03
like ENOCSI or EL2HLT and that in musl they currently just say "No error
information". Have those been deprecated by POSIX? Is there any other place that
can provide context about them? I can find some information online, but seems to
be mismatched.
Best,
Pablo
>
> Second, I was asked about the first day of the week. It seems that is a glibc
> extension that can be queried passig "_NL_TIME_FIRST_WEEKDAY" to
> nl_langinfo[2].
> Although this is obviously not in POSIX, I really wonder why is it not, when
> it's something clearly tied to the system language. Indeed, I dag a bit into
> it,
> only to realize that it works in my system due to the toolkit I used the most
> having some ugly hack[3] working around this limitation. I would be pretty
> interested if we could make sure that the source and binary format have enough
> flexibility to support adding such potential use-case in the future, would
> POSIX
> be updated to support such useful situation.
>
>
> [1]
> https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap07.html#tag_0
> 7_03_03
> [2] https://sites.uclouvain.be/SystInfo/usr/include/langinfo.h.html
> [3] https://gitlab.gnome.org/GNOME/gtk/-
> /blob/main/po/es.po?ref_type=heads#L1898
>
> >
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.
