From: "honyk" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: Index - ranges
Date: Fri, 8 Nov 2013 20:53:57 +0100 [thread overview]
Message-ID: <34741.1060393371$1383940474@news.gmane.org> (raw)
In-Reply-To: <007801cedc04$43767660$ca636320$@tosovsky@email.cz>
On 2013-11-07 honyk wrote:
>
> 1) when a range for my subject index entry is specified and the text
> between doesn't overflow to the next page, even in this case
> the range of pages 1-1 is created. Is there any option to normalize
> it to a single page number?
>
> \startregister[index][range_01]{primary}
> Dummy text.
> \stopregister[index][range_01]
It is rare, but any help to eliminate it completely is appreciated.
> 2) when ranges are used heavily, confusing results are produced. In
> following examples I would expect a single range 1-6:
> a) 1-3, 3-6
> b) 1-6, 2-4
> c) 1-6, 5-6
This one was caused by improper Docbook => dbcontext => ConTeXt conversion.
All ranges of secondaries were treated as primaries so they were collected
at primaries. After fixing the XSLT such cases dissapeared completely.
Great. This would be a blocker for me.
> 3) when several single index entries are used on consecutive pages, the
> result 1,2,3,4,5 is produced. Is there any option to create a range
> from this?
I'm reconsidering this now. I designed my 'subject' index to use ranges when
the subject is thoroughly explained, which obviously needs to define
beginning and end. On the contrary, when the subject is just mentioned
(above the threshold of importance), I inserted just a single index entry
instance.
Collecting these single instances into the range of e.g. 1-5 would bring
false expectations that the subject is thoroughly explained there...
This logic goes slightly against the case (1). When the range would be
collapsed into to a single value, we would loose the info that the subject
is described here. But it looks weird.
Jan
___________________________________________________________________________________
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 parent reply other threads:[~2013-11-08 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <007801cedc04$43767660$ca636320$@tosovsky@email.cz>
2013-11-08 19:53 ` honyk [this message]
2013-11-12 21:14 ` honyk
[not found] ` <00d401cedfec$3eb0c090$bc1241b0$@tosovsky@email.cz>
2013-11-15 12:50 ` honyk
[not found] ` <008c01cee201$4a65bff0$df313fd0$@tosovsky@email.cz>
2013-11-15 17:32 ` honyk
2013-11-07 21:56 honyk
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='34741.1060393371$1383940474@news.gmane.org' \
--to=j.tosovsky@email.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).