On Mon, Feb 10, 2025 at 04:54:24PM +0000, Gavin Smith wrote: > On Mon, Feb 10, 2025 at 03:46:27PM +0000, Werner LEMBERG wrote: > > > > >> And Japanese people are probably even offended because, as it > > >> currently happens, almost all Japanese characters are represented > > >> with Chinese syllables... > > > > > > In addition to --no-transliterate-file-names, it is also possible to > > > set the customization variable USE_UNIDECODE to 0, [...] > > > > Japanese cross-reference labels detected while > > `--transliterate-file-names` is active. Please read section 'XXX' in > > the manual how this influences the naming of split HTML files. > > ``` > > If we turned off file name transliteration by default we wouldn't > have any of these problems.
At least I can't see another way to avoid clashes in file names. One thing to think about is that the file names are truncated to 250 characters and non-transliterated file names could be longer in some cases, therefore turning off transliteration by default could lead to more cases of file name clashes for long non-ASCII node/anchor names with the same 240 protected name beginning (48 characterss if no ASCII at all and no spaces). Transliterated could allow twice more characters in favorable cases, but less than no transliteration in unfavourable cases such as some scripts with long transliterations, or transliterations to symbols that are afterwards escaped. -- Pat
