From: John MACFARLANE <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: pandoc-citeproc weirdness: how to @cite in YAML?
Date: Wed, 11 Oct 2017 08:48:42 -0700 [thread overview]
Message-ID: <20171011154842.GA40031@protagoras> (raw)
In-Reply-To: <c8ad42a2-8e0f-cdb0-47b5-e61be52e4059-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
No, there's no way to have citations in the abstract
resolved by pandoc-citeproc. 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?
+++ Joseph Reagle [Oct 11 17 11:36 ]:
>I have a bibliographic entry as follows
>
>```
>- id: Groth2015edh
> type: post-weblog
> genre: Web log message
> abstract: "Argument for risk and privilege by way of @LevineRubinstein2013siw; @BlackEtal2015ort"
> author:
> - family: "Groth"
> given: "Aimee"
> container-title: "Quartz"
> custom2: "field-notes-2016-cat.mm"
> issued:
> year: 2015
> month: 07
> day: 17
> keyword: "privilege"
> title: "Entrepreneurs don't have a special gene for risk---they come from families with money"
> URL: "http://qz.com/455109/entrepreneurs-dont-have-a-special-gene-for-risk-they-come-from-families-with-money/"
> accessed:
> year: 2016
> month: 04
> day: 23
>```
>
>The @Cites cause all sort of weirdness including references for non-existent citations in the prose.
>If I escape them with a backslash (\@BlackEtal2015ort), that causes other brokenness.
>If I remove `@` I am good, but is there a way to keep them and have it work?
>
>--
>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/c8ad42a2-8e0f-cdb0-47b5-e61be52e4059%40reagle.org.
>For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2017-10-11 15:48 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 [this message]
2017-10-12 14:05 ` 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=20171011154842.GA40031@protagoras \
--to=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).