From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2574 invoked by alias); 5 Dec 2004 21:41:32 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 2564 invoked from network); 5 Dec 2004 21:41:28 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 5 Dec 2004 21:41:28 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1Cb483-0006It-2k; Sun, 05 Dec 2004 16:41:15 -0500 Date: Sun, 05 Dec 2004 23:39:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: Baurjan Ismagulov , gdb-patches@sources.redhat.com Subject: Re: i18n, part 2 Message-ID: <20041205214115.GA24180@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , Baurjan Ismagulov , gdb-patches@sources.redhat.com References: <20041204195702.GA25306@ata.cs.hun.edu.tr> <20041204200605.GA15732@nevyn.them.org> <20041204215404.GA2413@ata.cs.hun.edu.tr> <01c4db12$Blat.v2.2.2$4dfdf600@zahav.net.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01c4db12$Blat.v2.2.2$4dfdf600@zahav.net.il> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-12/txt/msg00137.txt.bz2 On Sun, Dec 05, 2004 at 11:34:10PM +0200, Eli Zaretskii wrote: > This code produces a complete sentence one word at a time, which I > think is bad for translating. I think the code needs to be rewritten > to have full sentences like these: > > "tid %d, %s, suspended, detached, cancel pending" > "tid %d, %s, detached, cancel pending" > "tid %d, %s, cancel pending" > "tid %d, %s" > "tid %d, %s, suspended, cancel pending" > "tid %d, %s, suspended, detached" > "tid %d, %s, detached, cancel pending" > "tid %d, %s, detached" > > etc. That makes the code less clever, but the translation is much > easier. As the code is now, it will be almost impossible to get right > in some languages. Yuck! What if someone wants to add another status? I understand that there is a translation problem here, but I find it really hard to accept that enumerating exponential combinations is really the solution. I suspect either: - the message needs to be redesigned in some more friendly way - we need a more friendly way to output a list of translated statuses - or else we need to leave the status message untranslated pending some thought on the above. -- Daniel Jacobowitz