From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: bibtexing problems
Date: Fri, 02 Dec 2005 16:39:15 +0100 [thread overview]
Message-ID: <43906AA3.4000102@elvenkind.com> (raw)
In-Reply-To: <4390382C.9000604@student.kuleuven.be>
Hi Wolfgang,
For 1. and 2., see Thomas' reply.
Wolfgang Zillig wrote:
> 3. I have in the bibtex field: "comment = {genauere Analyse des Papers
> nötig!}," some comments. They are added at the end the individual
> reference. Is there a possibility to suppress this field?
In the bibl-apa.tex file, you can simply remove all the \insertcomment
commands. Or you can delete the \comment lines from <\jobname>.bbl
(probably easier).
> 4. is there a way of citing by bibtex key? (to get (Hameury2005) for the
> entry @ARTICLE{Hameury2005,...)). I think that is nice to have during
> writing the document and only to change this in the final version.
Sure you can:
\cite[key][Hameury2005] will give you "Hameury2005"
Greetings,
Taco
prev parent reply other threads:[~2005-12-02 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 12:03 Wolfgang Zillig
2005-12-02 13:41 ` Thomas A. Schmitz
2005-12-02 15:16 ` Wolfgang Zillig
2005-12-02 15:39 ` Taco Hoekwater [this message]
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=43906AA3.4000102@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).