why kdelibs?

Chusslove Illich caslav.ilic at gmx.net
Fri Oct 29 17:01:30 BST 2010

>> [: Stephen Kelly :]
>> KLocale: More powerful i18n than QObject::tr and friends. Based on
>> gettext.
> [: Kevin Ottens :]
> Why not push its features in Qt itself?

Gettext itself (format, runtime, tools) is a feature. So "pushing features"
would, for one, mean replacing Qt's current translation systems with a
Gettext-based one. Which is obviously not going to happen (since it didn't
happen in the first place).

The most important feature specific to KDE on top of Gettext is Transcript (
http://techbase.kde.org/Localization/Concepts/Transcript). Gettext is not a
prerequisite here, so it could be added to Qt system as it is. But this
won't happen either, as it is too complicated for target clients (based on
private communication with Oswald).

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

More information about the kde-core-devel mailing list