> Date: Sun, 13 Sep 2026 20:02:37 +0200 > From: Patrice Dumas <[email protected]> > > Hello, > > Coming back again on the issue of encoding used for Info files. After > the change in the plaintext and Info converters, encoding to any output > encoding does not add much complexity anymore. However, I still think > that it would be better if the Info files were UTF-8 encoded > irrespective of the input Texinfo file encoding and if, in the long > term, there were mostly UTF-8 encoded Info files. > > My proposal is to use UTF-8 as encoding independentely of Texinfo input > file encoding, with the possibility to set the output encoding with > OUTPUT_ENCODING_NAME. > > What do you think?
I think this is an unusual thing to do, and needs a serious justification. Do we have one? Forcing users to use OUTPUT_ENCODING_NAME is a nuisance.
