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 using filename
On Apr 1 10:01, Warren Young wrote:
On Apr 1, 2015, at 7:34 AM, Corinna Vinschen corinna-cyg...@cygwin.com
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
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't
On Apr 1, 2015, at 7:34 AM, Corinna Vinschen corinna-cyg...@cygwin.com 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
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 filename as
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
*
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 - 06 Jul 2006
, 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 would be a major
redesign in Cygwin that would require considerable
Christopher Faylor wrote:
On Fri, Jul 07, 2006 at 01:14:36PM +0900, SUZUKI Hisao wrote:
Christopher Faylor wrote:
I hate to say this but I really don't like doing things this way. If
we need to use wide character support then it should just be a
wholesale replacement, not a bunch of wrappers
Larry Hall wrote:
SUZUKI Hisao wrote:
[snip]
Yes, I have filled out the assignment form and have sent it to Red
Hat. I hope you can adopt and adapt the patch without any legal
fears now ;-).
P.S.
Based on Cygwin 1.5.20-1, I have updated the UTF-8 patch.
In fact, I have just diff -c'ed
On 06 July 2006 07:28, SUZUKI Hisao wrote:
Sorry, but I cannot access to CVS server because of firewall. So the
patch file was made from the cygwin-1.5.20-1-src.
Here it is, blindly applied to current CVS and then regenerated. I've
checked that it still builds and I've installed and
Dave Korn wrote:
On 06 July 2006 07:28, SUZUKI Hisao wrote:
Sorry, but I cannot access to CVS server because of firewall. So the
patch file was made from the cygwin-1.5.20-1-src.
Here it is, blindly applied to current CVS and then regenerated. I've
checked that it still builds and I've
Christopher Faylor wrote:
On Tue, Jun 27, 2006 at 02:46:56PM +0900, SUZUKI Hisao wrote:
# I should have posted this message to this list from the first.
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
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
On Tue, Jun 27, 2006 at 02:46:56PM +0900, SUZUKI Hisao wrote:
# I should have posted this message to this list from the first.
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
# I should have posted this message to this list from the first.
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
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
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
allowed in
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
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 perfect
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 remind
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.
22 matches
Mail list logo
