Ah, but, wait. $ touch àéù.txt
$ guile3.0 scheme@(guile-user)> (open-file "àéù.txt" "r") $1 = #<input: àéù.txt 13> ~/tmp $ LC_ALL=C guile3.0 scheme@(guile-user)> (open-file "àéù.txt" "r") ice-9/boot-9.scm:1685:16: In procedure raise-exception: In procedure open-file: No such file or directory: "??????.txt" OK, so Guile is assuming that the locale encoding determines the encoding of file names (which is quite reasonable), and so, when run under the C locale, it's transforming non-ASCII characters into question marks before resolving the path, as part of converting to the locale encoding. Can someone remind me why the build system sets the C locale in the first place?
signature.asc
Description: This is a digitally signed message part
