public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: pandoc-citeproc weirdness: how to @cite in YAML?
Date: Wed, 11 Oct 2017 11:36:35 -0400	[thread overview]
Message-ID: <c8ad42a2-8e0f-cdb0-47b5-e61be52e4059@reagle.org> (raw)

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?


             reply	other threads:[~2017-10-11 15:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11 15:36 Joseph Reagle [this message]
     [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

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=c8ad42a2-8e0f-cdb0-47b5-e61be52e4059@reagle.org \
    --to=joseph.2011-t1oy19wchswdnm+yrofe0a@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).