[GRASS-translations] incorrect refs?

[Maxim Dubinin]

Hi all,

We've another community effort underway to translate GRASS POs in
Russian, but here is one thing which looks suspicious.

It seems that some of the references to the code are incorrect, here
is an example from grassmods_ru.po:

> #: ../raster/r.cost/main.c:275 ../raster/r.walk/main.c:392
> msgid "Input null cell will be retained into output map"
> msgstr ""

If I look this code up in grass-6.3.0, first ref is this:
>G_fatal_error(_("No start points"));
and second is a blank line. I.e. links are wrong?

I wonder if this is either ok or minor code/refs error, or this is bigger and
we should fix it first before translating (this I'm little scared to
think of).

I checked some other links, they are ok.
--
Best regards,
 Maxim                          mailto:[hidden email]
 http://gis-lab.info


_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations

[Martin Landa]

Hi,

2008/8/2 Maxim Dubinin <[hidden email]>:

> It seems that some of the references to the code are incorrect, here
> is an example from grassmods_ru.po:
>
>> #: ../raster/r.cost/main.c:275 ../raster/r.walk/main.c:392
>> msgid "Input null cell will be retained into output map"
>> msgstr ""
>
> If I look this code up in grass-6.3.0, first ref is this:
>>G_fatal_error(_("No start points"));
> and second is a blank line. I.e. links are wrong?

take a look at locale/README file.

In locale directory run first

make pot
make update-po

to update PO files.

Good luck, мартин

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *

_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations

[Maxim Dubinin]

Thanks, Martin.

I'm afraid no one has experience in dealing with po-files besides
translation itself (which we do with poedit).

Practically, did I understand right, that these incorrect messages are not a big
deal and can be fixed later after the translation by updating?

--
Best regards,
 Maxim                          mailto:[hidden email]
 http://gis-lab.info

Вы писали 2 августа 2008 г., 13:06:00:

ML> Hi,

ML> 2008/8/2 Maxim Dubinin <[hidden email]>:

>> It seems that some of the references to the code are incorrect, here
>> is an example from grassmods_ru.po:
>>
>>> #: ../raster/r.cost/main.c:275 ../raster/r.walk/main.c:392
>>> msgid "Input null cell will be retained into output map"
>>> msgstr ""
>>
>> If I look this code up in grass-6.3.0, first ref is this:
>>>G_fatal_error(_("No start points"));
>> and second is a blank line. I.e. links are wrong?

ML> take a look at locale/README file.

ML> In locale directory run first

ML> make pot
ML> make update-po

ML> to update PO files.

ML> Good luck, мартин


_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations

[Martin Landa]

Hi,

2008/8/2 Maxim Dubinin <[hidden email]>:
> I'm afraid no one has experience in dealing with po-files besides
> translation itself (which we do with poedit).
>
> Practically, did I understand right, that these incorrect messages are not a big
> deal and can be fixed later after the translation by updating?

you should update your PO files before you start translation.

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *
_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations

[Maxim Dubinin]

hmm, now that's scary given how much we've translated.

We took source *_ru.po files from here:
http://trac.osgeo.org/grass/browser/grass/trunk/locale/po

where it says somewhere that the file were updated with the current
code.

the code I used to link was taken from here
http://grass.osgeo.org/grass63/source/grass-6.3.0.tar.gz

So, given that significant portion is translated, what should we do?

--
Maxim

Вы писали 2 августа 2008 г., 13:53:18:

ML> Hi,

ML> 2008/8/2 Maxim Dubinin <[hidden email]>:
>> I'm afraid no one has experience in dealing with po-files besides
>> translation itself (which we do with poedit).
>>
>> Practically, did I understand right, that these incorrect messages are not a big
>> deal and can be fixed later after the translation by updating?

ML> you should update your PO files before you start translation.

ML> Martin


_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations

[Martin Landa]

Hi,

2008/8/2 Maxim Dubinin <[hidden email]>:
> We took source *_ru.po files from here:
> http://trac.osgeo.org/grass/browser/grass/trunk/locale/po
>
> where it says somewhere that the file were updated with the current
> code.
>
> the code I used to link was taken from here
> http://grass.osgeo.org/grass63/source/grass-6.3.0.tar.gz

