Hi Yves. You are correct; separate sphinx-builds for each project and one conf.py for each langauge. It's probably duplicating work, but we figured that sandboxing each project was better than trying to string them all together. Our situation is different since we're a community project where the onus of translation is on the community (and no one has yet taken the plunge). If we had 15 different language projects that were already created, we might have done things differently.
Thanks, Mike Pumphrey OpenGeo - http://opengeo.org yvesm wrote: > > On Sep 22, 10:53 am, Mike Pumphrey <[email protected]> wrote: >> Hi Yves. The GeoServer project (geoserver.org) just had a similar >> discussion. We decided that each language project should be independent of >> each other, with no direct translations. So we're doing it manually: >> >> ...trunk/doc/[LANGUAGE]/[MANUALS]/source/... >> >> where MANUALS are the User Manual, Developer Manual, etc. >> >> You can take a look at our subversion repo >> athttps://svn.codehaus.org/geoserver/... > > Hi Mike, > > Indeed one of the urls I came across was the discussion you led on > multiple languages docs for GeoServer. So you've got SOURCE rst's for > each language and you run a sphinx-build on each ? One conf.py for > each language ? Will look at your SVN. Thanx. > > Yves > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en -~----------~----~----~----~------~----~------~--~---
