Encoding customization variable names

[Gavin Smith]

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.

I've renamed  DATA_INPUT_ENCODING_NAME to COMMAND_LINE_ENCODING and
LOCALE_OUTPUT_ENCODING_NAME to MESSAGE_ENCODING in an attempt to make
them more meaningful and distinctive. I know that
LOCALE_OUTPUT_ENCODING_NAME was also used when invoking latex2html and
others but the messages seemed to be the primary use and it is not
immediately obvious that it should also be used for encoding parts of
command lines.

Still to review: LOCALE_INPUT_FILE_NAME_ENCODING,
LOCALE_OUTPUT_FILE_NAME_ENCODING, DOC_ENCODING_FOR_INPUT_FILE_NAME and
DOC_ENCODING_FOR_OUTPUT_FILE_NAME. I don't know if I'll get to these
today.

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.