You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That 06-01 is normally going to be read by many people outside the US as January 6th, not as June 1st. I'm not sure how to make it unambiguous without including the year or spelling out the month name.
The text was updated successfully, but these errors were encountered:
timparenti
added a commit
to timparenti/channeltime
that referenced
this issue
Sep 2, 2019
Use month abbreviations instead of numeric months, since day-of-week
abbreviation is already locale-dependent anyway. Putting the day-of-month
before the month abbreviation avoids the need for a comma after the
day-of-week.
Resolvesmonkbroc#5.
The existing format is actually already close to the format specified in ISO.8601.2000 (and referenced in RFC 6350) for dates without a year specified. --06-01, for instance, refers to 1 June in any year, as with a birthday or anniversary. However, that is not the context in which dates are being presented by this application.
Since the day-of-week is already being presented in a locale-dependent format, a month abbreviation can similarly be used, which resolves the potential ambiguity. #11 prefers to put the day-of-month before the month abbreviation to avoid the need for a separating comma; e.g., Fri 1 Jun instead of Fri, Jun 1.
/time tomorrow at noon
posted on May 31st generates a message that states:That 06-01 is normally going to be read by many people outside the US as January 6th, not as June 1st. I'm not sure how to make it unambiguous without including the year or spelling out the month name.
The text was updated successfully, but these errors were encountered: