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 > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
