[Qgis-community-team] Transifex and doc 1.8

Diethard Jansen diethard.jansen at gmail.com
Sun Mar 31 09:46:10 PDT 2013


Hello,

I think we should act carefully now.
We might loose too much work done in transifex if we act too hasty. To
loose work is a pity, to loose further commitment of translators is short
of a disaster. We do not want that too happen. So we really should try to
first minimize the lost of translations.

First of all, I do not have rights to run the scripts to update the files
to transifex, I believe only Otto, Tim and Alexander have this right.
However, before we run this update script we should try to pull in the
changes of *new* translated documents from transifex first. We should not
try to pull in *updated* translated files, that is files that first were
translated for 100% and on transifex seems to be translated for less then
100%. pulling in those translated files (that were update in transifex back
to 100%) will definitely result in a loss of translated material!

For new translated files it is however a good idea to pull these in first
and then run the update.
For each language we have to investigate which files to pull in. For the
Dutch translation, this is done. No files need to be pull in anymore. The
Dutch translation team will wait until the new update has been done.

For the Japanese, German, French and Russian translation teams, they have
to look closely if files exist that needs to be pulled into git using the
transifex client. To speed up things, I will first try to see if I can help
the Japanese translation team and propose which translation files should be
pulled in and how they should do it (I will not do it myself).

Next I will work on a proposal how we should do translations in future. I
believe when we have updated the files from a branch (1.8/1.9/2.0) from
github to transifex we should not touch the reST code in that branch
anymore. We should only focus on translation and when we find mistakes
these should be corrected in the master branch and not in the 1.8/1.9/2.0
branch. Only then we can create a CRON job to automate the update of
translations to github that works. Otherwise you will see that the job
continually will erase translated work.

Regards,
Diethard Jansen


2013/3/29 Marie Silvestre <marie_silvestre at yahoo.fr>

> Ok Diethard, that reassures me!
> Now how are the english files updated in transifex? Does Tim's script
> (create-transifex-resources.sh) update, replace or create new files?
> The japanese team seems to work a lot in transifex at the moment. Maybe
> they should pause until files are updated?
>
> Regards,
> Marie
>
>
>   ------------------------------
> *De :* Diethard Jansen <diethard.jansen at gmail.com>
> *À :* Marie Silvestre <marie_silvestre at yahoo.fr>
> *Cc :* Otto Dassau <dassau at gbd-consult.de>; "
> qgis-community-team at lists.osgeo.org" <qgis-community-team at lists.osgeo.org>
>
> *Envoyé le :* Mardi 26 mars 2013 21h55
>
> *Objet :* Re: [Qgis-community-team] Transifex and doc 1.8
>
> Hello,
>
> Marie you are right..
>
> I decided to run the pre translate script and commit and push the changes
> so the english po files are up to date.
> When these are now updated to transifex I am sure the translation rate
> will be much higher for the Dutch and french translations.
>
> sh ./scripts/pre_translate.sh en
>
> When I ran the script for Dutch only the file that I got from transifex
> was updated (so it really is indeed necessary).
>
> Regards,
> Diethard
>
> 2013/3/24 Marie Silvestre <marie_silvestre at yahoo.fr>
>
> Hi Otto,
> Here is what I think (so correct me if I'm wrong!) :
> Since the creation of the 1.8 branch, updates have been made on the 1.8
> rst doc (typo, etc.).
> As I understand, strings to be translated on transifex are based on the
> english po files.
> The problem is that english po files have not been updated since 3 months.
> So when uploading po files in transifex, some string translations are lost!
> (and I'm afraid some of the work that people have started in transifex is
> already out of date).
>
> So I think we need first to update the english po files for the 1.8
> branch. I can do it if needed but I don't want to step outside of "my
> territory" without permission!
>
> And if I'm wrong, I'd like to understand why I'm loosing so many
> translations when uploading french po files (normally 100% translated) in
> transifex without any error messages...
>
> Marie
>
>
>   ------------------------------
> *De :* Otto Dassau <dassau at gbd-consult.de>
> *À :* qgis-community-team at lists.osgeo.org
> *Cc :* Marie Silvestre <marie_silvestre at yahoo.fr>
> *Envoyé le :* Vendredi 22 mars 2013 19h08
> *Objet :* Re: [Qgis-community-team] Transifex and doc 1.8
>
> Hi Marie,
>
> since those .po file are for QGIS 1.8 documentation translation it should
> not
> be a problem, if they are 3 months old. They were created when the update
> to
> the english 1.8 manual was finished and the branch was created.
>
> Updates in master branch go into the 1.9 documentation branch.
>
> Regards
> Otto
>
> Am Fri, 22 Mar 2013 17:44:02 +0000 (GMT)
> schrieb Marie Silvestre <marie_silvestre at yahoo.fr>:
>
> > Hi all!
> > I hope I'm not going crazy and I'm sorry to insist but the english
> > directory for po files is still not up to date on github, is it ?
> > https://github.com/qgis/QGIS-Documentation/tree/manual_en_v1.8/i18n/enIt
> > is still 3 months old... Are those files being pushed in transifex?
> > I think I can update it tomorrow if needed, just tell me!
> >
> >
> > Marie
>
>
>
> _______________________________________________
> Qgis-community-team mailing list
> Qgis-community-team at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-community-team
>
>
>
>
>
> _______________________________________________
> 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/20130331/d01b5ebc/attachment.html>


More information about the Qgis-community-team mailing list