From: "Bruce D'Arcus" <firstname.lastname@example.org> To: org-mode-email <email@example.com> Subject: Re: [org-cite] add convention for direct commands, process for adding mappings to export processor(s)? Date: Sun, 10 Oct 2021 10:28:10 -0400 [thread overview] Message-ID: <CAF-FPGMWHyWe7Pb9v0nLVHdCTQW-oxvKyUg0vmxQqZFLk1VXfirstname.lastname@example.org> (raw) In-Reply-To: <CAF-FPGNWhACCNrJOU-Q5QtaLEEcOz0=AXTwv47rFNrud09+CWA@mail.gmail.com> Just bumping this. Nicolas, in particular, any thoughts? On Thu, Sep 9, 2021 at 2:37 PM Bruce D'Arcus <email@example.com> wrote: > > 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? > > 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. > > 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 > anyway. > > 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 > oc processors. > > Thoughts? > > Bruce
next prev parent reply other threads:[~2021-10-10 14:29 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 [this message] 2021-10-10 20:41 ` Nicolas Goaziou 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: 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-FPGMWHyWe7Pb9v0nLVHdCTQW-oxvKyUg0vmxQqZFLk1VXfirstname.lastname@example.org' \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [org-cite] add convention for direct commands, process for adding mappings to export processor(s)?' \ /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
Code repositories for project(s) associated with this 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).