ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: Index
Date: Thu, 10 Nov 2005 20:57:39 +0100	[thread overview]
Message-ID: <4373A633.1000104@seznam.cz> (raw)
In-Reply-To: <4373444D.2090804@wxs.nl>

Hans Hagen wrote:
> Thomas A. Schmitz wrote:
> 
>> ... it's still missing a few features (I  don't think it can 
>> post-process pdf-files yet) and has a few buglets...
> 
> 
> 
> it should at least i remember writing some code -)

Here is an old example:
------------------------------------
\defineregister[Name][Names]
\setupregister[Name][pagestyle=\it]
\setupregister[Name][bf][pagestyle=\bf]

\starttext
   Names:
   \Name[bf::]{Hans}
   \Name{Taco}
   \startregister[Name][bf::]{Patrick}

   \page[yes]
   \Name{Hans}
   \stopregister[Name][bf::]{Patrick}

   \page[yes]
   \Name{Patrick}
   \placeregister[Name]
\stoptext
--------------------------------------

Regrettably, I have now no time to install and check the new version of 
newtexexec.rb, so perhaps it is already done. Please, for quick check 
focus on 'Patrick' entry, it should have "1--2, 3" page numbers.

Or more complex example:
------------------------------------
\defineregister[Name][Names]
\setupregister[Name]
\setupregister[Name][bf][pagestyle=\bf]

\starttext
   Names:
   \Name{Patrick}
   \Name[bf::]{Hans}
   \Name{Taco}
   \startregister[Name][bf::]{Patrick}

   \page[yes]
   \Name{Patrick}

   \page[yes]
   \Name{Hans}
   \stopregister[Name][bf::]{Patrick}

   \placeregister[Name]
\stoptext
--------------------------------------

Possible variants:
1) Patrick 1, 2, {\bf 1--3}
2) Patrick {\bf 1--3}, 1, 2
3) Patrick 1--2, {\bf 1--3}
4) Patrick {\bf 1--3}, 1--2

in case of variants 1 v. 2 and 3 v. 4 I am not sure how the categories 
'empty_string' and "bf" are sorted. But it does not matter since user 
can set any category name.

variants 3, 4 should be set if some register option (coupling?) is set on

vit

  reply	other threads:[~2005-11-10 19:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 20:44 Index Olivier
2005-10-15 22:11 ` Index Thomas A. Schmitz
2005-10-15 23:07   ` Index Olivier
2005-11-09 13:11     ` Index Hans Hagen
2005-11-09 14:14       ` Index Thomas A. Schmitz
2005-11-09 15:53         ` Index Hans Hagen
2005-11-09 16:07         ` Index Hans Hagen
2005-11-09 17:32           ` Index Thomas A.Schmitz
2005-11-09 18:48             ` Index Hans Hagen
2005-11-09 22:42               ` Index Thomas A. Schmitz
2005-11-09 23:35                 ` Index Hans Hagen
2005-11-10  9:03                   ` Index Thomas A. Schmitz
2005-11-10 12:58                     ` Index Hans Hagen
2005-11-10  8:33                 ` Index Gerben Wierda
2005-11-10  9:16                   ` Index Thomas A. Schmitz
2005-11-10 12:59                     ` Index Hans Hagen
2005-11-10 19:57                       ` Vit Zyka [this message]
2005-11-10 10:37                   ` Index Hans Hagen
     [not found] <20051110221209.7525512828@ronja.ntg.nl>
2005-11-14 13:13 ` Index Duncan Hothersall
2005-11-14 14:22   ` Index Hans Hagen

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=4373A633.1000104@seznam.cz \
    --to=vit.zyka@seznam.cz \
    --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).