From: Thomas S. Dye <tsd@tsdye.com>
To: Richard Lawrence <richard.lawrence@berkeley.edu>
Cc: Matt Lundin <mdl@imapmail.org>, emacs-orgmode@gnu.org
Subject: Re: Citation processing via Zotero + zotxt
Date: Thu, 03 Dec 2015 09:14:42 -1000 [thread overview]
Message-ID: <m2mvtrjqe5.fsf@tsdye.com> (raw)
In-Reply-To: <87k2ovwh4w.fsf@berkeley.edu>
Aloha all,
At the risk of introducing noise, I've long wondered if tex4ht might
help with citation processing in Org mode? IIUC, tex4ht uses the
device-independent dvi file produced by TeX to make html, odt, and other
formats. With an Org mode that relied on tex4ht, users would use BibTeX
bibliographies, and Org mode documents with citations would be processed
by LaTeX and a tex4ht script that would yield the correctly formatted
in-text citations and bibliography in the desired output format. Org mode
would then parse this output and plug in the pieces at the right places.
This approach, if feasible, would please LaTeX users happy with BibTeX
and wary of translating bibliographic databases to Zotero. It would
only require a working LaTeX installation, and so would avoid the
Haskell hassle, etc. And, it would make use of BibTex/BibLaTeX,
arguably the best bibliography software out there.
I'm in way over my head here and won't be surprised to learn that this
idea is a bad one. Given the wide-ranging nature of this discussion, I
thought this might be the time to suggest it.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2015-12-03 19:15 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 20:16 Citation processing via Zotero + zotxt Richard Lawrence
2015-11-30 8:12 ` Martin Yrjölä
2015-12-01 0:32 ` John Kitchin
2015-12-01 2:59 ` Richard Lawrence
2015-12-03 0:27 ` Matt Lundin
2015-12-03 1:41 ` Christian Wittern
2015-12-03 14:25 ` Matt Lundin
2015-12-03 4:32 ` Richard Lawrence
2015-12-03 15:27 ` Matt Lundin
2015-12-03 17:56 ` Richard Lawrence
2015-12-03 19:14 ` Thomas S. Dye [this message]
2015-12-03 22:05 ` Rasmus
2015-12-03 20:45 ` Matt Lundin
2015-12-03 21:04 ` Matt Lundin
2015-12-03 23:31 ` John Kitchin
2015-12-04 0:03 ` Rasmus
2015-12-04 1:49 ` John Kitchin
2015-12-05 21:18 ` Matt Lundin
2015-12-05 22:23 ` John Kitchin
2015-12-04 2:06 ` Matt Lundin
2015-12-04 11:22 ` John Kitchin
2015-12-04 14:13 ` Matt Lundin
2015-12-05 1:23 ` John Kitchin
2015-12-04 9:20 ` Eric S Fraga
2015-12-01 9:34 ` Ramon Diaz-Uriarte
2015-11-30 11:35 ` Eric S Fraga
2015-11-30 12:02 ` Ramon Diaz-Uriarte
[not found] ` <CAN_Dec-JCmwQ2bc=U93rRaPMYyXOiN_PRbtyya9x396r3qqMrg@mail.gmail.com>
2015-12-01 12:12 ` Fwd: " Matt Price
2015-12-01 15:28 ` Eric S Fraga
2015-12-01 15:51 ` Richard Lawrence
2015-12-01 19:20 ` Matt Price
2015-12-01 21:34 ` Eric S Fraga
2015-12-01 21:51 ` Matt Lundin
2015-12-02 15:21 ` Richard Lawrence
2015-12-01 14:36 ` Rasmus
2015-12-01 19:37 ` Matt Price
2015-12-02 15:58 ` Richard Lawrence
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=m2mvtrjqe5.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.org \
--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).