From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: oc-biblatex too aggressive in replacing styles
Date: Sun, 28 Nov 2021 18:01:25 +0100 [thread overview]
Message-ID: <87r1b0usd6.fsf@gmx.us> (raw)
Hi,
Thanks for providing ox-biblatex.
It works very well and has replaced my local hacks for LaTeX
bibliographies.
However, I think it is currently too aggressive in overwriting styles.
Could it perhaps accept any style that is given in
‘org-cite-biblatex-options’ / ‘org-latex-packages-alist’ and only
overwrite it if another style is explicitly specified in the file to be
exported?
A bit like how ox-koma-letter looks for in-buffer changed values.
Currently, the only way I have found that I can specify that I want to use
biblatex-chicago is by issuing
#+cite_export: biblatex chicago-authordate
But this is a bit blunt as it overrules ‘org-cite-export-processors’ and
thus biblatex is used for e.g. text export (of course I can replicate
org-cite-export-processors with a macro that looks at the current export
backend).
(If you want I am happy to try to work on this)
Thanks,
Rasmus
Example:
See [cite/t:@OrgCitations]
#+bibliography: lit.bib
# only way to "actuallyhicago:
#+cite_export: biblatex chicago-authordate
* settings :noexport:
#+begin_src emacs-lisp
(require 'oc-biblatex)
;; test 1: style is gobbled
;; (setq org-cite-biblatex-options "style=chicago-authordate, maxcitenames=2")
;; test 2: style is gobbled
;; (setq org-latex-packages-alist '(("style=chicago-authordate, maxcitenames=2" "biblatex")))
;; test 3: biblatex and biblatex-chicago are both loaded
;; (setq org-latex-packages-alist '(("authordate" "biblatex-chicago")))
#+end_src
--
9000!
next reply other threads:[~2021-11-28 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 17:01 Rasmus [this message]
2021-11-28 17:19 ` oc-biblatex too aggressive in replacing styles Bruce D'Arcus
2021-11-28 17:38 ` Bruce D'Arcus
2021-11-28 17:48 ` Rasmus
2021-11-28 18:10 ` Nicolas Goaziou
2021-11-30 19:43 ` Rasmus
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=87r1b0usd6.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).