Hi Andy! I think this is good idea, but it worth only if localized version(s) will be synchronized with English one and be always up-to-dated. There is nothing worst that outdated docs(:
For localization process it's better to follow Sphinx guide about: http://sphinx-doc.org/latest/intl.html This approach is different from CouchDB: The Definition Guide, but much more friendly and common for translators. To compile whole documentation just: git clone https://git-wip-us.apache.org/repos/asf/couchdb.git cd couchdb ./bootstrap && ./configure cd share/doc make html open in browser build/html/index.html file Note, that following internationalization guide will require modify a bit Makefile. -- ,,,^..^,,, On Sat, Oct 12, 2013 at 6:53 PM, Andy Wenk <[email protected]> wrote: > Hi all, > > as the documentation has found it's way into Futon and after having met Jan > at JSConf.eu with a short talk about how to participate in the project, I > am thinking about starting to translate the docs into German. I understood, > that the documentation source files are placed in /share/doc/src . Am I > right, that the only language available is English for now? If so, what > would be a good idea to start with multilingual docs? An idea would be to > have > > /share/doc/src/en-GB > /share/doc/src/de-DE > > and so on. Any thoughts about this? > > Further more. What is the best way to compile the whole documentation? Is > there a best way to do or a good process? > > Any ideas and help is highly appreciated. > > Cheers > > Andy > > > -- > Andy Wenk > Hamburg - Germany > RockIt!
