From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Mitchell To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: other/2857: i18n, translations does not work Date: Tue, 22 May 2001 23:06:00 -0000 Message-id: <20010523060600.28022.qmail@sourceware.cygnus.com> X-SW-Source: 2001-05/msg00663.html List-Id: The following reply was made to PR other/2857; it has been noted by GNATS. From: Mark Mitchell To: zackw@Stanford.EDU Cc: db@zigo.dhs.org, Gabriel.Dos-Reis@cmla.ens-cachan.fr, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: other/2857: i18n, translations does not work Date: Tue, 22 May 2001 23:03:36 -0700 >>>>> "Zack" == Zack Weinberg writes: Zack> A translation is something that could easily get added in a Zack> 3.0.x patch release, if it isn't ready in time for 3.0.0, so Zack> don't feel pressured. I think that independent of this the Zack> machinery should work in 3.0.0. Just to emphasize both of these points: adding translations is something that I think would be perfect for a .x release. There is no risk to anyone not using the translation, and the only real risk to those using the translation is of wrong messages, not wrong code generation. I'd be much more nervous about reworking diagnostic.c for the dot-release, so we should do that now, if we can. My goal is for the dot releases to contain sufficiently minor tweaks that it will be easy to have high confidence. -- Mark Mitchell mark@codesourcery.com CodeSourcery, LLC http://www.codesourcery.com