Ki18n mostly ready

[Chusslove Illich]

> [: Albert Astals Cid :]
> How would that
>     set(TRANSLATION_DOMAIN "foobar")
> help you knowing if you want a i18n() or a tr() based system?

It would automatically use i18n() if TRANSLATION_DOMAIN is defined :)
Because it would have no purpose with tr()-based code.

>> [: Chusslove Illich :]
>> (Of the usual non-code files, only .rc files in principle (?) cannot be
>> handled in this way; would need .rc.cmake treatment, or else manually.)
>
> [: Albert Astals Cid :]
> I got lost here.

Code files can get TRANSLATION_DOMAIN everywhere through CMake-configured
header (.h.cmake). .ui and .kcfg files are converted to code at build time,
so TRANSLATION_DOMAIN can be passed along through command line options of
the the tools that interpret them. That leaves .rc files, which are
interpreted at runtime. They have to carry information about the translation
domain within them, in attribute to top tag. So this attribute has either to
be set manually, or there should be .rc.cmake files which are configured at
build time with CMake. I think.

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