Bugzilla – Bug 106104
SL10_LOC - Linux - DE - Beta2 050819
Last modified: 2005-09-07 15:28:26 UTC
Detailed Description: YaST software install: Languages: language names untranslated Build: Beta2 050819 Steps to reproduce: 1. Click Start/System/YaST to launch YaST Control Center 2. Click the "Software" option in the left navigational panel. 3. Click "Install and remove software"option. 4. Change the filter to "Languages" Expected result: all language names should be translated. Actual result: all language names are untranslated. The country names in brackets behind some languages are translated correctly Attachment: software_install_3.jpg
Created attachment 46856 [details] install and remove software, languages filter
Also a bug on Japanese Beta2 050819 build.
Created attachment 46869 [details] Japanese language filter
Also occuring on Simplified Chinese, build Beta 2 050822
Created attachment 46887 [details] Simplified Chinese language filter
Configuration: Suse 10
Unable to find the string "German (Deutschland)" in the language list from the screenshot. Can you help to source this string?
btw, it's package-manager, not language selection
Also occurs in Traditional Chinese build Beta 2 050819.
I have not been able to find any untranslated language name in the Japanese or Chinese YaST po files, so I guess this is not a translation bug. Klaus, any ideas?
Also occurs in Italian
Also occuring on Brazilian Portuguese, Beta 2
Those are from iso-languages.pot AFAIK the translation of these strings were recently provided using some public available translations - Karl?
I guess "de_DE" is aggregated "German" + "Germany" and both these strings are translated here: #: src/ISOLanguage.cc:237 msgid "German" msgstr "Deutsch" #. :CZE:203: #: src/ISOCountry.cc:265 msgid "Germany" msgstr "Deutschland" I guess Yast must pickup the first part of the message from the different textdomain named "iso-languages". In case of doubt, please ask.
Not me: it's package manager as I wrote already.
Not package manager, but liby2util. Anyway, it's not a matter of translations. ISOLanguage and ISOCountry contain a static map, which holds the translated strings. Map entries are currently created by cm["de"] = _( "German" ); Once created, they are not rebuilt if the language changes. Due to some change in YaST, an ISOLanguage object gets created before gettext is initialized. That's why the map is initialized in english. In fact the map should be created as cm["de"] = "German"; A translated value should be returned when accessing the map, not when it is built.
fixed in liby2util-2.12.8