[ZOO-PSC] [Zoo-discuss] ZOO translation reloaded >> mainly done in French

[Fenoy Gerald]

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 <osgeo.mailinglist at gmail.com> a écrit :

> 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 http://thomasg77.github.io/zoo-project-docs/fr/
> and can find the corresponding repo https://github.com/ThomasG77/zoo-project-docs
> 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 http://lists.osgeo.org/pipermail/zoo-psc/2013-August/000505.html :
> 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 http://www.zoo-project.org/svn/trunk/docs/ and https://github.com/ThomasG77/zoo-project-docs 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 http://www.zoo-project.org/svn/trunk/docs/locale 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 http://sphinx-doc.org/latest/intl.html#using-transifex-service-for-team-translation)
> 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
> Zoo-discuss at lists.osgeo.org
> http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-discuss



Gérald Fenoy
gerald.fenoy at geolabs.fr

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.osgeo.org/pipermail/zoo-psc/attachments/20140212/bec03d1e/attachment.pgp>