On Mon, Mar 10, 2025 at 07:28:54PM +0000, Gavin Smith wrote: > On Mon, Mar 10, 2025 at 02:33:40PM +0100, pertu...@free.fr wrote: > > On Sun, Mar 09, 2025 at 12:33:40PM +0000, Gavin Smith wrote: > > > > > > > > What I plan to do is: > > > > * name for links to external nodes is the default one independently of > > > > customization variables. If users ask for it, we can add to htmlxref > > > > hello type translit > > > > * name for redirection files is the default one independently of > > > > customization variables > > > > * if TRANSLITERATE_FILE_NAMES is set, additional redirection files > > > > with translitarated file names are produced, similar to > > > > ADD_TRANSLITERATED_REDIRECTION_FILES, but not as a temporary > > > > measure > > > > > > I don't know which redirection files you mean here. I understood that > > > --transliterate-file-names is to change the output file names, not to > > > create extra redirection files. > > > > My idea was that, if --transliterate-file-names is specified, then the > > generated manual can be the target of cross-references from another > > manual that assumes transliterated file names, which requires > > redirection files with transliterated file names for anchors and also > > for nodes if not split at node. > > 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). -- Pat
