The bug which #27273 fixes (for Windows) is really very old, it goes back to a Jan. 11, 2012 (over a year before Julia v0.1 was released!) commit by @jeff.bezanson to j/libc.j (over a year before Julia v0.1 was released!). The comment by @alkorang : The problem was invalid UTF-8 characters from s…

Thank you for your comment. [image] ScottPJones: the characters are not “invalid”, they are completely valid EUC-KR (or CP949) encoded characters They could be valid EUC-KR characters but it does not mean they are valid UTF-8. EUC-KR is not compatible with UTF-8 except ASCII plane. It bother…

[image] alkorang: They could be valid EUC-KR characters but it does not mean they are valid UTF-8 . My point was that calling them “invalid UTF-8” leads people to believe they were supposed to be UTF-8, which was not the case at all. The function correctly returned them using EUC-KR encodin…

Here is an example of the bug on the Mac (with %A instead of %Z, because for some reason on the Mac, the time zone always comes out with the ASCII abbreviation): julia> setlocale(lc) = unsafe_string(ccall((:setlocale,"libc"), Cstring,(Cint,Cstring),0,lc)) setlocale (generic function with 1 method) …

[image] ScottPJones: My point was that calling them “invalid UTF-8” leads people to believe they were supposed to be UTF-8, Right. Instead of saying strftime returns invalid UTF-8, I should say strftime returns EUC-KR string which Julia does not know about it. Other languages mostly support f…

[image] alkorang: Other languages mostly support functions for converting Unicode (mostly ‘UTF-8’) from/to system encoding. In my opinion, Julia also needs to support those features. Yes, definitely. It’s part of what I’d planned to add when I get around to implementing a StrEncodings.jl pac…

[image] UTF8 space/difficulty tradeoffs [image] UTF8 space/difficulty tradeoffs concerned me about the “UTF-8 is always best” mentality, text from the languages of the vast majority of the world’s population generally takes up 50% to 200% more space encoded with UTF-8 This is correct, but a…

[image] ScottPJones: To make myself more clear: I feel that the bugs in strftime and strptime come from a lack of awareness of how character set encodings are used around the world, stemming from this UTF-8 only or centric view. No, it is a bug, plain and simple.

[image] StefanKarpinski: No, it is a bug, plain and simple. I think the fact that nobody on the GitHub discussion recognized that it was an issue with not respecting locale settings, and not some Windows specific problem, illustrates my point. If I hadn’t spoken up by starting this post on D…

[image] StefanKarpinski: it is a bug, plain and simple. Yes, it’s a bug, and in my opinion the main reason is that Julia cannot handle different encodings inside base or stdlib. It may not be a problem if I can use other packages such as StringEncodings.jl, but this happens inside of Julia w…

[image] alkorang: Luckly, we have wchar_t version of strftime and strptime : wcsftime and wcsptime . Actually ccall(:wcsptime, Cwstring, (Cwstring, Cwstring, Ref{TmStruct}), timestr, fmt, tm) fails. julia> r = ccall(:wcsptime, Cwstring, (Cwstring, Cwstring, Ref{TmStruct}), timestr, fmt, tm) …

Strftime & strptime bug #27239 is present on all platforms, not just Windows

Internals & Design

Topic		Replies	Views
Problems with deprecations of islower, lowercase, isupper, uppercase Internals & Design	179	14757	January 1, 2018
Julia's UTF-8 handling [vs. new Python's 3.7 UTF-8 PEP 540] Internals & Design	29	4925	January 24, 2018
Julia install issue (foreign name) New to Julia	16	843	October 20, 2025
Julia 0.7.0-alpha.0 ERROR: PCRE.exec error: UTF-8 error: isolated byte with 0x80 bit set New to Julia	14	1814	June 9, 2018
Changes to the representation of Char Internals & Design	14	2990	December 12, 2017

Strftime & strptime bug #27239 is present on all platforms, not just Windows

Related topics