change launchpad translation to 'structured' to give translation teams more control
Bug #286850 reported by
Jasper Groenewegen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar GTK+ Frontends |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Was a question, seems more like a bug/wishlist to me.
Original text:
Can you please change the translation model for your project from open to structured ?
I am the coordinator of Romanian Ubuntu translation and we receive many wrong translations from your project.
By using the open model everybody can add translations and there is no way to assure translation quality.
By using the structured mode, and assigning translations to Ubuntu Translation team, everybody can add suggestions and only members of a translation team can validate the translations.
Changed in bzr-gtk: | |
importance: | Undecided → Wishlist |
status: | Confirmed → Triaged |
tags: | added: i18n |
To post a comment you must log in.
bzr-gtk ships with it's own po folder. I checked some files and the last update seems to have been March 11th, 2008.
As far as I can see we use Rosetta only to track and control the translation process. Some questions:
- Should we automate the process of updating the .po files, maybe a script to run before a new release.
- Is the set of strings in Rosetta automatically updated with new strings added in trunk?
- Is giving full control over the translations to the Ubuntu Translation team what we want? (I think so, they are the experts)