Re: Encoding customization variable names

[Patrice Dumas]

On Sat, Jul 23, 2022 at 09:20:19AM +0300, Eli Zaretskii wrote:
> This should IMO come with a set of recommendations regarding the
> practices: when and for what reasons to override the defaults, and
> with what recommended values.  Otherwise, users of Texinfo will not
> necessarily understand the subtleties, and the result will be chaos.

It seems to me that there should be very little need for the user to set
anything.  On GNU/Linux and unix which use UTF-8 everywhere nowadays,
there is no real issue.  On Windows, DOC_ENCODING_FOR_INPUT_FILE_NAME
default is set especially based on your recommendations.  The situations
where some customization would be needed are likely to be very rare,
involving non ascii filenames and manuals produced on computers with
different encodings.  In those cases, the users will also probably have
trouble with use of mixed encodings for file and directory names,
reducing even more the plausibility of situations handled with setting
encodings using customization variables in texi2any.

Correctly encoding and decoding file names, however, and setting the
right defaults, is important to handle non ascii characters in files.

-- 
Pat