On Thu, 15 May 2008, Marc Lehmann wrote: > On Wed, May 14, 2008 at 11:55:40PM +0200, demerphq <demerphq@gmail.com> wrote: > From what I saw, however, filename handling on win32 is broken beyond > repair, as much of the win32 code overloads the utf-8 flag with the > additional meaning "unicode encoded, not ansi codepage" (see for example > almost all functions dealing with paths in Win32.xs). Why is this beyond repair? The problem of course is that Perl on Windows assumes that strings without the utf-8 flag are encoded with Latin-1 encoding whereas they really are ANSI encoded. So once the automatic upgrading assumes ANSI encoding instead of Latin-1, everything should be working correctly, no? Cheers, -Jan