emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Erik Hetzner <egh@e6h.org>
To: emacs-orgmode@gnu.org
Cc: Richard Lawrence <richard.lawrence@berkeley.edu>
Subject: Re: exporting zotxt or orgref links to HTML and ODF
Date: Tue, 27 Jan 2015 22:37:20 -0800	[thread overview]
Message-ID: <54c883a3.ea28460a.55f8.ffff9133@mx.google.com> (raw)
In-Reply-To: <8761bsp26n.fsf@berkeley.edu>

On Tue, 27 Jan 2015 at 09:24:00 PST,
Richard Lawrence <richard.lawrence@berkeley.edu> wrote:
> 
> 
> Although my home-baked solution presently works for me, I am inclined to
> agree.
> 
> I've just had a glance at: http://pandoc.org/README.html#citations
> 
> It looks to me like Pandoc has a quite general solution, and it also
> looks like Org could use Pandoc's citation syntax as-is.  I would
> suggest borrowing this syntax as a starting point for building citation
> support into Org.

Hi all,

I agree completely. For what it’s worth, using pandoc citations now
will work right now if you output to markdown and then parse in
pandoc. e.g.

  [see @doe:2006article, p. 10]

will work.

I wrote a parser for pandoc citations (that assumes you start with a
citation string, that is, it doesn’t work unless you have extracted
the citation string from the document):

  https://bitbucket.org/egh/zot4rst/src/master/xciterst/parser.py

but it doesn’t seem that org-element.el uses a grammar, so I’m not
sure how much that would help. There is also, of course, the pandoc
parser.

best, Erik
--
Sent from my free software system <http://fsf.org/>.

  parent reply	other threads:[~2015-01-28  6:37 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 16:29 exporting zotxt or orgref links to HTML and ODF Matt Price
     [not found] ` <54C67E1A.8080706@law.lsu.edu>
2015-01-26 20:40   ` Matt Price
2015-01-26 21:53     ` Monroe, Will
2015-01-27  8:25 ` Eric S Fraga
2015-01-27  9:23 ` Christian Moe
2015-01-27 13:30   ` Rasmus
2015-01-27 13:51     ` Matt Price
2015-01-27 14:14       ` Rasmus
2015-01-27 18:17         ` John Kitchin
2015-01-27 15:24       ` Christian Moe
2015-01-27 17:24     ` Richard Lawrence
2015-01-27 17:50       ` Rasmus
2015-01-28  4:09         ` Richard Lawrence
2015-01-27 20:01       ` Christian Moe
2015-01-27 22:08         ` Rasmus
2015-01-27 22:15         ` John Kitchin
2015-01-28  2:10         ` Matt Price
2015-01-28  6:37       ` Erik Hetzner [this message]
2015-02-01  4:20         ` Erik Hetzner
2015-01-27 12:01 ` Vikas Rawal
2015-01-27 13:12   ` Matt Price
2015-01-27 14:28     ` Eric S Fraga
2015-01-27 13:31   ` Albert Krewinkel
     [not found] ` <m2vbjsvay0.fsf@christianmoe.com>
     [not found]   ` <CAN_Dec9qBWWWgdX+wQhdgbthMg_ZOgbOMFoXFixSc4=74avMjw@mail.gmail.com>
2015-01-27 14:41     ` Christian Moe
     [not found] <CAMfbzvA83eSWe79Ot=yX+_s_g33gpLnP-z+zQ52QFJm+iJTR+Q@mail.gmail.com>
2015-01-28 21:53 ` Matt Price
2015-01-28 23:01   ` John Kitchin
2015-01-29  1:34     ` Matt Price
2015-01-29  1:48       ` John Kitchin
     [not found]         ` <CAN_Dec80Su+5Nh5mqNxBXsLu_gm93aY77B=2Zrce-TJ1RPKCig@mail.gmail.com>
2015-01-29 13:06           ` John Kitchin
2015-01-29 13:11             ` Vikas Rawal
2015-01-29 13:24               ` John Kitchin
2015-01-29 13:39                 ` Vikas Rawal
2015-01-29 13:09       ` John Kitchin
2015-01-29  2:26     ` Vikas Rawal

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=54c883a3.ea28460a.55f8.ffff9133@mx.google.com \
    --to=egh@e6h.org \
    --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).