Re: [Qgis-developer] Backport of master feature in QGIS 2.18
2016-10-18 11:40 GMT+02:00 Jürgen E. Fischer : > Hi Harrissou, > > On Tue, 18. Oct 2016 at 11:30:57 +0200, DelazJ wrote: > > > Transifex is already target for QGIS3 (as it sticked with master). > > > > @Jürgen, are you sure about that? > > Yes. But it's not updated regularly. So you might find stuff that isn't > in > master anymore, but still appears in master_2. Not sure if that fits your > example. > > Actually, the string still exists in both file but not at the same row (few lines differences). And it's the address in master_2 that matches the one in Transifex. But I trust you if you say 2.18 is not being translated in Transifex. Could be nice to announce the interim steps of 2.18 translation in the translators/community(?) list. Harrissou > > > master_2, we talked about returning to the old scheme (ie. > > > scripts/update_ts_files.sh and committing language update individual). > > > As stated above, I don't know if this decision is effective but I'm not > sure > > translators were informed about it. > > I'm not sure either. And at the time it wasn't clear that there would be > any > more 2.x releases at all. > > > Jürgen > > > -- > Jürgen E. Fischer norBIT GmbH Tel. > +49-4931-918175-31 > Dipl.-Inf. (FH) Rheinstraße 13 Fax. > +49-4931-918175-50 > Software Engineer D-26506 Norden > http://www.norbit.de > QGIS release manager (PSC) GermanyIRC: jef on FreeNode > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Backport of master feature in QGIS 2.18
Hi, 2016-10-18 2:02 GMT+02:00 Jürgen E. Fischer : > Hi Even, > > On Thu, 13. Oct 2016 at 12:18:38 +0200, Even Rouault wrote: > > - this PR adds new strings to translate (the DBManager changes might > also). > > Will translators do another round of translations for 2.18.x ? If not, > this > > might not be material appropriate for 2.18.x > > Transifex is already target for QGIS3 (as it sticked with master). @Jürgen, are you sure about that? Looking at the metadata of this new string in Transifex ( https://www.transifex.com/qgis/QGIS/translate/#fr/qgis-application/96618210 - sorry, it may not be visible to all), it appears that its source is ../src/ui/qgslabelingguibase.ui:4009 While https://github.com/qgis/QGIS/blob/master_2/src/ui/ qgslabelingguibase.ui#L4009 leads to the same strings, https://github.com/qgis/QGIS/blob/master/src/ui/qgslabelingguibase.ui#L4009 doesn't. > For > master_2, we talked about returning to the old scheme (ie. > scripts/update_ts_files.sh and committing language update individual). > As stated above, I don't know if this decision is effective but I'm not sure translators were informed about it. Afaics, I didn't see such information and believed that (if my previous assumptions are false) I was translating the next release (2.18) in Transifex and not the one after. And unfortunately I may not be alone. Regards, Harrissou > > - as we are in 2.18.0 feature freeze, must I wait for 2.18.0 to be > released > > before backporting (depending on previous question) ? > > When we decided on the time frame for 2.18 in Bonn, we also decided that > you > can add your geopackage improvements into 2.18.1 and I can add DWG support > once > it ready - regardless of the feature freeze that normally applies to > releases. > IMHO it shouldn't be applied now before 2.18 is released. > > > Jürgen > > -- > Jürgen E. Fischer norBIT GmbH Tel. > +49-4931-918175-31 > Dipl.-Inf. (FH) Rheinstraße 13 Fax. > +49-4931-918175-50 > Software Engineer D-26506 Norden > http://www.norbit.de > QGIS release manager (PSC) GermanyIRC: jef on FreeNode > > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Backport of master feature in QGIS 2.18
Hi Even, On Thu, 13. Oct 2016 at 12:18:38 +0200, Even Rouault wrote: > - this PR adds new strings to translate (the DBManager changes might also). > Will translators do another round of translations for 2.18.x ? If not, this > might not be material appropriate for 2.18.x Transifex is already target for QGIS3 (as it sticked with master). For master_2, we talked about returning to the old scheme (ie. scripts/update_ts_files.sh and committing language update individual). > - as we are in 2.18.0 feature freeze, must I wait for 2.18.0 to be released > before backporting (depending on previous question) ? When we decided on the time frame for 2.18 in Bonn, we also decided that you can add your geopackage improvements into 2.18.1 and I can add DWG support once it ready - regardless of the feature freeze that normally applies to releases. IMHO it shouldn't be applied now before 2.18 is released. Jürgen -- Jürgen E. Fischer norBIT GmbH Tel. +49-4931-918175-31 Dipl.-Inf. (FH) Rheinstraße 13 Fax. +49-4931-918175-50 Software Engineer D-26506 Norden http://www.norbit.de QGIS release manager (PSC) GermanyIRC: jef on FreeNode pgpLOObnfJ9aq.pgp Description: PGP signature ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Backport of master feature in QGIS 2.18
Hi, Even, I think your message also question the strategy followed for translation: one version at time and as soon as a version is released, let's focus on the next one. I'm refering to Transifex, of course, which is the default and most encouraged interface for translation. This means that normally, once 2.18.0 is released, strings available in Transifex wil focus on the next release (master_2? master?). Translators are no longer able to translate QGIS 2.18 strings from Transifex web interface. The only step I'm aware of and that could ensure a kind of translation for new strings is that translators individually pull texts from source, translate them and make PR against 2.18 branch. Something that few people will likely do. @devs after qgis 2.18 is released, will the master_2 branch kept? For a 2.20 version? If no master_2 and thus 2.20 is expected, maybe we could keep Transifex focus on what would be the 2.18 branch and people will easily continue translating. And maybe at some stage (when 3.0 release schedule is more clear), we'll push master branch into Transifex and people begin translating 3.0 release... Unless there's a way to have two branches being translated at the same time? That said, if compatible, I'd prefer to have a feature backported, even with some parts in english (actually, there are 14 on 40 activated languages that have more than 90% translated - people can still find web translators if needed) rather than no feature. my 2cts, Harrissou 2016-10-17 16:27 GMT+02:00 Even Rouault : > Any opinion ? > > > Hi, > > > > I'm currently working on improving geopackage support in QGIS and a first > > part of this is https://github.com/qgis/QGIS/pull/3597 (other part will > be > > DBManager changes) > > It has been raised that this would be worth backporting in QGIS 2.18.x, > > hence a few questions: > > - this PR adds new strings to translate (the DBManager changes might > also). > > Will translators do another round of translations for 2.18.x ? If not, > this > > might not be material appropriate for 2.18.x > > - as we are in 2.18.0 feature freeze, must I wait for 2.18.0 to be > released > > before backporting (depending on previous question) ? > > > > Even > > -- > Spatialys - Geospatial professional services > http://www.spatialys.com > ___ > Qgis-developer mailing list > Qgis-developer@lists.osgeo.org > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
Re: [Qgis-developer] Backport of master feature in QGIS 2.18
Any opinion ? > Hi, > > I'm currently working on improving geopackage support in QGIS and a first > part of this is https://github.com/qgis/QGIS/pull/3597 (other part will be > DBManager changes) > It has been raised that this would be worth backporting in QGIS 2.18.x, > hence a few questions: > - this PR adds new strings to translate (the DBManager changes might also). > Will translators do another round of translations for 2.18.x ? If not, this > might not be material appropriate for 2.18.x > - as we are in 2.18.0 feature freeze, must I wait for 2.18.0 to be released > before backporting (depending on previous question) ? > > Even -- Spatialys - Geospatial professional services http://www.spatialys.com ___ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer