[opensuse-translation] bug 402885 - missing options in zypper
Hi all! Looking in bug 402885 (https://bugzilla.novell.com/show_bug.cgi?id=402885) from the spanish fellows, makes me remember something that I felt when doing a revision in the zypper.*.po file for my language... I found that some strings that I think was fully translated, in fact wasn't(the help messages --help). There where some new options and they where not marked as fuzzy, for example the "--new-recomends" that the bug talks. I think it was my fault, but seeing this bug I start thinking that was some automaticaly update without marking as fuzzy. Looking in some languages, (in the toplist, the 11 firsts) I was this error (--no-recomends missing) in: Italian, Spainish, Hungarian, Japanese, Ukrainian and Czech Regards, Luiz Fernando Ranghetti --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
Hi ElCheVive, Thanks for your indication. I've just fixed Japanese translation. The root cause of this Japanese translation bug is only a carelessness of me. Although the revision 26200 changes some entries of menus, I missed out. Best regards, -- Yasuhiko Kamata E-mail: belphegor@belbel.or.jp --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
"¡ElCheVive!"
Looking in bug 402885 (https://bugzilla.novell.com/show_bug.cgi?id=402885) from the spanish fellows, makes me remember something that I felt when doing a revision in the zypper.*.po file for my language... I found that some strings that I think was fully translated, in fact wasn't(the help messages --help). There where some new options and they where not marked as fuzzy, for example the "--new-recomends" that the bug talks. I think it was my fault, but seeing this bug I start thinking that was some automaticaly update without marking as fuzzy. Looking in some languages, (in the toplist, the 11 firsts) I was this error (--no-recomends missing) in:
Italian, Spainish, Hungarian, Japanese, Ukrainian and Czech
Thanks for investigating. I debugged it for Ukrainian (uk) and found that the message in r27386 was properly marked fuzzy. Run: svn cat -r27386 \ https://forgesvn1.novell.com/svn/suse-i18n/trunk/lcn/uk/po/zypper.uk.po \ | sed -n '/..\/src\/zypper.cc:763/,/^$/p' It is probably the same with the other translation files. It can happen very easily that you miss such an added option. The message looks very uniform, and without using diff you cannot spot it reliably. It might be the best best, if we'd spilt the help message even more. Jan, what do you think? -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2008-06-27 at 14:33 +0200, Karl Eichwalder wrote:
Thanks for investigating. I debugged it for Ukrainian (uk) and found that the message in r27386 was properly marked fuzzy. Run: svn cat -r27386 \ https://forgesvn1.novell.com/svn/suse-i18n/trunk/lcn/uk/po/zypper.uk.po \ | sed -n '/..\/src\/zypper.cc:763/,/^$/p'
It is probably the same with the other translation files. It can happen very easily that you miss such an added option. The message looks very uniform, and without using diff you cannot spot it reliably. It might be the best best, if we'd spilt the help message even more. Jan, what do you think?
That would help, but, IMO, the best thing would be to have kbabel or its sucessor really having a working diff mode. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIZPfhtTMYHG2NR9URAoA/AJ9CqeBSzRp0tfjPV8Da3qtaVMpIpwCfXIZx sEJys2urQ0J2gX7XL+ZQOMY= =w4vM -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
"Carlos E. R."
The Friday 2008-06-27 at 14:33 +0200, Karl Eichwalder wrote:
Thanks for investigating. I debugged it for Ukrainian (uk) and found that the message in r27386 was properly marked fuzzy. Run: svn cat -r27386 \ https://forgesvn1.novell.com/svn/suse-i18n/trunk/lcn/uk/po/zypper.uk.po \ | sed -n '/..\/src\/zypper.cc:763/,/^$/p'
Instead of a sed heck, you'd better use msggrep (part of gettext): svn cat -r27386 \ https://forgesvn1.novell.com/svn/suse-i18n/trunk/lcn/uk/po/zypper.uk.po \ | msggrep -K -e '--no-recommends'
That would help, but, IMO, the best thing would be to have kbabel or its sucessor really having a working diff mode.
Yes, there is still hope. AFAIK, forthcoming gettext tools will offer the option to keep the old msgid as a comment in PO files; thus you can reliable diff the old and new msgid. -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-06-30 at 11:36 +0200, Karl Eichwalder wrote:
That would help, but, IMO, the best thing would be to have kbabel or its sucessor really having a working diff mode.
Yes, there is still hope. AFAIK, forthcoming gettext tools will offer the option to keep the old msgid as a comment in PO files; thus you can reliable diff the old and new msgid.
Hum! Now that would be interesting :-) But not as a comment, but as field, like 'msgostr ""', and add support for it on the editors, so that they could automatically show in red the "comma" that was added. The msgostr would have to contain the last nonfuzzy translation, ie, the last good translation; it should not be created nor modified if the translation is already fuzzy. As a comment it would perhaps be better than kbabel keeping a database that doesn't work, but it wouldn't work for diff mode either, it would require manual work by the translator to use and remove. Another option is having versioned backup files. The backup file has the last file on which the translator worked (commited) and he knows that it is correct. The new file has to be checked. Diff mode with those two files would work. It would be a "diff.po/" dir. (If I don't make much sense, never mind, it is 3:28 AM, I should be sleeping) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIaYhptTMYHG2NR9URAmkCAJ9v/UchzWd+iGRZJIBjCIm7dnN7cwCfSeRs 6sXZyCCovG/2D0+VGTATXBg= =mySq -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-translation+help@opensuse.org
participants (4)
-
Carlos E. R. -
Karl Eichwalder -
Yasuhiko Kamata -
¡ElCheVive!