GNOME Bugzilla – Bug 781933
Translation statistics are not accurated
Last modified: 2018-05-22 12:21:22 UTC
In the git repository you have a translation like this: #~ msgctxt "shortcut window" #~ msgid "View" #~ msgstr "Visualitza" that when an application is built is not showed. However, dammed lies process the PO file in a way that the string is: msgctxt "shortcut window" msgid "View" msgstr "Visualitza" and the string that in the application will not show as translated is shown as such as the translation statistics. This is really misleading because you think that the file is completely translated according to the statistics but it is not true. This behaviour caused the Catalan translate team two miss updates two applications already.
Please provide a link to an example.
For example the ca.po before this commit: https://git.gnome.org/browse/epiphany/commit/?h=gnome-3-24&id=2bd4624bee40ff3f4154526ca93037cc8fc8fde5 It was reported to be fully translated except for 15 fuzzy strings by Dammed Lies. Unfortunally most of the menus were showing in English when the app was ran. I committed the file from Dammed files with the commit referenced at the top. My suggest fix: do stats on the original PO from Git not with the PO file that you provide for people to download. Jordi,
> (In reply to Jordi Mas from comment #2) > My suggest fix: do stats on the original PO from Git not with the PO file > that you provide for people to download. That's not an option, as the stats have to be computed after being merged with the latest generated pot file. There is no value in simply giving stats for the committed po from Git. What we could imagine is doing two different merges, one with a po file stripped from any obsolete msgstr value and an other with the "normal" po file. That would double the merge computing load on the server, for a marginal benefit. I think I still have to make my mind about it.
If it helps to clarify, my use case is simple. I look at Damned Lies to understand if we have to update the translations in a file. If Damned Lies tells me that the file is 100% translated but then the application is not showing 100% translated, it is not reliable. In the case of the Catalan translation, in 3.24 cycle, we missed the update of Nautilus (a key component of the user experience) and Epiphany browser due to this. Thanks Claude
I understand the issue and I'm sorry for the missing deadline. However, the probability for that to happen is still relatively low. The package must have new translatable strings which have 100% matches in the obsolete strings of a language, and no new translatable strings with no match have been introduced. The fact you are the first reporter for such an issue in years of GNOME translations is also confirming the low probability. That doesn't mean we shouldn't try to fix it, of course, but the solution I currently imagine is quite "heavy".
I created a related issue in gettext tracker: https://savannah.gnu.org/bugs/index.php?50910
Hello, I want to comment that this is happening in more cases. For Catalan is also happen for mutter project: What was in Git msgfmt -c --statistics ca.po 34 translated messages. What was in Damned Lies: https://l10n.gnome.org/POT/mutter.master/mutter.master.da.po 124 translated messages, 5 fuzzy translations, 2 untranslated messages. But the same problem happens with DA: (look for string "Switch windows of an application") in these files: https://l10n.gnome.org/POT/mutter.master/mutter.master.da.po https://git.gnome.org/browse/mutter/tree/po/da.po And also for pt_BR and BG languages
Jordi, this is totally expected. String modules are moving all the time, and it can happen that a translator commit happen at a time where some strings are obsoleted, then the module maintainer fixes something and the day after, stats are completely different. I accepted the ticket because the problem is when the stats show 100% translated, while some of these translations are strings that are retrieved from obsoleted strings. The discussion with Bruno in the gettext bug was interesting. In the standard gettext workflow, it was expected that the build system should get a fresh pot file and merge it with committed translations (make update-po). In this case, the problem you mention about missing deadline because of apparent 100% translation status would not have happened. However many modules currently merely compile existing po files during their build process without any merging process. In other words, they trust DL too much!
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/damned-lies/issues/68.