X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Lapo Luchini Subject: Re: non-BMP character width Date: Mon, 21 Sep 2009 18:52:55 +0200 Lines: 22 Message-ID: References: <200909161148 DOT n8GBm4ha001469 AT mail DOT bln1 DOT bf DOT nsn-intra DOT net> <20090921163348 DOT GL20981 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit User-Agent: Thunderbird 2.0.0.23 (X11/20090831) In-Reply-To: <20090921163348.GL20981@calimero.vinschen.de> OpenPGP: id=C8F252FB 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 Corinna Vinschen wrote: > On Sep 16 13:48, Thomas Wolff wrote: >> Hi, >> I see one small remaining glitch with Unicode display; non-BMP characters >> (those with Unicode value > 0xFFFF) are displayed as two boxes. > > Can you please create a simple self-contained testcase? I'm not exactly > sure how this is supposed to work and if a solution exists. Is that a > problem for the non-UTF-8 case, too, or for UTF-8 only? I guess he meant anything like U+10001, which seems to be assigned to linear-B charset on the DecodeUnicode database: 𐀁 = http://www.decodeunicode.org/U+10001 UTF-8 as F0 90 80 81 Or this (Iguess that's traditional Chinese?) example taken from en.wiki: 𤭢 = http://www.decodeunicode.org/U+24B62 UTF-8 as F0 A4 AD A2 -- Lapo Luchini - http://lapo.it/ -- 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