From: Alan Braslau <braslau.list@comcast.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: nvitacolonna@gmail.com
Subject: Re: BibTeX inproceedings entries not rendered correctly in APA style
Date: Mon, 24 May 2021 20:12:22 -0600 [thread overview]
Message-ID: <20210524201222.2db107fd@poo.hsd1.co.comcast.net> (raw)
In-Reply-To: <85ca4ca9-e7ee-d15d-34d4-e0aa282a9b8e@rik.users.panix.com>
On Mon, 24 May 2021 17:53:49 -0400
Rik Kabel <ConTeXt@rik.users.panix.com> wrote:
> This is intended. Or rather, it is a side-effect of the intended
> behavior.
>
> If you add an editor ("editor={Baz, Bar}") you will get something
> like:
>
> Foo, B. (1983). Title of the paper. In B. Baz (Ed.), /Booktitle/.
> Author.
>
> And if you then add a publisher ("publisher={Paymefirst}") you will
> get:
>
> Foo, B. (1983). Title of the paper. In B. Bar (Ed.), Booktitle.
> Paymefirst.
>
> The APA presumes that you have both an editor and a publisher for
> pieces contained in other works. It calls for the use of the author
> as publisher if no publisher is present. It is silent about what to
> do if you have no editor.
It looks like a missing editor field should be caught. What should the
rule be?
Actually, @inproceedings should not be used without an editor - makes
no sense. If the author of the paper happens to be the editor, then the
.bib data file should define this with an editor= field.
We can change the behavior if a clear case can be made as to what
fallback would make sense. Keep in mind the dictum: "garbage in/garbage
out"...
Alan
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-05-25 2:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 20:28 Nicola
2021-05-24 21:53 ` Rik Kabel
2021-05-25 2:12 ` Alan Braslau [this message]
2021-05-25 3:10 ` Rik Kabel
2021-05-25 15:20 ` Alan Braslau
2021-05-27 20:21 ` Nicola
2021-05-28 15:52 ` Alan Braslau
2021-05-28 17:02 ` Aditya Mahajan
2021-05-28 18:21 ` Alan Braslau
2021-05-28 19:52 ` Nicola
2021-05-28 20:33 ` Alan Braslau
2021-05-29 3:30 ` Rik Kabel
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=20210524201222.2db107fd@poo.hsd1.co.comcast.net \
--to=braslau.list@comcast.net \
--cc=ntg-context@ntg.nl \
--cc=nvitacolonna@gmail.com \
/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).