From: "András Simonyi" <firstname.lastname@example.org>
To: "Bruce D'Arcus" <email@example.com>,
Subject: Re: [wip-cite-new] Initial implementation of `csl' citation processor
Date: Fri, 28 May 2021 22:31:03 +0200 [thread overview]
Message-ID: <CAOWRwxCCKAixRet4PNhyyGToCFtGY3x23KV7QVPNM1xKcPy8EA@mail.gmail.com> (raw)
I'm trying to catch up with the new developments, it isn't easy :-).
I think it would be really helpful to be able to map different
backends to different processors, because latex based solutions like
natbib can handle only latex-based backends, so anybody who wanted to
export both to latex (with a latex citation processor) and something
else would need to constantly change the used citation processor.
Maybe instead of a full alist mapping backends to citation processors
we could have only options to declare a separate processor for
latex-based backends and another for non-latex ones?
On Fri, 28 May 2021 at 21:41, Nicolas Goaziou <firstname.lastname@example.org> wrote:
> "Bruce D'Arcus" <email@example.com> writes:
> > On Fri, May 28, 2021 at 1:54 PM Timothy <firstname.lastname@example.org> wrote:
> >> Nicolas Goaziou <email@example.com> writes:
> >> > I wouldn't hold my breath.
> >> >
> >> > First, IIUC, there's no reason to force biblatex over natbib OOTB as
> >> > both are widely in use. But, more importantly, "oc-csl" require the
> >> > external Citeproc library, so it cannot be loaded by default. As
> >> > a consequence, no default configuration can use it.
> >> If you don't mind some follow-up questions.
> >> + I take it that natbib is used by default for LaTeX then? Is it fairly
> >> easy for the user to switch to biblatex?
> >> + With citeproc, I don't suppose something could be put behind a
> >> (featurep) switch to use oc-csl if citeproc is available, and fall
> >> back gracefully otherwise?
> > Not sure about generally (Nicolas can comment on that), but in this
> > case, if you specify this:
> > #+cite_export: natbib
> > ... the export process runs through that processor, even if you are
> > outputting to plain text or HTML, where natbib is not supported.
> By default, no export processor is selected. All citations are removed
> from output, and print_bibliography keywords, ignored.
> You have to actively select what processor you want for the document,
> globally, through a variable, or with a cite_export keyword. Therefore,
> the processor does not depend on the back-end used; you are supposed to
> choose the one you think to be appropriate. There is no falling back
> either. You get what you asked for. That's the way.
> It could be possible to change `org-cite-export-processor' so it becomes
> an alist where you can associate back-ends to processors. But I can't
> see how to transpose it nicely to cite_export keyword.
> I'm not convinced this would be an improvement either. For example, you
> may want to use two different processors with the same back-end.
next prev parent reply other threads:[~2021-05-28 20:32 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
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 [this message]
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).