[opensuse-translation] Stats and "freeze"
We, the Danish team, have a problem with the stats. Apparmor-utils.da.po is shown with 100% strings untranslated and the progressbar is purple. However according to svn (and me) it's fully translated. Do the stats have a problem? Or is something more serious wrong? http://i18n.opensuse.org/stats/da/lcn/index.php I'm not very happy with the interpretation of freeze either. I look very bad when I assign po-files to my team members and then they're updated in svn in the meantime. Actually, to me there seems to be more activity now than before freeze - at least for the last 2-3 days. Most of the time the updates don't include new strings - only proofreading I guess. What should I do? a) should I just commit the translations my team members have done based on outdated .pos? b) should I try to merge with msgmerge? c) is it necessary to start over? d) something else? Can we expect this level of svn activity to continue until october 26? Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Martin Schlander <suse@linuxin.dk> writes:
We, the Danish team, have a problem with the stats. Apparmor-utils.da.po is shown with 100% strings untranslated and the progressbar is purple. However according to svn (and me) it's fully translated. Do the stats have a problem? Or is something more serious wrong? http://i18n.opensuse.org/stats/da/lcn/index.php
Yes ;-) Syntax error! You all must really, really check the files before committing. That's especially important for the yast files--if there is a syntax error the package build will fail. In the yast/50-tools directory find a script that you should call with a directory name of the po files. For example, that way: cd .../yast 50-tools/y2-check-po.sh da/po Then study check.log. Klára, can we reserve "red" for files with syntax errors and another nice color (grey?) for untranslated messages.
a) should I just commit the translations my team members have done based on outdated .pos?
Yes. We will merge the files from time to time to make sure everthing is syntactical correct.
b) should I try to merge with msgmerge?
That's not required, but if all devel tools are install, you can proceed as outlined in lcn/README ("Usage Information for Translators").
Can we expect this level of svn activity to continue until october 26?
No, only once the second translation round starts. And, as said yesterday, the desktop files are kind of special. -- Karl Eichwalder R&D / Documentation SUSE Linux Products GmbH GPG: 1024D/06EB882E B2A3 AF2F CFC8 40B1 67EA 475A 5903 A21B 06EB 882E --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Tirsdag 10 oktober 2006 09:46, skrev Karl Eichwalder:
Yes ;-) Syntax error! You all must really, really check the files before committing. That's especially important for the yast files--if there is a syntax error the package build will fail. In the yast/50-tools directory find a script that you should call with a directory name of the po files. For example, that way:
cd .../yast 50-tools/y2-check-po.sh da/po
I translate SUSE files with a commercial CAT tool and then run them through kbabel, partly to update file headers and partly to perform the integrated checks in kbabel. Doesn't kbabel perform all necessary checks? Olav -- Olav Pettershagen Grøndalen NO-2429 Tørberget Tel. +47 62454707 Mob. +47 48141781 http://home.online.no/~olav.pet/current_view.jpg --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Olav Pettershagen <olav.pet@online.no> writes:
cd .../yast 50-tools/y2-check-po.sh da/po
I translate SUSE files with a commercial CAT tool and then run them through kbabel, partly to update file headers and partly to perform the integrated checks in kbabel. Doesn't kbabel perform all necessary checks?
I think it calls msgfmt, so checking with kbabel is also ok (make sure to have the latest gettext package installed). y2-check-po.sh is a simple wrapper around msgfmt. -- Karl Eichwalder R&D / Documentation SUSE Linux Products GmbH GPG: 1024D/06EB882E B2A3 AF2F CFC8 40B1 67EA 475A 5903 A21B 06EB 882E --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Dne úterý 10 říjen 2006 09:46 Karl Eichwalder napsal(a):
Martin Schlander <suse@linuxin.dk> writes:
We, the Danish team, have a problem with the stats. Apparmor-utils.da.po is shown with 100% strings untranslated and the progressbar is purple. However according to svn (and me) it's fully translated. Do the stats have a problem? Or is something more serious wrong? http://i18n.opensuse.org/stats/da/lcn/index.php
Yes ;-) Syntax error! You all must really, really check the files before committing. That's especially important for the yast files--if there is a syntax error the package build will fail. In the yast/50-tools directory find a script that you should call with a directory name of the po files. For example, that way:
cd .../yast 50-tools/y2-check-po.sh da/po
Then study check.log. Klára, can we reserve "red" for files with syntax errors and another nice color (grey?) for untranslated messages.
Of course we can :-), next stats will use the red for syntax error and gray for untranslated strings. -- Klara --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Klara Cihlarova <cihlarov@suse.cz> writes:
Of course we can :-), next stats will use the red for syntax error and gray for untranslated strings.
I just noticed that files with syntax errors are painted in pink :-) That's good enough and there is no need to swap the other colors... -- Karl Eichwalder R&D / Documentation SUSE Linux Products GmbH GPG: 1024D/06EB882E B2A3 AF2F CFC8 40B1 67EA 475A 5903 A21B 06EB 882E --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Tirsdag 10 oktober 2006 09:46 skrev Karl Eichwalder:
Yes ;-) Syntax error!
Fixed. Omfg that's embarrasing. Usually use kbabel but this time I had done proofreading in kwrite and messed up there, won't happen again.
a) should I just commit the translations my team members have done based on outdated .pos?
Yes. We will merge the files from time to time to make sure everthing is syntactical correct.
Cool. Will be more careful about the desktop-files. Martin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Martin Schlander <suse@linuxin.dk> writes:
Tirsdag 10 oktober 2006 09:46 skrev Karl Eichwalder:
Yes ;-) Syntax error!
Fixed. Omfg that's embarrasing. Usually use kbabel but this time I had done proofreading in kwrite and messed up there, won't happen again.
This happens all the time, you are not the only one (sure, from time to time I'm also committing broken files...). The good news is, that we are in the process of installing an verification script. In the future the SVN server will stop accepting files with syntax errors. Be prepared to see strange response messages from the server. In those case you must fix your file and submit it again! Because it's work in progress report any problem you encounter during the next days. For more info, see http://devzilla.novell.com/forge/show_bug.cgi?id=74 . -- Karl Eichwalder R&D / Documentation SUSE Linux Products GmbH GPG: 1024D/06EB882E B2A3 AF2F CFC8 40B1 67EA 475A 5903 A21B 06EB 882E --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Karl Eichwalder <ke@suse.de> writes:
Because it's work in progress report any problem you encounter during the next days. For more info, see http://devzilla.novell.com/forge/show_bug.cgi?id=74 .
Now the checker is active. It makes use of a msgfmt version before 0.15. So it will not detect all plural related issues, but it is very valuable nevertheless! -- Karl Eichwalder R&D / Documentation SUSE Linux Products GmbH GPG: 1024D/06EB882E B2A3 AF2F CFC8 40B1 67EA 475A 5903 A21B 06EB 882E --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
participants (4)
-
Karl Eichwalder
-
Klara Cihlarova
-
Martin Schlander
-
Olav Pettershagen