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
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
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
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
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
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
6 matches
Mail list logo
