public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jsm28@gcc.gnu.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: other/2857 Date: Mon, 28 May 2001 04:26:00 -0000 [thread overview] Message-ID: <20010528112602.19712.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR other/2857; it has been noted by GNATS. From: jsm28@gcc.gnu.org To: Gabriel.Dos-Reis@cmla.ens-cachan.fr, mark@codesourcery.com, pthomas@suse.de, zackw@stanford.edu, db@zigo.dhs.org, gcc-gnats@gcc.gnu.org, jsm28@cam.ac.uk, nobody@gcc.gnu.org Cc: Subject: Re: other/2857 Date: 28 May 2001 11:17:27 -0000 Synopsis: i18n, translations does not work State-Changed-From-To: open->closed State-Changed-By: jsm28 State-Changed-When: Mon May 28 04:17:25 2001 State-Changed-Why: I think all the changes needed for working i18n are now in CVS on the 3.0 branch, and I've fixed the release script to include generated .gmo files in the release tarball. Could someone generate a .pot file corresponding to the 20010527 3.0 prerelease, and put it in the GNU translation project system (and the responsible people then add completed translations to CVS, mainline and branch). http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2857&database=gcc
reply other threads:[~2001-05-28 4:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20010528112602.19712.qmail@sourceware.cygnus.com \ --to=jsm28@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).