From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17896 invoked by alias); 15 Feb 2005 02:10:45 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 17827 invoked from network); 15 Feb 2005 02:10:38 -0000 Received: from unknown (HELO netlx014.civ.utwente.nl) (130.89.1.88) by sourceware.org with SMTP; 15 Feb 2005 02:10:38 -0000 Received: from weblx058.utsp.utwente.nl (weblx058.utsp.utwente.nl [130.89.1.228]) by netlx014.civ.utwente.nl (8.11.7/HKD) with SMTP id j1F2A1R11800; Tue, 15 Feb 2005 03:10:01 +0100 From: "M.M. Kettenis" Subject: Re: i18n and internal errors MIME-Version: 1.0 Message-Id: <731992780126277@weblx058.utsp.utwente.nl> Date: Tue, 15 Feb 2005 04:55:00 -0000 To: Eli Zaretskii , Kevin Buettner , kettenis@gnu.org, gdb@sources.redhat.com Cc: cagney@gnu.org In-reply-to: <01c510f5$Blat.v2.4$edb4acc0@zahav.net.il> Content-description: Message body Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: Quoted-Printable X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-MailScanner-From: m.m.kettenis@alumnus.utwente.nl X-SW-Source: 2005-02/txt/msg00103.txt.bz2 "Eli Zaretskii" wrote: > Mark gave 2 reasons for not translating internal errors: > > . end users should not see these messages > . having them translated makes it difficult to fix bugs > > If I understand these reasons as Mark meant, they actually say: if an > end user sees and reports such a message in translated form, those of > us who don't understand the translated message will have difficulty > finding and fixing the bug. Yup, that's what I meant. > If that's what Mark meant, then he obviously says that end users > _will_ see these messages. Messages that end users see should be > translated, so that the users will understand them easily. Fatal > messages should certainly be understood unequivocally, because it's > crucial that the user understands the situation on which she is asked > to act (dump core, continue, etc.) Hmm, that's a pretty darn convincing argument. > As for the difficulty in fixing the bugs, the fatal messages typically > include a file name and a line number which point to the place where > the bug was caught. I think that alleviates some of the difficulties. Although line numbers might be a bit off compared to the current CVS versio= n or even compared to the release. > Also, it is customary for users to translate the messages into English > when reporting bugs (a case in point is messages from the OS utilities > that have some relevance to the bug being reported), since the users > generally understand that English is a better language to talk to > maintainers. So we should update the bug reporting instructions to instruct users to run= gdb with env LC_ALL=3D"C". Hmm, hopefully that doesn't make the bug disappear. Mark