Finalized proposal for changes to i18n in KF5

[Dominik Haumann]

On Saturday, December 22, 2012 10:44:22 AM Chusslove Illich wrote:
> I have written up the headers and Doxygen pages for the Ki18n framework as
> it should finally look like, available here:
> 
>   http://nedohodnik.net/misc/ki18n-kf5-01/html/index.html
>   http://nedohodnik.net/misc/ki18n-kf5-01/klocalizedstring.h
>   http://nedohodnik.net/misc/ki18n-kf5-01/kuitmarkup.h
> 
> As I have proposed earlier on k-c-d, this introduces two major changes.
> 
> The first change is that every i18n call looks up translations in strictly
> one catalog, which is even determined statically in library code (i.e. at
> compile time). This will stop undefined results when several catalogs in use
> contain the same message. The section "Connecting Calls to Catalogs" in the
> documentation above shows how to make the link.
> 
> The second change is that KUIT markup is gone -- if not quite. It is totally
> gone from i18n* calls; one can always write an i18n* call and be sure that
> there will be no markup processing. But I just couldn't plainly kill it (a
> few people were not happy with that either), so I added separate markup-
> aware xi18n* calls. Markup processing is now stricter, but allows
> customization (new tags, etc). The section "Semantic Markup" describes this.

Following e.g. QUrl, QSql, QXml, ..., shouldn't it be KUitSetup instead of 
KUITSetup etc?

And the API documentation should at least state once what KUIT stands for.
K User Interface Translator? Just a guess, and probably wrong ;)

Greetings,
Dominik