public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "'Nick Bart' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: "pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org"
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How to represent circa and BCE in yaml?
Date: Mon, 19 Aug 2019 20:01:32 +0000	[thread overview]
Message-ID: <0BcHZ2jZu6reb3WfbjFUgQHOhfC1ISgZpBTNqOmTx4X03NHk1WMizlndDHmtOifrP_NilrzUUiW7gg6zKfSpBpEXV6Qa3bIQU4eD3XXjbeM=@protonmail.com> (raw)
In-Reply-To: <5361bd16-d212-c418-2e2b-1e58423947fa-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>

> Is this documented anywhere?

Actually, I don’t think so. There’s some documentation on CSL JSON dates (https://citeproc-js.readthedocs.io/en/latest/csl-json/markup.html#date-fields), but nothing I’m aware of on CSL YAML date syntax - which is in part different from CSL JSON’s.

I really wish both CSL JSON and CSL YAML were using a fully standardized date format such as ISO8601/EDTF - it would make things so much easier.

Fortunately, biblatex does use ISO8601/EDTF, so if in doubt, you can always put together a minimal biblatex record, run it through `pandoc-citeproc -y` and inspect the output.

> Why Zotero discussions rather than CSL issues?

This at first appeared strange to me as well, but while bug reports at https://github.com/citation-style-language/styles/issues eventually will be taken note of, too, de facto it is the Zotero forum where the vast majority of CSL style file issues are being reported and discussed.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, August 19, 2019 2:10 PM, Joseph Reagle <joseph-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> wrote:

> On 8/18/19 7:22 AM, 'Nick Bart' via pandoc-discuss wrote:
>
> > -   year: 2007
> >     month: 1
> >     day: 31
> >     circa: true
> >
>
> Is this documented anywhere? I was reading these issues and '1' was used instead of 'true' -- which led to problems.
>
> https://github.com/jgm/pandoc-citeproc/issues/103
>
> https://github.com/jgm/pandoc-citeproc/issues/240
>
> > Concerning the latter two I’d recommend, again, filing a bug report
> > at https://forums.zotero.org/discussions.
>
> Why Zotero discussions rather than CSL issues?
>
> https://github.com/citation-style-language/styles/issues
>
> -----------------------------------------------------------------------------------------------------------
>
> 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/5361bd16-d212-c418-2e2b-1e58423947fa%40reagle.org.


-- 
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/0BcHZ2jZu6reb3WfbjFUgQHOhfC1ISgZpBTNqOmTx4X03NHk1WMizlndDHmtOifrP_NilrzUUiW7gg6zKfSpBpEXV6Qa3bIQU4eD3XXjbeM%3D%40protonmail.com.


  parent reply	other threads:[~2019-08-19 20:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16 17:17 Joseph Reagle
     [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 [this message]
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='0BcHZ2jZu6reb3WfbjFUgQHOhfC1ISgZpBTNqOmTx4X03NHk1WMizlndDHmtOifrP_NilrzUUiW7gg6zKfSpBpEXV6Qa3bIQU4eD3XXjbeM=@protonmail.com' \
    --to=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).