Please share translations between lp:elisa/0.5 with lp:elisa/1.0

Asked by Michał Sawicz on 2009-06-29

Please mark translations from elisa/0.5 series to be shared with elisa/1.0

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Данило Шеган Edit question
Solved by:
Michał Sawicz
Solved:
2009-08-14
Last query:
2009-08-14
Last reply:
2009-08-13
Adi Roiban (adiroiban) said : #1

Hi Michal.

When you want the translations to be shared, you want to change a translation in 0.5 and to be automaticaly updated in 1.0, and when changing a translation in 1.0 to be automaticaly changed in 0.5?

I am not sure about that (a Rostta dev should know more) but I think that if your 1.0 series is based on 0.5, now we have an implicit message sharing feature, and unchanged strings will be shared between series.

Adi Roiban (adiroiban) said : #2

Hi again,

I see that the transltations for elisa are open, and everyone can change them. Maybe you would like to change them to Structured and assing the translatoin to Launchpad Translation Group.

At the following page you can read more about Maintainting translations quality
https://help.launchpad.net/Translations/YourProject#Maintaining%20quality

Also maybe you would like to rename your project to Moovida, in this way it will be easy for translators to recognize the project.

Cheers

Michał Sawicz (saviq) said : #3

Yes, danilos@#launchpad asked me to file a question here to keep track of it as sharing was not yet possible here but said it will be done in a few days.

About the second reply - yes we're discussing some options about Structured permissions, we're a bit afraid that would lock out some possible translators as we're not yet quite sure what that will actually change and what would be the possibilities.

Renaming the project - I'll pick that up with core devs soon.

Michał, we've tested this and we have a few problems we need to fix in our code before we can do this. Let's keep this Open until we can actually do it (we'll first do it on staging, to make sure it works there).

Still not done.

Michał Sawicz (saviq) said : #6

Any news on this one?

Jeroen T. Vermeulen (jtv) said : #7

I just ran a test, but hit a database constraint so needs a bit more investigation. :(

Michał Sawicz (saviq) said : #8

OK keep us posted, please :)

Karl Fogel (kfogel) said : #9

Jeroen, any news?

Jeroen T. Vermeulen (jtv) said : #10

Still fighting another unique violation (bug 403992), but haven't made much progress on it. :-(

Jeroen T. Vermeulen (jtv) said : #11

We just ran a test on staging that looks successful. Now I'll need to go over the resulting data to make sure it's correct. If you're willing to give it a look as well, I can make the "before" and "after" tarballs available to you somewhere.

Jeroen T. Vermeulen (jtv) said : #12

We've run that test now. There was one small thing that looked wrong to me: a few messages such as "Season %s" were marked with the python-format flag before sharing but not after sharing. Investigation of that particular case turned up that the 0.5 template used that flag but the 1.0 template didn't. The sharing algorithm considers 1.0 more "representative" because it has the translation focus, and so uses the 1.0 version of the message.

That is the correct behaviour, but this also means that you may want to check your latest templates to see that it doesn't omit "format" flags in cases where they are appropriate.

We will now schedule a real migration of the project on production, and keep you posted. Please keep a sharp eye open for anything unusual!

Jeroen T. Vermeulen (jtv) said : #13

At last, it's done! We've run the migration on production and all of the project's translations should now be shared.

If you should see anything wrong, try contacting jtv, danilos, or henninge on the #launchpad IRC channel, or filing another question or a bug here.

Michał Sawicz (saviq) said : #14

Thank you.