Consistent representation of datetimes and use of calendar attribute#641
Conversation
Co-authored-by: JonathanGregory <j.m.gregory@reading.ac.uk>
Co-authored-by: JonathanGregory <j.m.gregory@reading.ac.uk>
|
All comments/suggestions to date have been resolved. Thanks to @JonathanGregory and @larsbarring for their contributions. Inviting others to review and comment. |
|
Thanks, @pvanlaake. I don't think you've changed the time-zone symbol to TZ yet, which you preferred in #625. That seems fine to me: both T and Z individually are problematic, but together they make a solution. :-) |
|
Yes, TZ is a good solution. |
|
Thanks for flagging that @JonathanGregory, changes have been made in chapter 4. |
|
What ever was done for the |
|
My naive editing of my own PR... It should now be fixed. That is, if I preview the file I can see TZ consistently, as well as in the diffs |
|
Yep, looks fixed to me now! |
Deleted RFC 3339 references from lines 251, 277, 283, 284
Removed RFC 3339 reference from bibliography.
Clarify the handling of leading zeros in datetime strings for backwards compatibility and ISO 8601 compliance.
Clarified wording regarding leading zeros in datetime strings for better understanding.
Add requirement for leading zeroes in datetime strings.
See issues #624 and #625 for discussion of these changes.
Release checklist
history.adocup to date?For maintainers
After the merge remember to delete the source branch.
Tags are set at the conclusion of the annual meeting; until then,
mainalways is a draft for the next version.