Hi, the gcc and cpplib domains have been completely translated to German for a while. Unfortunately, the Translation Project file robot is broken. I'm the usual translator as for the previous gcc versions, and you can download the de.po files from http://antcom.de/i18n/ It would be frustrating doing all the work and not seeing it incorporated into gcc. Thanks. bye, Roland
Please just post the patch for this to gcc-patches@.
Attaching the files themselves makes the mail for the list too big. GZipping them makes the spam checker reject them. Any idea? Remember: po file patches tend to be quite big for gcc, sometimes bigger than the file itself, and due to the translator's input being (re-)generated, there are sometimes changes without actual translation updates (e.g. line numbers.) Please consider incorporating the above linked files themselves, or look at the diff yourself, since I don't know to which version you want to apply the patch to. 4.1.0? 4.1.1? CVS?
Just send an email to the pist pointing to the .po. I wonder why the automatic bot is not working for the german translation.
Subject: Re: German translation of gcc 4.1 On Sun, 2 Apr 2006, stigge at antcom dot de wrote: > Attaching the files themselves makes the mail for the list too big. GZipping > them makes the spam checker reject them. The web page translation.html (in CVS) gives the procedures that are followed to get translations, and that is what would need patching. In particular: * Before a release, the RM will download the translations from the TP and commit any that differ from those in SVN. If the procedure is to be "download most from TP, but German from elsewhere", that needs documenting. * Similarly, after a release and a new .pot file has been provided to the TP, the new automerged .po files are downloaded and committed to SVN to resync with the versions in the TP - any special-case languages need documenting. Really, fixing the bug in the TP would be better so we don't need to special-case languages.
It's not that we need special casing for a certain language: The TP robot is generally broken (doesn't respond to translator's requests). I reported it there several times, to no avail.
(In reply to comment #5) > It's not that we need special casing for a certain language: The TP robot is > generally broken (doesn't respond to translator's requests). I reported it > there several times, to no avail. I think we only officially take stuff from the TP robot.
Is this still valid?
Fixed now. Thanks for your care.
Thanks to you!