From: Alan Braslau <braslau.list@comcast.net>
To: Rik Kabel <context@rik.users.panix.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: combined / compressed / collapsed page and numbered citation references in bibliographies
Date: Sat, 12 Aug 2017 20:30:22 -0600 [thread overview]
Message-ID: <20170812203022.03b8ad21@zoo.hsd1.co.comcast.net> (raw)
In-Reply-To: <89559774-31d0-1047-427d-6f93bd32b3a7@rik.users.panix.com>
On Sat, 12 Aug 2017 20:32:17 -0400
Rik Kabel <context@rik.users.panix.com> wrote:
> I noticed that in bibliographies, page indexing combines runs of two
> or more pages (pp. 150–151), as does page number compression in
> registers, while it takes three or more numbered citations to cause a
> similar collapse (per the MKIV-Publications manual, page 38, I do not
> have an example) for citation number references.
>
> Is there a way to change such compression minimums so that they can
> be made consistent?
What seems more logical to you?
pp 150,151 or pp 150-151 - of course pp 150-152 makes perfect sense.
[2,3] or [2-3] - of course [2-4] also makes sense.
I prefer the first choices. ConTeXt registers do the second, and I do
not know what led to that choice and if Hans would like to change it
(or even make this a parameter).
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-08-13 2:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-13 0:32 Rik Kabel
2017-08-13 2:30 ` Alan Braslau [this message]
2017-08-13 3:05 ` Rik Kabel
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=20170812203022.03b8ad21@zoo.hsd1.co.comcast.net \
--to=braslau.list@comcast.net \
--cc=context@rik.users.panix.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).