This is the mail archive of the
mailing list for the Cygwin project.
Re: using rsync with Win32/UNC pathnames?
On Apr 14 13:15, Tomasz Chmielewski wrote:
> Corinna Vinschen schrieb:
>> On Apr 14 11:30, Tomasz Chmielewski wrote:
>>> Corinna Vinschen schrieb:
>>>> On Apr 12 13:15, Tomasz Chmielewski wrote:
>>>>> Corinna Vinschen schrieb:
>>>>>> What's the wchar hex code value of that character?
>>>>> Hmm, I don't know.
>>>>> Is there some obvious way to get it?
>>>> You could write a small application which does nothing but calling
>>>> FindFirstFileW/FindNextFileW and print the found file names as hex
>>> ...which sounds much more complicated than just copying the file to
>>> another machine.
>> I don't do remote debugging. If you want this fixed, find a method to
>> provide the file as zip attachment to this mailing list. Or, cd to the
>> directory in which the file is stored and run the below application. It
>> builds OOTB if you have gcc installed. Just call `gcc -o foo foo.c'.
>> ============ foo.c ==================
> It says (where "?" substitutes this strange character):
> 1?.doc (1): 0031 f021 002e 0064 006f 0063
> So that character is "f021".
I should have thought about that from the beginning. Well, there's no
workaround and there will be no patch for this. The problem is that
this character value is within the 0xf000-0xf0ff range. This range is
part of the UNICODE block 95, "Private Use Area". There is by
definition no valid UNICODE character assigned within this area and
Cygwin reserves the right to use this 0xf000-0xf0ff for its own
purposes. Besides, I have a hard time to imagine how a user could
create a filename with this value except wantonly.
The range from 0xf000-0xf0ff is used by Cygwin 1.7.0 to map special
characters which are disallowed in DOS filenames. You can use every
other UNICODE character in Cygwin, except for these values.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html