From: Taco Hoekwater <taco@elvenkind.com>
Cc: ntg-context@ntg.nl
Subject: Re: some m-bib problems
Date: Tue, 3 Sep 2002 09:29:30 +0200 [thread overview]
Message-ID: <20020903092930.0bf43ecf.taco@elvenkind.com> (raw)
In-Reply-To: <B997B553.9C35%king@dircon.co.uk>
On Sun, 01 Sep 2002 12:15:15 +0100, Nigel wrote:
> 1. Using
> ghi03 the publication data for abc01
> ghi03 the publication data for def02
> 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].
> 3. Formatting the publication list does not appear to take commands such as
> strut=yes. Bibmod.pdf suggests that \setuplist commands should work but not
> many seem to. The specific problem I am trying to address is the spacing
> between items in the publication list which is variable and much too small
> it is like framed with no strut and no \blank.
These are all bugs that keep appearing and re-appearing. The main problem is
that the bibliographic module delves deep into the context core, without being
an actual part of context itself. It is near-impossible to keep these bugs
away (and keep them away) with different context versions.
Currently we are working on version 2.0 of the bib module. Hopefully this
will solve all of the current issues. One thing I'll probably do is move away
from the standard context list mechanism altogether (hopefully fixing 4.).
Besides that, here is what will be new:
- XML bibliographic database
- More types of publications possible (audio CD, movies)
- XML style specifications
- More citation options (ibid., in-line data, footnotes, endnotes)
- Better memory management (this implies 'slower' unfortunately)
- Separate filters for (bibtex|docbook xml|RIS) <-> our.xml
--
groeten,
Taco
next prev parent reply other threads:[~2002-09-03 7:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-01 11:15 Nigel King
2002-09-03 7:29 ` Taco Hoekwater [this message]
2002-09-03 4:23 ` Hans Hagen
2002-09-02 9:00 Peter Jander
2002-09-02 14:37 ` Nigel King
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=20020903092930.0bf43ecf.taco@elvenkind.com \
--to=taco@elvenkind.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).