X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 21 Sep 2009 18:33:49 +0200 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: non-BMP character width Message-ID: <20090921163348.GL20981@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <200909161148.n8GBm4ha001469@mail.bln1.bf.nsn-intra.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200909161148.n8GBm4ha001469@mail.bln1.bf.nsn-intra.net> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com 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. > The reason is probably related to their representation as two > surrogates at some point. > I do not expect to have visible display of non-BMP in the cygwin > console, esp. as the two available console fonts, Raster and Lucida, > don't support them anyway. But they should at least have the proper > width, i.e. one box instead of two. 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? 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