public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Carlos Franke <carlosfranke-1KBjaw7Xf1+zQB+pC5nmwQ@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: localisation of "and others" in biblatex name lists
Date: Tue, 23 Feb 2021 15:54:11 +0100	[thread overview]
Message-ID: <dabefa91eaebc296d77bb5c1c4437c20cd4d4735.camel@posteo.de> (raw)
In-Reply-To: <PWVXqUu44Lx_hAkn2QC4F5REKYzoaUVyKOF98umWHu-nsuXv2IAwn7D2M5RTqvd_d9SVHJjphCeguLXIozJdayAqsIukkyRYZlXjVCDXmgI=@protonmail.com>

> 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

I see. In my case the publication itself provides only the abbreviated
editors list. I guess the best workaround for now is to include my
desired translated variant of "and others" verbatim in the biblatex
file.

I just found an old, but still active as of last June, issue about this
in the CSL Github repo:

https://github.com/citation-style-language/schema/issues/34

So it seems there is a chance that support for explicit "and
others"/"et al" will be implemented in CSL at some point in the future.


By the way, sorry to the list for the unnecessary in my last email.
Just after sending it I realised that a more lightweight output like
txt would have been better.

-- 
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/dabefa91eaebc296d77bb5c1c4437c20cd4d4735.camel%40posteo.de.


      parent reply	other threads:[~2021-02-23 14:54 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
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 [this message]

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=dabefa91eaebc296d77bb5c1c4437c20cd4d4735.camel@posteo.de \
    --to=carlosfranke-1kbjaw7xf1+zqb+pc5nmwq@public.gmane.org \
    --cc=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).