X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 21 Sep 2009 19:57:59 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: non-BMP character width Message-ID: <20090921175759.GM20981@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com 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=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-02-20) 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 On Sep 21 18:52, Lapo Luchini wrote: > 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: Sure. I was specificially asking for a testcase, preferrably in plain C, which allows to reproduce this under a debugger. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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