It is, but I would translate on master (since that is where the initial
pull request will land).
It may only be necessary to translate -
https://github.com/geoserver/geoserver/tree/master/doc/en/user/source
(as the instructions on how to contribute docs and build them as a
developer are not that interesting).
Jody Garnett
On Wed, Apr 9, 2014 at 12:10 AM, François Van Der Biest <
[email protected]> wrote:
> Hi,
>
> Very recently, we've been contacted by a student who was looking for
> en->fr translation work.
> So, we pointed her to the geoserver documentation.
>
> Can you confirm that working on the RST files from the 2.5.x branch
> located in
> https://github.com/geoserver/geoserver/tree/2.5.x/doc/en/docguide/source
> and https://github.com/geoserver/geoserver/tree/2.5.x/doc/en/user/source
> is the correct way to go ?
>
> Many thanks,
> F.
>
> --
> Camptocamp France SAS, Chambéry
> http://www.camptocamp.com/fr/geospatial-solutions
>
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
