Red Hat Bugzilla – Bug 1313607
[zh_TW, zh_CN, ko_KR, pt_BR, fr_FR, it_IT, es_ES] rhn-setup-gnome.desktop translations missing.
Last modified: 2016-11-04 02:21:24 EDT
The current state of translations for this package is
de.po: 284 translated messages, 26 fuzzy translations, 113 untranslated messages.
es.po: 380 translated messages, 37 fuzzy translations, 6 untranslated messages.
fr.po: 341 translated messages, 31 fuzzy translations, 51 untranslated messages.
it.po: 253 translated messages, 26 fuzzy translations, 144 untranslated messages.
ja.po: 272 translated messages, 26 fuzzy translations, 125 untranslated messages.
ko.po: 253 translated messages, 26 fuzzy translations, 144 untranslated messages.
pt_BR.po: 323 translated messages, 29 fuzzy translations, 71 untranslated messages.
ru.po: 301 translated messages, 27 fuzzy translations, 95 untranslated messages.
zh_CN.po: 323 translated messages, 29 fuzzy translations, 71 untranslated messages.
zh_TW.po: 299 translated messages, 27 fuzzy translations, 97 untranslated messages.
which included untranslated string "Satellite Registration" which is required for this bug fix.
Should this project be imported in zanata, if yes please add me as maintainer there.
v6.8 100% translated, no such string 'Satellite Registration'. I can't find your username there. Are you rhn-client-tool is for rhn-setup-gnome-2.0.2-6.el7.noarch?
I have not given the permissions to push the pot in zanata hence you will not find this new string "Satellite Registration" in Zanata. When I created new pot file from existing source I can see untranslated strings. This is the bug for untranslated string "Satellite Registration".
Thanks Noriko. I have pushed new pot file in Zanata.
In order to fix this bug ('Satellite Registration' is reused in gnome-menu of RHEL-7.3), only one string translation is required. Besides I can see many of fuzzies and untranslated strings, which workload would be btw 3 to 7 hours per language. rhn-client-tools package is not in Tier1 important list for RHEL-7.
I don't know if this entire translation update is important and impact to rhel-7.3 or your team is planning to request update later time to suit your development cycle for another product release. Could you kindly give some input on this?
from comment#0 I don't think this is related with rhn-client-tools and it looks like the issue lies within gnome-menus package. Could you please provide reproducer so we can double check that this issue is not related to rhn-client-tools?
Okay let's go through gnome-menus source code again.
1) checkout 7.3 branch of gnome-menus
2) rhpkg prep
3) Generate new pot
3) grep -in "Satellite Registration" gnome-menus-3.13.3/po/gnome-menus-3.0.pot
===> No results
1) checkout 7.3 branch of rhn-client-tools
2) rhpkg prep
3) Generate new pot
[parag@localhost po]$ grep -in "Satellite Registration" rhn-client-tools.pot
934:"To learn more about RHN Classic/Red Hat Satellite registration and "
2120:msgid "Satellite Registration"
This can clearly show that untranslated string "Satellite Registration" is from rhn-client-tools package.
If we look from where this string is coming then check in pot file
msgid "Satellite Registration"
Then also if we want to check what desktop file is this then see
$ cat rhn_register.desktop.in
_GenericName=Register for software updates from Spacewalk/Red Hat Satellite/Red Hat Network Classic
_Comment=Register to Spacewalk/Red Hat Satellite/Red Hat Network Classic.
Can you please now confirm that string is really coming from rhn-client-tools package?
Now nine languages have been 100% completed for rhel-7.3 branch, including targeted string. Could you please repackage with these latest translations?
I am expecting this translation update to be reflected in Alpha release, so that we can use alpha for l10n QA test. Could you please also give '+' to devel-ack.
Package rhn-client-tools-2.0.2-8.el7 which contains updated strings has been built in Brew.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.