Re: SOLVED: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-11-02 Thread Corinna Vinschen
On Nov 2 19:16, Andy Koppe wrote: > 2009/11/2 Corinna Vinschen: > >> >> You must not use characters > >> >> in this range from U+f000 up to U+f0ff.  There's no solution to this > >> >> except for "don't use these characters in filenames if they are not > >> >> explicitely written there by either C

Re: SOLVED: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-11-02 Thread Andy Koppe
2009/11/2 Corinna Vinschen: >> >> You must not use characters >> >> in this range from U+f000 up to U+f0ff.  There's no solution to this >> >> except for "don't use these characters in filenames if they are not >> >> explicitely written there by either Cygwin or Microsoft's SUA". >> >> Actually the

Re: SOLVED: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-11-02 Thread Corinna Vinschen
On Oct 31 20:33, Andy Koppe wrote: > >> You must not use characters > >> in this range from U+f000 up to U+f0ff.  There's no solution to this > >> except for "don't use these characters in filenames if they are not > >> explicitely written there by either Cygwin or Microsoft's SUA". > > Actually t

Re: SOLVED: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-10-31 Thread Steven Monai
Andy Koppe wrote: > Any idea how that U+f020 character had got in there in the first place? Someone probably discovered the Windows Character Map app, and decided it would be fun to put some weird chars into their filenames. I guess I'll have to ask my colleagues not to use chars from the Unicode

Re: SOLVED: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-10-31 Thread Andy Koppe
2009/10/31 Steven Monai: >> That's the problem.  The character in that file is *not* U+0323, but >> U+f020, a character in the Unicode private use range, which is used in >> Cygwin to map ASCII characters invalid in Windows filenames but valid >> in POSIX filenames.  It's also used to map multibyte

SOLVED: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-10-31 Thread Steven Monai
Corinna Vinschen wrote: >>22 12422 [main] ls 1300 fhandler_disk_file::readdir_helper: wchar >> filename: "Mikey12\xf020.ai" > > That's the problem. The character in that file is *not* U+0323, but > U+f020, a character in the Unicode private use range, which is used in > Cygwin to map ASCII

Re: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-10-29 Thread Steven Monai
Corinna Vinschen wrote: > Can I send you a link to another Cygwin > DLL in private email, which I tweaked to get better debug output? Yes, of course. I greatly appreciate your interest in trying to resolve this problem. -SM -- -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-10-29 Thread Corinna Vinschen
On Oct 28 12:58, Steven Monai wrote: > Corinna Vinschen wrote: > > I'm seriously puzzled. Could you please run > > > > $ strace -o ls.trace ls -l weird/ > > > > and send the ls.trace file as attachment? Maybe there's some hint > > in it. > > Done. Thanks. Unfortunately it's not very helpfu

Re: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-10-28 Thread Steven Monai
Corinna Vinschen wrote: > I'm seriously puzzled. Could you please run > > $ strace -o ls.trace ls -l weird/ > > and send the ls.trace file as attachment? Maybe there's some hint > in it. Done. -SM -- 3 3 [main] ls 288 open_shared: name shared.5, n 5, shared 0x60FC (wanted 0x

Re: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-10-27 Thread paul . hermeneutic
On Tue, Oct 27, 2009 at 09:11, Thomas Wolff wrote: > I agree absolutely. This setting is needed for many apps and I suggest > adding it to the default cygwin.bat, where it should probably be > 'set LC_CTYPE=C.UTF-8' to be more specific and to avoid a national > preference. If it is to be added to

Re: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-10-27 Thread Thomas Wolff
ext Andy Koppe wrote: 2009/10/27 Corinna Vinschen: I added 'set LC_ALL=en_US.UTF-8' (without the quotes) to Cygwin.bat, as suggested in the Internationalization section of the 1.7 User Guide, but there was no improvement. Uh oh, I guess this must be changed again in the docs. Cygwin

Re: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-10-27 Thread Andy Koppe
2009/10/27 Corinna Vinschen: >> I added 'set LC_ALL=en_US.UTF-8' (without the quotes) to Cygwin.bat, as >> suggested in the Internationalization section of the 1.7 User Guide, but >> there was no improvement. > > Uh oh, I guess this must be changed again in the docs.  Cygwin is using > UTF-8 throug

Re: Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-10-27 Thread Corinna Vinschen
On Oct 26 19:26, Steven Monai wrote: > Hello folks, > > I recently removed Cygwin 1.5.25 from a WindowsXP box (as per FAQ # > 2.17), and then installed the Cygwin 1.7.0 beta in its place. The > install seemed to go flawlessly. I was looking forward to having more > robust handling of filenames wit

Removed 1.5.25 and installed 1.7.0, but still cannot access filenames containing Unicode

2009-10-26 Thread Steven Monai
Hello folks, I recently removed Cygwin 1.5.25 from a WindowsXP box (as per FAQ # 2.17), and then installed the Cygwin 1.7.0 beta in its place. The install seemed to go flawlessly. I was looking forward to having more robust handling of filenames with Unicode chars, but unfortunately, I'm not havin