Re: [1.7] Proposal: the filename encoding in C locale uses UTF-8 instead of SO/UTF-8

[Andy Koppe <andy dot koppe at gmail dot com>]

> - why do you need to touch the filename at all? I haven't read all of it. Is
> the UTF-16 on disk and we need to work around UTF-16 being intractable as C
> string?

Yes. If you simply treated each UTF-16 symbol as two chars, you'd get
unintended NULs and slashes. For starters, the upper halves of all
ISO-8859-1 characters are NUL in UTF-16. And even without that, the
resulting filenames would be completely unusable.

Andy

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/