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 s
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
> > migh
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 targ
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 norma
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:
>
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 t
