Hello everybody,
My name is Luca Casagrande and I am a PhD student at University of
Perugia (Italy).
Speaking with Andrea, I expressed my intention to contribute with the
Italian translation of GeoServer manual.
I thought of doing a checkout of the Sphinx repository so I can work off
line and then move the updated files to someone with write permission.
What do you think?
Ciao
Luca
Hi Luca,
That would be great!! Contributions are always welcome, and we are always in sore need of language translations.
I think the workflow you present makes a lot of sense. Check out the current docs, do the translation work, and then send the end result back to the project via a patch or attachment to a JIRA task.
However if you do require a faster workflow I think people here can look into getting you direct version control access.
-Justin
Luca Casagrande wrote:
Hello everybody,
My name is Luca Casagrande and I am a PhD student at University of
Perugia (Italy).
Speaking with Andrea, I expressed my intention to contribute with the
Italian translation of GeoServer manual.
I thought of doing a checkout of the Sphinx repository so I can work off
line and then move the updated files to someone with write permission.What do you think?
Ciao
Luca------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Hi Justin,
Il giorno lun, 05/10/2009 alle 11.48 -0400, Justin Deoliveira ha
scritto:
Hi Luca,
That would be great!! Contributions are always welcome, and we are
always in sore need of language translations.I think the workflow you present makes a lot of sense. Check out the
current docs, do the translation work, and then send the end result back
to the project via a patch or attachment to a JIRA task.However if you do require a faster workflow I think people here can look
into getting you direct version control access.-Justin
I can start without the write permission, no problem.
Here some considerations:
- Using https://svn.codehaus.org/geoserver/trunk/doc/en/user/ ;
- I keep folder and files with the same name of the English one, using
this syntax for reference :ref:`installazione <installation>` ;
- Each time a folder is completed, I'll send it as patch;
- I leave the pictures in English, replacing them only after completing
the whole text;
What do you think?
Ciao
Luca
Luca Casagrande ha scritto:
Hi Justin,
Il giorno lun, 05/10/2009 alle 11.48 -0400, Justin Deoliveira ha
scritto:Hi Luca,
That would be great!! Contributions are always welcome, and we are always in sore need of language translations.
I think the workflow you present makes a lot of sense. Check out the current docs, do the translation work, and then send the end result back to the project via a patch or attachment to a JIRA task.
However if you do require a faster workflow I think people here can look into getting you direct version control access.
-Justin
I can start without the write permission, no problem.
Here some considerations:- Using https://svn.codehaus.org/geoserver/trunk/doc/en/user/ ;
- I keep folder and files with the same name of the English one, using
this syntax for reference :ref:`installazione <installation>` ;
- Each time a folder is completed, I'll send it as patch;
- I leave the pictures in English, replacing them only after completing
the whole text;What do you think?
Sounds like a good plan. Your docs should end up in
/doc/it/user/
That is, the "en" is english, each other language picks its abbreviation
and that's how we build the tree. Thanks again for working on this!
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Hi. There is currently a template Sphinx project in Spanish:
.../doc/es/user
It currently contains no content, So you could easily copy it into
.../doc/it/user
and start from there...
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
Andrea Aime wrote:
Luca Casagrande ha scritto:
Hi Justin,
Il giorno lun, 05/10/2009 alle 11.48 -0400, Justin Deoliveira ha
scritto:Hi Luca,
That would be great!! Contributions are always welcome, and we are always in sore need of language translations.
I think the workflow you present makes a lot of sense. Check out the current docs, do the translation work, and then send the end result back to the project via a patch or attachment to a JIRA task.
However if you do require a faster workflow I think people here can look into getting you direct version control access.
-Justin
I can start without the write permission, no problem.
Here some considerations:- Using https://svn.codehaus.org/geoserver/trunk/doc/en/user/ ;
- I keep folder and files with the same name of the English one, using
this syntax for reference :ref:`installazione <installation>` ;
- Each time a folder is completed, I'll send it as patch;
- I leave the pictures in English, replacing them only after completing
the whole text;What do you think?
Sounds like a good plan. Your docs should end up in
/doc/it/user/That is, the "en" is english, each other language picks its abbreviation
and that's how we build the tree. Thanks again for working on this!Cheers
Andrea