From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 52126@debbugs.gnu.org
Subject: bug#52126: Problematic characters in info node names
Date: Fri, 26 Nov 2021 18:26:23 +0200 [thread overview]
Message-ID: <834k7y3mts.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmngs+bGWrrFbvqp44E-Mais+1fuFcP+BgFrhrUKNB-P5g@mail.gmail.com> (message from Stefan Kangas on Fri, 26 Nov 2021 16:24:15 +0100)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 26 Nov 2021 16:24:15 +0100
>
> admin/release-process says:
>
> ** Manuals
> Check for node names using problematic characters:
> find doc -name '*.texi' -exec grep '^@node[^,]*[:.()]' {} +
> Sadly makeinfo does not warn about such characters.
>
> Running that gives me some matches:
Please report to the respective developers, but other than that, we
don't care too much. It isn't a grave problem, and in practice slmost
never causes any trouble.
> However, there are no instructions for what to do about these cases.
There cannot be any instructions, since the manual authors should
rewrite the relevant parts not to use those characters, if possible.
Thanks.
next prev parent reply other threads:[~2021-11-26 16:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 15:24 bug#52126: Problematic characters in info node names Stefan Kangas
2021-11-26 16:26 ` Eli Zaretskii [this message]
2021-11-29 16:03 ` Lars Ingebrigtsen
2021-11-29 17:44 ` Stefan Kangas
2021-11-29 17:52 ` Eli Zaretskii
2021-11-29 18:04 ` Protesilaos Stavrou
2021-11-29 18:07 ` Eli Zaretskii
2021-11-29 19:32 ` Protesilaos Stavrou
2021-11-29 19:46 ` Eli Zaretskii
2021-11-29 20:07 ` Protesilaos Stavrou
2021-11-29 20:32 ` Eli Zaretskii
2021-11-29 20:56 ` Protesilaos Stavrou
2021-11-30 3:25 ` Eli Zaretskii
2021-11-30 6:39 ` Stefan Kangas
2021-11-30 7:16 ` Protesilaos Stavrou
2021-11-30 7:41 ` Stefan Kangas
2021-11-30 16:48 ` Eli Zaretskii
2021-11-29 18:31 ` Stefan Kangas
2021-11-29 18:17 ` Glenn Morris
2021-11-30 4:31 ` Kyle Meyer
2021-11-30 4:39 ` Kyle Meyer
2021-12-03 1:12 ` Stefan Kangas
2021-12-03 1:45 ` Kyle Meyer
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834k7y3mts.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52126@debbugs.gnu.org \
--cc=stefan@marxist.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.