From: <denis.maier@unibe.ch>
To: <braslau.list@comcast.net>
Cc: ntg-context@ntg.nl
Subject: Re: Different authorconversion for citation alternatives and bibliographic entries
Date: Fri, 2 Jul 2021 08:00:51 +0000 [thread overview]
Message-ID: <6a62f1f6e19a4bd1ba18efc8fd601875@unibe.ch> (raw)
In-Reply-To: <20210630154956.3c74c145@poo.hsd1.co.comcast.net>
> -----Ursprüngliche Nachricht-----
> Von: Alan Braslau <braslau.list@comcast.net>
> Gesendet: Mittwoch, 30. Juni 2021 23:50
> An: Maier, Denis Christian (UB) <denis.maier@unibe.ch>
> Cc: ntg-context@ntg.nl
> Betreff: Re: [NTG-context] Different authorconversion for citation alternatives
> and bibliographic entries
>
[...]
> >
> > So what would be needed to make add real support for it?
>
> First of all, come to a consensus on a clear style guide to base this on, so as not
> to run after ambiguous and perhaps contradictory specifications. This would be
> distinct from the APA (author-year) model as well as from the minimalist APS
> (numbered) style. Could this perhaps be the Chicago style? (does that have a
> footnote specification?)
Chicago is certainly not a bad choice for this. It's probably one of the most complete footnote specifications out there. (I knows multiple variants though, so you need to settle for one or support both.)
One thing to be aware of is that Chicago is utterly complex. Other styles like MHRA are a bit simpler. This complexity might be an advantage and a disadvantage at the same time. It may be hard to get this completely right. The already mentioned biblatex-chicago package shows how much is involved. OTOH, if you get this right that should cover almost everything that might come up in note based styles.
Denis
___________________________________________________________________________________
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-07-02 8:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 8:20 Ágoston Volcz
2021-06-30 9:51 ` Aditya Mahajan
2021-06-30 11:28 ` Ágoston Volcz
2021-06-30 16:06 ` Hans Hagen
2021-06-30 17:00 ` path for custom files (was Different authorconversion for citation alternatives and bibliographic entries) Jan U. Hasecke
2021-06-30 17:14 ` Hans Hagen
2021-06-30 17:26 ` Different authorconversion for citation alternatives and bibliographic entries Alan Braslau
2021-06-30 18:08 ` Ágoston Volcz
2021-06-30 18:59 ` denis.maier
2021-06-30 19:11 ` Alan Braslau
2021-06-30 19:40 ` denis.maier
2021-06-30 21:49 ` Alan Braslau
2021-07-01 13:09 ` J Huisman
[not found] ` <20210701094214.7c69a7b2@poo.hsd1.co.comcast.net>
2021-07-01 18:46 ` Gavin
2021-07-02 8:00 ` denis.maier [this message]
2021-07-02 8:02 ` denis.maier
2021-08-28 1:11 Joey McCollum via ntg-context
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=6a62f1f6e19a4bd1ba18efc8fd601875@unibe.ch \
--to=denis.maier@unibe.ch \
--cc=braslau.list@comcast.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).