emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: TRS-80 <lists.trs-80@isnotmyreal.name>
To: emacs-orgmode@gnu.org
Subject: Re: Fixing the automatic generation of Tex info node names
Date: Wed, 04 May 2022 18:52:28 -0400	[thread overview]
Message-ID: <87ee183o7n.fsf@isnotmyreal.name> (raw)
In-Reply-To: 874k2ptj1z.fsf@posteo.net

Philip Kaludercic <philipk@posteo.net> writes:

> Ihor Radchenko <yantar92@gmail.com> writes:
>> Philip Kaludercic <philipk@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.


      parent reply	other threads:[~2022-05-04 22:53 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
2022-04-20  4:28     ` Ihor Radchenko
2022-05-04 22:52     ` TRS-80 [this message]

Reply instructions:

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 \
    --in-reply-to=87ee183o7n.fsf@isnotmyreal.name \
    --to=lists.trs-80@isnotmyreal.name \
    --cc=emacs-orgmode@gnu.org \


* 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).