From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: bibliography questions
Date: Tue, 3 Oct 2023 16:32:26 +0200 [thread overview]
Message-ID: <8a09147d-edc8-5409-afde-2bff0080de4d@fiee.net> (raw)
In-Reply-To: <20231002180258.11cdaab3@boo.my.domain>
Am 03.10.23 um 02:02 schrieb Alan Braslau:
> On Mon, 2 Oct 2023 13:13:52 +0200
> Henning Hraban Ramm <texml@fiee.net> wrote:
>
>> Consider:
>> @Book {rattenhka,
>> author = "Bettina von Arnim and Gisela von Arnim",
>> title = "Das Leben der Hochgräfin Gritta von Rattenzuhausbeiuns",
>> …
>> }
>>
>> The authors are usually given as “Bettina and Gisela von Arnim”
>> (mother and daughter; similar “Jacob and Wilhelm Grimm” as brothers
>> or “Bettina and Achim von Arnim” as a couple) – is there a good
>> solution for related authors?
>
> Multiple authors should be treated as multiple authors. That they are
> related is not and should not be a consideration in citing works. At
> least this is the practice that I know of for academic texts.
>
> You can cheat and try to define one author with a combined first name,
> like
> author={Eames, Ray & Earl},
> but I don't know how that parses as I have never tried it; "and" is a
> reserved token used to define multiple authors. I wouldn't do it as I
> can think of many examples (Bjaer & Bjaer) where we give both credit,
> individually.
Thank you.
It seems like database solutions like BibTeX & Cie are generally not
suitable for quoting books as they were published – and that’s important
in the contexts of “my” authors (literary studies, history).
For my ConTeXt book, I thought it would make sense, and I would jump
through some hoops just to use the system, but
– most sources that I want to list are never quoted (method=dataset)
– I would need to define my own rendering, e.g. don’t like the handling
of names
– I need additional fields (custom rendering again)
– if I refer to sources, I want a URL or file path in a footnote (custom
cite wrapper macro)
This all works fine without the btx subsysten (I just need to find
solutions for some edge cases, or avoid them), so I probably had wrong
ideas about bibliographies (at least in TeX).
OTOH, for my novel I can use the bib database approach for an extended
person register; the required rendering is much less involved.
Hraban
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2023-10-03 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 11:13 [NTG-context] " Henning Hraban Ramm
2023-10-03 0:02 ` [NTG-context] " Alan Braslau via ntg-context
2023-10-03 14:32 ` Henning Hraban Ramm [this message]
2023-10-03 21:08 ` Aditya Mahajan
2023-10-04 7:00 ` Henning Hraban Ramm
2023-10-05 7:05 Rik Kabel
2023-10-05 7:11 ` 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=8a09147d-edc8-5409-afde-2bff0080de4d@fiee.net \
--to=texml@fiee.net \
--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).