From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 39347@debbugs.gnu.org
Subject: bug#39347: 28.0.50; iso8601-parse can't handle all legal date values?
Date: Wed, 29 Jan 2020 15:23:47 -0800 [thread overview]
Message-ID: <87h80dsv7g.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87lfppyj1i.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 29 Jan 2020 23:50:01 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> I'm testing out `iso9601-parse' with the example values from the vcard
>> RFC, and am getting errors from the example date value "---12", from
>> https://tools.ietf.org/html/rfc6350#section-4.3.1.
>>
>> My understanding is that "---12" as a date should parse to:
>>
>> (nil nil nil 12 nil nil nil -1 nil)
>
> I'm unable to find that form in
>
> http://www.loc.gov/standards/datetime/iso-tc154-wg5_n0038_iso_wd_8601-1_2016-02-16.pdf
>
> The RFC talks about the ISO8601 standard from 2000 -- perhaps those
> forms have been deprecated?
I sure hope so! Anyway, looks like the library is correct, and I just
get to decide if I want to support deprecated forms that might be sent
by someone's random outdated carddav server. Bleagh.
I want this package to support older Emacs than 27 -- I wonder if anyone
would yell at me if stuck a copy of iso8601.el in the package, and only
load it if the built-in one can't be found.
Eric
next prev parent reply other threads:[~2020-01-29 23:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 21:00 bug#39347: 28.0.50; iso8601-parse can't handle all legal date values? Eric Abrahamsen
2020-01-29 22:50 ` Lars Ingebrigtsen
2020-01-29 23:23 ` Eric Abrahamsen [this message]
2020-01-29 23:28 ` Lars Ingebrigtsen
2020-01-30 0:38 ` Eric Abrahamsen
2020-01-30 1:03 ` Lars Ingebrigtsen
2020-01-30 1:11 ` Lars Ingebrigtsen
2020-01-30 1:14 ` Eric Abrahamsen
2020-01-30 1:15 ` Lars Ingebrigtsen
2020-01-30 2:05 ` Lars Ingebrigtsen
2020-01-30 3:32 ` Eric Abrahamsen
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=87h80dsv7g.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=39347@debbugs.gnu.org \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.