From: "Bruce D'Arcus" <email@example.com>
To: "Org Mode List" <firstname.lastname@example.org>,
"András Simonyi" <email@example.com>
Subject: Re: [wip-cite-new] Initial implementation of `csl' citation processor
Date: Wed, 26 May 2021 17:11:58 -0400 [thread overview]
Message-ID: <CAF-FPGPKYojRS7qTXgjABnDnvQYAU9H=R7VsuHvOmPGbLYohoA@mail.gmail.com> (raw)
I'll take a close look at this and test it over the coming days, but
in the meantime, on two more general points:
On Wed, May 26, 2021 at 4:39 PM Nicolas Goaziou <firstname.lastname@example.org> wrote:
> I called it `csl' instead of `citeproc'. It is a bit ambiguous, but it
> is shorter, and "org-cite-csl" prefix sounds less redudant than
> "org-cite-citeproc...". But I know this is a weak argument, so if you think "citeproc"
> is still more appropriate, I can revisit this.
From my perspective, that's totally fine, and arguably better: csl
export processor for citeproc library.
The citeproc name is just a convention for the processors that's
developed over time I think mostly because people couldn't be bothered
to come up with better names. I actually wrote the very first one, in
XSLT, called citeproc-xsl.
I think CSL would be more widely known among users though.
And this processor doesn't actually do the formatting, so it makes sense.
> Also, I don't expect a different CSL-based citation processor any time soon, so it should be fine.
Well, I'll ask you the same question I asked Andras recently:
What if a developer has the idea to hook up one of the new, very fast,
csl libraries: either the haskell version associated with pandoc, or
the rust-based version associated with Zotero?
Possible reasons they might want to do that: performance and/or
Could you make sure this module is coded in such a way that it should
be relatively straightforward to do that?
next prev parent reply other threads:[~2021-05-26 21:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 20:33 [wip-cite-new] Initial implementation of `csl' citation processor Nicolas Goaziou
2021-05-26 21:11 ` Bruce D'Arcus [this message]
2021-05-26 22:07 ` Nicolas Goaziou
2021-05-27 0:47 ` Bruce D'Arcus
2021-05-27 1:58 ` Bruce D'Arcus
2021-05-27 8:01 ` Denis Maier
2021-05-27 12:45 ` Bruce D'Arcus
2021-05-27 13:12 ` Nicolas Goaziou
2021-05-27 14:18 ` Bruce D'Arcus
2021-05-27 14:34 ` Bruce D'Arcus
2021-05-27 15:02 ` Bruce D'Arcus
2021-05-27 16:13 ` Bruce D'Arcus
2021-05-27 17:49 ` Matt Price
2021-05-28 13:05 ` Bruce D'Arcus
2021-05-28 13:52 ` Nicolas Goaziou
2021-05-28 21:37 ` Bruce D'Arcus
2021-05-29 16:34 ` Nicolas Goaziou
2021-05-29 17:25 ` Bruce D'Arcus
2021-05-29 17:56 ` Bruce D'Arcus
2021-05-29 20:07 ` Nicolas Goaziou
2021-05-27 12:59 ` Nicolas Goaziou
2021-05-27 9:15 ` Denis Maier
2021-05-27 12:24 ` Nicolas Goaziou
2021-05-27 12:59 ` Bruce D'Arcus
2021-05-28 15:54 ` Nicolas Goaziou
2021-05-28 16:13 ` Bruce D'Arcus
2021-05-28 16:14 ` Timothy
2021-05-28 17:11 ` Nicolas Goaziou
2021-05-28 17:32 ` Timothy
2021-05-28 17:38 ` Nicolas Goaziou
2021-05-28 17:54 ` Timothy
2021-05-28 18:26 ` Bruce D'Arcus
2021-05-28 19:40 ` Nicolas Goaziou
2021-05-28 20:31 ` András Simonyi
2021-05-29 13:52 ` Bruce D'Arcus
2021-05-29 16:22 ` Nicolas Goaziou
2021-05-30 13:17 ` Bruce D'Arcus
2021-05-30 20:20 ` Nicolas Goaziou
2021-05-31 23:44 ` Bruce D'Arcus
2021-05-31 17:46 ` András Simonyi
2021-06-05 17:16 ` Nicolas Goaziou
2021-05-29 7:51 ` Stefan Nobis
2021-05-29 14:08 ` Bruce D'Arcus
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).