X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 4 Mar 2008 16:05:46 -0800 (PST) From: "Peter A. Castro" To: Paul-Kenji Cahier cc: cygwin AT cygwin DOT com Subject: Re[2]: ZSH - UTF-8 In-Reply-To: <39555993.20080304132111@F1-Photo.com> Message-ID: 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> <39555993 DOT 20080304132111 AT F1-Photo DOT com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-1463811017-270908215-1204675546=:11811" X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com ---1463811017-270908215-1204675546=:11811 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 4 Mar 2008, Paul-Kenji Cahier wrote: Greetings, Paul-Kenji, >>> ?LC_ALL set to C.UTF-8 in all cases. Cygwin freshly installed. >>> ?Also tried LC_ALL=3Den_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:) Can you send me the specific key sequence you are using to generate this? Are you using a CMD window or rxvt or an xterm? Also, are you using the stock zsh 4.3.5 source distro or have you applied the Cygwin patches from 4.3.4 to it before building? I've recently built 4.3.5 for Cygwin and have been testing it before releasing it. Send me the key sequences you are using and I'll see if I can repro it. As Corinna noted, Cygwin doesn't really support utf-8, so this might have some bearing on the matter. And, you should know that some multi-byte delete issues have been identified on other, supposedly, UTF-8 compliant systems, so you aren't the first to hit this. > 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 =E9=E9" > 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/ > --=20 Peter A. Castro or "Cats are just autistic Dogs" -- Dr. Tony Attwood ---1463811017-270908215-1204675546=:11811 Content-Type: text/plain; charset=us-ascii -- 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/ ---1463811017-270908215-1204675546=:11811--