[Live-demo] Motion: Changing translation system to use Sphinx internationalization instead of directory approach

[Cameron Shorter]

Hi Thomas, all,
You were describing good ideas about improving the OSGeo-Live 
translation process.
What are ideas on moving forward with this?
Should we aim to incorporate translation improvements into the next 
OSGeo-Live 9.5?
Who needs to do what to make this happen?

Key Milestones
11 Jan 2016 All new applications installed, most old applications updated
01 Feb 2016 Feature Freeze (all apps updated)
15 Feb 2016 User Acceptance Test (all apps installed and working)
21 Mar 2016 Final ISO sent to printers

Warm regards, Cameron



On 18/09/2015 10:52 am, Thomas Gratier wrote:
> Hi,
>
> I will work on this next week. I was quite busy with job.
> I will make a branch to create a first working demo with my Github 
> user name and then start discussion with explanations in a markdown 
> file in this discussion
>
> Cheers
>
> Thomas
>
> 2015-09-16 11:00 GMT+02:00 Angelos Tzotsos <gcpp.kalxas at gmail.com 
> <mailto:gcpp.kalxas at gmail.com>>:
>
>     Hi Thomas,
>
>     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.
>     Thoughts?
>
>     Best,
>     Angelos
>
>     On 07/18/2015 04:14 PM, Thomas Gratier wrote:
>>     Hi, I had a discussion at FOSS4G Europe about using Sphinx
>>     internationalization <http://sphinx-doc.org/latest/intl.html>
>>     <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 athttp://mapserver.org/fr/development/translation.htmlThe
>>     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 at lists.osgeo.org <mailto:Live-demo at lists.osgeo.org>
>>     http://lists.osgeo.org/mailman/listinfo/live-demo
>>     http://live.osgeo.org
>>     http://wiki.osgeo.org/wiki/Live_GIS_Disc
>
>
>     -- 
>     Angelos Tzotsos, PhD
>     OSGeo Charter Member
>     http://users.ntua.gr/tzotsos
>
>
>
>
> _______________________________________________
> Live-demo mailing list
> Live-demo at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/live-demo
> http://live.osgeo.org
> http://wiki.osgeo.org/wiki/Live_GIS_Disc

-- 
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009

P +61 2 9009 5000,  Wwww.lisasoft.com,  F +61 2 9009 5099

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/osgeolive/attachments/20151203/6f5adb86/attachment.html>