need an idea for kxkb (multiple variants UI)

[Andriy Rysin]

Nicolas Goutte wrote:
> On Friday 03 March 2006 12:33, Nicolas Goutte wrote:
>   
>> On Thursday 02 March 2006 17:25, Andriy Rysin wrote:
>>     
>>> Nicolas Goutte wrote:
>>>       
>>>> On Thursday 02 March 2006 09:38, Nicolas Goutte wrote:
>>>>         
>>>>> On Thursday 02 March 2006 05:30, Andy Rysin wrote:
>>>>>           
>>>>>>> On Wednesday 01 March 2006 15:33, Andriy Rysin wrote:
>>>>>>>               
>>>>>> Well there's worse problem with translation I've just discovered: the
>>>>>> name for layouts  in XFree were adjectives (Belgian, Thai, Finnish)
>>>>>> and in some version Xorg it's changed to nouns (Beglium, Thailand,
>>>>>> Finland). As strings for tranlsation in KDE are still old that means
>>>>>> almost all of layout names will be untranslated for new versions of
>>>>>> Xorg. So I don't know if one UI string will go untraslated in some
>>>>>> languages :(
>>>>>>             
>>>>> We have translations of country names already in KDE, see kdebase/l10n.
>>>>> The problem is how to use it in kxkb. (I have no idea right now.)
>>>>>           
>>>> You can look at kdebase/kcontrol/locale/kcmlocale.cpp from line 257 on,
>>>> the function KLocaleConfig::loadCountryList
>>>> (Apparently there is not any other way than to load the .entry files.)
>>>>         
>>> hmm, that means to translate list of countries I need to load (and
>>> parse) >200 files? Does not look like acceptable way to me :(
>>>
>>> Can anybody tell me if its hard to have things like Country name
>>> translations in common *.po files so that we could reuse them with
>>> simple insertCatalog() ???
>>>       
>> If you really must, you can use desktop_kdebase.po. But it would be the
>> first time a desktop*.po module is called directly in KDE (as there were
>> not meant for that).
>>     
>
> Sorry, I have realized that you cannot do that as desktop*.po files are not 
> packaged for the release.
>   
Yes, that's what I found, it's there but not in release. The question 
would be for core people if it's ok to include desktop_kdebase.po into 
release, should not be too hard unless there's architectural reasons not 
to do it?

Thanks,
Andriy