From: "Eckhart Guthöhrlein" <eckhart_guthoehrlein@public.uni-hamburg.de>
Cc: ntg-context@ntg.nl
Subject: Re: m-bib problems
Date: Tue, 10 Jul 2001 17:14:01 +0200 [thread overview]
Message-ID: <5.1.0.14.0.20010710170544.00a8d590@public.uni-hamburg.de> (raw)
In-Reply-To: <3.0.6.32.20010710155437.0180a6e0@server-1>
At 15:54 10.07.2001 +0200, Hans Hagen wrote:
>At 10:37 AM 7/10/01 +0000, Taco Hoekwater wrote:
> >
> >
> >Eckhart Guthöhrlein wrote:
> >
> >> At 09:35 10.07.2001 +0000, you wrote:
> >>
> >>>> I have some minor problems with the bibliography module.
> >>>> 1. A space after \cite[...] disappears in the output.
>
>what would you expect from
>
>blabla \cite[a] blabla? two spaces? As with most commands that can leas to
>spae builduo, beter si to say:
I would expect one space before and one after the citation:
blabla (...) bla
>blabla \cite[a]\ blabla if you really want two spaces [keep in mind that
>tex is special with spaces,
Hm, but this is only necessary because \cite acts differently form other
commands. For a command with one argument, delimited by square brackets, in
plain tex
\def\command[#1]{...}
blablabl \command[...] bla
will lead to two spaces, so I expected the space. The same goes for
commands like \in in context
blablabla \in[nowhere] bla
gives two spaces. At least, there seems to be an inconsistency. (But \in
etc have a different syntax, so perhaps the comparison is not quite adequate.)
And if I got things right, \cite[keys] and \cite[options][keys] are
presented as valid uses of \cite in the documentation, so \cite[keys] and
\cite[][keys] should have the same effect. I would say that the [optoins]
argument of \cite is not really optional if a space is gobbled in search
for it.
Eckhart
next prev parent reply other threads:[~2001-07-10 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-08 21:25 Eckhart Guthöhrlein
2001-07-10 9:35 ` Taco Hoekwater
2001-07-10 7:46 ` Hans Hagen
2001-07-10 8:16 ` Eckhart Guthöhrlein
2001-07-10 10:37 ` Taco Hoekwater
2001-07-10 13:54 ` Hans Hagen
2001-07-10 15:14 ` Eckhart Guthöhrlein [this message]
2001-07-10 17:05 ` Taco Hoekwater
2001-07-10 23:10 ` 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.20010710170544.00a8d590@public.uni-hamburg.de \
--to=eckhart_guthoehrlein@public.uni-hamburg.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).