Bazaar GTK+ Frontends

change launchpad translation to 'structured' to give translation teams more control

Bug #286850 reported by Jasper Groenewegen
10
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.

Tags: i18n
Revision history for this message
Jasper Groenewegen (colbrac) wrote :

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)

Changed in bzr-gtk:
status: New → Confirmed
Revision history for this message
Szilveszter Farkas (phanatic) wrote :

- Should we automate the process of updating the .po files, maybe a script to run before a new release.

This has been on my todo list for a long time. Actually the translations come from the olive project. Those should be moved to the bzr-gtk project as a first step.

- Is the set of strings in Rosetta automatically updated with new strings added in trunk?

It would make a great addition (too bad that the Launchpad API doesn't cover translations yet, so we still need some manual work there).

- Is giving full control over the translations to the Ubuntu Translation team what we want? (I think so, they are the experts)

I think it's okay to restrict translations to the Ubuntu Translations team. That would assure some quality, at least for me. (I'm trying to bump over from the 'Open' status, but my internet connection is a bit bad at the moment.)

Revision history for this message
Adi Roiban (adiroiban) wrote :

Initialy this was a question whether you want to switch from an opend to a structured translations mode to ensure translations quality.

If you will update on trunk a new .pot file it will be automaticaly imported in rosetta. Only when it is first added it must be manualy approved by a rosetta admin.

Jelmer Vernooij (jelmer)
Changed in bzr-gtk:
importance: Undecided → Wishlist
status: Confirmed → Triaged
tags: added: i18n
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.