KLocale and rejecting languages if the application is not translated

[Aaron J. Seigo]

hi ...

see: http://bugs.kde.org/show_bug.cgi?id=172774

the cause of the problem is that the desktop:/ ioslave has no translatable 
strings (and is a QCoreApplication if that matters any?) and therefore when 
setLanguage is called on KLocale upon construction when calling 
KGlobal::locale(), the default local language is rejected.

this is all well and good until we try and access anything via KConfig, 
including KDesktopFile, and then all entries come out untranslated.

i've added a little hack to kio_desktop for 4.2 to work around this (it now 
manually calls setLanguage), but i wonder if it makes sense to allow the 
language through if there is no mainCatalog at all for the application? or, 
probably even more sensibly, is there some reasonable way to separate the 
concept of "the language to use when translating the application" and "the 
language to use when accessing KConfig data".

because right now *any* application which is not translated into the local 
language will also show all KConfig data untranslated afaics.

so, localization gurus: any thoughs?

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090103/8e42aeae/attachment.sig>