> Date: Fri, 22 Jul 2022 22:41:26 +0200 > From: Patrice Dumas <[email protected]> > > On Fri, Jul 22, 2022 at 05:55:01PM +0100, Gavin Smith wrote: > > > * Use document encoding > > > * Use locale encoding > > > * Specify encoding explicitly > > > > ... > > > > > I'm going to make a start by stripping out the LOCALE_ prefix and then > > > have a look to see if something else is needed to give these variables > > > priority (from the user's perspective). > > > > > > > My current idea is to save the locale encoding, perhaps in a hidden or > > undocumented customization variable. In > > Texinfo::Convert::Converter::encoded_input_file_name and similar functions, > > the value of INPUT_FILE_NAME_ENCODING should always take priority over both > > the locale encoding, and the document encoding. If INPUT_FILE_NAME_ENCODING > > is not given, then either the locale or document encoding should be used > > according to the value of DOC_ENCODING_FOR_INPUT_FILE_NAME. I think this > > would be quite clear. > > This looks good to me. I think that the locale encoding should also be > a customization variable, but in the documentation it would be stated that > "You should not need to explicitly set this variable." It is possible > to pass it simply as a key (in lower case) as is done for 'values'. But > I think that the less variables like that there is, the best it is. And > it could even make sense for a user to override the locale encoding if > the system is not well set up. Maybe simply LOCALE_ENCODING?
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.
