This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 3 Jun 2009 12:02:25 -0400
- Subject: Re: 1.7.0-48: [BUG] Passing characters above 128 from bash command line
- References: <4A200287.8030403@sidefx.com> <3f0ad08d0905290852xe41338alfda89c622f92f677@mail.gmail.com> <4A200BC0.9010704@sidefx.com> <e2480c70905291142o2bcc65ccw2287d175dbd09dd5@mail.gmail.com> <4A204149.2050009@sidefx.com> <e2480c70905291337g6c8bcca7xd0baba79c84629db@mail.gmail.com> <4A2051E5.6060600@sidefx.com> <20090602205440.GF23519@calimero.vinschen.de> <4A26782C.9040207@sidefx.com> <20090603142755.GM23519@calimero.vinschen.de>
- Reply-to: cygwin at cygwin dot com
On Wed, Jun 03, 2009 at 04:27:55PM +0200, Corinna Vinschen wrote:
>On Jun 3 09:18, Edward Lam wrote:
>> Corinna Vinschen wrote:
>>> The question is, what do you expect? [...]
>> [...]
>> Wikipedia has several suggestions on how to handle invalid UTF-8 byte
>> sequences (http://en.wikipedia.org/wiki/UTF-8). Personally, I favor the
>> rule that uses the replacement character.
>
>Chris implemented using the invalid code point solution. The discussion
>in http://www.mail-archive.com/linux-utf8@nl.linux.org/msg00080.html
>supports this solution. What's missing so far is the way back, from
>an invalid single second half of a surrogate pair in the 0xDCxx range
>back to the correct byte value. I'm just looking into that.
The way back was not, AFAIK, needed for Cygwin programs. I don't think
there is a valid way back for Windows programs.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/