Hi, I had a discussion at FOSS4G Europe about using Sphinx internationalization <http://sphinx-doc.org/latest/intl.html> (i18n) instead of the current directory approach.
Why? It's already used in QGIS project, MapServer project, Python project,.. The advantages: * Untied translators and contributors jobs by using Transifex * Keeping the translation updated. For instance, if I do a translation in French, then the English doc evolves slightly, it's difficult to track the differences and I need to read nearly everything again or browse the original file history then apply the change in French. It's not friendly IMO * Do not use symbolic links when missing files: fallback to english directly with i18n and not issue with Git (try to build the doc and do a "git status" to understand) If you wonder about the simplicity of Transifex, you can see the MapServer documentation at http://mapserver.org/fr/development/translation.html The drawbacks: * It can't make documents differ per language (strict translation) I've already worked a bit to make things happen about this at the code sprint but I would like to reorganize the documentation to improve the experience. Do you have any opinions before I go further? Cheers Thomas Gratier
_______________________________________________ Live-demo mailing list Live-demo@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/live-demo http://live.osgeo.org http://wiki.osgeo.org/wiki/Live_GIS_Disc
