Follow-up Comment #2, bug #50910 (project gettext): OK, I'll try!
Time t: a module is translated at 100% in language ll. The committed ll.po contains some unused obsolete strings (from previous history). Time t+1: the source code changes and adds a new string which maps exactly to one of the ll.po obsolete strings. Damned Lies is our tracking application at https://l10n.gnome.org which always provides up-to-date po files by merging them with the latest pot file. As the merged file was able to reuse an obsolete string, the stats are still at 100%, so the translator doesn't care to update and commit ll.po. However, the compiled .mo file will not contain the "missing" new string until the translator commit a fresh ll.po (with the obsolete string "de-obsoleted"). If msgmerge would tell in its verbose output that some obsolete strings we reused during the merge operation, our application would be able to detect that issue and add a notice to translators that the merged file needs to be committed in the software repository, albeit it shows stats at 100%. I hope I was able to clarify the issue! _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?50910> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
