emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: Richard Lawrence <richard.lawrence@berkeley.edu>
Cc: emacs-orgmode@gnu.org, Marcin Borkowski <mbork@wmi.amu.edu.pl>
Subject: Re: Biblatex and Org [was: [OT] Don't use BibTeX!]
Date: Sun, 06 Apr 2014 22:34:11 -1000	[thread overview]
Message-ID: <m21tx9h724.fsf@tsdye.com> (raw)
In-Reply-To: <87k3b1iyrg.fsf@berkeley.edu> (Richard Lawrence's message of "Sun, 06 Apr 2014 20:50:27 -0700")

Aloha Richard,

I think you'll be fine with org-bibtex and biblatex.

Richard Lawrence <richard.lawrence@berkeley.edu> writes:

> So it looks like switching to biblatex is just a matter of changing my
> compilation process and the bibliography commands in my documents.  Does
> that sound right?

Here is a description of using bibtex and biblatex with the old
exporter that should still be useful:

http://orgmode.org/worg/org-tutorials/org-latex-export.html#sec-17

It is easy to switch from one to the other.

We use the Chicago Manual of Style at work and the BibTeX chicago
style. We find that it approximates the Chicago Manual fairly well, but
not completely. A couple of years ago we contemplated moving to
biblatex, which has an extremely competent chicago style, but gave up on
the idea because it would have meant adding information to thousands of
entries in our BibTeX database.  It seemed like a lot of work to meet a
standard that most of our readers don't know or care about.

Where biblatex has helped me the most is writing for history
journals. Biblatex is much better at humanities styles than BibTeX,
which was designed with science publications fairly firmly in mind.
Also, because the biblatex styles are based on LaTeX, rather than
BibTeX's weird style language, it is in my experience relatively easy to
tweak a biblatex style to meet a journal's specification.

In the sciences you'll undoubtedly find journals that accept LaTeX
manuscripts and require that a BibTeX style be used, so I would
recommend against putting all your eggs in the biblatex basket.

All the best,
Tom

-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

  reply	other threads:[~2014-04-07  8:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-05  4:59 Images not showing up in PDF output Mark S.
2014-04-05  9:55 ` Eric S Fraga
2014-04-05 16:46   ` Richard Lawrence
2014-04-05 19:33     ` [OT] Don't use BibTeX! (was: Images not showing up in PDF output) Marcin Borkowski
2014-04-07  1:39       ` [OT] Don't use BibTeX! Richard Lawrence
2014-04-07  2:58         ` Thomas S. Dye
2014-04-07  3:50           ` Biblatex and Org [was: [OT] Don't use BibTeX!] Richard Lawrence
2014-04-07  8:34             ` Thomas S. Dye [this message]
2014-04-07 15:12               ` Biblatex and Org Richard Lawrence
2014-04-06 18:14     ` Images not showing up in PDF output Mark S.

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=m21tx9h724.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@wmi.amu.edu.pl \
    --cc=richard.lawrence@berkeley.edu \
    /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).