Philip Kaludercic writes:
> Ihor Radchenko writes:
>
>> Philip Kaludercic 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 na
Philip Kaludercic writes:
> 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.
The link I shared is all I know. Apparently, using some sym
Ihor Radchenko writes:
> Philip Kaludercic 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 abbre
Philip Kaludercic 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").
Accordi
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").
This patch should resolve the issue:
>Fro
