From: "Bruce D'Arcus" <email@example.com>
To: org-mode-email <firstname.lastname@example.org>
Subject: Re: [wip-cite-new] Initial implementation of `csl' citation processor
Date: Sat, 29 May 2021 10:08:47 -0400 [thread overview]
Message-ID: <CAF-FPGM9S906pWYAF13cz9=oVSHFzed8R4Y1bjnrdvCqgRu_eg@mail.gmail.com> (raw)
On Sat, May 29, 2021 at 3:51 AM Stefan Nobis <email@example.com> wrote:
> Nicolas Goaziou <firstname.lastname@example.org> writes:
> > By default, no export processor is selected. All citations are
> > removed from output, and print_bibliography keywords, ignored.
> As I'm coming from LaTeX and have been bitten more than once by
> missing citations in the output (which is solved far better today by
> biblatex), I would say this is not a very good default.
> Citations should never be removed (or only with quite some effort). If
> you publish a text where citations have been removed by accident,
> that's asking for much trouble.
> Therefore I would suggest to set some sensible default that at least
> does not remove citations. For example a simple ASCII export with
> number or author-year style could be the default citation export for
> all back-ends. For quite some users (e.g. non-academic, internal
> white-papers etc.) this may be also a "good enough" solution, so they
> get easy citation support OOTB.
> Everyone else would choose some more sophisticated back-end.
> > 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.
> What about "cite_export" for a single/default export engine and
> "cite_export_<backend>" (with "<backend>" something like "html",
> "latex", "md", etc.) for overriding the citation exporter for the
> given back-end, e.g.
> cite_export ascii
> cite_export_latex biblatex chicago
> cite_export_html csl "some style"
> (I forgot about the correct syntax for cite_export, so just a really
> rough sketch to illustrate the idea).
> Would that be feasible?
This is similar to what Andras was suggesting, though his suggestion
is even simpler, because it would only have one for latex; so just
default and latex.
I think that's all we need.
> > 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.
> I'm not sure if this is true for many back-ends. Currently, I would
> assume that this is only the case for the LaTeX back-end (e.g.
> preparing a paper for different journals with different citations
> requirements). But in this case LaTeX has already quite some tools
> that could be utilized. All the different kinds of citation commands
> are there to be able to easily switch styles for the whole document
> (within a single back-end).
To review, for people that may not be that familiar with CSL, in particular.
LaTeX does all that, with the major limitation that it doesn't do
HTML, docx, rtf, etc.
CSL with citeproc-el does LaTeX (completely bypassing
bibtex/biblatex), and plain text and HTML, and implementations like
pandoc, also do docs, rtf, etc.
So even LaTeX users would likely still want to have oc-csl as their
default processor, for when they want to export to HTML or plain text.
Some, or even many, LaTeX users would prefer to use oc-natib or
oc-biblatex for primary latex export though.
I'm not convinced it's necessary or useful to separately configure for
plain text vs HTML.
prev parent reply other threads:[~2021-05-29 14:09 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
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 [this message]
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).