Re:ISO-8601, YYYY, yyyy, and why your year may be wrong
by wool_gather on Wednesday December 26, 2018 @10:56AM
(#18762721)
> they will certainly have very different formats
Not necessarily; as the article discussed, the format characters are part of a Unicde standard. Apple/Swift Foundation uses the ICU library[0] for the heavy lifting of date formatting, which is certainly widely available (by design).
Re:ISO-8601, YYYY, yyyy, and why your year may be wrong
by marcosdumay on Wednesday December 26, 2018 @12:01PM
(#18763150)
That reference seems to be offline at the moment...
I don't think it's widely used. It is great that some standards body took that problem into their scope, but it may take a long while until most languages agree on anything here.
Re:ISO-8601, YYYY, yyyy, and why your year may be wrong
by tedunangst on Wednesday December 26, 2018 @01:57PM
(#18763928)
Yeah, what crazy obscure languages expose a binding to strftime???
Re:ISO-8601, YYYY, yyyy, and why your year may be wrong
by saagarjha on Wednesday December 26, 2018 @05:32PM
(#18765481)
> I don't think it's widely used.
You may wish to look at this: http://site.icu-project.org/#TOC-Who-Uses-ICU-
Re:ISO-8601, YYYY, yyyy, and why your year may be wrong
by hafthor on Wednesday December 26, 2018 @02:27PM
(#18764150)
Java affected in exactly the same way.
Re:ISO-8601, YYYY, yyyy, and why your year may be wrong
by johnlbevan2 on Friday December 28, 2018 @05:20AM
(#18775977)
I thought the same; context is everything; this isn't an issue with a date format, but a date format when used by a specific language (or specific languages).
I understand other languages may have similar problems, but they will certainly have very different formats.