[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Is QObject::tr() OK, or should one always use i18n & friends?
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2015-06-22 22:00:28
Message-ID: 4287611.qNYgOBMYo4 () xps
[Download RAW message or body]

El Dilluns, 8 de juny de 2015, a les 22:47:51, Burkhard Lück va escriure:
> Am Sonntag, 7. Juni 2015, 19:30:41 schrieb Milian Wolff:
> > as the title says - is tr() OK or should one always prefer to use i18n &
> > friends from KLocalizedString?
> 
> First and foremost this is a developers decision about the dependencies of
> his software.
> 
> Scripty supports:
> 
> * Qt only translation system -> tr()  -> catalog naming scheme foo_qt.po
> 
> * Mixed Qt + gettext translation system, e.g. like in marble, using tr() to
> extract to catalog named foo_qt.po and i18n to extract to catalogs named
> foo.po

AFAIR this is only available for kdelibs4-based projects only.

Cheers,
  Albert

> 
> * pure xgettext translation system -> i18n
> 
> From a translators point of view I'd prefer i18n (due to KUIT, Scripting,
> context) compared to Qt translation system.
> 
> Thanks for asking for advice.

[prev in list] [next in list] [prev in thread] [next in thread]