On Wed, Dec 10, 2025 at 11:22 AM Nico Williams <nico@cryptonector.com> wrote:
> On Wed, Dec 10, 2025 at 11:03:00AM +1300, Thomas Munro wrote:
> > On Wed, Dec 10, 2025 at 10:54 AM Thomas Munro <thomas.munro@gmail.com> wrote:
> > > if you create codesetless symlinks
> >
> > Oops, wrote that too fast... you want to add the suffixes. Well then
> > it's the other way around, and you'd have to generate new files with
> > the right encoding and suffixes (which means knowing which
> > combinations the target system has), instead of making symlinks, and
> > make sure that the "en_US" one is in the appropriate encoding, maybe?
>
> How about supporting only UTF-8 locales?
Yeah, if nobody noticed this wasn't working at all, then it makes
sense to defer the generation of .mo files for non-UTF-8 codesets
until someone eventually does notice that it still doesn't work in
legacy locales and feels inclined to do something about it, ie
forever. Tom's goal of having basic tests pass will be satisfied by
UTF-8-only.
