Eli Zaretskii <e...@gnu.org> writes: > Windows stores file names on disk encoded in UTF-16, but converts them > to the current codepage if you use Posix-style interfaces like 'open' > and 'rename'. (There are parallel APIs that accept UTF-16 encoded > file names.)
Okay, so on Windows we should use the parallel APIs that accept UTF-16,
thus (apparently) completely avoiding the issue on that platform.
Mark
