ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: Elided page numbers in registers
Date: Thu, 06 Oct 2005 20:58:23 +0200	[thread overview]
Message-ID: <434573CF.1090500@seznam.cz> (raw)
In-Reply-To: <4344FE5E.9090905@capdm.com>

Duncan Hothersall wrote:
> On 31 Aug I wrote:
> 
> 
>>I have page ranges in my index, such as 1/1-1/3, or 2/24-2/26.
>>
>>I would like these ranges to be elided - in other words, the first one
>>would read 1/1-3 (remove repeated chapter number), and the second would
>>read 2/24-6 (remove repeated chapter number and also the repeated 2 in
>>page number).
>>
>>Question: is there an already existing system to do this? I guess no :-)
>>
>>Followup: I would be willing to help to code this if it doesn't exist (I
>>have some experience with such systems) if someone can point me at the
>>right bit of code to look at (things seem to be changing around
>>texutils, newtexexec etc. so I don't want to start at the wrong place).
> 
> 
> Sorry to be a pain, but can anyone help with this? I'm converting a
> legacy system, in which everything (cross referencing, tables of
> contents, indices) was hand-coded in plain tex and Perl, across to
> ConTeXt. The advantage of having hand-coded the indexing stuff was that
> I could easily add features like eliding, or funny sort orders. I now
> need to reproduce the same output. I suspect I could apply the same
> techniques to the ConTeXt code, but I don't want to embark on a fool's
> errand if (a) it's already done somewhere, or

My experience: It is not implemented in (old) texutil.pl. It is even not 
implemented in simpler only-page-number case.
In the code there is secret switch '$CollapseEntries', by default it is 
off. Switching manually on leads to all index page entries collaps to 
one (generally noncontinuous) range.

The same sad result you obtain if you use startregister...stopregister pair.

If you know Perl it is not difficult to insert such stuff for one 
application. It is very difficult to create a general solution.

I have no (positive and deep) experience with new ruby texutil equivalent.

vit

 > (b) the code I hack is about to be replaced.
> 
> Thanks,
> 
> Duncan
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
> 

-- 
=======================================================
Ing. Vít Zýka, Ph.D.                         TYPOkvítek

database publishing              databazove publikovani
data maintaining and typesetting in typographic quality
priprava dat a jejich sazba v typograficke kvalite

tel.: (+420) 777 198 189     www: http://typokvitek.com
=======================================================

  reply	other threads:[~2005-10-06 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06 10:37 Duncan Hothersall
2005-10-06 18:58 ` Vit Zyka [this message]
     [not found] <20050831142920.905D812815@ronja.ntg.nl>
2005-09-01  9:27 ` Duncan Hothersall
  -- strict thread matches above, loose matches on Subject: below --
2005-08-31 13:28 Duncan Hothersall
2005-08-31 14:22 ` Vit Zyka

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=434573CF.1090500@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).