From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bib module in mkiv
Date: Fri, 17 Apr 2009 11:32:30 +0200 [thread overview]
Message-ID: <D98D4AA1-3C09-401E-A7D0-A77F14BAFE89@uni-bonn.de> (raw)
In-Reply-To: <49E835F3.5060906@elvenkind.com>
On Apr 17, 2009, at 9:55 AM, Taco Hoekwater wrote:
> Hi,
>
> Hans sent me a patch for the bib module so that it now should
> work with the latest mkiv once again, but the code needs testing
> before being included in the context distribution, so please
> do so. You can get the new version of the module from
>
> http://modules.contextgarden.net/bib
>
> Note: you need the latest context beta, because the bib module
> required a small extension to the core.
>
> Best wishes,
> Taco
Hi Taco,
just to clarify things: on the download site in the garden, you write:
"This release has support for the new mkiv structure code, but it
needs a very new beta (2009.04.16 23:52)" The latest beta I could find
was 2009.04.16 22:27, and with this, I still get the error
! Undefined control sequence.
<argument> ... [\bibrefprefix ][\sectionseparator
]
\expanded ...\long \xdef \@@expanded {\noexpand #1
}\@@expanded
\preparebibreflist ...refix ][\sectionseparator ]}
\storeitem
\expandrefs ...ibrefprefix \preparebibreflist {#1}
\global
\bibreffoundfalse ...
\next2 #1,->\expandrefs {#1}
\doprocesscommaitem
\doprocesscommalist ...item \gobbleoneargument #1,
]\relax \global
\advance \...
...
l.182 ...lications[criterium=cite,option=continue]
Should we wait for a still newer beta, or is this a typo and I need to
dig deeper?
Thomas
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-04-17 9:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 7:55 Taco Hoekwater
2009-04-17 9:32 ` Thomas A. Schmitz [this message]
2009-04-17 10:08 ` Hans Hagen
2009-04-17 11:58 ` Wolfgang Schuster
2009-04-17 17:05 ` Hans Hagen
2009-04-17 17:20 ` Wolfgang Schuster
2009-04-17 17:30 ` Hans Hagen
2009-04-17 17:39 ` Wolfgang Schuster
2009-04-17 17:48 ` Hans Hagen
2009-04-17 17:49 ` Thomas Prochaska
2009-04-20 10:30 ` Thomas Prochaska
2009-04-20 10:55 ` Taco Hoekwater
2009-04-20 11:43 ` Thomas A. Schmitz
2009-04-20 11:46 ` Taco Hoekwater
2009-04-17 20:40 ` Peter Münster
2009-04-18 12:16 ` Hans Hagen
2009-04-17 17:06 ` Hans Hagen
2009-04-17 17:37 ` Hans Hagen
2009-04-17 17:52 ` Taco Hoekwater
2009-04-17 18:28 ` 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=D98D4AA1-3C09-401E-A7D0-A77F14BAFE89@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).