From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Karl Eichwalder <keichwa@gmx.net>
Cc: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>,
gcc@gcc.gnu.org, translation@IRO.UMontreal.CA
Subject: Re: Downloads
Date: Mon, 19 May 2003 21:04:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.53.0305192159280.18843@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <shaddislsf.fsf@tux.gnu.franken.de>
On Mon, 19 May 2003, Karl Eichwalder wrote:
> "Joseph S. Myers" <jsm28@cam.ac.uk> 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
next prev parent reply other threads:[~2003-05-19 21:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 8:38 Downloads Volker Reichelt
2003-05-16 10:09 ` Downloads Gerald Pfeifer
2003-05-16 10:20 ` Downloads Joseph S. Myers
2003-05-19 21:01 ` Downloads Karl Eichwalder
2003-05-19 21:04 ` Joseph S. Myers [this message]
2003-05-20 16:17 ` Downloads Karl Eichwalder
2003-05-20 18:24 ` Downloads Joseph S. Myers
2003-05-16 19:24 ` Downloads Mark Mitchell
2003-05-16 14:58 ` Downloads E. Weddington
-- strict thread matches above, loose matches on Subject: below --
2003-05-15 17:35 Downloads Joe Laffey
2003-05-15 19:05 ` Downloads Gerald Pfeifer
2003-05-15 19:21 ` Downloads Joe Laffey
2003-05-15 22:22 ` Downloads Joseph S. Myers
2003-05-15 22:25 ` Downloads Joe Laffey
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=Pine.LNX.4.53.0305192159280.18843@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=keichwa@gmx.net \
--cc=pfeifer@dbai.tuwien.ac.at \
--cc=translation@IRO.UMontreal.CA \
/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: link
Be 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).