Philip Kaludercic <phil...@posteo.net> writes: > Ihor Radchenko <yanta...@gmail.com> writes: > >> Philip Kaludercic <phil...@posteo.net> writes: >> >>> For some reason ox-texinfo removes periods from node names. It seems >>> this is not necessary as info can render these files without any issues, >>> and in certain cases not intended (e.g. I had a node named "Emacs 28.1" >>> and it was abbreviated to "Emacs 281"). >> >> According to >> https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#Node-Line-Requirements >> >>>> Unfortunately, you cannot reliably use periods, commas, or colons >>>> within a node name; these can confuse the Info reader. Also, a node >>>> name may not start with a left parenthesis preceding a right >>>> parenthesis, as in (not)allowed, since this syntax is used to specify >>>> an external manual. (Perhaps these limitations will be removed some >>>> day.) >> >> Not that we cannot work around this, but we need something different >> than the proposed patch. > > Would you happen to know what the issue is? As I said, the documents > appear to render just as expected in my case, but it might just be due > to the version or because I didn't hit some specific edge-case.
Personally, if I were interested, I think I would follow-up to the texinfo mailing list (or whatever they have) and ask them? As it even says above: > Perhaps these limitations will be removed some day Maybe they already have been? If not, worst case, I think you probably learn more about what the problem might be. Just a thought. Cheers, TRS-80