faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Translation
by Rinse on Saturday 25/Jun/2005, @00:39
|
Looking at the German stats, Except for kio_svn.po and some strings in spy.po their translation of the official KDE-modules is completed.
kio_svn.po was added after the release of kde 3.4.1 (afaik), so it's no wonder that one is untranslated. The german team has until july 17 to translate it :)
Looking at the stats of the german koffice, You will notice that krita, kplato and kivio are unfinished.
Both krita and kivio contain a lot of strings that need more than average knowledge of the subject to translate.
In those cases, the fact that they are po-files is not the barrier, but being familiar with the typ of application is.
I don't see how a wiki or other webbased solution can solve that.
One of the major issues that a wiki does not solve either is the quality of the translation in order of consistency with other parts of KDE. One can translate the hundreds of different colors in krita, or the hundreds of different stencils kivio by sucking them out of you thumb, but that would end up with a shamefull translation rather then a usefull translation.
Looking back at the Dutch translation of Krita, most of the color strings are left untranslated. But you won't see that in the stats, because we copied/pasted the English phrase to the translation. If the German team also decides not to translate the named colors, but does not copy them to the translation fields, then their stats would put them behind the Dutch team, while in real life they are not. (like i said earlier, stats don't tell the whole story) |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Translation
by Andre on Saturday 25/Jun/2005, @08:33
|
Forget about the stats. It is about the fact that in the current translation model translation is not the easy taks it is supposed to be.
And documentation is really worse than GUI. The team does not scale. The question is: how long will it last to translate 100%, is the change and new string expansion faster than what a translation team contributes.
We don't want a translation lag.
I understand pretty well that translation is not that easy, that it requires high skills.
It is more a recruitment issue. Open models are always superiour.
|
[
Reply To This | View ]
|
Re: Translation
by Rinse on Saturday 25/Jun/2005, @21:11
|
> It is about the fact that in the current translation model translation is not the easy taks it is supposed to be.
But why isn't it?
You don't come up with any reason of why the current model fails...
>I understand pretty well that translation is not that easy, that it requires high skills.
>It is more a recruitment issue
You won't reach more users with high skills by lowering the barier to join a team.
It is the opposite, to ensure that you get volunteers that are capable of doing the job right, you need to have some kind of tresshold.
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
