On Mon, Mar 17, 2014, at 15:09, Albert Astals Cid wrote: > El Dilluns, 17 de març de 2014, a les 08:25:59, Aurélien Gâteau va > escriure: > > On Sat, Mar 15, 2014, at 8:52, Albert Astals Cid wrote: > > > El Divendres, 14 de març de 2014, a les 03:48:49, Aurélien Gâteau va > > > > > > escriure: > > > > Hi, > > > > > > > > I started working on ensuring frameworks can be correctly localized and > > > > have some questions. > > > > > > > > # Messages.sh place > > > > > > > > I noticed some frameworks already have Messages.sh files in there. Most > > > > of them are in src/. Some are in subdirs of src/ (kio, plasma-framework, > > > > solid, kwallet, kactivities, kde4support). Are we OK with src/ being the > > > > default place, but then its up to the framework maintainer to adjust > > > > based on the framework needs? > > > > > > > > I already updated the framework template in kde:kdeexamples to put a > > > > Messages.sh in src/. > > > > > > > > # No translations > > > > > > > > Some frameworks have no translatable strings. I think in this case there > > > > should not be any Messages.sh file. Is it OK for everybody? > > > > > > Do we want to to guarantee they will keep having no translatable strings > > > in > > > future releases? How do we do it? Or just add a Messages.sh if they have > > > translatable strings in the future? > > > > You are right, it feels safer to add a Messages.sh by default. > > But if you do that you also need to add the code to load the catalog (for > the > non ki18n based ones since ki18n will do it automatically).
Yes. I am currently working on a way to streamline catalog loading for Qt-based translations (going to post about it in a few minutes), but it would still need some manual work for the framework user. So I guess it's still an opened question. Aurélien _______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
