X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Mon, 7 Feb 2011 12:20:24 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: A bug with UTF-8 output in a console Message-ID: <20110207112024.GA24247@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) 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 Feb 7 01:31, Bengt Larsson wrote: > I think I have found a bug with UTF-8 output in a console in a UTF-8 > locale ("C.UTF-8"). If an UTF-8 character straddles a write() boundary, > then the output gets garbled. > > An example program is attached. Thanks for the testcase! I think I fixed the problem in CVS. The handling of truncated multibyte sequences missed to print the so far collected full multibyte sequences. Instead it just returned. Weird that this hasn't been encountered before, but I assume that's because most people started to use mintty instead of the console. Thanks again, 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