[Qgis-community-team] Transifex updates

[Otto Dassau]

Hi,

Am Fri, 22 Mar 2013 14:45:12 +0200
schrieb Tim Sutton <tim at linfiniti.com>:

> Hi
> 
> On Fri, Mar 22, 2013 at 2:36 PM, Otto Dassau <dassau at gbd-consult.de> wrote:
> > Hi Tim,
> >
> > Am Fri, 22 Mar 2013 14:29:36 +0200
> > schrieb Tim Sutton <lists at linfiniti.com>:
> >
> >> Hi All
> >>
> >> On Fri, Mar 22, 2013 at 10:47 AM, Otto Dassau <dassau at gbd-consult.de>
> >> wrote:
> >>
> >> 8<---------------------snip--------
> >>
> >> >>
> >> >> First I generated them from Master, and then from 1.8, updating /
> >> >> overwriting the ones pushed from master. Perhaps I should flush all
> >> >> files and push them up again with the amendment that I include the
> >> >> version number in the resource name so transfiex would list them as
> >> >> e.g. v1.8-Introduction.po
> >> >>
> >> >> Then we could use the versions feature of transifex to identify all
> >> >> the po files for 1.8 and we could also provide for simultaneous
> >> >> translations of 1.8 and 2.
> >> >>
> >> >> If it doesnt cause any invonvenience to others (please let me know if
> >> >> you think it will), I will do this today (friday).
> >> >>
> >> >> Regards
> >> >>
> >> >> Tim
> >> >
> >> > Good idea, I think this would be great! If anyone wants to complain,
> >> > please do it now ;).
> >> >
> >> > Thanks a lot Tim
> >> >
> >>
> >> I have created a transifex release and tagged all the resources in 1.8
> >> accordingly. The release is visible here:
> >>
> >> https://www.transifex.com/projects/p/qgis-documentation/r/1-8/
> >>
> >> I am busy pushing the po files up for the release version - it would
> >> be great if you could all do the same cross checking to see if
> >> everything is as expected. Your workflow woould then need to be
> >> updated to edit only the files in the transifex release. I will make
> >> another 2-0 release resource set which will correspond to the files in
> >> master.
> >>
> >> Note: the tx push is still underway - it may take an hour or two
> >> more....
> >>
> >> Regards
> >>
> >> Tim
> >
> > ok, this means, we have to stop committing files translated with linguist
> > etc and only use transifex from now on?
> >
> 
> No not at all - you can still push your hand updated po files - just
> click on any v1.8 resource and choose 'upload file' from the box that
> appears.
> 
> 
> > And what if we make changes to the english master document. Is it
> > necessary to use some special tool also, or can we just use a normal
> > editor as we did so far and commit our changes to master?
> 
> If you change the source texts, you (as in specifically Otto as at the
> moment only you and I have admin rights) should run
> 
> scripts/pre_translate.sh
> scripts/create-transifex-resources.sh
> 
> > Will it be updated in the 2-0 release resource automatically?
> 
> No we can push all the 1.8 po translation files to the transifex 2.0
> version and it should pick up all the matching strings. Probably we
> can make a script to automate forwarding translations from one release
> to the next.
> 
> Just bear in mind that I am learning this stuff as we go so I
> apologise for any wrong steps we may have along the way.
> 
> Regards
> 
> Tim

With Tim's help I updated transifex again with create-transifex-resources.sh
script and pushed all .po files to transifex from the current "manual_v1.8"
branch. All files get a prefix v1-8-docs but as I can see this also happens
for the web files. There is no seperation between docs and web and also not
between the various documents - it seems all mixed up. And now we also have a
lot of duplicated files that probably have to be removed in transifex for
each language.

Then, as we found out before, we need to figure out, how to fix the errors
in the .po files, because most of them cannot be pushed to transifex at the
moment. I found them with fixed some of them manually and that works, but we
need to find a better solution.

At the moment I think that transifex might be a very nice solution, but we
need a lot more testing and work and I am afraid that people already work
with it and that translations get lost during our testing or that lots of
conflicts appear, when we rename / remove / restructure it and make a tx pull
again?

Would it be possible to structure the files as they are in github? 

How should we proceed here? I can spend some time on it, but I will be
travelling until next wednesday and probably won't be able to work on it
before again.

Regards
Otto