On Wed, Nov 26, 2025 at 02:43:04PM +0100, Patrice Dumas wrote: > On Tue, Nov 25, 2025 at 10:02:04PM +0100, Patrice Dumas wrote: > > Here is a proposal: > > > > * use transliteration for section id based on > > --transliterate-file-names/TRANSLITERATE_FILE_NAMES same as for nodes. > > * do not output error messages when iconv gives EILSEQ when doing > > transliteration > > * add to the manual a short sentence in the description of > > --transliterate-file-names stating that the precise transliteration > > is platform dependent. > > This is implemented. > > In the end I added more information to the description of > --transliterate-file-names to clarify the relationship with > --node-files.
Thanks. This resolves one of the doubts I had about the change to the file name transliteration, that redirection files would be created. I hadn't realised that this could be turned off with --no-node-files. So users can get the old behaviour back with '--transliterate-file-names --no-node-files'. > With the recent changes related to transliteration, it seems to me that > it is not so important now. I would suggest moving the paragraph > related to transliteration out of 'HTML Cross-reference 8-bit Character > Expansion' to 'HTML Output Customization', and more precisely to > 'File Names and Links Customization for HTML'. > > What do you think? It seems relevant to mention it in that section but I'm happy if you want to move it as we don't especially recommend transliteration for non-English manuals.
