From: Gavin Smith <gavinsmith0123@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 34023@debbugs.gnu.org, bug-texinfo@gnu.org
Subject: bug#34023: Support double colons in Info index entries
Date: Fri, 11 Jan 2019 20:13:23 +0000 [thread overview]
Message-ID: <20190111201323.GC14925@darkstar> (raw)
In-Reply-To: <h4lg3s580v.fsf@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
On Thu, Jan 10, 2019 at 07:53:52PM -0500, Glenn Morris wrote:
> Gavin Smith wrote:
>
> > This is what is implemented in the standalone info browser (since
> > change on 2017-04-08).
>
> "Defining the Entries of an Index" in the Texinfo manual continues to
> say (through Texinfo 6.5.90) "Caution: Do not use a colon in an index entry".
Even if Info mode and the standalone Info browser are changed to
support colons in index entries, people running older versions of these
won't be able to read them. However, texi2any does output the colon in
the index entry without complaint. See attached Texinfo input and Info
output. Newer versions of 'info' can deal with the colons in the index
entries that are output here.
[-- Attachment #2: colon-index.info --]
[-- Type: text/plain, Size: 924 bytes --]
This is colon-index.info, produced by texi2any version 6.5.90 from
colon-index.texi.
\x1f
File: colon-index.info, Node: Top, Next: One, Up: (dir)
* Menu:
* One::
* Concept Index::
\x1f
File: colon-index.info, Node: One, Next: Concept Index, Prev: Top, Up: Top
node one
\x1f
File: colon-index.info, Node: Concept Index, Prev: One, Up: Top
\0\b[index\0\b]
* Menu:
* :: One. (line 3)
* :a: One. (line 3)
* b:c: One. (line 3)
* d::e: One. (line 3)
* f :d: One. (line 3)
* g: h: One. (line 3)
\x1f
Tag Table:
Node: Top\x7f86
Node: One\x7f184
Node: Concept Index\x7f276
\x1f
End Tag Table
[-- Attachment #3: colon-index.texi --]
[-- Type: application/x-texinfo, Size: 203 bytes --]
next prev parent reply other threads:[~2019-01-11 20:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 21:14 Support double colons in Info index entries Gavin Smith
2019-01-11 0:04 ` bug#34023: " 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 [this message]
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=20190111201323.GC14925@darkstar \
--to=gavinsmith0123@gmail.com \
--cc=34023@debbugs.gnu.org \
--cc=bug-texinfo@gnu.org \
--cc=rgm@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).