From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: emacs-orgmode@gnu.org
Cc: Aaron Ecay <aaronecay@gmail.com>
Subject: Re: org-cite and org-citeproc
Date: Mon, 06 Apr 2015 11:51:22 -0700 [thread overview]
Message-ID: <87vbh9nl91.fsf@berkeley.edu> (raw)
In-Reply-To: <87k2xue8gm.fsf@berkeley.edu>
Hi Aaron and all,
Richard Lawrence <richard.lawrence@berkeley.edu> writes:
> Alright, I'll try to move to json.el, and possibly change to having
> org-citeproc generate Org markup in the meantime.
Just a heads up: I've pushed some changes to my branch of Org to make
org-cite use json.el, and to add a basic Org format writer to
org-citeproc.
I have not made any other changes to org-cite to use the Org formatted
output from org-citeproc, though, as I believe doing this properly will
involve parsing the output and inserting it into Org's exporter's parse
tree (to accommodate the bibliography and note-based styles). I won't
have time to work on that this week, but I'll come back to it.
Best,
Richard
next prev parent reply other threads:[~2015-04-06 18:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 18:53 org-cite and org-citeproc Richard Lawrence
2015-03-31 8:16 ` Eric S Fraga
2015-03-31 19:13 ` Richard Lawrence
2015-03-31 19:34 ` Nick Dokos
2015-03-31 20:29 ` Thomas S. Dye
2015-03-31 21:57 ` Richard Lawrence
2015-04-01 0:41 ` Thomas S. Dye
2015-04-01 15:42 ` Richard Lawrence
2015-04-01 19:41 ` Thomas S. Dye
2015-04-02 15:57 ` Richard Lawrence
2015-04-02 16:45 ` Thomas S. Dye
2015-03-31 21:12 ` Eric S Fraga
2015-04-01 7:49 ` Andreas Leha
2015-04-02 14:29 ` Eric S Fraga
2015-04-02 15:11 ` Richard Lawrence
2015-04-02 19:26 ` Andreas Leha
2015-03-31 22:03 ` Rasmus
2015-04-01 14:39 ` Richard Lawrence
2015-04-02 0:08 ` Rasmus
2015-04-02 15:26 ` Richard Lawrence
2015-04-02 15:51 ` Aaron Ecay
2015-04-02 17:38 ` Richard Lawrence
2015-04-06 18:51 ` Richard Lawrence [this message]
2015-06-16 19:36 ` Matt Price
2015-06-18 22:44 ` Richard Lawrence
2015-04-02 19:17 ` Rasmus
2015-04-03 2:56 ` 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=87vbh9nl91.fsf@berkeley.edu \
--to=richard.lawrence@berkeley.edu \
--cc=aaronecay@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).