www.delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS |
X-Spam-Check-By: | sourceware.org |
MIME-Version: | 1.0 |
In-Reply-To: | <26777598.post@talk.nabble.com> |
References: | <26774467 DOT post AT talk DOT nabble DOT com> <20091214105915 DOT GF8059 AT calimero DOT vinschen DOT de> <26776766 DOT post AT talk DOT nabble DOT com> <20091214123509 DOT GI8059 AT calimero DOT vinschen DOT de> <26777598 DOT post AT talk DOT nabble DOT com> |
Date: | Mon, 14 Dec 2009 13:44:12 +0000 |
Message-ID: | <416096c60912140544g380fe8b3s261b32a4894be97d@mail.gmail.com> |
Subject: | Re: Cygwin 1.7: Empty/white-space output when display Chinese characters in GBK charset encoding? |
From: | Andy Koppe <andy DOT koppe AT gmail DOT com> |
To: | cygwin AT cygwin DOT com |
X-IsSubscribed: | yes |
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 |
2009/12/14 LiuYan =E5=88=98=E7=A0=94: > > The only unexpected thing is the empty output of GBK-encoded chinese > characters when LANG is xxxx.UTF-8. > > I mean it should display something visible(malformed characters, squares = or > whatever visible characters) regardless the LANG setting. > > echo -e "Chinese characters in GBK encoding: [\xba\xba\xd7\xd6] =C2=A0-- = Output > will be [ =C2=A0 =C2=A0] in Cygwin 1.7" I'm getting: $ echo -e "Chinese characters in GBK encoding: [\xba\xba\xd7\xd6]" Chinese characters in GBK encoding: [=E2=96=92=E2=96=92=E2=96=92=E2=96=92] (In case they don't show up, that's four grey blocks in the brackets, representing invalid UTF-8 bytes.) Same both with the default raster font and with Lucida Console. With the default raster font, the output is limited to your console codepage, which may not have that replacement character, so try it with a different font that puts the console into Unicode mode. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |