From: Alan Braslau <braslau.list@comcast.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Problem with \seeindex and two + entries
Date: Wed, 15 Nov 2017 10:15:24 -0700 [thread overview]
Message-ID: <20171115101524.32145653@zoo.hsd1.co.comcast.net> (raw)
In-Reply-To: <20171115095504.313aea24@zoo.hsd1.co.comcast.net>
On Wed, 15 Nov 2017 09:55:04 -0700
Alan Braslau <braslau.list@comcast.net> wrote:
> Hello,
>
> I wish to confirm the following "bug" (or feature request).
>
> Alan
>
>
> https://mailman.ntg.nl/pipermail/ntg-context/2017/087966.html
>
> > ConTeXters,
> >
> > An index register entry with two + components does not get set
> > properly. With the following example, the text “/see Mmm+Plus/”
> > should be on a separate, indented line as “Plus /see Mmm+Plus/” but
> > I see it on the first line as “Aaa /see Mmm+Plus/”. When there are
> > zero or one + components, all is well.
> >
> > \starttext
> > \seeindex{Aaa+Plus}{Mmm+Plus}
> > \seeindex{Bbb+Plus}{Nnn, Comma}
> > \seeindex{Ccc, Comma}{Ooo, Comma}
> > \seeindex{Ddd, Comma}{Ppp+Plus}
> > Some text.
> > \index{Aaa+SecondPlus}
> > \index{Bbb+SecondPlus}
> > \index{Mmm+Plus}
> > \index{Mmm+SecondPlus}
> > \index{Ppp+Plus}
> > \index{Ppp+SecondPlus}
> > \index{Ooo, Comma}
> > \index{Nnn, Comma}
> > Some more text.
> > \page
> > \placeindex
> > \stoptext
> >
> >
> > --
> >
> > Rik
>
>
interface indicates:
\seeindex [...][..+...+..]{...}
1 OPT 2 3
1 TEXT PROCESSOR->TEXT
2 INDEX
3 TEXT PROCESSOR->TEXT
so I am not sure that I understand the intended use.
Alan
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-11-15 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 16:55 Alan Braslau
2017-11-15 17:15 ` Alan Braslau [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-13 15:53 Rik
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=20171115101524.32145653@zoo.hsd1.co.comcast.net \
--to=braslau.list@comcast.net \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).