[Qgis-tr] linguist vs. transifex in GUI translation
Werner Macho
werner.macho at gmail.com
Wed Apr 16 02:00:01 PDT 2014
Hi Jacob!
Thanks for the hint .. Going to take a look at it ..
regards
Werner
On Wed, Apr 16, 2014 at 10:36 AM, Jacob Overgaard Madsen
<u2jacob at gmail.com> wrote:
> Hi Werner
>
> I've started using CrowdIn for another translation project (CyanogenMod).
> They tested Transifex but had Unicode issues, so they moved to CrowdIn
> instead. Would this be an option?
>
> Jacob
>
>
> 2014-04-16 10:04 GMT+02:00 Werner Macho <werner.macho at gmail.com>:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Dear Translators!
>>
>> During the last Codesprint I took the time for a few Discussions with
>> developers and users and took a look on transifex.
>>
>> I decided to make a TEST PHASE for transifex:
>>
>> Short conclusion:
>> You can EITHER use transifex OR linguist with the direct qgis_*.ts file.
>> There is currently no fast/reasonable way to merge them both.
>>
>> Longer story:
>> The current way of translations is to checkout the source from github
>> (or download only the qgis_**.ts file of your language and translate
>> it with linguist.
>>
>> With Linguist this has a few benefits:
>> * If you checked out the source and probably compiled QGIS on your own
>> you will see the "environment" of the string you are currently
>> translating and will have a better feeling if the strings will fit or not.
>> * You can easily work offline
>>
>> Transifex:
>> * Is easier to handle for beginners
>> * Is Web based with the possibility to download the file (but that
>> will lock it for other users)
>>
>> We tried a lot of things to combine these two possibilities but the
>> merge was always problematic.
>>
>> So I am going to leave it to the language coordinators (of a team) or
>> if there is only one person translating to the translator if he wants
>> to choose either linguist and the qgis_**.ts file _OR_ webbased transifex.
>>
>> Remember there is only ONE source that can be included into QGIS.
>>
>> For all language-coordinators I only want to know which way you choose
>> so that I can make a list which translation is coming from which
>> source before a release.
>>
>> (direct translation in linguist means less work for me :) - with
>> transifex I will download the "finished" file and integrate it into
>> QGIS Source.
>>
>> I will "clean" the transifex page soon to only include the languages
>> that decided to translate with transifex.
>>
>> So lets test if we can integrate transifex this way.
>>
>> Please bear in mind that whenever you choose one translation type the
>> OTHER one will be overruled by your decision.
>>
>> If you decide to use transifex I can update the language to the very
>> latest state from github.
>>
>> I need some volunteers to test! :)
>> Let's hope it will work the way we want it.
>>
>> thanks a lot for all your effort in translation!
>>
>> kind regards
>> Werner
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.15 (GNU/Linux)
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>
>> iEYEARECAAYFAlNOOXUACgkQDAH1YiCxBglw8wCdGhN3nSl4QmGVa9WQT/YBPk9A
>> fF8An2t0UhBdf55BNsVKNSjyiFaoxL/a
>> =r+Qq
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> Qgis-tr mailing list
>> Qgis-tr at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/qgis-tr
>
>
>
> _______________________________________________
> Qgis-tr mailing list
> Qgis-tr at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-tr
More information about the Qgis-tr
mailing list