From: "Peter Jander" <pj@orc.soton.ac.uk>
Subject: Re: BIBTEX module for Context
Date: Mon, 23 Apr 2001 09:14:12 GMT [thread overview]
Message-ID: <3AE3F2CE.27105.24AD04@localhost> (raw)
Hi,
your lit-verz.bib file is not a bib file after all. The first entry is already
in .bbl format ao if you rename the file to lit-bibl.bbl the first
reference comes out ok.
The secong entry is a mixture of .bbl (\startpublication) and .bib
file(the entries) which is no good.
You will only need to run BIBTEX if you have a genuine BIBTEX file
with entries like @BOOK{...}. If you format all your references like
the first, then you are allright without running BIBTEX.
Hope this helps,
Peter
P.S. And check the \setuppublications bit as well.It didn't work
when I renamed the file as lit-verz.bbl but I can't figure out why,
because I don't have the docs here.
next reply other threads:[~2001-04-23 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 9:14 Peter Jander [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-22 20:44 Willi Egger
2001-04-23 7:35 ` Taco Hoekwater
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=3AE3F2CE.27105.24AD04@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).