[Scilab-loc] Settings for the scilab localization in LaunchPad Translations

[Kenneth Nielsen]

Hallo Sylvester

2011/5/4 Sylvestre Ledru <sylvestre.ledru at scilab.org>:
> I am copying and pasting the email of Yuri which has been stuck in the
> moderation queue (and which I just saw)
>
> Kenneth, what is your opinion on this ?
> I am not familiar enough with launchpad/translation to judge here...

Yes I'll try an answer.

> Hi,
>
> написане Wed, 27 Apr 2011 19:15:03 +0300, Kenneth Nielsen [via
> Scilab /
> Xcos - Mailing Lists Archives]
> <[hidden email]>:
>
>> So in short my suggestion is to assign the translation of Scilab to
>> the ~launchpad-translators group and ask your existing translators to
>> join the respective language teams within that group.
>
> Please do not do this. Some of ~launchpad-translators groups are dead
> and
> cannot be reached (at least Ukrainian one). It will be very hard for me
> to
> maintain the translation if you do so.

It is true that it can happen that a Lauchpad translators team run out
of steam and become inactive. However, the appropriate way to solve
that then is to try and take over the team and revive it (which Yuri
actually is doing now). Please consider this: The launchpad
translators group is meant to be a gathering project for all the
independent projects in Launchpad, so if language team cannot be
maintained there, then it is unlikely that it can around just at
single project. So if you want to assign a group to your translation
to provide them with the opportunity to make translations of higher
quality, then surely this group is the best bet.

> There is no reason to restrict open project translation by just
> Ubuntu
> users or Ubuntu teams. I have no reasonable proof that the quality of
> these group translations (at least in case of Ukrainian and Russian)
> are
> in any kind better than the quality of open translations.

Well first off, there a few things that need to be cleared up. The
Launchpad translators group has nothing to do with Ubuntu nor is it
specific to Ubuntu users. Launchpad is a generic code hosting site
with support for translation, specification and bug tracking and
answers. Ubuntu is just one of the projects being hosted on this site,
even though it certainly is the biggest. That is also the reason why
it has its own translators-group with its own translation teams, which
has nothing to do with launchpad-translators. Just to re-iterate,
lauchpad-translators is created for all the "little" independent
projects in LP and being a member of that group only requires that you
have a LP-account, NOT that you are a Ubunt user.

As for quality. You are correct that restricting translations to a
group like launchpad translators, does not _guarantee_ that the
translations will become of high quality, but it does give the teams,
that are willing to make an effort to produce the high quality
translations, the tools (and control) to make that possible, tools
that don't have if the translations is open.

Regards Kenneth

>
> Just my 5 cents.
>
> Best regards,
> Yuri
>
> Le mercredi 27 avril 2011 à 18:14 +0200, Kenneth Nielsen a écrit :
>> Hallo
>>
>> I am interested in starting to translate Scilab into Danish and I had
>> a look at the project in Launchpad and I noticed a few things I think
>> might be set up better. I hope you will consider these humble
>> suggestions.
>>
>> I Launchpad there are four settings for translation permissions,
>> "Open", "Structured", "Restricted" and "Closed". For Scilab it is set
>> to "Structured", which means that if there is a team or person
>> assigned to a language within the group that is assigned to the entire
>> translation*, the only that team or group can make contributions and
>> if there isn't assigned a team of person to a language within that
>> group, then it is open to everyone. The thing is, that there is no
>> group assigned to the translation, which means that the defacto
>> results is that it is open, which I am guessing wasn't the purpose
>> since you set it to "Structured". If you value quality in the
>> translation, then it should indeed be set to "Structured" or
>> "Restricted" and assign the translation to a group. You could off
>> course form a Scilab specific group on launchpad and assign the
>> translation to that group, but there is actually already one set up
>> for exactly this purpose, the ~launchpad-translators group. This group
>> has the purpose of translation all the independent projects on
>> Launchpad and therefore already has language teams with active
>> translators set up.
>>
>> So in short my suggestion is to assign the translation of Scilab to
>> the ~launchpad-translators group and ask your existing translators to
>> join the respective language teams within that group.
>>
>> When it comes to deciding between "Structured" and "Restricted" then
>> it is really a matter of where you priority lie between quantity and
>> quality when it comes to how many languages you cover. The difference
>> concerns the languages for which there is no person or team assigned
>> within the group. With "Structured" permissions the translations for
>> that language will then be open to everyone, with "Restricted"
>> permissions it is closed to all. I would suggest making it
>> "Restricted" since that ensures maximum quality.
>>
>> Regards Kenneth Nielsen
>>
>> * Launchpad makes the distinction between translation groups and
>> teams. Groups are assigned to the task of localizing into all
>> languages and consist of teams that localize into a single language ;)
>
>
>