public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Guido Milanese <guido.milanese-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: citeproc and "related" field
Date: Tue, 20 Aug 2019 10:22:42 +0200	[thread overview]
Message-ID: <CAFsD75Q1dfQT8X5Q9usctbf9rdUPzDdPPLaELUHB0Sk0yUqbpw@mail.gmail.com> (raw)
In-Reply-To: <_YdyL8q3jBoJ-JMffharjdfWIMGA7ANVgMtHkCOOd7CneS3SPlY32aCAKl1VkkVLkrNoomKBp42dHQ3crkF5-OAsr330aQphFgdAvZ4j43k=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 5104 bytes --]

Thank you. Indeed, the CSL variables for translation/reprint and the like
are the same of the old BibTeX files, now deprecated by the Biblatex
format. This new  format is much more practical, but I agree that a
conversion would be a bit heavy. A sort of pre-filter should read the
related entry, extract the needed data (e.g. title), add data with a new
label (e.g.  original-title), and reshape the cited item. Not difficult,
but a bit cumbersome. Do you think that a proposal would be worth
submitting?

Il giorno mar 20 ago 2019 alle ore 09:06 'Nick Bart' via pandoc-discuss <
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> ha scritto:

> 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 a topic in the
> Google Groups "pandoc-discuss" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/pandoc-discuss/gcv2qSIRn0c/unsubscribe.
> To unsubscribe from this group and all its topics, 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
> .
>


-- 
Guido Milanese - Professor of Classics - Docteur H.C. Paris ICP
Universita' Cattolica d.S.C., Milano - Brescia
http://docenti.unicatt.it/ita/guido_fabrizio_milanese
<http://www.arsantiqua.org>

-- 
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/CAFsD75Q1dfQT8X5Q9usctbf9rdUPzDdPPLaELUHB0Sk0yUqbpw%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 7622 bytes --]

  reply	other threads:[~2019-08-20  8:22 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
2019-08-20  8:22         ` Guido Milanese [this message]
     [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=CAFsD75Q1dfQT8X5Q9usctbf9rdUPzDdPPLaELUHB0Sk0yUqbpw@mail.gmail.com \
    --to=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).