RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1272892 - [ALL_LANG][RHEL7.3][policycoreutils] Translations incomplete
Summary: [ALL_LANG][RHEL7.3][policycoreutils] Translations incomplete
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: policycoreutils
Version: 7.3
Hardware: All
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Petr Lautrbach
QA Contact: Engineering Localization bugs mailing list
URL:
Whiteboard:
Depends On:
Blocks: 1262678 1340415
TreeView+ depends on / blocked
 
Reported: 2015-10-19 07:38 UTC by Satyabrata Maitra
Modified: 2016-11-04 02:13 UTC (History)
16 users (show)

Fixed In Version: policycoreutils-2.5-5.1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 02:13:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
FAIL Category definition document (15.53 KB, application/vnd.oasis.opendocument.graphics)
2015-10-19 07:38 UTC, Satyabrata Maitra
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:2279 0 normal SHIPPED_LIVE policycoreutils bug fix and enhancement update 2016-11-03 13:35:48 UTC

Description Satyabrata Maitra 2015-10-19 07:38:16 UTC
Created attachment 1084278 [details]
FAIL Category definition document

Description of problem:
As reported by the translators in the l10n qa event, translations for this package falls under FAIL-1, FAIL-4 Category - POT is inconsistent with UI.

Version-Release number of selected component (if applicable):
policycoreutils-2.2.5-19.el7

How reproducible:
Always

Steps to Reproduce:
1. N/A
2.
3.

Actual results:
Translations are not completed 100%

Expected results:
Translation should be completed 100% and be pulled and build in the package in order to reflect the translation work done in UI/CLI.

Additional info:
FAIL Categories are defined by l10n team lead, and the file is attached with this bug.

Comment 2 Petr Lautrbach 2016-01-06 12:50:58 UTC
I've created rhel7 branch in https://fedora.zanata.org/project/view/selinux and pushed strings from the current sources there.

Comment 3 Noriko Mizumoto 2016-01-06 13:02:04 UTC
Thanks Petr,

rhel-7.3 translation is scheduled after string freeze, it means btw 25-May and 3-Jun. Once the translation is completed, this bug will be assigned back to you.
QA Test is planned btw 15-21 Jun against either of public beta or snapshot-1 image.
Can you include latest translation in public beta and snapshot-1?

If you like to have the translation to be done earlier than planned dates, please feel free to let me know the date.

Comment 4 Petr Lautrbach 2016-01-06 19:36:47 UTC
I'm fine with the dates and I'll include latest translations when they're available.

Comment 5 Krishna Babu K 2016-01-15 12:12:56 UTC
branch: * rhel-7.3
Name:	 policycoreutils
Version: 2.2.5
Release: 20%{?dist}
 
./policycoreutils.pot: 0 translated messages, 1096 untranslated messages.

Translated LANGs:
./de.po: 1096 translated messages.
./es.po: 1096 translated messages.
./fr.po: 1096 translated messages.
./it.po: 1096 translated messages.
./ja.po: 1096 translated messages.
./ko.po: 1096 translated messages.
./pt_BR.po: 1096 translated messages.
./ru.po: 1096 translated messages.
./zh_CN.po: 1096 translated messages.
./zh_TW.po: 1096 translated messages.
 
Fuzzy LANGs:
 
Untranslated LANGs:

Comment 6 sandeep shedmake 2016-01-22 15:48:54 UTC
(In reply to Krishna Babu K from comment #5)
> branch: * rhel-7.3
> Name:	 policycoreutils
> Version: 2.2.5
> Release: 20%{?dist}
>  

Correction: Used 'make update-po' inside 'po' sub directory and regenerated PO statistics.

branch: * rhel-7.3
Name:	 policycoreutils
Version: 2.2.5
Release: 20%{?dist}

./policycoreutils-2.2.5/po/policycoreutils.pot: 0 translated messages, 825 untranslated messages.

./policycoreutils-2.2.5/po/de.po: 825 translated messages.
./policycoreutils-2.2.5/po/es.po: 825 translated messages.
./policycoreutils-2.2.5/po/fr.po: 825 translated messages.
./policycoreutils-2.2.5/po/it.po: 825 translated messages.
./policycoreutils-2.2.5/po/ja.po: 825 translated messages.
./policycoreutils-2.2.5/po/ko.po: 825 translated messages.
./policycoreutils-2.2.5/po/pt_BR.po: 825 translated messages.
./policycoreutils-2.2.5/po/ru.po: 825 translated messages.
./policycoreutils-2.2.5/po/zh_CN.po: 825 translated messages.
./policycoreutils-2.2.5/po/zh_TW.po: 825 translated messages.


Note!
./policycoreutils-2.2.5/po/zh_CN.po:3710: number of format specifications in 'msgid' and 'msgstr' does not match
msgfmt: found 1 fatal error

Comment 7 Noriko Mizumoto 2016-01-27 09:36:08 UTC
Hi Petr,
We decided to flag 'fast', thus the translation update will be organized early stage of development phase. We are going to work on rhel-7 branch. Pls advise if you like to have us work on master isntead.
https://fedora.zanata.org/iteration/view/selinux/rhel7

Comment 10 Noriko Mizumoto 2016-04-12 05:39:41 UTC
Hi maintainer

We have completed 8 out of 10 supported languages translation 100% for your package (de, es, fr, ja, pt-br, ru, zh-cn and zh-tw). I am planning to have second translation period in early to mid June to catch up rest 2 languages (ko and it), but can't 100% guarantee as we are in recruiting phase. So I assign this bug back to you. Please go ahead and move to next.

Comment 13 Noriko Mizumoto 2016-06-17 01:47:19 UTC
Hi Petr,

Now all ten languages have been 100% completed for rhel-7.3.
In case any further update is required later, please do let me know for re-arrange the translation resource.

Thanks

noriko

Comment 14 Noriko Mizumoto 2016-06-27 02:44:28 UTC
Hi Petr,

Could you kindly incorporate latest translation delivered for alpha?
We will have l10n QA test to check the quality using Alpha image.

Thanks 

noriko

Comment 17 Petr Lautrbach 2016-07-13 07:28:27 UTC
Either I have a bad workflow or there's a bug in Zanata. I downloaded all translations using zanata tool and fuzzy translations are there.
Please check the logs bellow.


shell$ zanata init
[INFO] Loading zanata user config from: /home/plautrba/.config/zanata.ini
        Found servers in zanata.ini:
        1) https://fedora.zanata.org/
        2) https://translate.engineering.redhat.com/
