Re: RFC on framework localization
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
Re: RFC on framework localization
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. Aurélien ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: RFC on framework localization
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). No? Cheers, Albert Aurélien ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: RFC on framework localization
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? Cheers, Albert ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
RFC on framework localization
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? For the record, here is the list of frameworks without any translatable strings (found out after creating Messages.sh for them and getting no .pot generated when testing it) - attica - karchive - kcrash - kdeclarative - kded - kdesu - kdewebkit - kemoticons - kf5umbrella - kguiaddons - kidletime - kimageformats - kitemmodels - kjs - kmediaplayer - kplotting - threadweaver Aurélien ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: RFC on framework localization
On Fri, Mar 14, 2014 at 11:48 AM, Aurélien Gâteau agat...@kde.org wrote: 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? It's fine with me, no file should work too. For the record, here is the list of frameworks without any translatable strings (found out after creating Messages.sh for them and getting no .pot generated when testing it) - attica - karchive - kcrash - kdeclarative - kded - kdesu - kdewebkit - kemoticons - kf5umbrella - kguiaddons - kidletime - kimageformats - kitemmodels - kjs - kmediaplayer - kplotting - threadweaver Aurélien ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel Thanks a lot Aurélien for taking care of this. BTW, is there everything in place for non-KI18n modules to be translated? Aleix ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
Re: RFC on framework localization
On Fri, Mar 14, 2014, at 8:55, Aleix Pol wrote: BTW, is there everything in place for non-KI18n modules to be translated? I am currently looking into this, some CMake code needs to be written and integrated in the release tarball at some point. Following Albert advice, I am looking at how Trojita does it. Aurélien ___ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
