> .... To handle such cases, texi2any offers the
> --transliterate-file-names command line option. [...]
>
> This is the default.
Well, it is customary to always show the opposite option of the
default in the `--help` screen. For file name transliteration,
however, this is not the case: The help screen of `texi2any` 7.2 shows
```
--transliterate-file-names use file names in ASCII transliteration.
```
You should either add a remark that this is the default, or you should
change this to
```
--no-transliterate-file-names don't use ASCII transliteration
for file names
```
[BTW, I miss a remark in the help screen that preceding an option with
'no-' does negate its meaning.]
>> so I could imagine that 'Bögen' gets mapped to 'B_oe_gen' or
>> something similar. Stripping off the umlaut dots from the 'ö'
>> character to convert 'Bögen' to 'Bogen' can never be the right
>> solution.
>
> That is what we do. We do the removal of diacritics ourselves in
> some cases, but we mainly use Text::Unidecode, or, in C iconv
> //TRANSLIT https://metacpan.org/pod/Text::Unidecode
Ouch. IMHO, this is something that should be mentioned prominently in
the section about `@anchor`.
> And, indeed, there are many such words in French. I used Prés et
> Près in the test of clashes (and an invented Prês).
OK, so let me recapitulate: If I want to support Texinfo manuals with
HTML output that could have both `@anchor{o}` and `@anchor{ö}`, and
there are other manuals that do cross references to these two anchors,
I must to use `--no-transliterate-file-names`, right?
Werner
