From: Taco Hoekwater <taco@elvenkind.com>
Cc: ConTeXt mailing list <ntg-context@ntg.nl>
Subject: Re: m-bib questions/remarks
Date: Mon, 25 Jun 2001 11:15:34 +0200 [thread overview]
Message-ID: <3B370136.3D9A1EB0@elvenkind.com> (raw)
In-Reply-To: <5.1.0.14.0.20010623180541.00a868e0@public.uni-hamburg.de>
Eckhart Guthöhrlein wrote:
>
> Hi,
>
> I just started to use the bib module for accessing my existing bibtex
> databases. I have some remarks/questions. First, my minimal input file:
>
> \usemodule[bib]
> \setupbibtex[database=test,sort=no]
> \starttext
> \cite[a], \cite[b], \cite[c]
> \completelistofpublications
> \stoptext
>
> 1. The first TeX run works fine, and so does running BibTeX. But in the
> subsequent TeX run, I get an error message because of an undefined control
> sequence \etalchar. This seems to be used for the short labels. I do not
> need them, so I said \def\etalchar#1{#1} as workaround, but I do not think
> that everything is as it should be now.
>
> 2. If I omit "sort=no" from the setup (since it is the default), TeX
> complains about \@@pbsort being undefined during the first run, probably an
> internal problem of the module.
>
> 3. I am unable to change the citation format.
> \setuppublications[refcommand=authoryears] has no effect, nor has
> \setupcite[author][]. However, \cite[authoryears][a] works fine, so a
> workaround is not difficult to do.
>
> 4. If there are abbreviations used only in titles in the list of
> publications, they won't make their way into the list of abbreviations. I
> guess I have to take care of them myself? I have noticed the same if you
> use another abbreviations in the full text for an abbreviation, and if this
> the only occurence of the second abbreviation, so that it is called only in
> the list of abbreviations. My workaround is "{\setbox0{\hbox{\EXMPL}}}" in
> the text, any better suggestions?
>
> If these problems are my fault, please tell me, if they are due to the beta
> stage of the module, please consider this a bug-report (1-3) or feature
> suggestion (4).
1. is definately a bug.
2. is probably an incompatibility with your context, it does not appear
in mine.
3. is also a bug.
4. I don't understand why it doesn't work. (It should, I think).
Thanks for the report, I'll look into them soon.
--
groeten,
Taco
next prev parent reply other threads:[~2001-06-25 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-23 16:44 Eckhart Guthöhrlein
2001-06-25 9:15 ` Taco Hoekwater [this message]
2001-06-25 11:06 ` Eckhart Guthöhrlein
2001-06-25 12:16 ` Taco Hoekwater
[not found] ` <5.1.0.14.0.20010625150034.00a8c380@public.uni-hamburg.de>
2001-06-25 13:44 ` 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=3B370136.3D9A1EB0@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).