From: Alex Fenton <alex.fenton@pressure.to>
To: Richard Lawrence <richard.lawrence@berkeley.edu>, emacs-orgmode@gnu.org
Subject: Re: pandoc-style citations
Date: Wed, 27 Apr 2016 21:45:46 +0200 [thread overview]
Message-ID: <572116EA.5000006@pressure.to> (raw)
In-Reply-To: <87r3dr3zzk.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me>
Hi Richard
On 27/04/16 16:09, Richard Lawrence wrote:
> As far as Elisp implementations go, I know of no specific parser for
> Pandoc citation syntax. But there is support for a Pandoc-like syntax
> (discussed in the threads you read) in the wip-cite branch of Org's
> repository.
> https://github.com/wyleyr/org-mode/
Thanks for your reply, and for all your work on specifying and
developing this. It looks like that for now I can adapt some of the
parsing in org-element.el (org-element-citation-reference-parser and
org-element-citation-parser etc) to get something that works for now in
standard mainline org.
> Export is where efforts stalled last year.
That's understandable, given that, as you say, it's a complex problem
given the range of citation styles and output formats. It's still a
shame given the work that you (pl.) have put into integrating citations
into the org parser & element tree so they are first class objects.
I don't know whether it's conceivable that the data structures and
parsing could be integrated into org, with the (presumably) relatively
easy latex output, which I suspect is the commonest use case, and then
with some kind of "adequate" output for other targets (html, text, odt)
- perhaps an output that would require further post-processing by a
third-party tool such as citeproc or pandoc.
Latex-outputters would be better off and other targets no worse off than
present, and it might act as a spur to solve the other target formats
one by one way. But I can see that this has been to some extent
considered and can also see the arguments against.
>
> You may also want to look at John Kitchin's org-ref, which I believe
> works similar to your homebrew link solution, but has a lot of features
> and may provide a better interface for what you're trying to do:
Org-ref does a lot of nice things, but on this particular point is not
very helpful, and has nothing to add for the case of multiple cites with
overall and individual pre/posts. The package states that this is low
priority b/c this style of citation is rare in scientific publishing (by
which I guess is meant natural sciences; footnotes with multiple
citations and linking text are of common in humanities and some social
sciences).
thanks again and best wishes
alex
next prev parent reply other threads:[~2016-04-27 19:45 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 [this message]
2016-04-27 20:36 ` John Kitchin
2016-04-28 15:58 ` Richard Lawrence
2016-04-27 19:41 ` John Kitchin
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=572116EA.5000006@pressure.to \
--to=alex.fenton@pressure.to \
--cc=emacs-orgmode@gnu.org \
--cc=richard.lawrence@berkeley.edu \
/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).