* [org-cite] add convention for direct commands, process for adding mappings to export processor(s)?
@ 2021-09-09 18:37 Bruce D'Arcus
0 siblings, 0 replies; only message in thread
From: Bruce D'Arcus @ 2021-09-09 18:37 UTC (permalink / raw)
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
But that raises an obvious question: what next?
I'd like, for example, to suggest adding "noauthor/bare" -> "cite*" to
I also think we should add a way for users to use a direct command for
natbib and biblatex.
As I've looked into some of what I'd call corner cases, consistency
breaks down a bit, so it may not be advisable to add explicit support
for certain options, since they won't work across different backends
Perhaps some prefix for a style that signals to pass on directly for a
specific export processor; like [cite/blx+footcite ...].
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.
The documentation would just need to emphasize use of such commands
would necessarily tie those citations to the specific export backend.
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-09-09 18:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-09-09 18:37 [org-cite] add convention for direct commands, process for adding mappings to export processor(s)? Bruce D'Arcus
Code repositories for project(s) associated with this 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 NNTP newsgroup(s).