<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi all,<br>
<br>
This proposal was discussed on the weekly meeting.<br>
We voted to accept this proposal and move to gettext and Sphinx
internationalization.<br>
<br>
The plan is to keep the English folder as the default and produce
a pot file from it.<br>
Then for each language a po file will be created so that
translators can work on them. The interface to work can be either
Transifex, poedit, vim or any other editor. More details will be
described on wiki soon.<br>
<br>
Since this effort would require time to produce the pot file, then
to setup languages and copy the existing content to the po files,
we don't see that possible for the 9.0 release. The target of this
change will be 9.5 release and work will happen in "gettext" git
branch.<br>
<br>
Thomas has agreed to be the champion of this process. Thank you
Thomas.<br>
<br>
Best,<br>
Angelos<br>
<br>
<br>
On 07/18/2015 04:14 PM, Thomas Gratier wrote:<br>
</div>
<blockquote
cite="mid:CACPZzQ3vCsrf0MigGftJf0A5_YK=o_j48LYunHTf8wqZGuUSjg@mail.gmail.com"
type="cite">
<pre wrap="">Hi,
I had a discussion at FOSS4G Europe about using Sphinx internationalization
<a class="moz-txt-link-rfc2396E" href="http://sphinx-doc.org/latest/intl.html"><http://sphinx-doc.org/latest/intl.html></a> (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 <a class="moz-txt-link-freetext" href="http://mapserver.org/fr/development/translation.html">http://mapserver.org/fr/development/translation.html</a>
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
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Live-demo mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Live-demo@lists.osgeo.org">Live-demo@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/live-demo">http://lists.osgeo.org/mailman/listinfo/live-demo</a>
<a class="moz-txt-link-freetext" href="http://live.osgeo.org">http://live.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/Live_GIS_Disc">http://wiki.osgeo.org/wiki/Live_GIS_Disc</a></pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Angelos Tzotsos, PhD
OSGeo Charter Member
<a class="moz-txt-link-freetext" href="http://users.ntua.gr/tzotsos">http://users.ntua.gr/tzotsos</a></pre>
</body>
</html>