From: Taco Hoekwater <taco@elvenkind.com>
Cc: davebnm@swcp.com
Subject: Re: problem using bibtex
Date: Tue, 26 Aug 2003 15:05:33 +0200 [thread overview]
Message-ID: <20030826150533.68c80295.taco@elvenkind.com> (raw)
In-Reply-To: <A83237DB73CF114F9B8E3BF7C5214A1908F41C@bel-msg-2.corp.covestic.com>
Hi,
It is a bug. In fact, it is a bug I believed to have been fixed. :-(
Solution: Start your favorite editor, load bibl-apa.tex, look for
the \setuppublicationlayout[inproceedings] and change
\insertartauthors
to
\insertauthors
Greetings. Taco
On Mon, 25 Aug 2003 16:14:35 -0600, Dave wrote:
> Hi---
>
> I've been trying to get an @InProceedings bibtex entry to format.
>
> The original entry looked like this:
>
> @InProceedings {aapga,
> author = {Williams, Jeffery and Schaefer, Marv and Landoll, Douglas },
> title = {Pretty good assurance},
> booktitle = {New Security Paradigms Workshop},
> year = {1995},
> publisher = {ACM Special Interest Group on Security, Audit, and
> Control}
> }
>
> When bibtexed, the authors appear in the .bbl file, but they do not
> appear in the references list. The references list entry begins at
> "(1995)."
>
> If I change the bibtex entry to an Article, as follows, all the
> information appears in the reference list.
> @Article{aapga,
> author = {Williams, Jeffery and Schaefer, Marv and Landoll, Douglas
> },
> title = {Pretty good assurance},
> journal = {New Security Paradigms Workshop},
> year = {1995},
> note = {ACM Special Interest Group on Security, Audit, and Control}
> }
>
> Is there a problem with the InProceedings entry type, or have I done
> something wrong?
>
> ---Dave Bailey
>
>
>
--
groeten,
Taco
next prev parent reply other threads:[~2003-08-26 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-25 22:14 Dave Bailey
2003-08-26 13:05 ` Taco Hoekwater [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-25 21:08 problem using Bibtex Dave Bailey
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=20030826150533.68c80295.taco@elvenkind.com \
--to=taco@elvenkind.com \
--cc=davebnm@swcp.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).