From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: oc-biblatex too aggressive in replacing styles
Date: Sun, 28 Nov 2021 12:19:58 -0500 [thread overview]
Message-ID: <CAF-FPGPB39MyJy8ynQYfr1nbPXh5A1Hoa7DhVZe-wgGDXxwyYA@mail.gmail.com> (raw)
In-Reply-To: <87r1b0usd6.fsf@gmx.us>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
On Sun, Nov 28, 2021, 12:04 PM Rasmus <rasmus@gmx.us> wrote:
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?
I raised a similar question awhile back, and am not sure the best approach.
But to give some context:
The current styles in the core processors are designed for portability;
they are not natbib or biblatex or CSL styles, but org styles that can be
mapped to those targets in more-or-less consistent ways.
This is tricky to do, in part because of inconsistencies; in particular
between natbib and biblatex.
Which is to say, in some cases the style mappings might be enhanced or
modified.
But I agree there should be some kind to fallback, in particular for
biblatex, which has an insane amount of commands.
Bruce
[-- Attachment #2: Type: text/html, Size: 1668 bytes --]
next prev parent reply other threads:[~2021-11-28 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 17:01 oc-biblatex too aggressive in replacing styles Rasmus
2021-11-28 17:19 ` Bruce D'Arcus [this message]
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=CAF-FPGPB39MyJy8ynQYfr1nbPXh5A1Hoa7DhVZe-wgGDXxwyYA@mail.gmail.com \
--to=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).