From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
Subject: Re: pandoc-citeproc weirdness: how to @cite in YAML?
Date: Thu, 12 Oct 2017 10:05:06 -0400 [thread overview]
Message-ID: <08999bdc-b933-96b0-56fd-a9c54434cfbb@reagle.org> (raw)
In-Reply-To: <20171011154842.GA40031@protagoras>
On 10/11/17 11:48 AM, John MACFARLANE wrote:
> No, there's no way to have citations in the abstract
> resolved by pandoc-citeproc.
I don't want them resolved but ignored. They create phantom citations in a document that cites @Groth2015edh. (I get references to them in the bibliography even though the prose never cites them).
> Pandoc-citeproc reads
> the references from the metadata before modifying the
> AST. Backslash-escaping these should just give you
> literal strings -- what do you get instead?
I'm not sure what this means, but when I backslash those keys in my source YAML I get this build error and none of my cites are found:
```
/usr/local/bin/pandoc -f markdown+mmd_title_block+yaml_metadata_block+implicit_header_references+superscript+subscript+tex_math_dollars+autolink_bare_uris -w html -s --smart --tab-stop 4 --email-obfuscation=references -c http://reagle.org/joseph/2003/papers.css -o /Users/reagle/joseph/2016/lh/09-conclusion.html --mathjax --csl=chicago-fullnote-bibliography.csl --filter pandoc-citeproc /Users/reagle/joseph/2016/lh/09-conclusion-2.md /Users/reagle/joseph/2016/lh/09-conclusion.yaml
[pandoc warning] Could not parse YAML header: found unknown escape character "source" (line 416, column 56)
pandoc-citeproc: reference Ferriss20155mr not found
pandoc-citeproc: reference Magnezi2016fys not found
pandoc-citeproc: reference Theisen-Jones2017mfo not found
pandoc-citeproc: reference Altucher2013hba not found
pandoc-citeproc: reference Altucher2016hmb not found
pandoc-citeproc: reference Williams2016wsh not found
pandoc-citeproc: reference Altucher2011hbs not found
pandoc-citeproc: reference Altucher2014lil not found
pandoc-citeproc: reference Altucher2013hba not found
pandoc-citeproc: reference Buchheit2009apk not found
pandoc-citeproc: reference LevineRubinstein2013siw not found
pandoc-citeproc: reference BlackEtal2015ort not found
pandoc-citeproc: reference Groth2015edh not found
pandoc-citeproc: reference Dziura2013wlh not found
pandoc-citeproc: reference Levy2001hhc not found
pandoc-citeproc: reference Connection1996nhe not found
```
--
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/08999bdc-b933-96b0-56fd-a9c54434cfbb%40reagle.org.
For more options, visit https://groups.google.com/d/optout.
prev parent reply other threads:[~2017-10-12 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 15:36 Joseph Reagle
[not found] ` <c8ad42a2-8e0f-cdb0-47b5-e61be52e4059-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2017-10-11 15:48 ` John MACFARLANE
2017-10-12 14:05 ` Joseph Reagle [this message]
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=08999bdc-b933-96b0-56fd-a9c54434cfbb@reagle.org \
--to=joseph.2011-t1oy19wchswdnm+yrofe0a@public.gmane.org \
--cc=jgm-TVLZxgkOlNX2fBVCVOL8/A@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).