<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Thomas and PSC,<br>
<br>
Thomas, thanks for the great effort with the translation.<br>
I this is excellent contribution should be incorporated<br>
in ZOO project. Should be great if transifex provides <br>
for a easier way to translate the po files, documents<br>
etc.<br>
<br>
Best<br>
<br>
Venka<br>
<br>
P.S. Sorry for the delay in my reply.<br>
<br>
On 2/13/2014 12:16 AM, Fenoy Gerald wrote:<br>
</div>
<blockquote
cite="mid:FF185C88-A37E-40C0-BC6D-E97E13221861@geolabs.fr"
type="cite">
<pre wrap="">Hi Thomas,
thanks a lo for your work and for this support.
Your ideas and proposals are really interesting to me and the translation support is obviously something requested so obviously any support for gathering efforts in one place can be great thing (I hope that Istvan hear me). Note that I’m not aware in details about those technologies but I agree that this should be discussed by PSC.
I would like to separate two distincts terms PSC dans Developpers, those last get SVN access, it is not mandatory for the PSC member to have SVN access.
I cced the PSC mailing list to let them know about your proposals and about the opened discussion.
Thanks again and hope to hear from other contributors.
Best regards
Le 9 févr. 2014 à 23:35, Thomas Gratier <a class="moz-txt-link-rfc2396E" href="mailto:osgeo.mailinglist@gmail.com"><osgeo.mailinglist@gmail.com></a> a écrit :
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
I've worked some days on the French translation by using po files.
FYI, I have translated all French content except workshops before 2013, the API parts and the ZOO-Project Committer Guidelines.
You can see the result <a class="moz-txt-link-freetext" href="http://thomasg77.github.io/zoo-project-docs/fr/">http://thomasg77.github.io/zoo-project-docs/fr/</a>
and can find the corresponding repo <a class="moz-txt-link-freetext" href="https://github.com/ThomasG77/zoo-project-docs">https://github.com/ThomasG77/zoo-project-docs</a>
So, now, we are able to maintain translation via Transifex if required.
I have some remaining issues like generating French PDF (latex issue) and making the workflow compatible with Windows.
I also need to update the documentation part to explain how to generate and update the docs using the proposed workflow. If my contribution is accepted, we will also need to create a zoo account on Transifex.
Also, I've seen that there were questions about translation e.g <a class="moz-txt-link-freetext" href="http://lists.osgeo.org/pipermail/zoo-psc/2013-August/000505.html">http://lists.osgeo.org/pipermail/zoo-psc/2013-August/000505.html</a> :
1) about how to track the changes >> Not a problem because po tools do it for you
2) the workflow for translation >>for this case, see propositions below:
The docs in the SVN is at <a class="moz-txt-link-freetext" href="http://www.zoo-project.org/svn/trunk/docs/">http://www.zoo-project.org/svn/trunk/docs/</a> and <a class="moz-txt-link-freetext" href="https://github.com/ThomasG77/zoo-project-docs">https://github.com/ThomasG77/zoo-project-docs</a> in my repo
To let the PSC work the usual way (and keep the rules about commit rights) but making people contribute to the translation, we have different possibilities:
2.1 We can imagine to sync (one way) the directory locale (from <a class="moz-txt-link-freetext" href="http://www.zoo-project.org/svn/trunk/docs/locale">http://www.zoo-project.org/svn/trunk/docs/locale</a> if my contribution is integrated in the current trunk) to a Github official Zoo organization account. After, we can sync Github with Transifex because it's quite easy now with Transifex client (see <a class="moz-txt-link-freetext" href="http://sphinx-doc.org/latest/intl.html#using-transifex-service-for-team-translation">http://sphinx-doc.org/latest/intl.html#using-transifex-service-for-team-translation</a>)
Sometimes, we will submit to a designated PSC member the translated content (so from the official Github account). We need to have a schedule or it can be on demand. It can be automated but we might have issues if we don't review content before submitting translations.
2.2 An alternative can also be to make a separate SVN repo for translations where rights are not restricted to PSC members.
In this case, we can upload the pot files (po files model for translations) to Transifex from SVN and people allowed can commit in this new created SVN repo.
Thanks for your feedback about those propositions
Cheers
Thomas Gratier
_______________________________________________
Zoo-discuss mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Zoo-discuss@lists.osgeo.org">Zoo-discuss@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss">http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss</a>
</pre>
</blockquote>
<pre wrap="">
Gérald Fenoy
<a class="moz-txt-link-abbreviated" href="mailto:gerald.fenoy@geolabs.fr">gerald.fenoy@geolabs.fr</a>
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Zoo-psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Zoo-psc@lists.osgeo.org">Zoo-psc@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc">http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc</a></pre>
</blockquote>
<br>
</body>
</html>