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: How to represent circa and BCE in yaml?
Date: Fri, 16 Aug 2019 13:17:59 -0400	[thread overview]
Message-ID: <d2ebd6b1-8877-03d7-9ab0-268207fcac79@reagle.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]

I've seen a couple of bugs discussing ranges, multiples, negatives (BCE), and circa, but in playing with a minimal example, I can't figure out the correct format. Is there documentation on this?


I can get BCE to work with a negative 'year' integer.

But circa...

```
  issued:
    - year: 161
    - circa: 1
```

 puts a `-` after AD?

```
<li id="fn1" role="doc-endnote"><p>Marcus Aurelius, <em>Meditations</em>, ed. Maxwell Staniforth (London: Penguin Books, 161AD–).<a href="#fnref1" class="footnote-back" role="doc-backlink">↩︎</a></p></li>
```

No idea how to do a range or multiple specification. (I do use 'original-date''year', but chicago-fullnote-bibliography.csl doesn't seem to use that...)




-- 
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 view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/d2ebd6b1-8877-03d7-9ab0-268207fcac79%40reagle.org.

[-- Attachment #2: test.md --]
[-- Type: text/plain, Size: 438 bytes --]

---
author: Joseph Reagle 
title: "Test"
suppress-bibliography: true
...

test of [@Aurelius2005mns]

---
references:
- id: Aurelius2005mns
  type: book
  publisher-place: "London"
  author:
  - family: "Aurelius"
    given: "Marcus"
  issued:
    - year: 161
    - circa: 1
  editor:
  - family: "Staniforth"
    given: "Maxwell"
  ISBN: "9780143036272"
  publisher: "Penguin Books"
  title: "Meditations"
...

             reply	other threads:[~2019-08-16 17:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16 17:17 Joseph Reagle [this message]
     [not found] ` <d2ebd6b1-8877-03d7-9ab0-268207fcac79-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-08-16 21:54   ` 'Nick Bart' via pandoc-discuss
2019-08-18 11:22   ` 'Nick Bart' via pandoc-discuss
2019-08-19 14:10     ` Joseph Reagle
     [not found]       ` <5361bd16-d212-c418-2e2b-1e58423947fa-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-08-19 20:01         ` 'Nick Bart' via pandoc-discuss
2019-08-20  8:25           ` 'Nick Bart' via pandoc-discuss
2019-08-20 18:22     ` Joseph Reagle
2019-08-18 12:09   ` 'Nick Bart' via pandoc-discuss
2019-08-20 10:58   ` Scot Mcphee
     [not found]     ` <CAFnRE0Sr6xopjG7cwCACfR+x3Rgok68Y0cQu7Xpajg1yF+VyLg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-08-20 12:11       ` Joseph Reagle
     [not found]         ` <d5ddc026-eda2-1c35-6e6e-7210c6f0ba22-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2019-08-20 13:54           ` Scot Mcphee

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=d2ebd6b1-8877-03d7-9ab0-268207fcac79@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).