[?] Which Zanata server do you want to use? 1
[INFO] Loading zanata user config from: /home/plautrba/.config/zanata.ini
[INFO] zanata server: https://fedora.zanata.org
Do you want to...
        1) Select an existing project
        2) Create a new project
(1/2)? 1
...
        4) selinux (selinux (policycoreutils))
...
[?] Please select your project (index number) or enter part of the project ID/name to filter: 4
[INFO] Now working with project selinux.
Do you want to...
        1) Select an existing version
        2) Create a new version
(1/2)? 1

        ======= Available versions(s) for project selinux ======
        1) master
        2) rhel6
        3) rhel7

[?] Please select your version (index number) or enter part of the version ID to filter: 1
[INFO] Now working with version: master
[!] If you want to customize your project's translatable language list, do so now on the following web page. Continue once it is done.
        -- Go to your project-version homepage to view details and change advanced options: https://translate.zanata.org/zanata/iteration/view/selinux/master
[?] Do you want to continue (y/n)? y
[>] Now working with Project: 'selinux' on Version: 'master' of Type: 'gettext'.
[?] What is your base directory for source files (eg '.', 'pot', 'src/main/resources')? .
[?] Continue with source directory settings (y/n)? y
[INFO] Source directory selected: .
[?] What is your base directory for translated files (eg '.', 'po', 'src/main/resources')? .
[?] Continue with target directory settings (y/n)? t
[?] Continue with target directory settings (y/n)? y
[INFO] Translation directory selected: .
[>] Project config created at: zanata.xml



shell$ cat zanata.xml
<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
<config xmlns="http://zanata.org/namespace/config/">
  <url>https://fedora.zanata.org</url>
  <project>selinux</project>
  <project-version>master</project-version>
  <project-type>gettext</project-type>
  <src-dir>.</src-dir>
  <trans-dir>.</trans-dir>
</config>


shell$ zanata pull

shell$ grep -A 2 fuzzy de.po
 #, fuzzy, fuzzy, fuzzy, fuzzy, fuzzy, fuzzy, fuzzy, fuzzy, fuzzy, python-format
 msgid "Could not enable module %s"
 msgstr "Modul %s konnte nicht aktiviert werden"
 --
 #, fuzzy, fuzzy, fuzzy, fuzzy, fuzzy, fuzzy, fuzzy, fuzzy, fuzzy, python-format
 msgid "Could not disable module %s"
 msgstr "Modul %s konnte nicht deaktiviert werden"
 --
 #, fuzzy, fuzzy, fuzzy, fuzzy, fuzzy, python-format
 msgid ""
 "Module %s already loaded in current policy.\n"

Comment 18 Carlos Munoz 2016-07-14 06:40:58 UTC
Hi Petr,

I used the zanata.xml you have posted and then did a zanata-cli pull (note that this is the java-based client and it sounds like you are using the python client) and had no problems. There were no fuzzy strings present in the files. This might be a bug with the python client. Can I suggest you use the java client and try your pull again? 

http://zanata-client.readthedocs.io/

Comment 19 sandeep shedmake 2016-07-14 07:37:51 UTC
From Comment 18,

Thanks Carlos for the valuable suggestion.

Comment 20 Petr Lautrbach 2016-07-14 07:38:58 UTC
I had tried zanata-cli on Fedora 24 but it didn't work - https://bugzilla.redhat.com/show_bug.cgi?id=1355948 so I used zanata.

zanata-cli on RHEL-7 seems to work fine. I'm working on the update.

Comment 23 errata-xmlrpc 2016-11-04 02:13:34 UTC
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.

https://rhn.redhat.com/errata/RHEA-2016-2279.html


Note You need to log in before you can comment on or make changes to this bug.