Thomas Munro <[email protected]> writes:
> On Wed, Dec 10, 2025 at 11:22 AM Nico Williams <[email protected]> wrote:
>> 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.
Right. For the moment I only care about verifying that (a) some
translation happens and (b) the PRI* macros work as-expected.
Since we've already discovered platform-specific failures on both
points, this seems like a very worthwhile exercise.
Encoding-specific behaviors might be worth testing later, but
I'm not excited about that personally.
regards, tom lane
