emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Grant Rettke <gcr@wisdomandwonder.com>
Cc: Fabrice Popineau <fabrice.popineau@supelec.fr>,
	"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
	Eric Schulte <schulte.eric@gmail.com>,
	John Kitchin <jkitchin@andrew.cmu.edu>
Subject: Re: org-ref in action
Date: Thu, 26 Jun 2014 09:39:22 -0500	[thread overview]
Message-ID: <8761jnu44l.fsf@fastmail.fm> (raw)
In-Reply-To: <CAAjq1md25eG-UGjbw0U0XntOv44JWDK6t+6__DCKdxU68fTPkw@mail.gmail.com> (Grant Rettke's message of "Thu, 26 Jun 2014 09:11:32 -0500")

Grant Rettke <gcr@wisdomandwonder.com> writes:

> On Thu, Jun 26, 2014 at 9:08 AM, Matt Lundin <mdl@imapmail.org> wrote:
>> I think the key in any possible feature merge is to remember citation
>> management is idiosyncratic.
>
> Off topic:
>
> How do people choose today?
>
> Why choose bibtex over biblatex?

Thanks to inertia, bibtex still has a number of users in the sciences,
since it was originally designed for scientific citations. In the
humanities, however, bibtex is a non-starter, since biblatex offers much
more flexibility. The good news is that bibtex and biblatex use the same
database format, so it's easy to transition from bibtex to biblatex.
However, there are other options, such as CSL.[1]

> Where do people discuss such questions like this in real life?

I'm not sure I understand your question. Could you clarify?

I simply meant that everyone will have a different workflow/system for
storing and managing citations. E.g., some will prefer to store
bibliographical data in a zotero database, others in a single bib file,
others in multiple bib files, others as properties in org headlines,
etc.

I think one can make a conception distinction here between citation
management (i.e., how one stores bibliographical data) and citation
processing (i.e., the software one uses to export that data to some
output format). There are many, many formats (mods, bib, etc.) and tools
(biber, bibtex, csl/citeproc, etc.) for formatting bibliographical data.

In an ideal world, one should be able to 1) process bibliographical data
from multiple formats; 2) choose from hundreds of citation styles; and
3) format citations for multiple backends. I am not suggesting that
org-mode should directly support all these things, but its default
methods of handling citations should not get in the way of using
external tools that provide such flexibility.

For instance, pandoc (an immensely impressive piece of software!)
accepts bibliographical data from numerous sources and processes it for
multiple outputs (html, plain text, docx, rtf, etc.). By contrast,
ox-bibtex.el runs citations through bibtex2html, which is pretty much
limited to the "old-fashioned" bibtex formats. Ironically, ox-bibtex.el
invokes pandoc to convert from html to plain text, but only after it has
already used bibtex2html to process the data.

Best,
Matt

Footnotes:

[1] Citation Style Language - http://citationstyles.org/

  parent reply	other threads:[~2014-06-26 14:39 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24 18:45 org-ref in action John Kitchin
2014-06-24 19:26 ` Thomas S. Dye
2014-06-24 20:53 ` Ista Zahn
2014-06-25  2:13 ` Matt Lundin
2014-06-25  8:28 ` Bastien
2014-06-25 16:26 ` Vikas Rawal
2014-06-25 20:25 ` Eric Schulte
2014-06-26  1:09   ` Grant Rettke
2014-06-26  1:10   ` Matt Lundin
2014-06-26 12:21     ` Fabrice Popineau
2014-06-26 12:48       ` John Kitchin
2014-06-26 14:08         ` Matt Lundin
2014-06-26 14:09           ` Matt Lundin
2014-06-26 14:11           ` Grant Rettke
2014-06-26 14:13             ` Ken Mankoff
2014-06-26 14:33             ` Jorge A. Alfaro-Murillo
2014-06-26 14:39             ` Matt Lundin [this message]
2014-06-26 17:19               ` Alan Schmitt
2014-06-26 18:44                 ` Matt Lundin
2014-06-27  4:27                   ` Xebar Saram
2014-06-27  7:37                     ` Thomas S. Dye
2014-06-27  7:38                     ` Vikas Rawal
2014-06-27  7:52                       ` Melleus
2014-06-27 13:39                     ` Ista Zahn
2014-06-27 23:56                     ` John Kitchin
2014-06-27  6:44                   ` Alan Schmitt
2014-06-27 14:26                     ` Matt Lundin
2014-06-27 17:19                       ` Matt Lundin
2014-06-27 15:49               ` Grant Rettke
2014-06-26 16:14         ` Eric Schulte
2014-06-27  6:55         ` Joseph Vidal-Rosset
2014-06-29 10:18 ` Joseph Vidal-Rosset
2014-06-29 12:09   ` John Kitchin
2014-06-29 18:19   ` Eric Schulte
2014-06-29 18:23     ` Joseph Vidal-Rosset
2014-06-30  9:29     ` Joseph Vidal-Rosset
2014-06-30  9:52       ` Eric Schulte
2014-06-30 10:06         ` Joseph Vidal-Rosset
2014-06-30 10:22           ` Eric Schulte
2014-06-30 11:27             ` Joseph Vidal-Rosset
2014-08-05 18:28               ` Xebar Saram
2014-08-05 21:08                 ` John Kitchin
2014-08-06 10:54                   ` Xebar Saram
2014-08-06 12:51                     ` John Kitchin
  -- strict thread matches above, loose matches on Subject: below --
2014-06-25  5:57 Leu Zhe
2014-06-26 22:33 Doyley, Marvin M.

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=8761jnu44l.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=fabrice.popineau@supelec.fr \
    --cc=gcr@wisdomandwonder.com \
    --cc=jkitchin@andrew.cmu.edu \
    --cc=schulte.eric@gmail.com \
    /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).