From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11741 invoked by alias); 19 May 2003 21:04:29 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 11724 invoked from network); 19 May 2003 21:04:29 -0000 Received: from unknown (HELO purple.csi.cam.ac.uk) (131.111.8.4) by sources.redhat.com with SMTP; 19 May 2003 21:04:29 -0000 Received: from student.cusu.cam.ac.uk ([131.111.179.82] helo=kern.srcf.societies.cam.ac.uk ident=mail) by purple.csi.cam.ac.uk with esmtp (Exim 4.12) id 19Hro4-0004Jd-00; Mon, 19 May 2003 22:04:28 +0100 Received: from jsm28 (helo=localhost) by kern.srcf.societies.cam.ac.uk with local-esmtp (Exim 3.35 #1 (Debian)) id 19Hro4-0005Nd-00; Mon, 19 May 2003 22:04:28 +0100 Date: Mon, 19 May 2003 21:04:00 -0000 From: "Joseph S. Myers" X-X-Sender: jsm28@kern.srcf.societies.cam.ac.uk To: Karl Eichwalder cc: Gerald Pfeifer , gcc@gcc.gnu.org, translation@IRO.UMontreal.CA Subject: Re: Downloads In-Reply-To: Message-ID: References: <200305160827.h4G8RqNZ015149@relay.rwth-aachen.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2003-05/txt/msg01801.txt.bz2 On Mon, 19 May 2003, Karl Eichwalder wrote: > "Joseph S. Myers" writes: > > > Can someone confirm whether the Translation Project robot will handle > > .tar.bz2 files? At present translation.html says to send the URL of a > > .tar.gz file to the robot at the start of a release branch, since I > > couldn't find it documented what formats the robot expects to find > > packaged distributions in. > > .bz2 file are perfectly okay for our purposes. I will have to adjust > the documentation. So, on the GCC side, http://gcc.gnu.org/translation.html can now be updated to say that .tar.bz2 files for snapshots should be submitted (and we may no longer need to generate .gz files for snapshots) - as well as correcting the inaccurate presumption that the release tarball submission is an automatic rather than a manual process on the TP side (though the 3.3 release *should* be submitted, and provide the current .pot file replacing the snapshot one there, and unlike the 3.2.3 release replace the distribution URL with that for the 3.3 release). The 3.3 gcc.pot file corresponds accurately with the 3.3 source code and should be a good basis for translators to produce up to date translations for the 3.3.1 release. -- Joseph S. Myers jsm28@cam.ac.uk