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 1272885 - [ALL_LANG][RHEL7.3][NetworkManager] - Translation incomplete
Summary: [ALL_LANG][RHEL7.3][NetworkManager] - Translation incomplete
Keywords:
Status: CLOSED DUPLICATE of bug 1188670
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.3
Hardware: All
OS: Linux
medium
low
Target Milestone: rc
: ---
Assignee: Noriko Mizumoto
QA Contact: Engineering Localization bugs mailing list
URL:
Whiteboard:
Depends On:
Blocks: 1262678
TreeView+ depends on / blocked
 
Reported: 2015-10-19 07:13 UTC by Satyabrata Maitra
Modified: 2015-10-21 18:55 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-21 18:55:51 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:13 UTC, Satyabrata Maitra
no flags Details

Description Satyabrata Maitra 2015-10-19 07:13:41 UTC
Created attachment 1084273 [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-3, FAIL-4 Category - POT is inconsistent with UI.

Version-Release number of selected component (if applicable):
NetworkManager-1.0.6-9.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 Jirka Klimes 2015-10-20 12:23:41 UTC
Unfortunately, NM developers are not able to make translations themselves. NetworkManager translation files in RHEL reflect what is in upstream branch.

Please, if you have translations or are able to translate, file a bug upstream and attach the translation file:
https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager
with Component: Translations and version: master

Comment 3 Satyabrata Maitra 2015-10-21 18:55:51 UTC
We have already a bug on this reported earlier, sorry for making a duplicate one. Closing this one as duplicate bug.

Although the bug https://bugzilla.redhat.com/show_bug.cgi?id=1188670 was created for RHEL7.0, but still in assigned state and FailedQA. So, better if we track NetworkManager translations through that (#1188670) bug.

*** This bug has been marked as a duplicate of bug 1188670 ***


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