From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: Alex Fenton <alex.fenton@pressure.to>, emacs-orgmode@gnu.org
Subject: Re: pandoc-style citations
Date: Thu, 28 Apr 2016 08:58:28 -0700 [thread overview]
Message-ID: <8737q54tej.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <572116EA.5000006@pressure.to>
Hi Alex,
Alex Fenton <alex.fenton@pressure.to> writes:
>> 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.
Unfortunately, even the LaTeX case is not so easy unless you assume
users are managing the bibliography database, and the mapping of
citation keys into that database, themselves. It's easy to map the Org
syntax to the LaTeX syntax if you can just pass the keys through, but
that isn't a great assumption to make. And things are a lot more
complicated once you have to worry about looking up the keys somewhere,
generating an appropriate .bib file, etc. We will have to do this stuff
for other backends anyway, so it seems sensible to do it for LaTeX too,
but that's what makes the project so big (especially if we can't just
pick one database format to support).
Maybe you're right that a good first step would just be to generate
LaTeX syntax, and just let users manage the bibliography database in
whatever way works for them, without trying to interface with it. This
could be done quickly -- indeed, I think it is already most of the way
done. And as you say, that would go a long way toward meeting many
people's needs.
I hope I will have some time next week to look at this. I'll report
back!
Best,
Richard
next prev parent reply other threads:[~2016-04-28 15:57 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 [this message]
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=8737q54tej.fsf@aquinas.i-did-not-set--mail-host-address--so-tickle-me \
--to=richard.lawrence@berkeley.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).