From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16030 invoked by alias); 24 Jan 2006 22:10:23 -0000 Received: (qmail 16020 invoked by uid 22791); 24 Jan 2006 22:10:23 -0000 X-Spam-Check-By: sourceware.org Received: from gandalf.inter.net.il (HELO gandalf.inter.net.il) (192.114.186.17) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 24 Jan 2006 22:10:21 +0000 Received: from nitzan.inter.net.il (nitzan.inter.net.il [192.114.186.20]) by gandalf.inter.net.il (MOS 3.7.1-GA) with ESMTP id HRE00345; Wed, 25 Jan 2006 00:10:15 +0200 (IST) Received: from HOME-C4E4A596F7 (IGLD-80-230-153-138.inter.net.il [80.230.153.138]) by nitzan.inter.net.il (MOS 3.7.3-GA) with ESMTP id CNU16541 (AUTH halo1); Wed, 25 Jan 2006 00:10:14 +0200 (IST) Date: Tue, 24 Jan 2006 22:10:00 -0000 Message-Id: From: Eli Zaretskii To: gdb-patches@sourceware.org In-reply-to: <20060124214858.GA27783@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 24 Jan 2006 16:48:58 -0500) Subject: Re: RFC: Clean up "show remote" Reply-to: Eli Zaretskii References: <20060122201759.GA28863@nevyn.them.org> <20060123051544.GA5009@nevyn.them.org> <20060124165326.GA19716@nevyn.them.org> <20060124214858.GA27783@nevyn.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-01/txt/msg00385.txt.bz2 > Date: Tue, 24 Jan 2006 16:48:58 -0500 > From: Daniel Jacobowitz > > Asking the translator do it defeats my goal - which is to adapt to the > user's terminal width, automatically. That's true, but does this work well with non-Latin scripts (i.e. those where the characters' widths are not equal)? > Right now the GDB CLI is generally run either in a TTY or in some > wrapping environment (e.g. emacs). I don't know much about the Emacs > case, The Emacs case is not interesting: Emacs disables the wrapping (both horizontal and vertical) and wraps itself, according to its rules and user's preferences. > but at least on a TTY, when we encounter the terminal's physical > margins we wrap - always. No matter where we are within a word. You mean, the TTY wraps, yes? > How is wrapping after spaces, as suggested by the Unicode TR but > without the remaining complexity of the TR, inferior to that? It might not work at all, when there are not enough spaces in the line. Which is not worse than what we have now, but at least now we don't claim we have this feature. > We'd check widths and space characters on the results of gettext, of > course, using appropriate wide character routines. Will this work on terminal emulators in a graphical environment, such as xterm? Won't we need some knowledge about the font? > There are probably some cases where this would lead to oddly placed > line breaks. I'm hypothesizing that there would be fewer oddly placed > line breaks even in the affected scripts than there are today. Maybe, I don't know. Anyway, since we don't yet support i18n, perhaps we shouldn't worry now about implementing Unicode line-breaking, or even subset thereof. There are more important things to do, I think. (Although, having once written a very unorthodox implementation of the Unicode Bidirectional Algorithm--see UAX#9 on the Unicode site--I can easily understand how tempting can it be to sit down and implement a significant subset of the line-breaking algorithm ;-)