Bug 838474

Summary: [zh_CN][abrt] Strings mismatch, the zh_CN strings displayed as zh_TW strings in Event list of 'Event Configuration' window.
Product: [Fedora] Fedora Reporter: Lijun Li <lijli>
Component: abrtAssignee: abrt <abrt-devel-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 17CC: abrt-devel-list, dvlasenk, iprikryl, jmoskovc, mmilata, mtoman, pwu, rvokal
Target Milestone: ---Keywords: Desktop, i18n, Translation
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 17:35:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 756771    
Attachments:
Description Flags
Strings mismatch in Event list of 'Event Configuration' window none

Description Lijun Li 2012-07-09 08:28:08 UTC
Description of problem:
Strings mismatch, the zh_CN strings displayed as zh_TW strings in Event list of 'Event Configuration' window.

Version-Release number of selected component (if applicable):
abrt-2.0.10-4.fc17.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install latest Fedora release build
2. Run abrt-gui from terminal or Applications->System Tools->Automatic Bug Reporting Tool in zh_CN locale
3. Click Edit-Preference
  
Actual results:
Strings mismatch, the zh_CN strings displayed as zh_TW strings in Event list of 'Event Configuration' window.

Expected results:
Those strings should be zh_CN strings in Event list of 'Event Configuration' window.


Additional info:

Comment 1 Lijun Li 2012-07-09 08:32:09 UTC
Created attachment 597024 [details]
Strings mismatch in Event list of 'Event Configuration' window

Comment 2 Jiri Moskovcak 2012-08-27 11:34:09 UTC
zh_CN and zh_TW are out of my area of expertise, but my guess here would be that the strings are wrong in the po files. ABRT uses gettext to handle the translation, so if the po files are ok but the text is not displayed correctly then the problem is in gettext.

Comment 3 Lijun Li 2012-08-28 01:22:19 UTC
(In reply to comment #2)
> zh_CN and zh_TW are out of my area of expertise, but my guess here would be
> that the strings are wrong in the po files. ABRT uses gettext to handle the
> translation, so if the po files are ok but the text is not displayed
> correctly then the problem is in gettext.

Yeah, I think so, should be the po files issue, the strings in zh_CN po files are zh_TW strings.

Comment 4 Fedora End Of Life 2013-07-03 19:17:08 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2013-07-31 17:35:49 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.