https://bugzilla.novell.com/show_bug.cgi?id=489139 User vuntz@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=489139#c1 Vincent Untz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@novell.com --- Comment #1 from Vincent Untz 2009-03-26 06:28:10 MST --- I see this in gnome-panel too, and I would expect many other packages to have this. Wondering if it could be happening because of the usage of translation-update-upstream. Stanislav? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=489139 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |ASSIGNED AssignedTo|bnc-team-screening@forge.pr |sbrabec@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=489139 User bruno@clisp.org added comment https://bugzilla.novell.com/show_bug.cgi?id=489139#c3 Bruno Haible changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno@clisp.org --- Comment #3 from Bruno Haible 2009-03-26 17:45:32 MST ---

It's not easy to get it rid with a standard gettext

Why? It's a built-in feature of "msgmerge --update" that it will not touch po files if the only change between the present and the new .po file would be a difference in POT-Creation-Date. If you don't use "msgmerge --update" for merging the .po files, that would explain it... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=489139 User bruno@clisp.org added comment https://bugzilla.novell.com/show_bug.cgi?id=489139#c5 --- Comment #5 from Bruno Haible 2009-03-27 05:52:16 MST ---

I am using:

msgcat --use-first $PO_PATH $PO -o $PO.new msgmerge --no-fuzzy-matching --compendium=$PO_PATH -o $PO $PO.new $POT

The use of msgcat is fishy: It means that the compendium overrides the contents of the PO file. What happens if you use: msgmerge --no-fuzzy-matching --compendium=$PO_PATH --update $PO $POT -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=489139 User sbrabec@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=489139#c7 --- Comment #7 from Stanislav Brabec 2009-03-27 06:22:58 MST --- Yes, overwriting of existing upstream strings by strings changed in later upstream versions is an intended behavior. As far as I remember my experiments, msgmerge have had an ugly problem: If there already exists a translation, it is never updated from compendium, even if the old one is an invalid fuzzy string. That is why I used msgcat. I would need something like --force-compendium. To save update size, only changes and updates are part of the updated po file. But the real problem causing behavior reported in this bug: Tool does not trust that upstream re-generated po file against the latest pot file. That is why it generates its own pot file (each time, as it is not a part of the package). This behavior is easy to work-around. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.