From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16485 invoked by alias); 4 Nov 2004 04:52:13 -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 16475 invoked from network); 4 Nov 2004 04:52:12 -0000 Received: from unknown (HELO balder.inter.net.il) (192.114.186.15) by sourceware.org with SMTP; 4 Nov 2004 04:52:12 -0000 Received: from zaretski (pns03-207-43.inter.net.il [80.230.207.43]) by balder.inter.net.il (Mirapoint Messaging Server MOS 3.3.7-GR) with ESMTP id DVT45728 (AUTH halo1); Thu, 4 Nov 2004 06:52:08 +0200 (IST) Date: Thu, 04 Nov 2004 04:52:00 -0000 From: "Eli Zaretskii" To: Paul Schlie Message-ID: <01c4c229$Blat.v2.2.2$72d18d40@zahav.net.il> Content-Transfer-Encoding: 7BIT Content-Type: text/plain; charset=ISO-8859-1 CC: gdb@sources.redhat.com In-reply-to: (message from Paul Schlie on Wed, 03 Nov 2004 19:27:19 -0500) Subject: Re: GDB 6.4 and translations Reply-to: Eli Zaretskii References: X-SW-Source: 2004-11/txt/msg00032.txt.bz2 > Date: Wed, 03 Nov 2004 19:27:19 -0500 > From: Paul Schlie > > Although I don't know if it's been considered or even an issue, but it may > be worth trying to avoid the use of Unicode's typographical quote characters > in otherwise ASCII message string output on even Unicode supported platforms > by default Sorry, I have no idea what you are talking about; please consider elaborating, e.g., by providing an example of such a problematic message. AFAIK, we don't use any non-ASCII characters in the GDB message text. If you know about any use of such characters in GDB, please point out where in the code we have them, since I believe that must be some bug. As for the translated messages, it's entirely up to the translators' teams to decide how they encode the text in their language. If they decide to use UTF-8 or some other Unicode encoding (and use Unicode quoting characters), there's no way we could prevent them from doing so. Nor do I think we should: the translators know better than we do what characters are supported by end-user platforms in their locale. > especially for text which may likely be subsequently parsed by tools likely > benefiting, and/or depending on the use of plain old ASCII quote characters. If you are talking about GDB GUI front ends, they should invoke GDB after setting the Posix locale anyway, since they want the messages in English to be able to parse them. THus, if the original messages we have in the code are in plain ASCII, the front ends will not have any problems here. Or did I miss something?