public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Guido Milanese
	<guido.milanese-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: citeproc and "related" field
Date: Mon, 19 Aug 2019 23:17:17 -0700	[thread overview]
Message-ID: <m2pnl0icnm.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <6a9af74f-d011-4733-a984-7c8f460ee41c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


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.


  parent reply	other threads:[~2019-08-20  6:17 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 [this message]
     [not found]     ` <m2pnl0icnm.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-08-20  7:06       ` 'Nick Bart' via pandoc-discuss
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=m2pnl0icnm.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=guido.milanese-Re5JQEeQqe8AvxtiuMwx3w@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).