> From: Andy Wingo <wi...@pobox.com> > Cc: Chris Vine <ch...@cvine.freeserve.co.uk>, guile-user@gnu.org > Date: Sun, 26 Feb 2017 21:58:00 +0100 > > On Wed 15 Feb 2017 18:07, Eli Zaretskii <e...@gnu.org> writes: > > > the [Emacs] MS-Windows port pretends towards Emacs internals that file > > names are encoded in UTF-8, and shadows relevant system APIs that > > accept or return file names, like fopen, opendir/readdir, stat, > > etc. with its own versions that convert UTF-8 to and from UTF-16 > > before calling the real OS APIs. > > > > Once again, just use that experience, and maybe even some > > infrastructure code. > > FWIW we are up for good suggestions. It's clear that file names (and > command line arguments and environment variables) aren't handled ideally > in Guile as they aren't fundamentally strings of characters in any > particular encoding, and hence this class of bug.
Let me know what kind of suggestions would help. E.g., if you need a more detailed descriptions of how Emacs goes about these issues, I can do that (guile-devel is probably a better place for that).
