+++ This bug was initially created as a clone of Bug #909536 +++

Description of problem:
abrt-gui displays Traditional Chinese Strings under Simplified Chinese locale, in the Events tab of the Configuration dialog.

Version-Release number of selected component (if applicable):
2.0.20

How reproducible:
100%


Steps to Reproduce:
1. Start abrt-gui in zh_CN.UTF-8 locale
2. In menu, choose 编辑 - 首选项 (Edit - Preferences), then click on the Events tab in the popup dialog.
3. Check the strings under each event type.
  
Actual results:
We see Traditional Chinese strings.

Expected results:
The strings should be in Simplified Chinese.

Additional info:
The bug appears the same as https://bugzilla.redhat.com/show_bug.cgi?id=747954 at first sight. But after I check the msgunfmt-ed zh_CN abrt.po, no Traditional Chinese found. So the two bugs seem different. Besides, I cannot find the English version of those strings in abrt.po, which is rather strange.

--- Additional comment from Alick Zhao on 2013-02-09 10:23:15 CET ---



--- Additional comment from Christopher Meng on 2013-07-26 05:59:52 CEST ---

Is it Fixed?

--- Additional comment from Jakub Filak on 2013-07-26 07:26:22 CEST ---

We have found the root cause of this bug and we are working on the proper patch.

The bug is in libreport's event configuration XML parser. The parser tries very hard to get localized string and for that reason it accepts text value of an element if short locale ('zh') matches the element's xml:lang attribute value prefix. The algorithm is bit more complex and results into usage of the last found localized text. In the XML event definition files, Traditional Chinese localizations ('zh_TW') follow Simplified Chinese localizations ('zh_CN'), therefore 'zh_TW' localizations are used under 'zh_CN' locale.

--- Additional comment from Jakub Filak on 2013-08-15 10:16:08 CEST ---



--- Additional comment from Jakub Filak on 2013-10-31 14:59:53 CET ---

Upstream commit 44cbdd5f6ed05db2bc7cbb3f4cc671a235f171be fixes this bug.

--- Additional comment from Christopher Meng on 2013-11-28 02:25:49 CET ---

Seems like this will be fixed "officially" in 2.10?

--- Additional comment from Fedora Update System on 2013-12-12 10:58:32 CET ---

abrt-2.1.10-1.fc18,libreport-2.1.10-1.fc18,satyr-0.12-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/abrt-2.1.10-1.fc18,libreport-2.1.10-1.fc18,satyr-0.12-1.fc18

--- Additional comment from Fedora Update System on 2013-12-13 06:07:03 CET ---

Package abrt-2.1.10-1.fc18, libreport-2.1.10-1.fc18, satyr-0.12-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing abrt-2.1.10-1.fc18 libreport-2.1.10-1.fc18 satyr-0.12-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-23306/abrt-2.1.10-1.fc18,libreport-2.1.10-1.fc18,satyr-0.12-1.fc18
then log in and leave karma (feedback).

--- Additional comment from Alick Zhao on 2013-12-13 08:33:23 CET ---

I am going to test the update. And note for other possible testers, the test steps need to be changed since abrt-gui has been replaced by gnome-abrt. (Not sure what is the case with KDE?)

Updated Steps to Test:
1. Start gnome-abrt in zh_CN.UTF-8 locale
2. In popdown menu, choose Preferences, then click on the Events tab in the popup dialog.
3. Check the strings under each event type.

--- Additional comment from Alick Zhao on 2013-12-15 03:54:34 CET ---

On Fedora 19, after the update I still see Traditional Chinese strings under Simplified Chinese locale. Reboot does not help either. I'll try with Fedora 18 later and report the result.

--- Additional comment from Alick Zhao on 2013-12-19 12:23:31 CET ---

On Fedora 18, after the update I still see Traditional Chinese strings under Simplified Chinese locale too. Seems this issue remains not fixed.

--- Additional comment from Fedora End Of Life on 2013-12-21 16:50:34 CET ---

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 18'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.

--- Additional comment from Alick Zhao on 2013-12-28 13:59:14 CET ---

I upgraded my F18 machine to F20, and still see the same issue with abrt-2.1.10-1.fc20.x86_64 and abrt-2.1.10-1.fc20.x86_64 .

--- Additional comment from Jakub Filak on 2014-02-07 16:14:28 CET ---

(In reply to Alick Zhao from comment #13)
> I upgraded my F18 machine to F20, and still see the same issue with
> abrt-2.1.10-1.fc20.x86_64 and abrt-2.1.10-1.fc20.x86_64 .

Could you please attach a screen shot of wrong strings. I have a suspicion that I'm looking at different screens.

--- Additional comment from Alick Zhao on 2014-02-08 07:20:26 CET ---

Here is a screenshot of the issue. Note the texts in big window is in Simplified Chinese, but the texts in small dialogue is in Traditional Chinese.

Versions:
gnome-abrt-0.3.5-1.fc20.x86_64

--- Additional comment from Jakub Filak on 2014-02-08 09:40:20 CET ---

Thank you! '.UTF-8' suffix was causing problems.

Upstream commit e652d1c2604eac52b622ded3839e94bc742a5c50 fixes this bug.