As I said to Sergio back via email in our mailing list, the best
solutions to this is: working with upstream.

It's not an easy task, and not something we can achieve in the short
time, but that's the best thing we can do to improve not only Ubuntu,
but all distros using those projects. This is something I personally do,
it takes you months to see the results... but that gives you the best
results.

One thing we (well... probably Launchpad) can do, as Matthew said, is
talking more to the projects maintainers about the translation teams
that exist inside Launchpad. For "talking" I mean explaining to them
what are the advantages of "using" a translation team. I don't know
what's the procedure of importing a project inside Launchpad, what does
it involve, but an explanation page on this issue would be great,
pointing out the translation teams, the best quality of translations...

That could be a solution for projects coming in Launchpad, but there are
lots of projects outside there and we can't be everywhere... or reach
everybody... or force somebody... it's up to us as translators trying to
improve this (i18n & l10n are not tasks that should be taken lightly in
these days... well... nothing should be... but that's another point :)
).

-- 
Consequences of "Open" translation permissions not obvious
https://bugs.launchpad.net/bugs/198305
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to