[Qgis-community-team] Transifex and doc 1.8

[Marie Silvestre]

Hi,
I agree with Nathan too. If  language maintainers follow the procedure there should be no problem with github (though maybe some points should be explained more precisely). Things are working fine for the french translation ... without Transifex.

About the workflow, are sources automatically updated on Transifex as Alexander said? Because files are still out of date for the 1.8 version. Shouldn't we restart from scratch on Transifex now that rst and english po files are synchronized on github?
Everything concerning french translations on transifex has been transferred to github, but almost manually because of merging conflicts. As long as files are not updated, I recommend french translators to stand by. So for the french team, you can erase everything from Transifex!

Marie





________________________________
 De : Alexander Bruy <alexander.bruy at gmail.com>
À : richard at duif.net 
Cc : qgis-community <qgis-community-team at lists.osgeo.org> 
Envoyé le : Mardi 2 avril 2013 11h45
Objet : Re: [Qgis-community-team] Transifex and doc 1.8
 
Hi,

I agreed with Nathan: it is better to stick with usual git workflow
and avoid any type or redundancy as much as possible.

When we used SVN for docs we have same workflow — separate branches
for each version and I can't remember any problems with this from
translators side.

Moreover putting sources to Transifex is single operation and
performed only when new version of the docs is out (BTW, I still
prefer to use git and offline translation).

Just my 2
 c.

On Mon, 01 Apr 2013 21:27:12 +0200
Richard Duivenvoorde <richard at duif.net> wrote:

> Hi Nathan,
> 
> no I'm not talking about a different repo, but  a copy of a directory in 
> the same (documentation) repo in master (after a release).
> 
> So now we have:
> https://github.com/qgis/QGIS-Documentation/tree/master/source/docs
> 
> and I my idea was to have IN the user_manual directory, a version of the 
> user_manual for every version
> 
> source/docs/user_manual/master (dev version)
> source/docs/user_manual/1.8
> source/docs/user_manual/2.0 (a copy dev version after 2.0 release) etc
> source/docs/qgis_governance is ok (no need for a new version)
> but
>
 source/docs/pyqgis_developer_cookbook/master
> source/docs/pyqgis_developer_cookbook/1.8
> source/docs/pyqgis_developer_cookbook/2.0
> etc
> 
> I know it is redundancy, and from a coder/github point of view this 
> should be done via branching and or tagging, but for a non-coder pov I 
> think it is more clear and 'transparant'.
> 
> But (even more important) we could just put the full source directory 
> into Transifex, no need to think about which version is to be put in 
> there etc etc..
> Making it easier to just fix an error in whatever translation you find 
> important.
> 
> For the git-users it is still possible to use github (only without 
> branches, allways working in 'master')

-- 
Alexander Bruy
_______________________________________________
Qgis-community-team mailing list
Qgis-community-team at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-community-team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-community-team/attachments/20130408/e3276fdf/attachment.html>