On Wednesday 17 August 2005 05:02, Chusslove Illich wrote:
(...)
> > [: Krzysztof Lichota :]
> > I am now thinking rather about making widgets accept only KI18n
> > reference, so that developer must wrap each message in i18n(). This
> > would not affect current (correct) code.
>
> Uh-oh, now we are talking about some angry people :) Aside from that one,
> there are two other problems that I see.
>
> First is conceptual. Can we really, without ambiguity, decide what
> parameter is to be KI18n and what not? I wouldn't bet...
>
> Second is technical. At some places naked strings wrapped in I18N_NOOP
> macros are used, so that translation really happens later (like in startup
> phase, for about data, before translation layer has been initialized).
> Then, rather than KDE widgets at places Qt widgets are used.

Yes, that is also the major obstacle that I see. How to make it work with 
Qt's .ui files.

Have a nice day!