This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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 there is a possible solution: when translating a U+F0xx
> character, first check whether the xx byte really is illegal in the
> target charset. If it's not, it won't roundtrip correctly, so encode
> the U+F0xx as a ^X sequence instead. Doesn't seem worth the effort
> though.

I was contemplating this over the weekend.  I just applied a patch to
do this.  I tested this with various filenames containing all sorts
of characters, including f000, which would represent an ASCII NUL, if
used wrongly.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]