[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260513120918.GJ1827@brightrain.aerifal.cx>
Date: Wed, 13 May 2026 08:09:19 -0400
From: Rich Felker <dalias@...c.org>
To: Pablo Correa Gomez <pabloyoyoista@...tmarketos.org>
Cc: musl@...ts.openwall.com
Subject: Re: Updated dumplocale/source format [Re: Selecting locale
source format]
On Wed, May 13, 2026 at 01:58:58PM +0200, Pablo Correa Gomez wrote:
> 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.
I think I mentioned this once before but I may have forgotten: there
are a bunch of errno values we traditionally never had messages for
because they're only used kernel-internally or in some way that isn't
exposed to userspace programs that would have reason to strerror them.
It's fine to omit translations for them for now; the musl logic for
translation will only attempt to lookup translations for items that
exist in its internal data (so that locales act as translation not as
arbitrary functionality-extension) so you'd just end up with the
translation for "Unknown error" (E_) either way.
At some point we may add them but I don't think it's important now. I
just went ahead and included them all in the data model for
completeness.
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.
