public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
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: citeproc and "related" field
Date: Tue, 20 Aug 2019 07:06:15 +0000	[thread overview]
Message-ID: <_YdyL8q3jBoJ-JMffharjdfWIMGA7ANVgMtHkCOOd7CneS3SPlY32aCAKl1VkkVLkrNoomKBp42dHQ3crkF5-OAsr330aQphFgdAvZ4j43k=@protonmail.com> (raw)
In-Reply-To: <m2pnl0icnm.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>

To the best of my knowledge, CSL does not provide any mechanisms for dealing with relations between different items. (For example, that’s why pandoc-citeproc needs to pull all the data from a `crossref`ed item and fold it into the `crossref`ing item when translating from bibtex/biblatex to CSL JSON/YAML.)

CSL-M has “`cs:alternative` to add supplementary reference information to a cited item, such as a translation or reprint” (https://citeproc-js.readthedocs.io/en/latest/csl-m/index.html#cs-alternative-extension), but even if we were to consider adding CSL-M extensions to pandoc-citeproc, we would still have to fold all the information from a number of different biblatex items (translation/reprint; orig. lang. version; earlier print; …) into one CSL JSON/YAML item.

Anyone who sees this a unsatisfactory could of course submit a proposal for enhancing CSL itself (https://github.com/citation-style-language/schema/issues).


‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, August 20, 2019 6:17 AM, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org> wrote:

> The question is whether CSL has any variables corresponding to
> these things.
>
> http://docs.citationstyles.org/en/stable/specification.html#standard-variables
>
> If so, we could try to be smarter about translating from
> bibtex/biblatex to citeproc json. If not, then it's out of scope
> for pandoc-citeproc.
>
> Guido Milanese guido.milanese-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org writes:
>
> > I am seriously experimenting pandoc filter "citeproc" as an interesting
> > alternative to the workflow I am more used to, i.e. markdown to write and
> > then compilation -- through pandoc -- as LaTeX + biber + Biblatex. I
> > noticed that the filter supports the BibTeX "crossref" field (e.g. an
> > article published in a volume of Proceedings) but not the "related" fields,
> > such as "translationof", "multivolume" and the like. Is this feature
> > planned? This would be a great advantage for those who save data in BibTeX
> > format.
> > Thank you. The pandoc "constellation" is incredibly useful and truly smart.
> > guido (NW Italy)
> > --
> > 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/6a9af74f-d011-4733-a984-7c8f460ee41c%40googlegroups.com.
>
> --
>
> 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/m2pnl0icnm.fsf%40johnmacfarlane.net.


-- 
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/_YdyL8q3jBoJ-JMffharjdfWIMGA7ANVgMtHkCOOd7CneS3SPlY32aCAKl1VkkVLkrNoomKBp42dHQ3crkF5-OAsr330aQphFgdAvZ4j43k%3D%40protonmail.com.


  parent reply	other threads:[~2019-08-20  7:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 21:15 Guido Milanese
     [not found] ` <6a9af74f-d011-4733-a984-7c8f460ee41c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-08-20  6:17   ` John MacFarlane
     [not found]     ` <m2pnl0icnm.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-20  7:06       ` 'Nick Bart' via pandoc-discuss [this message]
2019-08-20  8:22         ` Guido Milanese
     [not found]           ` <CAFsD75Q1dfQT8X5Q9usctbf9rdUPzDdPPLaELUHB0Sk0yUqbpw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-20  9:54             ` Denis Maier

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='_YdyL8q3jBoJ-JMffharjdfWIMGA7ANVgMtHkCOOd7CneS3SPlY32aCAKl1VkkVLkrNoomKBp42dHQ3crkF5-OAsr330aQphFgdAvZ4j43k=@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).