emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Denis Maier <denismaier@mailbox.org>
Cc: org-mode-email <emacs-orgmode@gnu.org>,
	Bruce D'Arcus <bdarcus@gmail.com>
Subject: Re: [wip-cite-new] Initial implementation of `biblatex' citation processor
Date: Fri, 21 May 2021 15:38:04 +0200	[thread overview]
Message-ID: <877djsxl4z.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <609f486c-ec1a-ae89-8e39-f9c428d54738@mailbox.org> (Denis Maier's message of "Thu, 20 May 2021 23:51:42 +0200")

Hello,

Denis Maier <denismaier@mailbox.org> writes:

> Is there a way to use styles that aren't loaded via biblatex package
> options, but as distinct package. E.g., biblatex-chicago is loaded as 
> \usepackage{biblatex-chicago}. Internally, the package will then load
> biblatex on its own.

You can add a package with, e.g, 

  #+latex_header: \usepackage{biblatex-chicago}

but style is controlled through style, bibstyle or citestyle options
from "biblatex" package.

Hopefully, the solution suggested by Thomas S. Dye works. Otherwise, we
will need a different mechanism for managing styles. I though about
doing something like

  #+cite_export: biblatex  package:style

e.g.,

  #+cite_export: biblatex biblatex-chicago:author-date

which would insert

  \usepackage[style=author-date]{biblatex-chicago}

instead of

  \usepackage[style=biblatex-chicago:author-date]{biblatex}

in the preamble of the document.

But we cannot presume all packages will use "style=..." syntax. So…
hopefully, the suggested solution works.

Crossing fingers,
-- 
Nicolas Goaziou


  parent reply	other threads:[~2021-05-21 13:38 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 15:13 [wip-cite-new] Initial implementation of `biblatex' citation processor Nicolas Goaziou
2021-05-18 18:40 ` Bruce D'Arcus
2021-05-20  7:22   ` Rudolf Adamkovič
2021-05-20 10:38     ` Bruce D'Arcus
2021-05-19 10:03 ` Denis Maier
2021-05-19 10:43   ` Bruce D'Arcus
2021-05-19 12:33     ` Denis Maier
2021-05-19 13:44       ` Nicolas Goaziou
2021-05-19 13:50         ` Bruce D'Arcus
2021-05-19 14:31         ` Denis Maier
2021-05-19 14:46           ` Bruce D'Arcus
2021-05-19 15:23           ` Nicolas Goaziou
2021-05-20  8:04             ` Denis Maier
2021-05-20 10:36               ` Bruce D'Arcus
2021-05-20 11:56                 ` Bruce D'Arcus
2021-05-20 11:59                   ` Bruce D'Arcus
2021-05-20 13:24                   ` Denis Maier
2021-05-20 13:07                 ` Denis Maier
2021-05-20 13:22                   ` Bruce D'Arcus
2021-05-20 13:56                     ` Denis Maier
2021-05-20 14:11                       ` Bruce D'Arcus
2021-05-20 14:29                         ` Denis Maier
2021-05-20 15:14                           ` Bruce D'Arcus
2021-05-20 17:06                         ` Nicolas Goaziou
2021-05-20 21:51                           ` Denis Maier
2021-05-20 22:37                             ` Thomas S. Dye
2021-05-20 22:51                               ` Bruce D'Arcus
2021-05-21  0:07                                 ` Thomas S. Dye
2021-05-21 13:38                             ` Nicolas Goaziou [this message]
2021-05-20 13:08                 ` Denis Maier
2021-05-20 17:15               ` Nicolas Goaziou
2021-05-20 21:54                 ` Denis Maier
2021-05-21 13:29                   ` Nicolas Goaziou
2021-05-20 14:32             ` Denis Maier
2021-05-19 13:00 ` Denis Maier
2021-05-21 11:49 ` Bruce D'Arcus
2021-05-21 13:13   ` Nicolas Goaziou
2021-05-21 13:25     ` Bruce D'Arcus
2021-05-25 14:30       ` Bruce D'Arcus
2021-05-26 20:04         ` Nicolas Goaziou
2021-05-29 14:44 ` [org-cite, oc-csl] print_bibliography options Bruce D'Arcus
2021-05-29 15:15   ` Nicolas Goaziou
2021-05-29 16:03     ` Bruce D'Arcus
2021-05-29 16:30       ` Nicolas Goaziou
2021-05-31 18:10         ` András Simonyi
2021-05-31 21:54           ` 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=877djsxl4z.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=bdarcus@gmail.com \
    --cc=denismaier@mailbox.org \
    --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).