[GRASS-dev] [GRASS-SVN] r71471 - grass/trunk/locale/po

GRASS GRASS developer
1

On Wed, Sep 6, 2017 at 8:19 PM, <svn_grass@osgeo.org> wrote:

Author: mlennert
Date: 2017-09-06 11:19:48 -0700 (Wed, 06 Sep 2017)
New Revision: 71471

Modified:
   grass/trunk/locale/po/grasswxpy_fr.po
Log:
french GUI translations: dangerous confusion between exiting GRASS and closing GUI

Modified: grass/trunk/locale/po/grasswxpy_fr.po

I think this get lost: it needs to be fixed in transifex.
Or did you fix it also there?

Markus

2

On 06/09/17 20:55, Markus Neteler wrote:

On Wed, Sep 6, 2017 at 8:19 PM, <svn_grass@osgeo.org> wrote:

Author: mlennert
Date: 2017-09-06 11:19:48 -0700 (Wed, 06 Sep 2017)
New Revision: 71471

Modified:
    grass/trunk/locale/po/grasswxpy_fr.po
Log:
french GUI translations: dangerous confusion between exiting GRASS and closing GUI

Modified: grass/trunk/locale/po/grasswxpy_fr.po

I think this get lost: it needs to be fixed in transifex.
Or did you fix it also there?

No, but will do immediately. I wanted to make sure it's in the tree before the release is tagged.

So, we should not touch po files in the source tree anymore ?
(Sorry, I know this was discussed, but I just don't remember)

Moritz

3

On 06/09/17 21:03, Moritz Lennert wrote:

On 06/09/17 20:55, Markus Neteler wrote:

On Wed, Sep 6, 2017 at 8:19 PM, <svn_grass@osgeo.org> wrote:

Author: mlennert
Date: 2017-09-06 11:19:48 -0700 (Wed, 06 Sep 2017)
New Revision: 71471

Modified:
     grass/trunk/locale/po/grasswxpy_fr.po
Log:
french GUI translations: dangerous confusion between exiting GRASS and closing GUI

Modified: grass/trunk/locale/po/grasswxpy_fr.po

I think this get lost: it needs to be fixed in transifex.
Or did you fix it also there?

No, but will do immediately.

Done.

Moritz

4

On Wed, Sep 6, 2017 at 9:03 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
...

No, but will do immediately. I wanted to make sure it's in the tree before
the release is tagged.

ok fine.

So, we should not touch po files in the source tree anymore ?

Yes, we translate in transifex and then (still manually) merge into
the source code. I did that recently.

From what I understood (Luca knows best) I described the procedure here:

https://trac.osgeo.org/grass/browser/grass/trunk/locale/README#L116

TODO: make the merge-back into trunk and relbranch72 a cronjob on the
grass.osgeo.org server.
Yet I had to do several manual cleanups after the merge, so probably a
cronjob is impossible.

Markus

5

Hi,

···

2017-09-06 21:24 GMT+02:00 Markus Neteler <neteler@osgeo.org>:

On Wed, Sep 6, 2017 at 9:03 PM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
…

No, but will do immediately. I wanted to make sure it’s in the tree before
the release is tagged.

ok fine.

So, we should not touch po files in the source tree anymore ?

Yes, we translate in transifex and then (still manually) merge into
the source code. I did that recently.

From what I understood (Luca knows best) I described the procedure here:
https://trac.osgeo.org/grass/browser/grass/trunk/locale/README#L116

TODO: make the merge-back into trunk and relbranch72 a cronjob on the
grass.osgeo.org server.
Yet I had to do several manual cleanups after the merge, so probably a
cronjob is impossible.

just out of curiosity… what kind of cleanups? Is there anything we could do when translating to avoid those cleanups afterwards?

Vero

6

On Sun, Sep 10, 2017 at 5:41 PM, Veronica Andreo <veroandreo@gmail.com> wrote:

2017-09-06 21:24 GMT+02:00 Markus Neteler <neteler@osgeo.org>:

...

Yes, we translate in transifex and then (still manually) merge into
the source code. I did that recently.

From what I understood (Luca knows best) I described the procedure here:
https://trac.osgeo.org/grass/browser/grass/trunk/locale/README#L116

TODO: make the merge-back into trunk and relbranch72 a cronjob on the
grass.osgeo.org server.
Yet I had to do several manual cleanups after the merge, so probably a
cronjob is impossible.

just out of curiosity... what kind of cleanups? Is there anything we could
do when translating to avoid those cleanups afterwards?

For example,
- disconnected (i.e. unused) translations accumulate at the end of the
.po files. This needs to be trimmed from time to time. There is a
gettext tool for that but it doesn't seem to have much effect
- if a new language is initiated on transifex, several .po file header
lines are not populated properly. To be fixed manually or some
advanced "sed" magic
- "make verify" reveils errors which need to be manually fixed.

Not sure how to address these issues in a scripted way.

Markus

7

On 10 September 2017 at 18:11, Markus Neteler <neteler@osgeo.org> wrote:

For example,
- disconnected (i.e. unused) translations accumulate at the end of the
.po files. This needs to be trimmed from time to time. There is a
gettext tool for that but it doesn't seem to have much effect
- if a new language is initiated on transifex, several .po file header
lines are not populated properly. To be fixed manually or some
advanced "sed" magic
- "make verify" reveils errors which need to be manually fixed.

Not sure how to address these issues in a scripted way.

could we check with other projects like QGIS or ZOO?

Markus

--
ciao
Luca

www.lucadelu.org

8

On 6 September 2017 at 21:24, Markus Neteler <neteler@osgeo.org> wrote:

From what I understood (Luca knows best) I described the procedure here:
https://trac.osgeo.org/grass/browser/grass/trunk/locale/README#L116

this is also what I know..

Markus

--
ciao
Luca

www.lucadelu.org