From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Bibliography in MKIV, custom rendering
Date: Sat, 12 Aug 2017 10:54:53 +0200 [thread overview]
Message-ID: <9abdf4fa-99ca-befb-4737-82005c388db1@wxs.nl> (raw)
In-Reply-To: <96c3fc40-10f8-41b8-5a7e-7eab4c0f7344@rik.users.panix.com>
On 8/11/2017 8:58 PM, Rik Kabel wrote:
> On 2017-08-11 10:01, Alan Braslau wrote:
>> ...
>>
>>
>> 2) Apple Inc. is not a name so you should not be using author:
>> organization is more appropriate.
>>
> I do not think that this should be the case.
>
> APA and Chicago/Turbanian (and doubtless others) accept association
> names as author names, and provide rules for handling them.
and as a consequence i bet this is why journals get typeset partly by
hand (tweak and cheat on these things) ... and why each publisher then
has its own style (with cheats and tricks)
> The lack of either an author or an editor is currently flagged in
> ConTeXt as an error for books and perhaps other bibtex entry types as
> well. Or do you mean to apply this recommendation to only the electronic
> type or some other limited subset of types?
>
> Perhaps it is better to use the association name as an author and
> protect it with a layer of curlies or quotation marks, as {{Apple,
> Inc.}}, "{Apple, Inc.}", or '{Apple, Inc.}', any one of which will do
one can do that of course (an dit will work) but then someone will come
along and say that ...
our recomendation is that one spends some time on a proper database as
it pays off
> the job and also serve to prevent what would surely be unwanted
> abbreviation for styles that abbreviate what are parsed as given names.
we really try to get away from fuzzyness ... in fact, the bib format or
at least the way it's often used is a structural coding nightmare (and
often tex commands are then used to bypass things) .. i think that it
never went through a proper 'design, test, review, revise' cycle
reverse engineering what is there + side effects took us quite a while
and esp the author bit is a pain (this parsing) ... there have been
proposals for alternatives in the past decades (take mlbibtex) but so
far we're stuck with historic stuff: making a database in a format that
is not that suitable (no nesting) using practices that are counter
intuitive and demand lots of obscure magic
(one day Alan will wrap this up in an article)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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-12 8:54 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 [this message]
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
-- 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=9abdf4fa-99ca-befb-4737-82005c388db1@wxs.nl \
--to=pragma@wxs.nl \
--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).