[GRASS-translations] incorrect refs?

Maxim Dubinin sim at gis-lab.info
Sun Aug 3 01:43:44 EDT 2008


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:sim at gis-lab.info

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

MN> On Sat, Aug 2, 2008 at 9:08 PM, Maxim Dubinin <sim at gis-lab.info> 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



More information about the grass-translations mailing list