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

Sylvestre Ledru sylvestre.ledru at scilab.org
Wed May 4 11:33:32 CEST 2011


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...

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. 

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. 

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 ;)





More information about the localization mailing list