Received: from spf1.us4.outblaze.com (spf1.us4.outblaze.com [205.158.62.23]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id iB6KO2LW006378 for ; Mon, 6 Dec 2004 20:24:02 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf1.us4.outblaze.com (Postfix) with ESMTP id 9B1C353344 for ; Mon, 6 Dec 2004 20:24:02 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CbPYe-0008Q4-45 for migo@homemail.com; Mon, 06 Dec 2004 15:34:08 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CbPYE-0008OW-P9 for gnu-arch-users@gnu.org; Mon, 06 Dec 2004 15:33:42 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CbPYE-0008O1-9s for gnu-arch-users@gnu.org; Mon, 06 Dec 2004 15:33:42 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CbPYE-0008Nu-7B for gnu-arch-users@gnu.org; Mon, 06 Dec 2004 15:33:42 -0500 Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CbPNr-00065I-6n for gnu-arch-users@gnu.org; Mon, 06 Dec 2004 15:22:59 -0500 Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id B0D5F8282B8; Mon, 6 Dec 2004 15:22:58 -0500 (EST) Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id 82B114AC66B; Mon, 6 Dec 2004 15:22:53 -0500 (EST) Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id 6C2438CA69; Mon, 6 Dec 2004 15:22:53 -0500 (EST) Message-ID: To: gnu-arch-users@gnu.org References: <20040615.105821.74747648.tez@kamihira.com> <20040819.114448.71097995.tez@kamihira.com> <1102190470.6937.18.camel@localhost> <1102246556.21407.4.camel@localhost> <41B4B662.1030908@arbash-meinel.com> From: Stefan Monnier Date: Mon, 06 Dec 2004 15:22:53 -0500 In-Reply-To: <41B4B662.1030908@arbash-meinel.com> (John A. Meinel's message of "Mon, 06 Dec 2004 13:43:30 -0600") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/21.3.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-3.708, requis 5, autolearn=not spam, AWL 1.19, BAYES_00 -4.90) X-MailScanner-From: monnier@iro.umontreal.ca Subject: [Gnu-arch-users] Re: [BUG] i18n (Re: Message translation - basic framework) X-BeenThere: gnu-arch-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: a discussion list for all things arch-ish List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org Status: RO Content-Length: 1762 Lines: 44 > What if the front-end could just always issue the command: > "LANG=C tla " > Or do it by setting the environment before the call, etc. > Wouldn't that cause it to always report back non-internationalized messages? Right. But it could also have undesired side-effects (e.g. on programs run by `tla' from hooks, ...). It'd be better if it wasn't necessary. > And if as a new front end you want to display the internationalized form, > you can have your front end use the gettext() functionality to translate > whatever messages you get. This also has the advantage that your front-end > is part-way to being internationalized itself. I'd much rather make sure the format is "redundant": the internationalized text messages are always accompagnied with computer-readable info (could be good old error-msg number or anything like that). Using `gettext' from outside would be not just a real pain in the butt but also generally not possible (you'd have to magically recover the format string passed to printf). > I think the best way is to get tla-2.0 librified and out the door so that > you can have much more meaningful return values, without having to parse > possibly ambiguous text. But in the mean-time it seems like frontends can > easily work around the internationalization parsing problem. Using a library rather than a binary executable is not always preferable (or even an option), so while it's good to have a library, it doesn't mean that the ability to do batch processing robustly is not needed. Stefan _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/