From: Alan Braslau <braslau.list@comcast.net>
To: Rik Kabel <context@rik.users.panix.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bibliography in MKIV, custom rendering
Date: Sun, 13 Aug 2017 20:50:05 -0600 [thread overview]
Message-ID: <20170813205005.06d98030@zoo.hsd1.co.comcast.net> (raw)
In-Reply-To: <ddb89860-5cf8-55e3-6dde-ea37abe00766@rik.users.panix.com>
On Sat, 12 Aug 2017 23:13:08 -0400
Rik Kabel <context@rik.users.panix.com> wrote:
> So organization will simply become a stand-in for author but with
> different parsing rules. A book will require an author or editor or
> organization. The first two will be parsed for surname, given name,
> and so on, while the last will not, and precedence rules will apply
> when more than one is present, as they do already.
I invite you to read the APA specifications.
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:[~2017-08-14 2:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 14:01 Alan Braslau
2017-08-11 18:58 ` Rik Kabel
2017-08-12 8:54 ` Hans Hagen
2017-08-12 15:28 ` Rik Kabel
2017-08-12 15:48 ` Rik Kabel
2017-08-12 16:10 ` Hans Hagen
2017-08-13 2:38 ` Alan Braslau
2017-08-13 3:13 ` Rik Kabel
2017-08-13 7:34 ` Hans Hagen
2017-08-14 2:50 ` Alan Braslau [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-31 2:23 Gerion Entrup
2017-07-31 19:28 ` Gerion Entrup
2017-08-01 14:26 ` 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=20170813205005.06d98030@zoo.hsd1.co.comcast.net \
--to=braslau.list@comcast.net \
--cc=context@rik.users.panix.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).