public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Erik Hetzner <egh-r1v5srsr4wc@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: How to extract all citation keys from a document
Date: Tue, 04 Jun 2013 12:36:54 -0700	[thread overview]
Message-ID: <87y5apllbd.wl%egh@e6h.org> (raw)
In-Reply-To: <20130604190129.GC5256-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>

At Tue, 4 Jun 2013 12:01:29 -0700,
John MacFarlane wrote:
> 
> Sorry, there's currently no way to do this.  '@foo' is ambiguous in
> pandoc markdown.  It could be a reference to an example list, or a plain
> string '@foo', or a citation.  Pandoc uses the actual bibliography file
> to help decide.  For example, in:
> 
> ```
> (@foo) hello
> 
> In example @foo, I show...
> ```
> 
> The second @foo will be interpreted as a citation if 'foo' is a defined
> key in the specified bibliography file; otherwise, it will be
> interpreted as a reference to the example list item marked (@foo).

If you don’t care about this problem, and you just want a hack that
works, you can easily scan the document with a script. See, e.g.,

  https://bitbucket.org/egh/zotxt/src/tip/scripts/extractcites.py

which builds a JSON file from @AuthorTitleDate keys via Zotero.

best, Erik

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/87y5apllbd.wl%25egh%40e6h.org?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.




  parent reply	other threads:[~2013-06-04 19:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04 18:34 Makaken Affe
     [not found] ` <06b38ec2-b028-48d8-89cf-50b3151158d8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2013-06-04 19:01   ` John MacFarlane
     [not found]     ` <20130604190129.GC5256-nFAEphtLEs+AA6luYCgp0U1S2cYJDpTV9nwVQlTi/Pw@public.gmane.org>
2013-06-04 19:36       ` Erik Hetzner [this message]
2013-06-05 19:12       ` Makaken Affe
     [not found]         ` <aa6ac405-ac89-47e5-a8e8-896688d3325b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2013-06-06  9:52           ` BP Jonsson
2013-06-04 19:39   ` Joseph Reagle

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=87y5apllbd.wl%egh@e6h.org \
    --to=egh-r1v5srsr4wc@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.
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 NNTP newsgroup(s).