[Inkscape-translator] Any interest for the translations to move to Rosetta on LP?

Hey Translators!

Following is a message that was sent to Bryce regarding translations. Given that I don't do any translating, I don't feel it appropriate to chime in other than saying that it sounds like it would be beneficial to our translators. Would you all be interested in giving it a shot?

Cheers, Josh

-------- Forwarded Message --------

Hi Bryce,

Seeing that now Inkscape has migrated to Bazaar, I was wondering if they could also benefit from another of the advantages of using Launchpad: Translations.

The current workflow for submitting translations in Inkscape (download PO file from the repo, translate it offline, submit it as a bug in LP and let the developers commit it) would greatly be improved for both translators and maintainers:

  * Translators: they could use the web UI to translate, not having
    to worry about browsing through repositories, downloading PO
    files and keeping track of when their translations are committed
    (they'd be used straight away, transparently). They'd then be
    able to use all the cool Rosetta features: global translation
    suggestions (i.e. point and click translation), spell checking
    from the browser, translation sharing (sharing between series
    means that they no longer will have to fix mistakes in all
    branches: they'll do it in one and changes instantly propagate
    to all shared ones), online translating with a clean interface,
    etc. For those still wanting to use the old workflow and
    translate offline, Rosetta is flexible enough in the sense that
    it allows downloading the PO files, translate offline and upload
    the finished translation.

  * Maintainers: choosing automatic imports and exports of
    translations from bzr branches, they will no longer have to
    worry about translations. They'll only have to update the POT
    template before release and announce the string freeze as usual,
    commit it and it will be updated in Launchpad exposing the new
    strings. With automatic exports translations will be committed
    daily to a branch of their choice. Additionally, the work that
    is currently going on in automatically regenerating POT
    templates means that in the future they won't even have to worry
    about that.

Using all these features is only a few clicks away, and I'd feel happy for both translators and the Inkscape maintainers if this move were also considered. I'd also be willing to give a hand with setting it up and advice if they decided to go ahead with it and need help.

The basic steps would be:

  * Enabling automatic translation imports from a bzr branch at
    https://translations.launchpad.net/inkscape/trunk/+translations-settings
  * Keeping the (already generated) POT template under version
    control, that is committing it to the bzr branch
  * Choosing a permissions policy for translations
  * Enabling translation sharing
  * Enabling automatic translation exports at
    https://translations.edge.launchpad.net/inkscape/trunk/+translations-settings

For more information:

  * Importing translations:
    https://help.launchpad.net/Translations/YourProject/ImportingTemplates and http://blog.launchpad.net/translations/screencast-importing-translation-templates-from-a-bazaar-branch
  * Choosing a permission policy:
    https://help.launchpad.net/Translations/YourProject/PermissionPolicies
  * Translation sharing:
    http://blog.launchpad.net/translations/screencast-sharing-translations-between-releases-of-the-same-project
  * Exporting translations:
    https://help.launchpad.net/Translations/YourProject/Exports and
    http://blog.launchpad.net/translations/screencast-exporting-translations-to-a-bazaar-branch

Do you think they'd be interested? If so, who should we talk to?