<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Why don't you ask the translators ? <br>
<br>
As the main translator for QGIS 2.2 Danish, I would give this a -1
until convinced otherwise:<br>
<ul>
<li>My current work-flow "just works" by having the source-tree
for QGIS - including the Danish ts file - on my computer. This
is a absolute _must_ because the Danish translated strings are
mostly longer than the original English strings. I have to
check the Danish strings in the QT based dialogues using the
QT linguist program for a large percentage of the strings.<br>
</li>
<li>Moving it to Transifex and splitting it in several parts
would just complicate my work-flow without any benefits.</li>
<li>I suspect that the different translation teams is often the
size of one person for a version release - removing the
benefit of crowd sourcing.</li>
</ul>
<p>Regards <br>
Bo Victor Thomsen<br>
Aestas-GIS<br>
Denmark<br>
</p>
<br>
Den 16-02-2014 17:29, Alexandre Neto skrev:<br>
</div>
<blockquote
cite="mid:CA+H0G_E1eYA1vMa1+tt=gw_kjMq+qeOwpsCKctcR7iUBz=MRLQ@mail.gmail.com"
type="cite">
<div dir="ltr">Hello all,
<div><br>
</div>
<div>Here goes my 50 cents.<br>
<div><br>
</div>
<div>I believe that using transifex will bring more
translators, as it's definitely more straightforward to just
register, login and start translating, than having to mess
with download files from git, and push them back to the
repository. In transiflex, if we could share the glossaries
between Documentation, Web and GUI it would also add
consistency to certain translated strings.</div>
<div><br>
</div>
<div>But... not being able to preview the GUI dialogs while
translating, makes it difficult to safely translate certain
strings that in English can have several meanings, but that
in other languages (my experience is with Portuguese) must
be more explicit. In the website and documentations this is
less troubling since generally strings are in some context.</div>
</div>
<div><br>
</div>
<div>This means that at least some of the translators will have
to keep downloading the files and edit them using QtLinguist
to ensure the quality of translation.</div>
<div><br>
</div>
<div>Alexandre Neto</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Sun, Feb 16, 2014 at 1:55 PM,
Alexander Bruy <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:alexander.bruy@gmail.com" target="_blank">alexander.bruy@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
Richard,<br>
<br>
2014-02-16 14:27 GMT+02:00 Richard Duivenvoorde <<a
moz-do-not-send="true" href="mailto:richard@duif.net">richard@duif.net</a>>:<br>
<div class="">> For Documentation and Website, nobody
should get .po files from Github.<br>
> If Application would come in Transifex, the same
rule: you should NOT go<br>
> to Github and get it from there.<br>
<br>
</div>
This is bad approach for application IHMO (well, actually I
think this is bad<br>
approach at all :-) ). Now I can update .ts file and
translation in any time,<br>
so translation will always about 100%. If we will use same
workflow as used<br>
for Documentation and Website then I'll have lot of
untranslated string before<br>
release.<br>
<div class=""><br>
> At Transifex, you can get the .ts file from their
website (and thereby<br>
> locking the translation from the website for one day
if you want).<br>
> You can then use Linguist to offline translate the ts
file (you got from<br>
> transifex). After Linguist-translating you can upload
that .ts file back<br>
> to transfex and it will be merged there.<br>
<br>
</div>
Yes I know about this and this is way I worked: download .po
files from<br>
Transifex, translate them using Qt Linguist and upload them
back after<br>
translation.<br>
<div class=""><br>
> Your second point: yes, you are right. You do not
have the old string<br>
> stuff, in Linguist then. But Transifex is getting
better and better, and<br>
> for example if we translate via transifex itself now,
you get<br>
> Suggestions and History too. But we win and loose
some<br>
> functionality/options.<br>
<br>
</div>
Uhmm, this is a matter of taste. I just logged into my
Transifex account<br>
to test file you mentioned and I found that I completely
loose in new<br>
Transifex interface. I spend about 10 minutes to find how I
can now<br>
download file.<br>
<br>
Also translating via Transifex requires internet connection.
Unfortunately,<br>
stable connections available not everywhere. For example
here internet<br>
sometimes become very slow and unstable. I already loosed
translations<br>
for two relatively large sections because of internet
failures when translating<br>
via Transifex.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Alexander Bruy<br>
</font></span>
<div class="HOEnZb">
<div class="h5">_______________________________________________<br>
Qgis-community-team mailing list for organizing
community resources such as documentation, translation
etc..<br>
<a moz-do-not-send="true"
href="mailto:Qgis-community-team@lists.osgeo.org">Qgis-community-team@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/qgis-community-team"
target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-community-team</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Qgis-developer mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-developer@lists.osgeo.org">Qgis-developer@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/qgis-developer">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a></pre>
</blockquote>
<br>
</body>
</html>