X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Tue, 4 Mar 2008 13:21:11 +0100
From:	Paul-Kenji Cahier <pkc AT F1-Photo DOT com>
X-Mailer:	The Bat! (v3.99.24) Professional
Reply-To:	Paul-Kenji Cahier <pkc AT F1-Photo DOT com>
Message-ID:	<39555993.20080304132111@F1-Photo.com>
To:	cygwin AT cygwin DOT com
Subject:	Re[2]: ZSH - UTF-8
In-Reply-To:	<20080304093652.GO18407@calimero.vinschen.de>
References:	<13510047732 DOT 20080303203325 AT F1-Photo DOT com> <20080304091535 DOT 168 AT blackhawk> <447314643 DOT 20080304035937 AT F1-Photo DOT com> <20080304093652 DOT GO18407 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

>>?LC_ALL set to C.UTF-8 in all cases. Cygwin freshly installed.
>>?Also tried LC_ALL=en_US.UTF-8(which shouldnt exist) and it did
>>?not work either.

>?Newlib uses "C-UTF-8", not "C.UTF-8" for some reason.  I don't see that
>?newlib understands the dot.  Moreover, Cygwin doesn't support utf-8 yet,
>?so you might have strange effects using utf-8 for filenames.

>?Corinna

(this time text under quote, didnt know it bothered)

I'm still failing to get zsh working with utf-8, even
with C-UTF-8 as LC_ALL: as specified in my previous message
non-ascii bytes get displayed as <00cxx> which the line editor
does manage properly. But there is still no way to actually see
utf-8 characters displayed, or even their unicode values(ie
it's still a single byte editing mode). If someone manages
to get it working, please post:)

Also I know about the lack of utf-8 support in cygwin for most
of the windows calls(and personally think that the cygwin utf-8
wrapper code patch would be a vast improvement, that is the one
from okisoft that got posted to cygwin's ml long ago, though
I understand some people dont like how it's done). This should
still not be a problem for one to do an "echo éé<backspace>"
in his term transparently.
(no problematic wide windows calls involved there as far as I know).

Paul-Kenji Cahier


--
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/

- Raw text -