From: "Bruce D'Arcus" <bdarcus@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: "David Lukeš" <dafydd.lukes@gmail.com>,
org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?)
Date: Sat, 18 Jun 2022 21:55:41 -0400 [thread overview]
Message-ID: <CAF-FPGNPJ=fufE_3GJ4yTd04Asa79QaZGX=J-0SLY5Ze1xz-TQ@mail.gmail.com> (raw)
In-Reply-To: <87h74h4ecd.fsf@localhost>
On Sat, Jun 18, 2022 at 9:43 PM Ihor Radchenko <yantar92@gmail.com> wrote:
>
> David Lukeš <dafydd.lukes@gmail.com> writes:
>
> > I recently started to get errors like the following:
> >
> > Error during redisplay: (jit-lock-function 544) signaled
> > (wrong-type-argument "Argument is not a string or a secondary string:
> > 2007")
> >
> > This patch makes them go away:
> >
> > - (caar date))
> > + (number-to-string (caar date)))
>
> Can you provide an example json file demonstrating the problem?
> I suspect that multiple json formats may be available in the wild. Some
> parsed as a list of strings and some parsed as a list of numbers.
The JSON schema allows either:
https://github.com/citation-style-language/schema/blob/5b8bbc824e026959417757d4ce4012a26b10e637/schemas/input/csl-data.json#L512
Bruce
next prev parent reply other threads:[~2022-06-19 1:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-18 6:34 oc-basic: CSL-JSON year as number vs. string (nativecomp?) David Lukeš
2022-06-19 1:44 ` Ihor Radchenko
2022-06-19 1:55 ` Bruce D'Arcus [this message]
2022-06-19 3:31 ` David Lukeš
2022-06-19 13:39 ` Bruce D'Arcus
2022-06-20 12:06 ` Ihor Radchenko
2022-06-20 13:11 ` Bruce D'Arcus
2022-06-20 14:13 ` David Lukeš
2022-06-20 14:24 ` Bruce D'Arcus
2022-06-21 3:28 ` Ihor Radchenko
2022-06-21 12:02 ` David Lukeš
2022-07-31 4:05 ` Ihor Radchenko
2022-06-20 12:04 ` Ihor Radchenko
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAF-FPGNPJ=fufE_3GJ4yTd04Asa79QaZGX=J-0SLY5Ze1xz-TQ@mail.gmail.com' \
--to=bdarcus@gmail.com \
--cc=dafydd.lukes@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).