From: "András Simonyi" <andras.simonyi@gmail.com>
To: "Bruce D'Arcus" <bdarcus@gmail.com>,
"András Simonyi" <andras.simonyi@gmail.com>,
org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [wip-cite-new] Initial implementation of `csl' citation processor
Date: Mon, 31 May 2021 19:46:58 +0200 [thread overview]
Message-ID: <CAOWRwxCeArbX+fNhO8a99q=24QxKdixT7JGQ6NOUzSGGmd9Bvg@mail.gmail.com> (raw)
In-Reply-To: <87sg25zf0z.fsf@nicolasgoaziou.fr>
Dear All,
On Sat, 29 May 2021 at 18:22, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Here's another proposal:
>
> `org-cite-export-processor' is now an alist, where keys are export
> back-ends or t, which is the default key.
>
> '((latex biblatex bibstyle citestyle)
> (beamer natbib nil nil)
> (my-latex natbib bibstyle)
> (t csl nil nil))
> The selected processor is the one associated to the back-ends closest to
> the current one used for export, by `org-export-derived-backend-p'
> order. So if `my-other-latex' is derived from beamer, it will use
> (natbib nil nil).
This looks perfect.
> OTOH, I suggest to stick to a single "cite_export" keyword, which
> overrides any selected processor above. IOW
>
> #+cite_export: basic
>
> will use basic whatever the current export back-end is.
>
> In practice, I think it is sufficient. The only case where it may be
> limiting is if you need to export with two different back-ends with two
> processors different from those set in `org-cite-export-processor'. But
> in that situation, I think swapping the cite_export keyword is
> acceptable.
>
> So overall, I think it is a good compromise between simplicity and
> power.
> WDYT?
I agree, can be revisited later if necessary, but seems to be a very
strong starting point -- thanks.
best regards,
András
next prev parent reply other threads:[~2021-05-31 17:50 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 [this message]
2021-06-05 17:16 ` Nicolas Goaziou
2021-05-29 7:51 ` Stefan Nobis
2021-05-29 14:08 ` Bruce D'Arcus
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOWRwxCeArbX+fNhO8a99q=24QxKdixT7JGQ6NOUzSGGmd9Bvg@mail.gmail.com' \
--to=andras.simonyi@gmail.com \
--cc=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).