The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Internationalisation
by Debian User on Sunday 29/May/2005, @13:48
|
Hello,
can you explain more why internationalisation must be quick?
Is it really going to be a disaster when it only catches up in 4.0.3?
I personally see no reason why i18n cannot be done only once the bugs are being ironed out...
That said, I often see wrong/unappropiate translations into my language. What I would love to have is a "tool" to run and submit the change proposal to some list of people who take it and put it to cvs.
Kay
|
[
Reply To This | View ]
|
Re: Internationalisation
by Nicolas Goutte on Sunday 29/May/2005, @15:20
|
It is one of the policy of KDE to release translations with the first stable version. (Yes, some other projects do otherwise.)
As for the "tool", you can use KDE Bugs: http://bugs.kde.org
Have a nice day!
|
[
Reply To This | View ]
|
Re: Internationalisation
by Anonymous on Sunday 29/May/2005, @15:20
|
> That said, I often see wrong/unappropiate translations into my language.
And how does that happen? Because some translators never run the application they translate or never the development version of it prior release. Those web translation interfaces intensify this effect additionally as translators may not even be interested in/run KDE. They get single strings presented and don't know how terms are translated elsewhere within the same application or elsewhere in KDE. And likely they don't even know the tools or lists/ways how to report ambiguous strings back to the developers of the for translation process aggregated projects.
> What I would love to have is a "tool" to run and submit the change proposal to some list of people who take it and put it to cvs.
http://bugs.kde.org exists: product="i18n", component=your language.
|
[
Reply To This | View ]
|
Re: Internationalisation
by Rinse on Tuesday 31/May/2005, @01:30
|
For reporting bugs in the translation, the Dutch team uses a html-interface:
http://www.kde.nl/helpen/bugs.html
wich can be used besides bugs.kde.org
|
[
Reply To This | View ]
|
|
Re: Internationalisation
by Anonymous on Sunday 29/May/2005, @15:23
|
> Translation should not be an easy task for average joe contributors
No, I would prefer quality over quantity anytime.
> not require special skills such as CVS knowledge
You don't need CVS knowledge for KDE (anymore). :-)
|
[
Reply To This | View ]
|
Re: Internationalisation
by Nicolas Goutte on Sunday 29/May/2005, @15:23
|
Only the I18N/L10N team leader needs a SVN account. The others do not and as far as I know, some teams are working that way (by dispatching the work).
Have a nice day!
|
[
Reply To This | View ]
|
Re: Internationalisation
by ac on Tuesday 31/May/2005, @01:24
|
>>There always is a project participation entrance barrier.
Which is mostly in the head of the people, I found that joining a team is quite easy, and that for every type of skill there is a job available.
>>Translation should not (not?) be an easy task for average joe contributors, not require special skills such as CVS knowledge.
Translating/localizing software does not require special skills that are too hard for joe user. For example, the Dutch translation is coordinated by a cook. How hard can it be if even someone with no link to ICT, like a cook, can handle it?
>Some premature web based contribution engines such as IRMA and pootle adress the important issue.
The problem with pootle and IRMA (AFIAK) is that it does not use a translation memory. If you have a large amount of applications translated, you can use those translations to translate new apps for about 40-60% (considering simple apps). This increases the consistency between apps and reduces workload for the translators.
> However now the translation does not catch up quickly enough.
KDE is shipped with 50 languages, which is quite a lot already.
The bottleneck in translating KDE is not the skills joe contributer should have in order to use the special tools for translating, it is the knowledge of the English/Native language, and the ability to figure out how a string is used in the application. Also, translation is very time consuming- not everyone has the time to participate in a translation project.
But anyone who prefers KDE in their own language should team up with their translation team. Even small contributions, like proofreading stuff or giving comments about the translation while using KDE, are more then welcome.
You can find your team on http://i18n.kde.org
|
[
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)
