From: Gavin Smith <gavinsmith0123@gmail.com>
To: bug-gnu-emacs@gnu.org
Cc: bug-texinfo@gnu.org
Subject: Support double colons in Info index entries
Date: Wed, 9 Jan 2019 21:14:33 +0000 [thread overview]
Message-ID: <20190109211433.GB1481@darkstar> (raw)
Emacs version checked: 26.1.
In the Info format colons are special, and for this reason, there is
limited support for colons in index entries. The Emacs Info mode
supports single colons in index entries as long as they are not followed
by a space.
There is this comment at the start of info.el:
;; Note that nowadays we expect Info files to be made using makeinfo.
;; In particular we make these assumptions:
;; - a menu item MAY contain colons but not colon-space ": "
;; - a menu item ending with ": " (but not ":: ") is an index entry
;; - a node name MAY NOT contain a colon
;; This distinction is to support indexing of computer programming
;; language terms that may contain ":" but not ": ".
It doesn't state it, but when I tested it double colons don't work even
if they are not followed by a space.
There is a fairly simple solution to this problem that I haven't seen
suggested in all the messages posted on this topic in the mailing list
archives. In index nodes only (which have a special marker included,
^@^H[index^@^H]), use a colon to terminate the text of the index entry,
but instead of looking for the first colon in the line, look for the
last. So this entry:
* a::b: a colon b. (line 129)
would refer to line 129 of the node "a colon b". This is possible
because node names cannot contain colons. This restriction is not too
important, whereas the inability to index items containing colons is
quite important. This is what is implemented in the standalone info
browser (since change on 2017-04-08).
This change shouldn't be made for all nodes, because the comment after
the closing '.' could contain a colon:
* label: node. comment: with a colon.
This shouldn't be interpreted as refering to a node "with a colon".
However, the "(line ...)" comment can't contain a colon.
I'm not familiar with Emacs Lisp enough to propose a patch to implement
this change myself.
The standalone info program also implemented a quoting mechanism
(surrounding the text with a pair of 0x7F bytes) to allow nearly all
characters to be included in node names and index entries. This has
never been implemented in Emacs Info and has never been used by default
in texi2any's output. I think my suggestion above would be sufficient
and would work with existing Info files and versions of
texi2any/makeinfo without anything breaking. The quoting mechanism could
potentially be removed from texi2any and info as nobody has ever used it
and it makes things more complicated for no reason.
next reply other threads:[~2019-01-09 21:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 21:14 Gavin Smith [this message]
2019-01-11 0:04 ` bug#34023: Support double colons in Info index entries Juri Linkov
2019-01-11 0:28 ` Drew Adams
2019-01-11 19:46 ` Gavin Smith
[not found] ` <20190111194631.GA14925@darkstar>
2019-01-11 19:49 ` Gavin Smith
2019-01-13 0:55 ` Juri Linkov
2019-01-11 0:53 ` Glenn Morris
2019-01-11 20:13 ` Gavin Smith
2019-01-11 20:14 ` Gavin Smith
2019-01-11 20:32 ` Glenn Morris
[not found] ` <hek1jbkk9o.fsf@fencepost.gnu.org>
2019-01-16 19:17 ` Gavin Smith
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190109211433.GB1481@darkstar \
--to=gavinsmith0123@gmail.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=bug-texinfo@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).