Fwd: Using multiple klocales uses stale translations

[Chusslove Illich]

> [: Stephen Kelly :]
> Clearly someone decided that should be commented out. Should what I am
> trying work already, or does that need to be uncommented?

It was I who both added and later commented out that code. As per the note,
I commented it out because I didn't think of the use case, even though
KLocalizedString::toString methods advertise the capability :) So it should
be uncommented, but let me first check what it will do to performance.

>   KLocale de("kwrite", "de");
>   [...]
>   kDebug() << de.formatDate(now, KLocale::ShortDate);
>   kDebug() << fr.formatDate(now, KLocale::ShortDate);
>
> I always get the date in the system locale instead of de or fr. Shouldn't
> that work?

The second argument to KLocale constructor is the language, whereas the date
is determined by country, which is the third parameter. If the country
parameter is left out, it is fetched from "the system" (whatever that
means), hence what you are seeing.

-- 
Chusslove Illich (Часлав Илић)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20101108/f30e4d50/attachment.sig>