other/2857: i18n, translations does not work

[Philipp Thomas]

* Joseph S. Myers (jsm28@cam.ac.uk) [20010524 14:25]:

> The first priority is presumably getting up to date translations for the
> 3.0 branch (and putting those on mainline as well, for now), before
> translating 3.1.

The correct way of doing that would be to send the current gcc.pot to the
translation robot. The robot in turn will give notice to the translation
teams that a new file is available for translation.
 
> Question: do the release scripts need to generate the compiled .gmo files?
> As those are binary, we surely don't want to put them in CVS.

Yes, they would need to do so, according to GNU standards, as the user
should not need to have the tools to create them.

Philipp

-- 
Philipp Thomas <pthomas@suse.de>
Development, SuSE GmbH, Deutscherrnstr. 15-19, D-90429 Nuremberg, Germany

Penguins shall save the dinosaurs
                          -- Handelsblatt about Linux on S/390