From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: [BIB] Extra space before surname
Date: Tue, 13 Sep 2005 20:13:49 +0200 [thread overview]
Message-ID: <432716DD.4050801@elvenkind.com> (raw)
In-Reply-To: <1252752178.20050913200741@iol.it>
Giuseppe Bilotta wrote:
> Tuesday, September 13, 2005 Taco Hoekwater wrote:
>
>
>> \def\invertedshortauthor#1#2#3#4#5%
>> {\doifnotempty{#2}{#2\bibalternative\c!vonsep}%
>> #3\bibalternative\c!surnamesep
>> \doifnotempty{#5}{#5\bibalternative\c!juniorsep}%
>> \doifnotempty{#4}{#4\unskip}}
>
>
>
> No luck ...
oh, I'm sorry. Wrap the definition in \unprotect ... \protect,
please.
>>(we slowly are getting to the point where it is easier on you to
>> send me the actual document and a list of errors in t-bib :))
>
> Can do that, if you want :)
If this doesn't work, ok?
Taco
next prev parent reply other threads:[~2005-09-13 18:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 12:37 Giuseppe Bilotta
2005-09-13 13:30 ` Taco Hoekwater
2005-09-13 14:10 ` Re[2]: " Giuseppe Bilotta
2005-09-13 15:51 ` Taco Hoekwater
2005-09-13 18:07 ` Re[2]: " Giuseppe Bilotta
2005-09-13 18:13 ` Taco Hoekwater [this message]
2005-09-14 4:13 ` Giuseppe Bilotta
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=432716DD.4050801@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).