bug#35920: strftime incorrectly assumes that nstrftime will produce UTF-8

2019-05-26 Thread Christopher Lam
Thanks! I'm glad to know this. I have adequate fluency in guile now but very basic C hence some bugs are very opaque to me. On Mon., 27 May 2019, 04:43 Mark H Weaver, wrote: > Hi Christopher, > > Christopher Lam writes: > > > Addendum - wish to confirm if guile bug (guile-2.2 on Windows): > > -

bug#35920: strftime incorrectly assumes that nstrftime will produce UTF-8

2019-05-26 Thread Mark H Weaver
Here's a patch that might fix the problem, but I don't have time to test it right now. Mark --8<---cut here---start->8--- diff --git a/libguile/stime.c b/libguile/stime.c index b681d7ee3..9a21b61fe 100644 --- a/libguile/stime.c +++ b/libguile/stime.c @@

bug#35920: strftime incorrectly assumes that nstrftime will produce UTF-8

2019-05-26 Thread Mark H Weaver
There might also be related problems with 'strptime'. These problems date back to when Guile was first extended to support non-ASCII strings. Here's the relevant commit in 2009 that added non-ASCII support to 'strftime' and 'strptime', but did so imperfectly: 587a33556fdef90025c1b7d4d172af649c8ebb

bug#35920: strftime incorrectly assumes that nstrftime will produce UTF-8

2019-05-26 Thread Mark H Weaver
Hi Christopher, Christopher Lam writes: > Addendum - wish to confirm if guile bug (guile-2.2 on Windows): > - set locale to non-Anglo so that (setlocale LC_ALL) returns > "French_France.1252" > - call (strftime "%B" 400) - that's 4x10^6 -- this should return > "février 1970" > > but the foll