SVN trunk is not corresponding to grass-6.3.0.tar.gz, its grass7 code
(still very similar to grass6 code-base, but it will change). If you
used po file from trunk you should checkout svn trunk then, see

http://trac.osgeo.org/grass/wiki/DownloadSource

Martin

--
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *
_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations

[Maxim Dubinin]

I should've told where I took our po-files, checking out new svn (https://svn.osgeo.org/grass/grass/trunk) fixed
the references.

Thanks for your help!

--
Maxim                          mailto:[hidden email]

Вы писали 2 августа 2008 г., 14:17:08:

ML> Hi,

ML> 2008/8/2 Maxim Dubinin <[hidden email]>:
>> We took source *_ru.po files from here:
>> http://trac.osgeo.org/grass/browser/grass/trunk/locale/po
>>
>> where it says somewhere that the file were updated with the current
>> code.
>>
>> the code I used to link was taken from here
>> http://grass.osgeo.org/grass63/source/grass-6.3.0.tar.gz

ML> SVN trunk is not corresponding to grass-6.3.0.tar.gz, its grass7 code
ML> (still very similar to grass6 code-base, but it will change). If you
ML> used po file from trunk you should checkout svn trunk then, see

ML> http://trac.osgeo.org/grass/wiki/DownloadSource

ML> Martin


_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations

[Markus Neteler]

On Sat, Aug 2, 2008 at 9:08 PM, Maxim Dubinin <[hidden email]> wrote:

> hmm, now that's scary given how much we've translated.
>
> We took source *_ru.po files from here:
> http://trac.osgeo.org/grass/browser/grass/trunk/locale/po
>
> where it says somewhere that the file were updated with the current
> code.
>
> the code I used to link was taken from here
> http://grass.osgeo.org/grass63/source/grass-6.3.0.tar.gz
>
> So, given that significant portion is translated, what should we do?

It's always possible to merge messages from some version to the
current version. I have written a small script (for me) which calls
msgmerge which does the job.

Indeed, the .po files should be updated from time to time (hi Carlos,
are you still working on this?).

For translators: please submit often! Only then we avoid to get out of sync.

Best,
Markus
_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations

[Maxim Dubinin]

MN> It's always possible to merge messages from some version to the
MN> current version. I have written a small script (for me) which calls
MN> msgmerge which does the job.

This is good to hear.

Martin took time to explain me how version control/svn and related
stuff works, which is really interesting, but I still find it quite
confusing. I also suspect, that I'm not the only one (though I'm
probably a representative of Windows wave which is relatively new to
GRASS and generally unaware of svn etc.) who is confused about how
much steps you need to do besides just translating.

I'd  suggest  it would help having more simple and direct procedure to
people  to start participating and not bothering with checking svn and
running  into  issues  with  code/po relations. We tried Pootle, which
seems  to  be  a  nice  alternative, especially for completely new and
finished  translations  that  require  some  revising. There should be
something else that can be done to make process easier to participate,
I guess.

I know you're great community and always ready to help, so this just a
suggestion and may be you already gave it some thought and I'm all
wrong :)

MN> For translators: please submit often! Only then we avoid to get out of sync.
We will!

--
Best regards,
 Maxim                          mailto:[hidden email]

Вы писали 2 августа 2008 г., 17:30:51:

MN> On Sat, Aug 2, 2008 at 9:08 PM, Maxim Dubinin <[hidden email]> wrote:

>> hmm, now that's scary given how much we've translated.
>>
>> We took source *_ru.po files from here:
>> http://trac.osgeo.org/grass/browser/grass/trunk/locale/po
>>
>> where it says somewhere that the file were updated with the current
>> code.
>>
>> the code I used to link was taken from here
>> http://grass.osgeo.org/grass63/source/grass-6.3.0.tar.gz
>>
>> So, given that significant portion is translated, what should we do?

MN> It's always possible to merge messages from some version to the
MN> current version. I have written a small script (for me) which calls
MN> msgmerge which does the job.

MN> Indeed, the .po files should be updated from time to time (hi Carlos,
MN> are you still working on this?).

MN> For translators: please submit often! Only then we avoid to get out of sync.

MN> Best,
MN> Markus

_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations

