On Mon, Feb 10, 2025 at 03:11:03PM +0100, pertu...@free.fr wrote: > On Fri, Feb 07, 2025 at 02:10:57PM +0000, Werner LEMBERG wrote: > > > Likewise, Finnish speakers strongly protest if "ä" is rendered as > > > "ae". > > > > 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, which would prevent > Text::Unicode from being used. I think that for ä, we do not use > unidecode (I didn't check precisely) to replace the character, so it may > not change the output, but for japanese, with USE_UNIDECODE = 0, the > Text::Unidecode transliterations would not be used. > > If someone wants to propose other ways to transliterate, this could be > possible. Instead of USE_UNIDECODE, there could be a more general > variable, like TRANSLITERATION_METHOD. We could even add the > possibility to read user-defined transliteration mappings, though I > doubt that it would be used much.
Users could do transliteration of node names in the Texinfo source if they wanted. Instead of writing @node garçonnière they could write @node garconniere (I searched Google for a French word with accents in it.) Then they would get garconniere.html etc. created. How acceptable this would be would depend on the language and possibly the user's opinions. (For example, I heard that in French it is common to drop accents on words that are in all caps, while this isn't done in other languages.) Outputting "Bogen.html" when the node was actually called "Bögen" is something we could avoid by default. It would also depend on the output format with the node names more visible in Info output. Another option is to use UTF-8 in created file names: "garçonnière.html" or "Bögen.html". I expect that this would work ok in most cases but could be turned off by default just in case.
