Dear All, On Sat, 29 May 2021 at 18:22, Nicolas Goaziou <m...@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
