From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Alex Fenton <alex.fenton@pressure.to>
Cc: emacs-orgmode@gnu.org
Subject: Re: pandoc-style citations
Date: Wed, 27 Apr 2016 15:41:39 -0400 [thread overview]
Message-ID: <m2shy6alfw.fsf@Johns-MacBook-Air.local> (raw)
In-Reply-To: <572045B8.4070904@pressure.to>
you might also checkout helm-bibtex. A recent note indicated "Support
for pre- and postnotes for pandoc-citeproc citations."
I haven't tried it, so I am not sure how it works for org-mode. org-ref
supports [[cite:somekey][pre-text::post-text]] syntax, without folding
the link on itself so you can see it.
I think your example would look like:
blah blah blah [[cite:ref1][::, p.23]], also cite:ref2, for a contrary
view see [[cite:ref3][:: pp148-152]]
this exports out of the org-ref box to:
blah blah blah \cite[][, p.23]{ref1}, also \cite{ref2}, for a contrary
view see \cite[][ pp148-152]{ref3}.
I don't use this style of citations, so I don't know if it is right.
Alex Fenton writes:
> Hello,
>
> I see that there were several extensive and fruitful discussions on this
> list last year on citation syntax. There seemed to be a reasonable
> degree of consensus that pandoc-style citation syntax was at the least a
> good model.
>
> I'd like to know if there are any implementations out there of elisp to
> parse pandoc citation syntax and turn it into latex \cites. My question
> is not so much "when/if this will be in org mode" but rather whether
> there's something I can drop in now (likely as a link type).
>
> I have a lot of longish citations with multiple references each with
> their own pre- and post- ("'blah blah blah @ref1, p.23, also @ref2, for
> a contrary view see @ref3 pp148-152") that end up as \cites. However my
> home-brew link solution, stuffing the multiple pre- and posts- with
> separator into the link description is unwieldy - difficult to write,
> hard to read and easy to get wrong or breaking output.
>
> thanks
> alex
--
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:[~2016-04-27 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 4:53 pandoc-style citations Alex Fenton
2016-04-27 14:09 ` Richard Lawrence
2016-04-27 19:45 ` Alex Fenton
2016-04-27 20:36 ` John Kitchin
2016-04-28 15:58 ` Richard Lawrence
2016-04-27 19:41 ` John Kitchin [this message]
2016-04-27 19:54 ` Alex Fenton
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=m2shy6alfw.fsf@Johns-MacBook-Air.local \
--to=jkitchin@andrew.cmu.edu \
--cc=alex.fenton@pressure.to \
--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).