From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Matt Lundin <mdl@imapmail.org>
Cc: "Martin Yrjölä" <martin.yrjola@gmail.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Citation processing via Zotero + zotxt
Date: Fri, 04 Dec 2015 20:23:24 -0500 [thread overview]
Message-ID: <m2a8ppg037.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <87poymfgio.fsf@fastmail.fm>
>
> Yes. And CSL and biblatex are far more complex and robust than bibtex.
> :) I use biblatex (biblatex-chicago), which finally gives those of us in
> the humanities robust automation of complex footnote styles. One of my
> dreams for citation processing in org mode is to be able to achieve in
> org the same level of automation, thus allowing non-LaTeX backends. IMO,
> the best hope of accomplishing this is to plug into the existing power
> of CSL, which has emerged as the new standard for automated citations.
>
> (A note: the other way to accomplish this right now it to export a file
> to org or markdown --- evaluating code blocks, etc. and converting
> citations to [@some_cite_key] --- and then running the output through
> pandoc, which uses CSL.)
On this note, it is also possible to have org-ref either insert pandoc
syntax, or replace the org-ref links with pandoc syntax as a pre-filter.
Alternatively, when you export markdown documents with org-ref
citations, they export as pandoc syntax right now.
>
> Best,
> Matt
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2015-12-05 1:23 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 [this message]
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=m2a8ppg037.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=martin.yrjola@gmail.com \
--cc=mdl@imapmail.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).