[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-i18n-doc
Subject: Re: Unified KDE GUI localization server
From: Viorel-Cătălin Răpițeanu <rapiteanu () linux ! com>
Date: 2015-10-26 22:44:07
Message-ID: CAP7KZLRzudhC3_dFV5Pa2fX3+JmxFFdCir8n_5if_K3SOVag0w () mail ! gmail ! com
[Download RAW message or body]
> Well, if a person finds it too difficult to learn to use a mailing list
(basically press ‘Get new messages' and perhaps the ‘Reply' and ‘Send'
button) or to use SVN (basically *two* commands, ‘svn up' and ‘svn commit',
or use a graphical UI), I very much doubt they're suited for translating
highly technical software like KDE.
From my limited experience, most new translators as I've managed to see are
just regular guys that don't want to translate complex technical
documentation of complex interfaces. They just want to translate the big
untranslated string (eg. 'Type to search' text from the dashboard) from a
visible component. After their small and insignificant change was merged,
they get a sense of accomplishment, thing that makes them try to translate
more. They usually don't have a technical background, so forcing them to
understand how SVN works, what program to use for translation and who to
mail to have their change submitted is, imho, a bit to much. I always seen
translation as an easy step that anyone can make to join a community.
> Actually, using offline translation tools like Lokalize is *much* more
efficient than current Web-based tools.
I agree on this part. Trying to translate large projects in a GUI is
inefficient if you know how to use an program for offline translations. The
GUI translation server is for allowing new inexperienced translators to
join by offering them a nice learning curve. In time they will realize on
their own that offline translation is more efficient, but this will learn
on their own after they are invested enough in the project. I think that a
good example for this is the LibreOffice translation server.
2015-10-26 23:57 GMT+02:00 Karl Ove Hufthammer <karl@huftis.org>:
> Den 26. okt. 2015 19:39, Viorel-Cătălin Răpițeanu skreiv:
>
>> I find it completely unnecessary for a translator to know how to use a
>> mailing list or SVN just to contribute to the translation of a software.
>>
>
> Well, if a person finds it too difficult to learn to use a mailing list
> (basically press ‘Get new messages' and perhaps the ‘Reply' and ‘Send'
> button) or to use SVN (basically *two* commands, ‘svn up' and ‘svn commit',
> or use a graphical UI), I very much doubt they're suited for translating
> highly technical software like KDE.
>
> I know that each team can create it's own server for translation, but
>> doing things these way, is like killing languages with small communities
>> that don't have a tech wise guy to make this set-up.
>>
>
> Actually, using offline translation tools like Lokalize is *much* more
> efficient than current Web-based tools. It may very well be that some
> people prefer Web-based tools, but note that they're more suitable for
> *larger* translation teams, that have the (human) resources to work with
> relatively inefficient tools. Smaller teams will be much more productive
> using Lokalize. I would also recommend using the summit workflow, which is
> very useful for smaller teams (so you don't have to retranslate files for
> the four branches, or manually manage and merge translations for the
> branches).
>
> --
> Karl Ove Hufthammer
>
[Attachment #3 (text/html)]
<div dir="ltr">> Well, if a person finds it too difficult to learn to use a \
mailing list (basically press ‘Get new messages' and perhaps the ‘Reply' and \
‘Send' button) or to use SVN (basically *two* commands, ‘svn up' and ‘svn \
commit', or use a graphical UI), I very much doubt they're suited for translating \
highly technical software like KDE.<br><div><br></div><div>From my limited \
experience, most new translators as I've managed to see are just regular guys \
that don't want to translate complex technical documentation of complex \
interfaces. They just want to translate the big untranslated string (eg. 'Type to \
search' text from the dashboard) from a visible component. After their small and \
insignificant change was merged, they get a sense of accomplishment, thing that makes \
them try to translate more. They usually don't have a technical background, so \
forcing them to understand how SVN works, what program to use for translation and who \
to mail to have their change submitted is, imho, a bit to much. I always seen \
translation as an easy step that anyone can make to join a \
community.</div><div><br></div><div>> <span style="font-size:12.8px">Actually, \
using offline translation tools like Lokalize is *much* more efficient than current \
Web-based tools.</span></div><div><span style="font-size:12.8px">I agree on this \
part. Trying to translate large projects in a GUI is inefficient if you know how to \
use an program for offline translations. The GUI translation server is for allowing \
new inexperienced translators to join by offering them a nice learning curve. In time \
they will realize on their own that offline translation is more efficient, but this \
will learn on their own after they are invested enough in the project. I think that a \
good example for this is the LibreOffice translation server.</span></div></div><div \
class="gmail_extra"><br><div class="gmail_quote">2015-10-26 23:57 GMT+02:00 Karl Ove \
Hufthammer <span dir="ltr"><<a href="mailto:karl@huftis.org" \
target="_blank">karl@huftis.org</a>></span>:<br><blockquote class="gmail_quote" \
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span \
class="">Den 26. okt. 2015 19:39, Viorel-Cătălin Răpițeanu skreiv:<br> \
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> I find it completely unnecessary for a translator to know \
how to use a mailing list or SVN just to contribute to the translation of a \
software.<br> </blockquote>
<br></span>
Well, if a person finds it too difficult to learn to use a mailing list (basically \
press ‘Get new messages' and perhaps the ‘Reply' and ‘Send' button) or to use \
SVN (basically *two* commands, ‘svn up' and ‘svn commit', or use a graphical UI), \
I very much doubt they're suited for translating highly technical software like \
KDE.<span class=""><br> <br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> I know that each team can create it's own server for \
translation, but doing things these way, is like killing languages with small \
communities that don't have a tech wise guy to make this set-up.<br> \
</blockquote> <br></span>
Actually, using offline translation tools like Lokalize is *much* more efficient than \
current Web-based tools. It may very well be that some people prefer Web-based tools, \
but note that they're more suitable for *larger* translation teams, that have the \
(human) resources to work with relatively inefficient tools. Smaller teams will be \
much more productive using Lokalize. I would also recommend using the summit \
workflow, which is very useful for smaller teams (so you don't have to retranslate \
files for the four branches, or manually manage and merge translations for the \
branches).<span class="HOEnZb"><font color="#888888"><br> <br>
-- <br>
Karl Ove Hufthammer<br>
</font></span></blockquote></div><br></div>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic