[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?)
From: |
David Lukeš |
Subject: |
Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?) |
Date: |
Tue, 21 Jun 2022 14:02:56 +0200 |
Bruce: Understood, I was just thinking forward :) Thank you for the
details. As far as I'm concerned, EDTF in CSL JSON sounds like a good
idea (but it's not like my opinion should particularly matter).
Ihor: Thank you for the feedback! I'll send a proper patch then.
Best,
David
- oc-basic: CSL-JSON year as number vs. string (nativecomp?), David Lukeš, 2022/06/18
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Ihor Radchenko, 2022/06/18
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Bruce D'Arcus, 2022/06/18
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), David Lukeš, 2022/06/18
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Bruce D'Arcus, 2022/06/19
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Ihor Radchenko, 2022/06/20
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Bruce D'Arcus, 2022/06/20
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), David Lukeš, 2022/06/20
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Bruce D'Arcus, 2022/06/20
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Ihor Radchenko, 2022/06/20
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?),
David Lukeš <=
- Re: oc-basic: CSL-JSON year as number vs. string (nativecomp?), Ihor Radchenko, 2022/06/20