emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Bruce D'Arcus" <bdarcus@gmail.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [org-cite] add convention for direct commands, process for adding mappings to export processor(s)?
Date: Sun, 10 Oct 2021 22:41:10 +0200	[thread overview]
Message-ID: <87czoctxy1.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAF-FPGMWHyWe7Pb9v0nLVHdCTQW-oxvKyUg0vmxQqZFLk1VX=g@mail.gmail.com> (Bruce D'Arcus's message of "Sun, 10 Oct 2021 10:28:10 -0400")


"Bruce D'Arcus" <bdarcus@gmail.com> writes:

>> The current list of styles and variants included in the oc export
>> processors was a first step, with a goal to provide a solid starting
>> point, and citations that are more-or-less portable across the
>> backends.
>> But that raises an obvious question: what next?

Are we at next already?

>> I'd like, for example, to suggest adding "noauthor/bare" -> "cite*" to
>> oc-biblatex.


>> I also think we should add a way for users to use a direct command for
>> natbib and biblatex.


>> Perhaps some prefix for a style that signals to pass on directly for a
>> specific export processor; like [cite/blx+footcite ...].

I'm not too keen on extending the citation syntax.

>> In that case, the oc-biblatex processor would pass that command on as
>> is, but other processors would ignore it, and use the default
>> instead.

This is the point of styles. We could allow custom ones.

>> And if we were to add this, we'd still need to answer my first
>> question: when and how to add specific style/variant mappings to the
>> oc processors.

It is possible to send a patch if it is something useful. Some
processors (probably only biblatex at this point, we probably cover
everything in natbib) may also introduce a customizable variable for
user-defined styles.

Nicolas Goaziou

  reply	other threads:[~2021-10-10 20:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 18:37 Bruce D'Arcus
2021-10-10 14:28 ` Bruce D'Arcus
2021-10-10 20:41   ` Nicolas Goaziou [this message]
2021-10-10 20:56     ` 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:

  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=87czoctxy1.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).