Re: Encoding customization variable names

[Patrice Dumas]

On Sun, May 29, 2022 at 02:08:42PM +0100, Gavin Smith wrote:
> On Fri, Mar 4, 2022 at 7:22 AM Patrice Dumas <pertusus@free.fr> wrote:
> > Also do not hesitate to propose other names for those customization
> > variables.
> 
> Another issue (I can't remember if I emailed you before about this) is
> the locale settings to run the test suites. You changed it from "C" to
> "C.UTF-8", but the latter encoding doesn't exist everywhere. I changed
> it to "en_US.UTF-8" (see ChangeLog entries on 2022-04-14) but this
> won't exist everywhere either. Perhaps we should find some way of
> keeping the test suite under the "C" locale, perhaps disabling or
> conditionalizing tests that require a UTF-8 locale.

Some tests need this either to have expected error messages, or
more fundamentaly for input file names decoding.  I can propose
something similar with 'Need recoded file names' with a dummy set
on the test command line.

How can the existence of "en_US.UTF-8" be tested?

-- 
Pat