On 2012-05-14 18:23, David Planella wrote:
Sorry for not having replied earlier, just got back from UDS, and thanks
for bringing this up!
My feeling is that we haven't seen much of this happening to justify a
change in the current permissions. In the current case, if the project
owner wants to have control over which translations go into their
software, they should use 'Restricted' and choose an appropriate
translations group or create their own.
I think in this case the project owner is the one to object, but it's an
issue that should be under the translation group's control.
I'd much rather see any development efforts in LP Translations put into
existing bugs that are much more critical.
There is no development effort involved. Just a matter of creating an
empty do-not-translate team, and setting it as the translator for
unwanted languages in the Launchpad translation group: en_CA, es_NI, and
so on. That is massively easier than development work.
Jeroen
_______________________________________________
Mailing list: https://launchpad.net/~launchpad-translations-coordinators
Post to : [email protected]
Unsubscribe : https://launchpad.net/~launchpad-translations-coordinators
More help : https://help.launchpad.net/ListHelp
