> > The disadvantage of using QObject::tr() compared to qApp->translate()
>
> eh? from what you wrote earlier i got the impression it is exactly the
> other way round.
You're right, kind of confusing. This is how I understood how it works:
When using QCoreApplication::translate() you have to pr
> The disadvantage of using QObject::tr() compared to qApp->translate()
eh? from what you wrote earlier i got the impression it is exactly the
other way round.
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/
> > Another consideration is that tr() is only available in classes
> derived
> > from
> > QObject - but since normally the strings you want to translate are
> > generated
> > in Gui-classes this is normally the case.
>
> iirc tr is a static method of QObject, ie QObject::tr() should be
> possible
> Another consideration is that tr() is only available in classes derived
> from
> QObject - but since normally the strings you want to translate are
> generated
> in Gui-classes this is normally the case.
iirc tr is a static method of QObject, ie QObject::tr() should be possible
regardless
ocati
> Sent: Thursday, April 30, 2009 6:41 AM
> To: List for Openmoko community discussion
> Subject: Re: [QtEI] Translation suggestion
>
> On the doc.trolltech.com, there isn't written that QApp->translate is
> better than tr, if I read correctly.
>
> http://doc.trollt
On the doc.trolltech.com, there isn't written that QApp->translate is
better than tr, if I read correctly.
http://doc.trolltech.com/4.5/qobject.html#tr
http://doc.trolltech.com/4.5/qcoreapplication.html#translate
Then is better leaving the tr() or switching to QApp->translate()?
On Sun, Apr 26,
On Sun, 26 Apr 2009 23:14:05 +0200
Fabio Locati wrote:
> I have looked around and it seems that QtEI should be translated with
> Qt Linguistic. Is this the best tool?
>
I don't know the tool, but I do believe there's much work to be done
here: many classes still use "" while I believe every cla
7 matches
Mail list logo
