incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Weir <robw...@apache.org>
Subject Translation testing
Date Tue, 19 Jun 2012 20:05:18 GMT
On Tue, Jun 19, 2012 at 3:31 PM, Andrea Pescetti <pescetti@apache.org> wrote:
> Jürgen Schmidt wrote:
>>
>> On 6/19/12 4:21 PM, Andrea Pescetti wrote:
>>>
>>> See https://issues.apache.org/ooo/show_bug.cgi?id=120036
>>>
>>> New translations are release blockers, so I expect this to be considered
>>> a  3.4.1 blocker with no need for discussion.
>>
>> we should at least discuss if we want to release the language ;-) No
>> default mechanism ...
>
>
> Well, everything happened on this list, and it has happened since June 1st,
> so people had plenty of time to comment. It was OK for Kay, me and you. You
> wrote that you would take care of including Slovenian in 3.4.1 and nobody
> opposed.
>
> I'd say lazy consensus has already been reached, but if anyone has anything
> against including Slovenian in 3.4.1 he can just write here or in the
> aforementioned issue.
>
> I can't read Slovenian, but since the guys have translated OpenOffice.org
> for years I'm confident about the translation quality.
>


Moving this to its own thread.

If we want to have a reputation for high quality I think we need to
find a way to get beyond "solo translations", by which I mean
translations done by own person, with no independent review.

We would never accept a code contribution in a language we could not
read or test, right?  We wouldn't ship an OS port if we didn't have
more than one user able to test it, would we?

And look at existing translations.  Even though we are not really
changing the UI in 3.4.1 we're getting a stream of corrections to the
AOO 3.4.0 translations.  This is not surprising.   Errare humanum est.
  Even repetitive data transcription tasks can have a 5% error rate.
That's why where accuracy is important we have consistency checks, for
example checksum digits in credit card and ISBN numbers.  That's why
we do QA with code.  That is why we have spell checkers.

It is almost guaranteed that a "solo translation" will have a higher
error rate.

What can we do about this?

Maybe we can promote the availability of a new translation, with help
from the translator, among our user base.  So notices on Twitter,
blogs, and native-language tech sites.  Invite users to download
snapshot builds with the goal of verifying the localization.   If  a
translation is worth doing we should be able to find a community (even
a small one) of users to help with this work.

Any other ideas?

Regards,

-Rob

> Regards,
>  Andrea.

Mime
View raw message