Re: With bad UTF-8, cygwin can create files it can't read

2015-04-01 Thread Corinna Vinschen
On Apr 1 10:01, Warren Young wrote: > On Apr 1, 2015, at 7:34 AM, Corinna Vinschen > wrote: > > > > As you probably know, Unicode values beyond the base plane (that is, > > everything > 0x in UTF-32 and > ef bf bf in UTF-8 notation) > > are represented as so-called surrogate pairs in UTF-16

Re: With bad UTF-8, cygwin can create files it can't read

2015-04-01 Thread Corinna Vinschen
On Apr 1 15:34, Corinna Vinschen wrote: > Hi Stuart, > > On Mar 30 13:04, Corinna Vinschen wrote: > > On Mar 25 14:34, Kyzer wrote: > > > Hello, > > > > > > I've found that if you use cygwin to create a file with badly-encoded > > > UTF-8, readdir() gives out an entry with a name that cygwin won

Re: With bad UTF-8, cygwin can create files it can't read

2015-04-01 Thread Warren Young
On Apr 1, 2015, at 7:34 AM, Corinna Vinschen wrote: > > As you probably know, Unicode values beyond the base plane (that is, > everything > 0x in UTF-32 and > ef bf bf in UTF-8 notation) > are represented as so-called surrogate pairs in UTF-16, two UTF-16 > values in the 0xd800 - 0xdfff range

Re: With bad UTF-8, cygwin can create files it can't read

2015-04-01 Thread Corinna Vinschen
Hi Stuart, On Mar 30 13:04, Corinna Vinschen wrote: > On Mar 25 14:34, Kyzer wrote: > > Hello, > > > > I've found that if you use cygwin to create a file with badly-encoded > > UTF-8, readdir() gives out an entry with a name that cygwin won't > > subsequently accept. > > > > * create a file usin

Re: With bad UTF-8, cygwin can create files it can't read

2015-03-30 Thread Corinna Vinschen
On Mar 25 14:34, Kyzer wrote: > Hello, > > I've found that if you use cygwin to create a file with badly-encoded > UTF-8, readdir() gives out an entry with a name that cygwin won't > subsequently accept. > > * create a file using filename with hex bytes F4 8F BF BF > * readdir() reports the filen

With bad UTF-8, cygwin can create files it can't read

2015-03-25 Thread Kyzer
Hello, I've found that if you use cygwin to create a file with badly-encoded UTF-8, readdir() gives out an entry with a name that cygwin won't subsequently accept. * create a file using filename with hex bytes F4 8F BF BF * readdir() reports the filename as hex bytes E2 8E B3 ED BF BF * attemptin

Re: UTF-8 Cygwin

2006-08-16 Thread Christopher Faylor
t;(cygwin-patches mail list, thread "UTF-8 Cygwin", 26 Jun - 06 Jul >2006), and Christopher's arguments didn't convince me: as it appears, >it was mostly an issue with function wrappers not being a solution as >clean and elegant as the ideal. The alternative woul

Re: UTF-8 Cygwin

2006-08-16 Thread Paulo Castro
Hello. I would like to ask that the decision to reject Mr Suzuki Hisao's patch to include UTF-8 file name support in Cygwin was reconsidered. I've read the discussion between Mr Suzuki Hisao and Mr Christopher Faylor (cygwin-patches mail list, thread "UTF-8 Cygwin", 26 Jun

Re: UTF-8 Cygwin

2006-07-05 Thread SUZUKI Hisao
Based on Cygwin 1.5.20-1, I have updated the UTF-8 patch, which modifies filename handling and console I/O to support UTF-8 encoding. In fact, I have just "diff -c"'ed the old ones and have patch'ed the results to cygwin-1.5.20-1-src, except for sys_wcstombs() in miscfuncs.cc. Its definition diff

Re: UTF-8 Cygwin

2006-06-26 Thread Igor Peshansky
On Mon, 26 Jun 2006, Linda Walsh wrote: > Christopher Faylor wrote: > > On Tue, Jun 06, 2006 at 02:24:29PM -0700, Linda Walsh wrote: > > > > > SUZUKI Hisao wrote: > > > > > > > I made a patch to cygwin1.dll to support UTF-8. > > > > It allows you to use all of characters and file (or path) names >

Re: UTF-8 Cygwin

2006-06-26 Thread Linda Walsh
Christopher Faylor wrote: On Tue, Jun 06, 2006 at 02:24:29PM -0700, Linda Walsh wrote: SUZUKI Hisao wrote: I made a patch to cygwin1.dll to support UTF-8. It allows you to use all of characters and file (or path) names allowed in Windows, while keeping binary-compatibility with the curr

Re: UTF-8 Cygwin

2006-06-06 Thread Christopher Faylor
On Tue, Jun 06, 2006 at 02:24:29PM -0700, Linda Walsh wrote: >SUZUKI Hisao wrote: >>I made a patch to cygwin1.dll to support UTF-8. >> >>It allows you to use all of characters and file (or path) names >>allowed in Windows, while keeping binary-compatibility with the >>current Cygwin. It is fairly

Re: UTF-8 Cygwin

2006-06-06 Thread Linda Walsh
When will we see this in the main-stream cygwin? Soon? :-) linda SUZUKI Hisao wrote: I made a patch to cygwin1.dll to support UTF-8. It allows you to use all of characters and file (or path) names allowed in Windows, while keeping binary-compatibility with the current Cygwin. It is fairly perf

Re: UTF-8 Cygwin

2006-06-02 Thread Larry Hall (Cygwin)
SUZUKI Hisao wrote: > I made a patch to cygwin1.dll to support UTF-8. > > It allows you to use all of characters and file (or path) names > allowed in Windows, while keeping binary-compatibility with the > current Cygwin. It is fairly perfect except for lack of locale > support etc. So it may re

UTF-8 Cygwin

2006-06-01 Thread SUZUKI Hisao
I made a patch to cygwin1.dll to support UTF-8. It allows you to use all of characters and file (or path) names allowed in Windows, while keeping binary-compatibility with the current Cygwin. It is fairly perfect except for lack of locale support etc. So it may remind you of the good old BeOS.