From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Thomas S. Dye" <tsd@tsdye.online>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: oc-biblatex and biblatex substyles
Date: Sun, 12 Dec 2021 16:25:48 +0100 [thread overview]
Message-ID: <8735mxn8ub.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87k0gctp25.fsf@tsdye.online> (Thomas S. Dye's message of "Fri, 10 Dec 2021 06:14:26 -1000")
Hello,
"Thomas S. Dye" <tsd@tsdye.online> writes:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Another possibility it to write, e.g., "oc-biblatex-chicago.el" and
>> define a new ‘biblatex-chicago’ export processor, re-using most
>> functions from "oc-biblatex.el". It would probably only be necessary
>> to
>> re-define ‘org-cite-biblatex-export-citation’ and
>> ‘org-cite-biblatex-prepare-preamble’.
>>
> This is probably the path of least resistance for users who want to use biblatex-chicago out of the box, rather than as a basis for deriving a specific style.
I can write a biblatex-chicago citation processor. However, it would
help me tremendously if someone could map styles/variants to LaTeX
commands when using this package.
See for example `org-cite-biblatex-styles' in main branch.
Any volunteer?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2021-12-12 15:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-28 17:11 oc-biblatex and biblatex substyles Rasmus
2021-12-10 9:54 ` Nicolas Goaziou
2021-12-10 16:14 ` Thomas S. Dye
2021-12-12 15:25 ` Nicolas Goaziou [this message]
2021-12-12 18:37 ` Thomas S. Dye
2021-12-12 18:46 ` Nicolas Goaziou
2021-12-12 19:15 ` Thomas S. Dye
2021-12-12 20:31 ` Nicolas Goaziou
2021-12-12 21:40 ` Thomas S. Dye
2022-01-06 21:26 ` Rasmus
2022-01-06 21:45 ` Rasmus
2022-01-06 21:46 ` Rasmus
2022-01-06 22:17 ` Thomas S. Dye
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=8735mxn8ub.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
--cc=tsd@tsdye.online \
/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).