On Tue, Mar 11, 2025 at 10:02:25AM +0100, pertu...@free.fr wrote: > On Mon, Mar 10, 2025 at 07:28:54PM +0000, Gavin Smith wrote: > > Isn't that changing the purpose of --transliterate-file-names? > > > > Before: "texi2any --transliterate-file-names" means to output files > > with transliterated file names. > > > > After: "texi2any --transliterate-file-names" means to output files > > without transliterated files, and additionally to output redirection > > files with transliterated names. > > Sorry, I was not clear, what I propose is to output transliterated > files, and additionally output redirection files with transliterated names. > (and also output redirection with non transliterated names).
When you say "redirection files" does this refer to the redirection files that would be output even without --transliterate-file-names? These include redirection files for anchors, and possibly for nodes as well depending on the splitting option. Or do you mean redirection files for every single node? For the case when --transliterate-file-names is on, I appreciate the purpose of outputting redirection files with non-transliterated names. However, this is still a change in program behaviour, and users may not always want these extra files. I wonder if there is a better way of supporting this. Maybe the new ADD_TRANSLITERATED_REDIRECTION_FILES variable could be changed to allow outputting untransliterated redirection files.
