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 590460 - [anaconda] [zh_CN] Incorrect translation
Summary: [anaconda] [zh_CN] Incorrect translation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 527925
TreeView+ depends on / blocked
 
Reported: 2010-05-09 16:43 UTC by Qian Cai
Modified: 2010-11-10 19:43 UTC (History)
8 users (show)

Fixed In Version: anaconda-13.21.68-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-10 19:43:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed patch (308 bytes, patch)
2010-05-09 16:44 UTC, Qian Cai 		no flags Details | Diff
zh_CN - Screenshot FIXED word (14.02 KB, image/png)
2010-08-15 10:00 UTC, A S Alam 		no flags Details
View All

Description Qian Cai 2010-05-09 16:43:54 UTC 
Description of problem:
提交 = file verb (STORE/RECORD INFORMATION);
文件 = file noun

Version-Release number of selected component (if applicable):
13.21.30
Comment 1 Qian Cai 2010-05-09 16:44:30 UTC 
Created attachment 412660 [details]
proposed patch
Comment 2 RHEL Program Management 2010-05-09 17:20:35 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 3 Chris Lumens 2010-05-10 15:20:35 UTC 
Can you get this patch in through transifex?  Make sure it gets applied to both rhel6-branch and master.  Thanks.
Comment 5 David Cantrell 2010-05-10 23:32:46 UTC 
This patch is small enough that I think we can just toss it in for master and rhel6-branch.
Comment 6 Qian Cai 2010-05-12 02:31:38 UTC 
(In reply to comment #3)
> Can you get this patch in through transifex?  Make sure it gets applied to both
> rhel6-branch and master.  Thanks.    
Is this a needinfo from me? I am not familiar with transifex.
Comment 7 Tommy He 2010-05-13 08:44:50 UTC 
Fixed po files were submitted to master and thel6 branches.

Thanks for reporting.
Comment 8 RHEL Program Management 2010-07-15 14:04:45 UTC 
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 9 Brian Lane 2010-07-15 15:43:31 UTC 
Note, this is still an issue as far as I can tell. It looks like a transifex commit dce88c8b un-did the change that Tommy made.
Comment 10 RHEL Program Management 2010-07-15 16:17:55 UTC 
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 11 Tommy He 2010-07-15 20:18:18 UTC 
(In reply to comment #9)
> Note, this is still an issue as far as I can tell. It looks like a transifex
> commit dce88c8b un-did the change that Tommy made.    

OK...what should I do now? Rolling back the commit?
Comment 13 Ankit Patel 2010-08-03 13:11:04 UTC 
Hi all,

Since it's a translation issue, it has to go through proper channel (localization team -> zh_CN translator).

Assigning it to Leah Liu, who's in charge of handling zh_CN translations. She will take the necessary actions.

Thanks!
Ankit
Comment 14 Wei Liu 2010-08-04 07:52:49 UTC 
The translation is modified to '提交' as the word 'File' here is a verb instead of noun.

Thanks
Leah
Comment 15 Ankit Patel 2010-08-04 08:07:12 UTC 
FIXED.

rhel6-branch: https://translate.fedoraproject.org/projects/p/anaconda/c/rhel6-branch/view/po/zh_CN.po

master branch: https://translate.fedoraproject.org/projects/p/anaconda/c/master/view/po/zh_CN.po

Thanks!
Ankit
Comment 16 Ankit Patel 2010-08-04 08:08:16 UTC 
if there is some problem with zh-CN, Leah Liu is still in the CC watch list.
Comment 17 David Cantrell 2010-08-04 14:26:26 UTC 
The zh_CN.po file has been broken recently and we have to either revert the changes or fix up the file so the builds can complete.

The problem that keeps happening is for plural format strings where there is a singular and plural translation choice.  For example, line 575 in po/zh_CN.po keeps breaking.  Here is what ends up in the translation file:

#: installinterfacebase.py:47
#, python-format
msgid ""
"Disk %s contains BIOS RAID metadata, but is not part of any recognized BIOS "
"RAID sets. Ignoring disk %s."
msgid_plural ""
"Disks %s contain BIOS RAID metadata, but are not part of any recognized BIOS "
"RAID sets. Ignoring disks %s."
msgstr[0] ""
"磁盘 %s 中包含 BIOS RAID 元数据，但该数据不包含在任何可识别 BIOS 组中。"
"忽略磁盘 %s。"
msgstr[1] ""
""

The problem here is the msgstr[1] part.  You cannot have "" as the string because the msgid has format strings in it.  Even if the string is the same for this language, it needs to be duplicated.  Copying the string from msgstr[0] to msgstr[1] allows our build to complete, so we change it to:

msgstr[1] ""
"磁盘 %s 中包含 BIOS RAID 元数据，但该数据不包含在任何可识别 BIOS 组中。"
"忽略磁盘 %s。"

Please make sure that translations are complete when you commit them to the git repository.  We cannot continue to fix up the po files, we will have to start reverting changes to ensure the builds succeed.
Comment 18 Ankit Patel 2010-08-04 14:34:58 UTC 
(In reply to comment #17)
> The zh_CN.po file has been broken recently and we have to either revert the
> changes or fix up the file so the builds can complete.
> 
> The problem that keeps happening is for plural format strings where there is a
> singular and plural translation choice.  For example, line 575 in po/zh_CN.po
> keeps breaking.  Here is what ends up in the translation file:
> 
> #: installinterfacebase.py:47
> #, python-format
> msgid ""
> "Disk %s contains BIOS RAID metadata, but is not part of any recognized BIOS "
> "RAID sets. Ignoring disk %s."
> msgid_plural ""
> "Disks %s contain BIOS RAID metadata, but are not part of any recognized BIOS "
> "RAID sets. Ignoring disks %s."
> msgstr[0] ""
> "磁盘 %s 中包含 BIOS RAID 元数据，但该数据不包含在任何可识别 BIOS 组中。"
> "忽略磁盘 %s。"
> msgstr[1] ""
> ""
> 
> The problem here is the msgstr[1] part.  You cannot have "" as the string
> because the msgid has format strings in it.  Even if the string is the same for
> this language, it needs to be duplicated.  Copying the string from msgstr[0] to
> msgstr[1] allows our build to complete, so we change it to:
> 
> msgstr[1] ""
> "磁盘 %s 中包含 BIOS RAID 元数据，但该数据不包含在任何可识别 BIOS 组中。"
> "忽略磁盘 %s。"
> 
> Please make sure that translations are complete when you commit them to the git
> repository.  We cannot continue to fix up the po files, we will have to start
> reverting changes to ensure the builds succeed.    


HI David,

Perhaps you haven't synched the zh_CN.po file from the git repo (rhel6-branch). Could you please check again. Because the corrected file is already submitted by Leah Liu this morning.

See the commit diff: http://git.fedorahosted.org/git/?p=anaconda.git;a=commitdiff;h=6ef0e970bfa1e180219a9a36e2fa9975c8b83c42
and the actual file: https://translate.fedoraproject.org/projects/p/anaconda/c/rhel6-branch/view/po/zh_CN.po

Thanks!
Ankit
Comment 19 Chris Lumens 2010-08-04 15:43:36 UTC 
We pull all updated translations automatically before doing builds, so this will get pulled in.  I did a test build and it looks good now.  Thanks for fixing.
Comment 20 David Cantrell 2010-08-04 15:54:24 UTC 
Looks like the zh_CN changes were pushed after we built yesterday (which makes sense given the time zones that we all work in).  The updated zh_CN.po file will be in the next build, which will be anaconda-13.21.68-1.
Comment 22 Kenichi Takemura 2010-08-09 01:29:31 UTC 
Hi I am trying to verify this translation.

Which screen are you mentioning this bug?

Can you tell me the steps to verify?
Comment 23 A S Alam 2010-08-15 10:00:04 UTC 
Created attachment 438813 [details]
zh_CN - Screenshot FIXED word
Comment 24 A S Alam 2010-08-15 10:08:40 UTC 
status - FIXED
tested package: anaconda-13.21.74-1.el6.x86_64

detail: Screenshot
Comment 25 releng-rhel@redhat.com 2010-11-10 19:43:13 UTC 
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.