From: "Eckhart Guthöhrlein" <eckhart_guthoehrlein@public.uni-hamburg.de>
Subject: Re: m-bib: passing extra information to \cite
Date: Fri, 07 Sep 2001 10:58:24 +0200 [thread overview]
Message-ID: <5.1.0.14.0.20010907103821.00a81fd0@public.uni-hamburg.de> (raw)
In-Reply-To: <3B988205.D0802432@elvenkind.com>
At 10:15 07.09.2001 +0200, Taco Hoekwater wrote:
>\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').
As far as I am concerned, it can be removed, since I'm planning to abandon
the use of latex entirely and do not have large bibtex databases yet.
A more general solution could be to use a different command for
cross-referencing inside the bib file, let's call it \crosscite for
example. Then you could say something like
\def\crosscite#1{\cite[#1]} % for context
or
\def\crosscite#1{\cite{#1}} % for latex
in the setup area of your document, or perhaps better in the bib module and
in a cont-bib.sty file provided for use with latex. Existing databases
could be converted with a single search and replace, and the context \cite
command would be free of restrictions due to backwards compatibility
issues. I think this simple conversion would be an acceptable price for
enhanced functionality.
Perhaps the definition of \crosscite should provide equivalent use of
\crosscite{..} and \crosscite[..], so context users can use the square
brackets consistently.
Eckhart
next prev parent reply other threads:[~2001-09-07 8:58 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
2001-09-07 8:58 ` Eckhart Guthöhrlein [this message]
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=5.1.0.14.0.20010907103821.00a81fd0@public.uni-hamburg.de \
--to=eckhart_guthoehrlein@public.uni-hamburg.de \
/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).