On May 12 15:53, Mark J. Reed wrote: > On Tue, May 12, 2009 at 3:22 PM, Corinna Vinschen > > > > http://cygwin.com/1.7/cygwin-ug-net/using-specialnames.html#pathnames-unusual > > OK, got it. So Mr. Iwamuro's proposal is that Cygwin ignore the > locale setting, and just automatically convert the Windows UTF-16 > filenames to UTF-8 (and back) no matter what.
No. Only if LANG=C. > That seems rife with possible confusion, though. If I have my codepage > set to ISO-2022 and paste in a filename, I expect it to be interpreted Cygwin 1.7 doesn't use the codepage. It uses what $LANG says. See http://cygwin.com/1.7/cygwin-ug-net/setup-locale.html > as ISO-2022, not as UTF-8 (which will probably fail with an invalid > encoding sequence). > > OTOH, the SO/UTF-8 hack would seem to bode ill for the portability of, > say, tar archives created under Cygwin. The filenames potentially look weird, but they are valid filenames. If anybody has a better idea how to workaround the problem of UTF-16 chars which don't translate into the current singlebyte or multibyte charset, feel free to suggest. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/
