From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: m-bib: passing extra information to \cite
Date: Fri, 07 Sep 2001 10:15:01 +0200 [thread overview]
Message-ID: <3B988205.D0802432@elvenkind.com> (raw)
In-Reply-To: <5.1.0.14.0.20010906214816.00a7bd90@public.uni-hamburg.de>
Eckhart Guthöhrlein wrote:
... [snip] ..
> and then, for example,
>
> \citeplus[authoryears][SomeBook][S.~100]
>
> This is of course not very elegant, so is there a better way? If not, I
Not at the moment, but I will add something in a future version. One
problem
with \cite that I am interested in hearing people's opinion about: the
currently is a 'latex compatibility' option available as well.
\cite{..} is accepted as meaning the same as \cite[..]. It is in there
because existing databases use this syntax when refering to other items
in the database. But: it is very latexy and not in sync with the context
rule that typeset arguments use {} and setup arguments use [].
So, question: to remove or not to remove? How many people share bibtex
databases between latex en context? (removal makes it easier to implement
the 'extra info').
> Apropos m-bib, there are those unresolved problems:
> \setupbibtex[sort=author] has no effect, and \cite[Xyz97] without the first
> (optional) argument gobbles the following space (just to remind you, I can
> work around it).
Noted. this wil be fixed somewhere before eurotex. Hans? the first one is
a conflict with the multi-lingual interface: author is defined already.
Could
you have a look and explain to me how to go about that?
> Ah, and another question (didn't try myself yet): If I want to use -- for
> page ranges, but I have pages={10-20} in my bib file, can this be done at
> the bibl-xxx.tex level? Or is it easier to change the cont-xx.bst file?
> Similar: what about a point after the title in the bib file, which I would
> like to remove because a point is added when typesetting the list of
> publications?
It's probably easier at the macro level. The bst files are weird, even for
bst files ;). I will look into it and try to explain in the documentation
how it should be done.
--
groeten,
Taco
next prev parent reply other threads:[~2001-09-07 8:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-06 20:07 Eckhart Guthöhrlein
2001-09-07 8:15 ` Taco Hoekwater [this message]
2001-09-07 8:58 ` Eckhart Guthöhrlein
2001-09-07 10:40 ` Hans Hagen
2001-09-07 12:48 ` Taco Hoekwater
2001-09-07 14:14 ` Re[2]: " Giuseppe Bilotta
2001-09-07 15:24 ` Hans Hagen
2001-09-07 10:42 ` 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=3B988205.D0802432@elvenkind.com \
--to=taco@elvenkind.com \
/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).