From: "Peter Jander" <pj@orc.soton.ac.uk>
Subject: Re: some m-bib problems
Date: Mon, 2 Sep 2002 09:00:10 GMT [thread overview]
Message-ID: <3D732ACC.6787.30A704@localhost> (raw)
>
> 2. A previously mentioned bug still appears to be there where (when using
> refcommand=num and numbering=yes) a cite[ref1,ref2,ref3] becomes [1-2]
> rather than [1-3].
> otherwise an already sorted list will be reduced to the first two elements.
> I think I am using the updated version
Are you sure you are using up-to-date Context? It works fine here
with a recent beta Context.
> 4. The publication list has references which are not enclosed in square
> brackets. How do I generate a more usual publication list (in the IEEE)
> which is enclosed in square brackets?
>
> [1] first publication
> [2] second publication
> Etc.
\def\refwithbrackets#1{[#1]\hss}
\setuppublications[numbering=yes,numbercommand=\refwithbrackets]
is what I am using.
Hope this helps,
Peter
next reply other threads:[~2002-09-02 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-02 9:00 Peter Jander [this message]
2002-09-02 14:37 ` Nigel King
-- strict thread matches above, loose matches on Subject: below --
2002-09-01 11:15 Nigel King
2002-09-03 7:29 ` Taco Hoekwater
2002-09-03 4:23 ` 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=3D732ACC.6787.30A704@localhost \
--to=pj@orc.soton.ac.uk \
/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).