From: Matt Lundin <mdl@imapmail.org>
To: Christian Wittern <cwittern@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Citation processing via Zotero + zotxt
Date: Thu, 03 Dec 2015 08:25:24 -0600 [thread overview]
Message-ID: <87y4dbhanf.fsf@fastmail.fm> (raw)
In-Reply-To: <565F9DB9.90600@gmail.com> (Christian Wittern's message of "Thu, 3 Dec 2015 09:41:13 +0800")
Christian Wittern <cwittern@gmail.com> writes:
> On 2015-12-03 8:27, Matt Lundin wrote:
>> Given these complexities, it seems that if we went the zotero route we
>> could end up with a fairly large installation chain (firefox, zotero,
>> zotxt, plugin for zotero). And this would require installing items from
>> multiple, heterogeneous sources.
> I guess it depends on where you come from. For those who already maintain
> the bibliography in Zotero this is not much of an extra load.
Yes, I think this is the key point. For those of us who maintain bib
databases within emacs, importing in zotero is problematic (overhead,
potential of data loss, etc.).
>> As a GNU/Linux user, I would find installing zotero and all the add-ons
>> messier and more cumbersome than installing pandoc and/or node-js (were
>> we to use citeproc-js) from the command line.
> Maybe the best situation would be to support both the pandoc and zotero
> toolchain as backends and let the user decide what to use. If the result is
> in both cases org-formated citations, that should not make it too difficult, no?
That sounds right. Ideally, org-cite could support zotero *and* bibtex
users (i.e., gui and text based/command line) solutions.
Matt
next prev parent reply other threads:[~2015-12-03 14:25 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 [this message]
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
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=87y4dbhanf.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=cwittern@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).