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

List:       kde-i18n-doc
Subject:    Re: Loading Qt 5 translations
From:       Albert Astals Cid <aacid () kde ! org>
Date:       2014-06-08 22:04:03
Message-ID: 13118939.rFeU0Hy8ZH () xps
[Download RAW message or body]

El Dimarts, 27 de maig de 2014, a les 07:08:45, Aurélien Gâteau va escriure:
> On Mon, May 26, 2014, at 9:41, Alexander Potashev wrote:
> > 2014-05-26 18:17 GMT+04:00 Aurélien Gâteau <agateau@kde.org>:
> > > Not sure where we could put this. Frameworks load their translations, I
> > > believe it should be up to Qt to load its own translations. The only
> > > framework where it could maybe make sense to add such feature is in
> > > KI18n, but even there it feels a bit out of place.
> > 
> > Aurélien,
> > 
> > You can't put .qm loading code in KI18n because Tier 1 frameworks
> > should not depend on KI18n.
> 
> I know, but I think we can assume devs who only use Qt and tier 1
> frameworks are aware that they need to load Qt translations themselves.
> This problem is not limited to frameworks: if you create a Qt-only
> application and make use of QDialogButtonBox or QMessageBox, then you
> already have to load Qt translations yourself, regardless of whether you
> are using KDE frameworks or not.

So we have a cmake macro that loads code to load your own Qt catalog. Can we 
have one cmake macro that creates the code to load the Qt "default" catalogs? 

Would that help? I don't want to make it hard, otherwise most devels will 
forget.

Cheers,
  Albert

> 
> Aurélien

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

Configure | About | News | Add a list | Sponsored by KoreLogic