From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Using citeproc-js instead of pandoc-citeproc
Date: Thu, 9 Nov 2017 23:34:53 -0500 [thread overview]
Message-ID: <20171110043453.GF70590@MacBook-Air-2.local> (raw)
In-Reply-To: <9bc33c56-9656-40f8-9bbf-4d01a2b43aae-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
You can report issues to jgm/pandoc-citeproc's bug tracker.
We will try to fix them.
+++ Denis Maier [Nov 09 17 00:50 ]:
> Ok, I understand.
> The reason for my question was that there are still some cases where
> pandoc-citeproc does not sticks to csl-rules
> (e.g. https://github.com/jgm/pandoc-citeproc/issues/79). And I thought
> it might be easier to use citeproc-js, which should be fully
> csl-compliant. But, if I understand your answer correctly, this will
> only lead to other problems.
> Am Samstag, 28. Oktober 2017 00:22:50 UTC+2 schrieb John MacFarlane:
>
> Several reasons:
> 1. citeproc-js would be an external dependency that users would
> have to install. pandoc-citeproc is a Haskell library we
> can just compile in.
> 2. pandoc would have to shell out to call citeproc-js
> (which, earlier, didn't even have a way to call it as a
> standalone program)
> 3. pandoc-citeproc works with native pandoc types.
> With citeproc-js, we'd have to convert to citeproc JSON,
> and then convert back.
> 4. pandoc-citeproc handles math better (because it was
> designed to work with pandoc's math support).
> +++ Denis Maier [Oct 27 17 06:55 ]:
> > I was wondering why pandoc does not use citeproc-js but its own
> > pandoc-citeproc. As far I understand citeproc-js is the
> canonical
> > csl-implementation, and, as such, fully compliant with the
> > csl-specification.
>
> --
> 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 [1]pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To post to this group, send email to
> [2]pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> [3]https://groups.google.com/d/msgid/pandoc-discuss/9bc33c56-9656-40f8-
> 9bbf-4d01a2b43aae%40googlegroups.com.
> For more options, visit [4]https://groups.google.com/d/optout.
>
>References
>
> 1. mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 2. mailto:pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> 3. https://groups.google.com/d/msgid/pandoc-discuss/9bc33c56-9656-40f8-9bbf-4d01a2b43aae-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org?utm_medium=email&utm_source=footer
> 4. https://groups.google.com/d/optout
prev parent reply other threads:[~2017-11-10 4:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 13:55 Denis Maier
[not found] ` <5fb0a253-1e36-4124-aad1-e1618c535456-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-10-27 22:23 ` John MACFARLANE
2017-11-09 8:50 ` Denis Maier
[not found] ` <9bc33c56-9656-40f8-9bbf-4d01a2b43aae-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-11-10 4:34 ` John MacFarlane [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=20171110043453.GF70590@MacBook-Air-2.local \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).