This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: New PO Template file for `gcc'
- From: Philipp Thomas <pthomas at suse dot de>
- To: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Cc: Karl Eichwalder <keichwa at gmx dot net>,Translation Project Robot <translation at IRO dot UMontreal dot CA>,gcc-patches at gcc dot gnu dot org
- Date: Mon, 26 May 2003 19:01:52 +0200
- Subject: Re: New PO Template file for `gcc'
- Organization: SuSE Linux AG
- References: <200304251904.h3PJ4bZU010167@vor.iro.umontreal.ca> <Pine.LNX.4.53.0304271709330.13472@kern.srcf.societies.cam.ac.uk> <sh3ck2ik6q.fsf@tux.gnu.franken.de> <Pine.LNX.4.53.0304281959260.4163@kern.srcf.societies.cam.ac.uk>
* Joseph S. Myers (jsm28@cam.ac.uk) [20030428 21:16]:
> I'd presumed (when writing <http://gcc.gnu.org/translation.html> in the
> hope it would encourage gcc.pot and the .po files to be kept more up to
> date in GCC CVS,
I wanted to update de.po, da.po, es.po and tr.po for 3.3, but as there is no
3.3 branch yet, how am I going to update the po files? The only chance I
currently see would be to update mainline and then update the respective
3.3.X branch if it ever gets created.
And regarding 3.2.3, that branch is closed, so how would I go about updating
files for it?
This seems to always be a problem for gcc. To get distributed, the
translations have to come in before the release, i.e. be done against a
snapshot or prerelease version. Once a version has been released, there is
no way to update that release version until an update branch is opened.
Philipp
--
Philipp Thomas <pthomas@suse.de>
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nuremberg, Germany