Description of problem:
The string "Display" is not shown correctly in the ko_KR locale.
I did a msgunfmt on the mo file and the entry is correct.
msgstr "íë©´ íì"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
The string "Display" is shown as "3"
The string should be displayed as "íë©´ íì"
Created attachment 106699 [details]
scrrenshot of firstboot in the ko_KR locale
Thanks larry for creating the bugzilla.
I confirm that po file has correct translation..so let's light the
fire and find the cause of this problem!
huh, interesting. I haven't a slightest idea why that
displays the "display" string as "3"
It seems to display "3" regardless of whats in
the translated string. No other translations
seem to do this.
Course, now that I do a make install from cvs,
it seems to work. screenshot attached.
I'll refresh the po's and rebuild and see if
that works. But since this isnt on any blocker
lists, it's probably too late.
Created attachment 108051 [details]
screenshot showing ko_KR screen with current cvs firstboot
From the latest screenshot just posted by Adrian, "the string
"Display" is shown as "3" problem seems fixed but I found
"Configure..." button is shown in English.
This is odd. I checked the entry in the ko.po file and it is translated:
#~ msgid "Configure..."
#~ msgstr "ì¤ì ..."
so it shouldn't be in English.
Could you look into this matter?
Tested with firstboot-1.3.39-2 and up2date-184.108.40.206-2, this strange "3" still exist.
This is actually a bug in system-config-display. If you look at the display
module in firstboot, you'll see:
So, we are translating in the s-c-display domain. Then if you msgunfmt
/usr/share/locale/ko/LC_MESSAGES/system-config-display.mo, you'll see:
This domain's translation is overriding the correct one in firstboot. Still
present in RHEL4 final, by the way.
Thanks for spotting this.
Now I have updated the file as follows:
msgstr "íë©´ íì"
The latest ko.po file's revision number is 1.57
Thank you Lawrence for looking into this matter as well as Chris!
So does this still need fixing in RHEL4?
The component this request has been filed against is not planned for inclusion
in the next update. The decision is based on weighting the priority and number
of requests for a component as well as the impact on the Red Hat Enterprise
Linux user-base: other components are considered having higher priority and the
number of changes we intend to include in update cycles is limited.
Product Management has reviewed and declined this request. You may appeal this
decision by reopening this request.