[Live-demo] Motion: Changing translation system to use Sphinx internationalization instead of directory approach
gcpp.kalxas at gmail.com
Wed Sep 16 02:00:05 PDT 2015
Since the 9.0 release is now out, this would be the best time to start
the move to Sphinx internationalization, to give time to translators to
catch up with the new system. I think 6 months are more than enough ;)
How should we proceed?
I propose we create a git branch until it is ready for a pull request.
On 07/18/2015 04:14 PM, Thomas Gratier wrote:
> 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.
> 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
> Do you have any opinions before I go further?
> Thomas Gratier
> Live-demo mailing list
> Live-demo at lists.osgeo.org
Angelos Tzotsos, PhD
OSGeo Charter Member
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Osgeolive