[Markus Neteler]

On Sun, Aug 3, 2008 at 7:43 AM, Maxim Dubinin <[hidden email]> wrote:
...
> Martin took time to explain me how version control/svn and related
> stuff works, which is really interesting, but I still find it quite
> confusing. I also suspect, that I'm not the only one (though I'm
> probably a representative of Windows wave which is relatively new to
> GRASS and generally unaware of svn etc.) who is confused about how
> much steps you need to do besides just translating.

Don't worry: for a time we had a translations manager who took care
to lead people through the process. In the end folks just translated
and he did the rest with messages merging.

I'll try to contact him to hear if he plans to continue (hope so!).
If not, we'll find a new person and people like you can just translate.
Makes sense?

> I'd  suggest  it would help having more simple and direct procedure to
> people  to start participating and not bothering with checking svn and
> running  into  issues  with  code/po relations. We tried Pootle, which
> seems  to  be  a  nice  alternative, especially for completely new and
> finished  translations  that  require  some  revising. There should be
> something else that can be done to make process easier to participate,
> I guess.

I agree but it is all a matter of time...

> I know you're great community and always ready to help, so this just a
> suggestion and may be you already gave it some thought and I'm all
> wrong :)

You are all right! It worked very well till recently, just the
translations manager
got busy with something else or summer time or whatever.
We'll work it out!

At OSGEo level, I once proposed
http://wiki.osgeo.org/wiki/Software_Translation_Portal
but wasn't yet successful. Since grass.osgeo.org is running in fact on a
telascience.org machine in San Diego where we have ssh access, we
could try to install some Web based software there.

> MN> For translators: please submit often! Only then we avoid to get out of sync.
> We will!

Perfect.
If you want, I can send you the updated .po files so that you can
start translating
directly.

Markus
_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations

[Carlos Dávila]

> You are all right! It worked very well till recently, just the
> translations manager
> got busy with something else or summer time or whatever.
I apologize for being disappeared for so long time, but I've been
working on other projects and left aside GRASS for some time. This list
has also been muted for a long time and it helped me forget the project.
For the next 3-4 month I'll be really busy, but I can try to put po
files up to date in a few days, so translators just have to translate
and can forget other things.
Regards
Carlos
_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations

[Maxim Dubinin]

Hi all,

probably another really simple question. I've considerable amount of
commented lines without code references in the end of my POs (for example grasslibs_ru.po, last svn).

#, fuzzy
#~ msgid "Can't open directory %s"
#~ msgstr "вектор  "

Should I translate them? What are they for anyway?

--
 Maxim                          mailto:[hidden email]

Вы писали 2 августа 2008 г., 11:18:25:

MD> Hi all,

MD> We've another community effort underway to translate GRASS POs in
MD> Russian, but here is one thing which looks suspicious.

MD> It seems that some of the references to the code are incorrect, here
MD> is an example from grassmods_ru.po:

>> #: ../raster/r.cost/main.c:275 ../raster/r.walk/main.c:392
>> msgid "Input null cell will be retained into output map"
>> msgstr ""

MD> If I look this code up in grass-6.3.0, first ref is this:
>>G_fatal_error(_("No start points"));
MD> and second is a blank line. I.e. links are wrong?

MD> I wonder if this is either ok or minor code/refs error, or this is bigger and
MD> we should fix it first before translating (this I'm little scared to
MD> think of).

MD> I checked some other links, they are ok.

_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations

[Glynn Clements]

Maxim Dubinin wrote:

> probably another really simple question. I've considerable amount of
> commented lines without code references in the end of my POs (for example grasslibs_ru.po, last svn).
>
> #, fuzzy
> #~ msgid "Can't open directory %s"
> #~ msgstr "вектор  "
>
> Should I translate them? What are they for anyway?

AFAICT, messages marked #~ are "obsolete"; the help for the msgattrib
program says:

`--no-obsolete'
     Remove obsolete #~ messages.

`--only-obsolete'
     Keep obsolete #~ messages, remove all other messages.

I can't find that particular string anywhere in the source code, so it
appears to be a translation of a string which no longer appears in the
source code.

--
Glynn Clements <[hidden email]>
_______________________________________________
grass-translations mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/grass-translations