[Geoserver-devel] Translating Website & Docs

GeoServer GeoServer Developer
1

Hi List.

I recently launched a proposal to the Spanish chapter to translate the
website & docs of Geoserver into Spanish. I'm asking you to get this
module activated
http://confluence.atlassian.com/display/DOC/I18N+Architecture or ideas
to accomplish this goal.

Thanks in advanced.

Eduin Yesid Carrillo Vega
Ingeniero Civil, Esp. Sistemas de Información Geográfica
Grupo IDE & GIG
Centro de Investigación y Desarrollo en Información Geográfica
Instituto Geográfico Agustín Codazzi - IGAC
Cr 30 48-51
Tel +57 1 3694000 ext 4305
Bogotá D.C., Colombia

2

Hey Eduin, we've actually been chatting about this a decent bit recently. Help translating the website and docs of GeoServer would be really great.

Mike should sound in soon, but we're hoping to come up with some better docs on how to translate and build up local language communities.

The path would probably be something like this:

* Translate GeoServer UI (2.0 needs all new translations, help there would be great, though I'm not sure if we have any docs yet on how to do it).

* Set up a mailing list (just started up http://groups.google.com/group/geoserver-es which it looks like you've found).

* Translate the docs. Note these are now in svn, using Sphinx, no longer in confluence. See http://docs.geoserver.org/trunk/docguide/ We still need to set up a structure for translations.

* Translate other parts of website.

Hopefully most everything useful should be in the docs. We still need to make a page on 'how to translate the docs', which should include things like which ones to focus on first, etc. And how to make screenshots in the right language. There's a lot to translate, so we should help guide people on the right way.

So some more 'meta' tasks remain to get in to a good place to translate, but it'd be great if you could help out with those - figure out and document how to translate 2.0 UI, the sphinx docs, etc.

We can probably set up the i18n plugin for confluence, but I don't think that many pages would need it.

best regards,

Chris

Eduin Carrillo wrote:

Hi List.

I recently launched a proposal to the Spanish chapter to translate the
website & docs of Geoserver into Spanish. I'm asking you to get this
module activated
http://confluence.atlassian.com/display/DOC/I18N+Architecture or ideas
to accomplish this goal.

Thanks in advanced.

Eduin Yesid Carrillo Vega
Ingeniero Civil, Esp. Sistemas de Información Geográfica
Grupo IDE & GIG
Centro de Investigación y Desarrollo en Información Geográfica
Instituto Geográfico Agustín Codazzi - IGAC
Cr 30 48-51
Tel +57 1 3694000 ext 4305
Bogotá D.C., Colombia

------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Chris Holmes
OpenGeo - http://opengeo.org
Expert service straight from the developers.

3

On Jun 25, 2009, at 12:25 PM, Chris Holmes wrote:

<snip />

* Translate the docs. Note these are now in svn, using Sphinx, no longer in confluence. See http://docs.geoserver.org/trunk/docguide/ We still need to set up a structure for translations.

Mike has already tasked himself with making http://docs.geoserver.org/ support multiple languages (http://jira.codehaus.org/browse/GEOS-3124) so working on the sphinx RST docs would be great as then they can be dropped right in.

<snip />

Eduin Carrillo wrote:

Hi List.
I recently launched a proposal to the Spanish chapter to translate the
website & docs of Geoserver into Spanish. I'm asking you to get this
module activated
http://confluence.atlassian.com/display/DOC/I18N+Architecture or ideas
to accomplish this goal.
Thanks in advanced.
Eduin Yesid Carrillo Vega
Ingeniero Civil, Esp. Sistemas de Información Geográfica
Grupo IDE & GIG
Centro de Investigación y Desarrollo en Información Geográfica
Instituto Geográfico Agustín Codazzi - IGAC
Cr 30 48-51
Tel +57 1 3694000 ext 4305
Bogotá D.C., Colombia
------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Chris Holmes
OpenGeo - http://opengeo.org
Expert service straight from the developers.

4

Hi Eduin. I'm pasting your comment to the JIRA task in the channel so we can have a discussion about it:

From http://jira.codehaus.org/browse/GEOS-3124:

---
I just want to suggest using rfc3066 LOCALE codes instead of ISO639 LANGUAGE codes. In spanish language we have a lot of differences from country to country. Most notably comparing spanish from Spain and spanish from latinamerica.

A special case I can cite here is the word "File", translated as "Fichero" in Spain and "Archivo" in LA. This is just a case but more applies to this issue.

Using locale we can have a global spanish translation "ES" and a special variants "ES_AR", "ES_CO" and so on.
---

This seems like a good idea, but I would like someone who has more than zero experience with this sort of thing to chime in with thoughts.

Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org

Eduin Carrillo wrote:

Hi List.

I recently launched a proposal to the Spanish chapter to translate the
website & docs of Geoserver into Spanish. I'm asking you to get this
module activated
http://confluence.atlassian.com/display/DOC/I18N+Architecture or ideas
to accomplish this goal.

Thanks in advanced.

Eduin Yesid Carrillo Vega
Ingeniero Civil, Esp. Sistemas de Información Geográfica
Grupo IDE & GIG
Centro de Investigación y Desarrollo en Información Geográfica
Instituto Geográfico Agustín Codazzi - IGAC
Cr 30 48-51
Tel +57 1 3694000 ext 4305
Bogotá D.C., Colombia

------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

5

On Jun 25, 2009, at 4:49 PM, Mike Pumphrey wrote:

Hi Eduin. I'm pasting your comment to the JIRA task in the channel so we can have a discussion about it:

From http://jira.codehaus.org/browse/GEOS-3124:

---
I just want to suggest using rfc3066 LOCALE codes instead of ISO639 LANGUAGE codes. In spanish language we have a lot of differences from country to country. Most notably comparing spanish from Spain and spanish from latinamerica.

A special case I can cite here is the word "File", translated as "Fichero" in Spain and "Archivo" in LA. This is just a case but more applies to this issue.

Using locale we can have a global spanish translation "ES" and a special variants "ES_AR", "ES_CO" and so on.
---

I think locales might be a good idea later on, but I worry doing them right out of the gate would divide the effort too much. We've had a hard enough time getting a critical mass of contributors around the English docs (and those aren't regionated into American and British). The way I see it the distinctions between Iberian and Western Spanish aren't so great as to be insurmountable to a reader and we can always fork the Spanish docs into regions when they are further along. Thoughts?

<snip />

Eduin Carrillo wrote:

Hi List.

I recently launched a proposal to the Spanish chapter to translate the
website & docs of Geoserver into Spanish. I'm asking you to get this
module activated
http://confluence.atlassian.com/display/DOC/I18N+Architecture or ideas
to accomplish this goal.

Thanks in advanced.

Eduin Yesid Carrillo Vega
Ingeniero Civil, Esp. Sistemas de Información Geográfica
Grupo IDE & GIG
Centro de Investigación y Desarrollo en Información Geográfica
Instituto Geográfico Agustín Codazzi - IGAC
Cr 30 48-51
Tel +57 1 3694000 ext 4305
Bogotá D.C., Colombia

------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

6

Hi, chiming in late due to travel and intermittent internet access.

I think we ought to start with a single spanish-language translation, yet enabling the single ES locale may be a good future proof decision, if it's not much more work.

As for the differences between regions, I'm far from being an expert but feel like at this point it might be more important to have a short guideline on terms so we can actually enable collaborative editing. As an example, there seems not to be a generally accepted translation for the term Feature. It is often translated as Evento, Característica, Rasgo, etc. Yet Feature also seems to be a well known accepted term in spanish for the GIS domain and hence a lot of people (me included) prefer it not to be translated at all.
There are other disambiguations that can be performed, like Data Store -> Almacén de Datos, Coverage -> Cobertura, etc.
I think this kind of guideline would be giving more direct value than a proliferation of spanish based locales, and we can discuss and agree on them on the geoserver spanish mailing list.

thoughts?

Gabriel

Rolando Peñate wrote:

On Jun 25, 2009, at 4:49 PM, Mike Pumphrey wrote:

Hi Eduin. I'm pasting your comment to the JIRA task in the channel so we can have a discussion about it:

From http://jira.codehaus.org/browse/GEOS-3124:

---
I just want to suggest using rfc3066 LOCALE codes instead of ISO639 LANGUAGE codes. In spanish language we have a lot of differences from country to country. Most notably comparing spanish from Spain and spanish from latinamerica.

A special case I can cite here is the word "File", translated as "Fichero" in Spain and "Archivo" in LA. This is just a case but more applies to this issue.

Using locale we can have a global spanish translation "ES" and a special variants "ES_AR", "ES_CO" and so on.
---

I think locales might be a good idea later on, but I worry doing them right out of the gate would divide the effort too much. We've had a hard enough time getting a critical mass of contributors around the English docs (and those aren't regionated into American and British). The way I see it the distinctions between Iberian and Western Spanish aren't so great as to be insurmountable to a reader and we can always fork the Spanish docs into regions when they are further along. Thoughts?

<snip />

Eduin Carrillo wrote:

Hi List.

I recently launched a proposal to the Spanish chapter to translate the
website & docs of Geoserver into Spanish. I'm asking you to get this
module activated
http://confluence.atlassian.com/display/DOC/I18N+Architecture or ideas
to accomplish this goal.

Thanks in advanced.

Eduin Yesid Carrillo Vega
Ingeniero Civil, Esp. Sistemas de Información Geográfica
Grupo IDE & GIG
Centro de Investigación y Desarrollo en Información Geográfica
Instituto Geográfico Agustín Codazzi - IGAC
Cr 30 48-51
Tel +57 1 3694000 ext 4305
Bogotá D.C., Colombia

------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.