On 2022-10-12 21:26:43 +0200, Patrice Dumas wrote: > On Wed, Oct 12, 2022 at 01:46:28PM +0200, Vincent Lefevre wrote: > > BTW, I thought that --enable-encoding was the default. But after, > > testing, it isn't. The makeinfo(1) man page should be clarified. > > Instead of > > > > --disable-encoding > > do not output accented and special characters in Info output > > based on @documentencoding. > > > > --enable-encoding > > override --disable-encoding (default). > > The default and effect depends on the output format. In the upcoming > release, this is now: > > --disable-encoding do not output accented and special characters > in Info output based on document encoding. > --enable-encoding based on document encoding, output accented > characters in XML-based output as well as > special characters in HTML instead of > entities. > > Does this seems clear to you? Do you see a way to clarify, if not?
Sorry, but I don't understand at all. For --disable-encoding, do you mean that if one has "@documentencoding UTF-8" with a "é" written in UTF-8 in the document, then the accented character will not be present in the Info output because it is based on the document encoding? And if one has "@'e" in the document, the accented character will be present (as not being based on the document encoding)? This looks weird. For --enable-encoding, do you mean that the output encoding is regarded as being the same as the input encoding? But this would be a strange decision: the machine on which the source document is written has nothing to do with the machines on which the document will be read. So the encodings do not have to be the same. The locale should be used for the output encoding as this is needed by "info". -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
