From: Philip Kaludercic <email@example.com>
To: Ihor Radchenko <firstname.lastname@example.org>
Subject: Re: Fixing the automatic generation of Tex info node names
Date: Tue, 19 Apr 2022 11:21:44 +0000 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <87zgkhnxv8.fsf@localhost> (Ihor Radchenko's message of "Tue, 19 Apr 2022 18:58:19 +0800")
Ihor Radchenko <firstname.lastname@example.org> writes:
> Philip Kaludercic <email@example.com> 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
>>> 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
> 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.
next prev parent reply other threads:[~2022-04-19 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 10:35 Fixing the automatic generation of Tex info node names Philip Kaludercic
2022-04-19 10:58 ` Ihor Radchenko
2022-04-19 11:21 ` Philip Kaludercic [this message]
2022-04-20 4:28 ` Ihor Radchenko
2022-05-04 22:52 ` TRS-80
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).