From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: "András Simonyi" <andras.simonyi@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Org citations, CSL and citeproc-el
Date: Wed, 10 Jan 2018 15:53:26 -0800 [thread overview]
Message-ID: <877espmft5.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87k1wtor6x.fsf@gmail.com>
Hi András and all:
Sorry for the delay.
András Simonyi <andras.simonyi@gmail.com> writes:
> Another question is the syntax for specifying the bibliography
> to be used and, maybe, the location where the bibliography
> should be placed. Org-ref (ab)uses links for these purposes as
> well. Was there a syntax proposal for these things too?
As far as I know, there was not. This was not settled because in
order to settle it, you need to know a bit more about the backend.
(Where is the citation data stored? do you have to get it from an
external program? if so, which? etc. etc.)
I think there was some agreement that we can do this with option
keywords. There is an existing syntax for specifying
bibliographies in contrib/ox-bibtex.el, which probably provides a
good model:
#+BIBLIOGRAPHY: bibfilename stylename optional-options When I was
playing around with hooking up the citation syntax to an external
citation processor, I was using something similar: I had keywords
like
#+CSL_FILE: the-csl-style-file.csl +BIBDB: bibtex testdoc.bib
in the header, and used
#+BIBLIOGRAPHY: here
to specify where the bibliography should be placed in the
document. That is obviously not the nicest solution, but the
basic idea might be a good starting point.
--
Best,
Richard
next prev parent reply other threads:[~2018-01-10 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 15:06 Org citations, CSL and citeproc-el Simonyi András
2018-01-05 16:52 ` Richard Lawrence
2018-01-05 17:02 ` Tory S. Anderson
2018-01-05 17:53 ` Eric S Fraga
2018-01-05 21:57 ` Nicolas Goaziou
2018-01-07 11:15 ` András Simonyi
2018-01-10 23:53 ` Richard Lawrence [this message]
2018-01-05 17:02 ` Christian Moe
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=877espmft5.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me \
--to=richard.lawrence@berkeley.edu \
--cc=andras.simonyi@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 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.