From: Nicolas Goaziou <email@example.com> To: "Bruce D'Arcus" <firstname.lastname@example.org> Cc: org-mode-email <email@example.com>, "András Simonyi" <firstname.lastname@example.org> Subject: Re: [wip-cite-new] Initial implementation of `csl' citation processor Date: Sat, 29 May 2021 18:22:04 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CAF-FPGN-wHv_vy=4UbH089DK=0p8VTMBu70ke02SkQOwELdPTA@mail.gmail.com> (Bruce D'Arcus's message of "Sat, 29 May 2021 09:52:34 -0400") Hello, "Bruce D'Arcus" <firstname.lastname@example.org> writes: > On Fri, May 28, 2021 at 4:31 PM András Simonyi <email@example.com> wrote: > >> 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? > > This would go a long way, and is probably all that's necessary. > > Really "latex" is the unique output mode here. But one may want to use a different processor for, say, beamer and regular latex. Both are "latex" based. Worse, all custom back-ends derived from "latex" are bound to use the same processor. 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). 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? Regards, -- Nicolas Goaziou
next prev parent reply other threads:[~2021-05-29 16:22 UTC|newest] Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-26 20:33 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 [this message] 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
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [wip-cite-new] Initial implementation of `csl'\'' citation processor' \ /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
Code repositories for project(s) associated with this 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).