From: "'Nick Bart' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: "pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org"
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: localisation of "and others" in biblatex name lists
Date: Tue, 23 Feb 2021 14:21:29 +0000 [thread overview]
Message-ID: <PWVXqUu44Lx_hAkn2QC4F5REKYzoaUVyKOF98umWHu-nsuXv2IAwn7D2M5RTqvd_d9SVHJjphCeguLXIozJdayAqsIukkyRYZlXjVCDXmgI=@protonmail.com> (raw)
In-Reply-To: <6c4d351890d56e3a701d80647aa373c2a2cdb0cf.camel-1KBjaw7Xf1+zQB+pC5nmwQ@public.gmane.org>
IIRC pandoc does not try to convert "and others" from bibtex or biblatex to CSL since the CSL specs just don’t seem to support abbreviating a list of authors with a placeholder - and I for one can’t really think of a sensible way of handling this automatically.
In effect, CSL assumes that it’s always possible to include a full list of authors in one’s database. Unless the names of the "others" are genuinely unobtainable, I guess that would be the way to go in this case, too.
What CSL does support is abbreviating lists of authors when formatting bibliographies. So if the number of authors seems too large to be included in the output, one could always try to find (or modify) a CSL style that renders an abbreviated list only.
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/PWVXqUu44Lx_hAkn2QC4F5REKYzoaUVyKOF98umWHu-nsuXv2IAwn7D2M5RTqvd_d9SVHJjphCeguLXIozJdayAqsIukkyRYZlXjVCDXmgI%3D%40protonmail.com.
next prev parent reply other threads:[~2021-02-23 14:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 18:24 Carlos Franke
[not found] ` <9824c91ca9f60d7d4928eb5c7256cb54db86cf57.camel-1KBjaw7Xf1+zQB+pC5nmwQ@public.gmane.org>
2021-02-23 0:12 ` John MacFarlane
[not found] ` <m24ki31w23.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-02-23 10:21 ` Carlos Franke
[not found] ` <6c4d351890d56e3a701d80647aa373c2a2cdb0cf.camel-1KBjaw7Xf1+zQB+pC5nmwQ@public.gmane.org>
2021-02-23 14:21 ` 'Nick Bart' via pandoc-discuss [this message]
2021-02-23 14:44 ` AW: " denis.maier-FfwAq0itz3ofv37vnLkPlQ
[not found] ` <e34f8a7159dd4ff299dbd4a18e3a5c96-FfwAq0itz3ofv37vnLkPlQ@public.gmane.org>
2021-02-23 14:57 ` BPJ
[not found] ` <CADAJKhAqNWMC6ZsNauj=gd2XMpkFaKNi92kk=z4LfW11TyYwtg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-02-23 19:22 ` Joost Kremers
2021-02-23 14:54 ` Carlos Franke
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='PWVXqUu44Lx_hAkn2QC4F5REKYzoaUVyKOF98umWHu-nsuXv2IAwn7D2M5RTqvd_d9SVHJjphCeguLXIozJdayAqsIukkyRYZlXjVCDXmgI=@protonmail.com' \
--to=pandoc-discuss-/jypxa39uh5tlh3mbocffw@public.gmane.org \
/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).