emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: "Bruce D'Arcus" <bdarcus@gmail.com>,
	John Kitchin <jkitchin@andrew.cmu.edu>,
	org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: org-cite citation commands
Date: Sat, 17 Jul 2021 10:44:41 -0400	[thread overview]
Message-ID: <CAF-FPGN_=CCg9YRN4MWJHcrkWPaKzNkZw9UX3AttgPZTP3WhSA@mail.gmail.com> (raw)
In-Reply-To: <20210717141605.2p6ja5awfm3qqda4@dalkati>

On Sat, Jul 17, 2021 at 10:20 AM Vikas Rawal <vikasrawal@gmail.com> wrote:

> Thanks, Bruce and John. Indeed, I used biblatex with natbib=true
> option, which gives me citet and citep in biblatex. But using
> \autocite and \textcite is perfect.
> I am noticing a few other issues at this stage.
> I have a large biblatex database, and loading it using C-c C-x @ to
> insert citations seems very slow (have not managed to load it thus
> far). Org-ref used to be much faster in this. org-cite works fine with
> a smaller biblatex database. I don't know if others have had the same
> experience.

Give this a try:


I hope to see similar "insert processors" for ivy-bibtex and helm-bibtex.

Bottomline, it's trivial to replace that "basic" processor with much
better options.

See discussion on:


> I understand that oc-biblatex.el loads biblatex in the background,
> produces the citations and the bibliography, and inserts them in the
> exported output. In that case, what are the possibilities of using
> biblatex commands to configure the output?

To be precise, you mean what are the options to configure the
oc-biblatex export processor to use different or additional commands?

ATM, I don't believe there are any, and the alternative is to write
your own export processor, say basing it off the oc-biblatex one.

What, specifically, do you need, that is not currently supported?

The current processors are pretty comprehensive; see the note from Andras.

When designing this sort of thing, you basically have a choice.

You can just have styles that map directly to the output targets.

This has an obvious advantage if you only ever use one target.

But it has a major disadvantage if you want to use others.

So the approach we took here is to design a common set of styles and
substyles, and then map to output formats from there.

The result is the citations are more-or-less export format agnostic.

> I realise that these will
> not work since most of it would be LaTeX specific. Does that mean the
> users will have to work with CSL styles to format the output even if
> they are using oc-biblatex.el? I am still somewhat confused about how
> this is going to work.

CSL styles are analogous to BST files in bibtex; you use those with oc-csl.

When using that, citeproc-el handles the output processing, including for latex.

Basically, if you want consistent output formatting across latex and
other targets like HTML or OpenDocument, you want to use oc-csl.

Give it a try.

Note, though, that citeproc-el does not currently support cite/t or
some others, but that should be coming "soon".

HTH; let me know if anything is unclear.


  reply	other threads:[~2021-07-17 14:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-17 11:35 org-cite citation commands Vikas Rawal
2021-07-17 12:37 ` John Kitchin
2021-07-17 12:47   ` Bruce D'Arcus
2021-07-17 14:16     ` Vikas Rawal
2021-07-17 14:44       ` Bruce D'Arcus [this message]
2021-07-17 20:52         ` John Kitchin
2021-07-18  4:05           ` Vikas Rawal
2021-07-18 16:37             ` Bruce D'Arcus
2021-07-17 12:39 ` Bruce D'Arcus
2021-07-17 13:55 ` András Simonyi
2021-07-17 14:44   ` Vikas Rawal

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='CAF-FPGN_=CCg9YRN4MWJHcrkWPaKzNkZw9UX3AttgPZTP3WhSA@mail.gmail.com' \
    --to=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jkitchin@andrew.cmu.edu \


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