From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Richard Lawrence <richard.lawrence@berkeley.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Citation processing via Zotero + zotxt
Date: Mon, 30 Nov 2015 11:35:22 +0000 [thread overview]
Message-ID: <87poyrlnyd.fsf@pinto.chemeng.ucl.ac.uk> (raw)
In-Reply-To: <87wpt1yj5k.fsf@berkeley.edu> (Richard Lawrence's message of "Sat, 28 Nov 2015 12:16:07 -0800")
On Saturday, 28 Nov 2015 at 12:16, Richard Lawrence wrote:
> Hi everyone,
>
> For the past few days, I've been looking more closely at using the
> combination of Zotero [1] with Erik Hetzner's zotxt plugin [2] as a
> means of processing citations when exporting to non-LaTeX backends. I
> am now thinking that this is probably our best option, but I'd like to
> know what other people think before I sink a lot of work into it.
Richard,
thanks for the long and descriptive email. What you propose does seem
like a potentially attractive way forward especially in the context of
minimal impact for installation.
I have two questions:
1. Is Zotero open source? I believe not so I wonder about the
implications of this for org.
2. How would I use this starting from an org-bibtex database (which I
typically export to bibtex)?
Regardless, my export requirements are usually satisfied by export to
LaTeX so my main concern will not be org to odt or HTML but on the user
interface aspects within org for inserting citations etc.
Thanks again,
eric
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org release_8.3beta-1229-ge900eb
next prev parent reply other threads:[~2015-11-30 11:35 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87poyrlnyd.fsf@pinto.chemeng.ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.