Hi,
I have one guy on the italian mailing list thinking about
contributing italian docs for GeoServer.
Question is, where? confluence? svn+sphinx?
I don't think we have any plan on an internationalized documentation.
We also have slides and stuff that could be contributed
but atm they are basically dispersed a bit everywhere.
Like I have slides I used for presentations in Italy,
Simone has some too, there is people that have pointed
us at OpenOffice documents with installation guides
and the like.
We should also have a place where we can gather all of
these.
Opinions on how to handle this?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
For user and developer docs I think it makes more sense to have multiple trees of documentation, one for each language:
doc/user/
en/
it/
...
I don't think sphinx provides any built in support for i18n. Which given the nature of rST makes sense.
As for slides, we have presentations.opengeo.org. We could perhaps use this or create a presentations.geoserver.org, and just create a file structure for slides and presentations. I believe a bunch of slides from foss4g08 are there.
-Justin
Andrea Aime wrote:
Hi,
I have one guy on the italian mailing list thinking about
contributing italian docs for GeoServer.
Question is, where? confluence? svn+sphinx?
I don't think we have any plan on an internationalized documentation.
We also have slides and stuff that could be contributed
but atm they are basically dispersed a bit everywhere.
Like I have slides I used for presentations in Italy,
Simone has some too, there is people that have pointed
us at OpenOffice documents with installation guides
and the like.
We should also have a place where we can gather all of
these.
Opinions on how to handle this?
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
For user and developer docs I think it makes more sense to have multiple trees of documentation, one for each language:
doc/user/
en/
it/
...
I don't think sphinx provides any built in support for i18n. Which given the nature of rST makes sense.
So you'd say if we do, the effort should be hosted into svn?
Makes sense, at least as long as we have a dedicated team.
The problem I see in the short term is that there is no documentation
in svn, and the guys over there would like to start doing some
translation now... I guess I should suggest them to use their
own wiki then?
As for slides, we have presentations.opengeo.org. We could perhaps use this or create a presentations.geoserver.org, and just create a file structure for slides and presentations. I believe a bunch of slides from foss4g08 are there.
Well, presentations.opengeo.org sounds a little big like opengeo only,
whilst for example we have some GeoSolutions stuff as well.
presentations.geoServer.org sounds like a better fit?
Or maybe even just the wiki, and stick a nice looking logo for
each presentation/material that originated from a specific company?
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
We can easily do presentations.geoserver.org , but either it'll be a resource only OpenGeo can update (which is not too bad since there are two full time outreach engineers here, and it probably won't change too frequently) or we need another authentication system in addition to Confluence and Codehaus / SVN.... The third option is WebDAV with a shared password, which I think I would prefer over another set of tokens.
But we've already got binary blobs in Confluence, and it looks like we'll have them in svn as well, so I think we should use one of those two.
Regarding multiple trees, we need to think about how we deal with shared stuff, like images that don't need to be copied for every language. Ideally I guess we would want them to use the language, but default to whatever images the English version is using if none are available. Will Sphinx let us do anything like that ?
-Arne
Justin Deoliveira wrote:
For user and developer docs I think it makes more sense to have multiple trees of documentation, one for each language:
doc/user/
en/
it/
...
I don't think sphinx provides any built in support for i18n. Which given the nature of rST makes sense.
As for slides, we have presentations.opengeo.org. We could perhaps use this or create a presentations.geoserver.org, and just create a file structure for slides and presentations. I believe a bunch of slides from foss4g08 are there.
-Justin
Andrea Aime wrote:
Hi,
I have one guy on the italian mailing list thinking about
contributing italian docs for GeoServer.
Question is, where? confluence? svn+sphinx?
I don't think we have any plan on an internationalized documentation.
We also have slides and stuff that could be contributed
but atm they are basically dispersed a bit everywhere.
Like I have slides I used for presentations in Italy,
Simone has some too, there is people that have pointed
us at OpenOffice documents with installation guides
and the like.
We should also have a place where we can gather all of
these.
Opinions on how to handle this?
Cheers
Andrea
--
Arne Kepp
OpenGeo - http://opengeo.org
Expert service straight from the developers
Arne Kepp ha scritto:
...
Regarding multiple trees, we need to think about how we deal with shared stuff, like images that don't need to be copied for every language. Ideally I guess we would want them to use the language, but default to whatever images the English version is using if none are available. Will Sphinx let us do anything like that ?
This plan looks like something that requires a significant commitment
on the translators part... ugh, can we hope about that much?
The guy asked explicitly about translating _parts_ of the user guide.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
This plan looks like something that requires a significant commitment
on the translators part... ugh, can we hope about that much?
The guy asked explicitly about translating _parts_ of the user guide.
An alternative would be to store all files under a single tree and add i18nized files with additional extensions. Something like:
installation/
install-image1.png
install-image2.png
install-iamge2.png.it
geoserver-install.rst
geoserver-install.rst.it
And then provide a simple shell or batch script to build the docs for a particular language. The script would be pretty simple and would just copy the files with the specified language over when they exist, falling back on the default / english file when they don't.
Just an idea... not sure if its a good one.
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Andrea Aime ha scritto:
Arne Kepp ha scritto:
...
Regarding multiple trees, we need to think about how we deal with shared stuff, like images that don't need to be copied for every language. Ideally I guess we would want them to use the language, but default to whatever images the English version is using if none are available. Will Sphinx let us do anything like that ?
This plan looks like something that requires a significant commitment
on the translators part... ugh, can we hope about that much?
The guy asked explicitly about translating _parts_ of the user guide.
Follow up from the IRC discussion, what they are asking is a place
and eventually a tool where to place some translations focused
on their needs/interests, not a generic statements about "I want
to be the official geoserver docs translator".
So I guess just giving them access to confluence would be the
best bet?
Anyways, the idea of having space for multiple languages in
svn looks like a good one, who ones, maybe one day we'll actually
have someone interested in such an endeavour? 
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
I agree with Andrea. For now, I think the option with the most minimal overhead, and one the jives with our present and future plans for documentation, is to have those interested in i18n d11n to use our wiki. Should we want to migrate the info to a different platform at some point, we can decide that then.
Thanks,
Mike Pumphrey
OpenGeo - http://opengeo.org
Andrea Aime wrote:
Andrea Aime ha scritto:
Arne Kepp ha scritto:
...
Regarding multiple trees, we need to think about how we deal with shared stuff, like images that don't need to be copied for every language. Ideally I guess we would want them to use the language, but default to whatever images the English version is using if none are available. Will Sphinx let us do anything like that ?
This plan looks like something that requires a significant commitment
on the translators part... ugh, can we hope about that much?
The guy asked explicitly about translating _parts_ of the user guide.
Follow up from the IRC discussion, what they are asking is a place
and eventually a tool where to place some translations focused
on their needs/interests, not a generic statements about "I want
to be the official geoserver docs translator".
So I guess just giving them access to confluence would be the
best bet?
Anyways, the idea of having space for multiple languages in
svn looks like a good one, who ones, maybe one day we'll actually
have someone interested in such an endeavour?
Cheers
Andrea