From: Horacio Suarez <horaciosuarez@hotmail.com>
To: <ntg-context@ntg.nl>
Subject: Re: index sort question
Date: Sun, 21 Nov 2010 21:48:23 +0000 [thread overview]
Message-ID: <SNT114-W546E3DE3EFFEBAE4749560B43C0@phx.gbl> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1944 bytes --]
Jano, thankyou very much.
It is a songs book, and I need an author table of content.
Your solution is very good, works fine, but using \pagenumber or incrementing a counter I can´t make it work.
I replace \pagenumber with a incremental number to assure the label sorting.
So using the original sample, instead of:A\index[arbol+\pagenumber]{arbol+rojo}\pageB\index[araña+\pagenumber]{araña+linda}\pageC\index[arbol+\pagenumber]{arbol+verde}\pageD\index[araña+\pagenumber]{araña+grande}\pageE\index[arbol+\pagenumber]{arbol+blanco}\page
it is nowA\index[arbol1]{arbol+rojo}\pageB\index[araña2]{araña+linda}\pageC\index[arbol3]{arbol+verde}\pageD\index[araña4]{araña+grande}\pageE\index[arbol5]{arbol+blanco}\page
Even it´not elegant, the Author index is very nice!
Maybe yo know why I can´t make it work.
Well, thankyou again.
--------------------
Horacio Suarez
Editorial Antropofagia
www.eantropofagia.com.ar
> To: ntg-context@ntg.nl
> From: jano.kula@tiscali.cz
> Date: Fri, 19 Nov 2010 10:49:35 +0100
> Subject: Re: [NTG-context] index sort question
>
> On 11/19/2010 10:45 AM, Jano Kula wrote:
> > Hello Horacio,
> >
> > if you have only one index item per page, than on the second level you
> > can use \pagenumber for sorting:
>
> or your own counter increased by every index item, which doesn't
> restrict it to one item per page.
>
> J.
>
> ___________________________________________________________________________________
> 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://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
[-- Attachment #1.2: Type: text/html, Size: 3513 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 bytes --]
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2010-11-21 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-21 21:48 Horacio Suarez [this message]
2010-11-22 7:52 ` Vianney le Clément
2010-11-23 10:37 ` Jano Kula
2010-11-23 12:27 ` Horacio Suarez
-- strict thread matches above, loose matches on Subject: below --
2010-11-18 21:50 Horacio Suarez
2010-11-19 9:45 ` Jano Kula
2010-11-19 9:49 ` Jano Kula
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=SNT114-W546E3DE3EFFEBAE4749560B43C0@phx.gbl \
--to=horaciosuarez@hotmail.com \
--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).