grass manual translation

5 messages Options
Embed this post
Permalink
Marco Curreli

grass manual translation

Reply Threaded More More options
Print post
Permalink
Hi,

I belong to a team for translating the grass64 manual in Italian.

Looking forward to define the technical aspects in order to insert
the manual pages in the code, we have decided to start translating
the description.html files. We have choose to use this list to
coordinate the work in progress.

If nobody is going to translate it yet, I'll initiate to translate
the following commands: r.average, r.category, r.reclass

I think to put the whole content of the translation on this list,
when it's finished, for a collective revision. It's a good idea?

Best regards,
          Marco

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

Re: grass manual translation

Reply Threaded More More options
Print post
Permalink
Hello all,

> On Mon, Mar 2, 2009 at 3:54 PM, Marco Curreli <[hidden email]>
wrote:
> > I belong to a team for translating the grass64 manual in Italian.
> >
> > Looking forward to define the technical aspects in order to insert
> > the manual pages in the code, we have decided to start translating
> > the description.html files. We have choose to use this list to
> > coordinate the work in progress.

good idea - how can I join the translation team?
This initiative can be of interest of GFOSS.it community, a note on wiki can
bring more people on this task [0].
If it is on some use, there is also a partial translation of GRASS 6.0 manual
on GFOSS.it wiki [1].

> > If nobody is going to translate it yet, I'll initiate to translate
> > the following commands: r.average, r.category, r.reclass

Yes - a further hint: why don't we rank translations for example giving
precedence to most used commands?

> > I think to put the whole content of the translation on this list,
> > when it's finished, for a collective revision. It's a good idea?

IMHO using wiki would be less flooding - anyway this is a low traffic list.

> > Best regards,
> >          Marco

best regards,

Anne

[0] http://wiki.gfoss.it/index.php/Traduzioni
[1] http://wiki.gfoss.it/index.php/GRASS_6.0.2_Reference_Manual

--
Please consider the environment before printing this email
Please do not send attachments in proprietary formats
http://www.gnu.org/philosophy/no-word-attachments.html
Use the UNI CEI Standard ISO/IEC 26300:2006
-----------------------------------------------------------
O< stop html mail - http://www.asciiribbon.org


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

signature.asc (204 bytes) Download Attachment
Stefano Costa

Re: grass manual translation

Reply Threaded More More options
Print post
Permalink
Il giorno mar, 03/03/2009 alle 11.39 +0100, Anne Ghisla ha scritto:
>
> good idea - how can I join the translation team?
> This initiative can be of interest of GFOSS.it community, a note on
> wiki can bring more people on this task [0].
> If it is on some use, there is also a partial translation of GRASS 6.0
> manual on GFOSS.it wiki [1].

Hi,
updating that wiki page is high on the priority list. We have agreed to
the workflow explained by Marco also with Markus. At this point, using
the wiki to translate is a bit overkill because it's extremely difficult
to extract translations from it and send them upstream. Each HTML page
is quite short so we shouldn't end up with incomplete pages - at least I
hope!

The wiki could still be useful to maintain a list of the translated man
pages.

> Yes - a further hint: why don't we rank translations for example
> giving precedence to most used commands?

I think that the best thing would be that each contributor ranks her/his
most used commands and starts from them. This way we should also get
higher quality translations :-)

So for the wiki page, the basic steps for the wanna-be contributor are:
     1. subscribe to this list
     2. look for an untranslated page
     3. translate it!
     4. send it here
     5. → 2

Please correct me if I'm wrong.

Cheers,
Steko

>
--
Stefano Costa
http://www.iosa.it/ Open Archaeology


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

signature.asc (204 bytes) Download Attachment
Markus Neteler

Re: grass manual translation

Reply Threaded More More options
Print post
Permalink
In reply to this post by Anne Ghisla-2
On Tue, Mar 3, 2009 at 11:39 AM, Anne Ghisla <[hidden email]> wrote:
>> On Mon, Mar 2, 2009 at 3:54 PM, Marco Curreli <[hidden email]>
...
>> > If nobody is going to translate it yet, I'll initiate to translate
>> > the following commands: r.average, r.category, r.reclass
>
> Yes - a further hint: why don't we rank translations for example giving
> precedence to most used commands?

Right.

I have the idea for years meanwhile to generate usage statistics
automatically with the parser. Each command used is saved in
an ASCII file in the home directory. From that these statistics
could be done easily.
How 'bout this?

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

Re: grass manual translation

Reply Threaded More More options
Print post
Permalink
In reply to this post by Stefano Costa
On Tuesday 03 March 2009 12:45:27 Stefano Costa wrote:
> The wiki could still be useful to maintain a list of the translated man
> pages.

+1 for this.
The wiki page can also be used to lock a page and prevent others to duplicate
translation effort.

> I think that the best thing would be that each contributor ranks her/his
> most used commands and starts from them. This way we should also get
> higher quality translations :-)
>
> So for the wiki page, the basic steps for the wanna-be contributor are:
>      1. subscribe to this list
>      2. look for an untranslated page
>      3. translate it!
>      4. send it here
>      5. → 2
>
> Please correct me if I'm wrong.
+1 for me. I can start browsing GFOSS wiki and send translated pages.

> Cheers,
> Steko

cheers,

Anne
--
Please consider the environment before printing this email
Please do not send attachments in proprietary formats
http://www.gnu.org/philosophy/no-word-attachments.html
Use the UNI CEI Standard ISO/IEC 26300:2006
-----------------------------------------------------------
O< stop html mail - http://www.asciiribbon.org


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

signature.asc (204 bytes) Download Attachment