It's a bug. There have been bugs on and off with guile utf8 handling. One of the guile-2.0 versions does almost everything right, but utf8 is semi-broken, again in 2.2 -- some things work, but various things that used to work great are now broken (again). I'm guessing that guile has a weak/non-existent unit-test suite for utf8.
Open bug reports. I could even (maybe) volunteer to fix some of them, cause I know where they are, and why they are, but would need encouragement/help from one of the core guile devs to create acceptable patches. (I'm doing Chinese text processing in guile, right now, so each of these bugs is painful to hit, and requires yet another work-around in my code.) --linas On Mon, Nov 28, 2016 at 2:54 AM, Thomas Morley <[email protected]> wrote: > 2016-11-27 13:16 GMT+01:00 Chaos Eternal <[email protected]>: >> Seems that UTF-8 encoded string has been converted to unicode before calling >> `open', >> but on filesystem the filename is utf8 string > > Your analysis is surely correct, but what to do? > I expected > guile filename_名字.scm > to work out of the box. > > Am I missing something? > Or is it a bug, worth reporting? > > Cheers, > Harm >
