From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15395 invoked by alias); 7 Dec 2004 05:08:39 -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 15372 invoked from network); 7 Dec 2004 05:08:36 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 7 Dec 2004 05:08:36 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1CbXaI-0003hc-20; Tue, 07 Dec 2004 00:08:22 -0500 Date: Tue, 07 Dec 2004 05:10:00 -0000 From: Daniel Jacobowitz To: Eli Zaretskii Cc: Kevin Buettner , gdb-patches@sources.redhat.com Subject: Re: i18n, part 2 Message-ID: <20041207050821.GD4648@nevyn.them.org> Mail-Followup-To: Eli Zaretskii , Kevin Buettner , gdb-patches@sources.redhat.com References: <20041204195702.GA25306@ata.cs.hun.edu.tr> <20041206103930.6bca4814.kevinb@redhat.com> <01c4dbd5$Blat.v2.2.2$98515300@zahav.net.il> <20041206155114.6bab8d59.kevinb@redhat.com> <01c4dc19$Blat.v2.2.2$c62c4660@zahav.net.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <01c4dc19$Blat.v2.2.2$c62c4660@zahav.net.il> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-12/txt/msg00193.txt.bz2 On Tue, Dec 07, 2004 at 07:00:10AM +0200, Eli Zaretskii wrote: > > Date: Mon, 6 Dec 2004 15:51:14 -0700 > > From: Kevin Buettner > > > > The code in question is simply outputting a list of attributes > > associated with a particular thread. How should we make the necessary > > context available to the translator without putting an undue burden > > on GDB maintainers? > > I suggested a way to do that. I don't think it's putting an undue > burden on us, but if someone comes with a better idea, I will gladly > vote in favor. Just let's not assume the problem does not exist. I do think it's an undue burden, as I said earlier. While the eight existing strings in that function aren't too bad: (A) what happens if someone needs to add another option? (B) I would like to have a standard answer to this question for GDB. For instance, infttrace.c:print_thread would need 128 (plus a dubious %s). I hope we agree that's too many. Of course, that seems to be a GDB-internal debugging aid; I wouldn't shed tears if it was never translated. > > What do other projects do in this regard? > > I don't have any statistics handy; the general request from > translators is to give as much context as possible, as close to full > phrases or sentences as possible. I find myself in the need to read > the sources while translating much more than I would like to, so I > guess the maintainers don't do a very good job at that. I'd like GDB > to be better. > > If we want more opinions and suggestions, we could take this to the TP > mailing list. I'm just concerned about the "as possible". It may be possible, but it isn't practical. No, I don't have a suggestion to offer you; I don't know enough about translation issues, but I do see that this change would create a code maintenance issue. -- Daniel Jacobowitz