Please remove all translation templates and pending imports from lp:elisa/1.0

Asked by Michał Sawicz on 2009-06-09

Hi, I'm a contributor for Elisa/Moovida (http://launchpad.net/elisa).
We're in the process of cleaning up our i18n to use automatic imports, but we have some conflicting templates, could you please remove all templates from https://translations.launchpad.net/elisa/1.0/+templates and all pending imports from the queue?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
Данило Шеган Edit question
Solved by:
Jeroen T. Vermeulen
Solved:
2009-06-23
Last query:
2009-06-23
Last reply:
2009-06-22
Whiteboard:
Assigning to danilo as he seems best able to deal with this.

This question was reopened

Philippe Normand (philn) said : #1

Yes please clean up the templates

(philn, from moovida team)

Michał Sawicz (saviq) said : #2

We want to use translations' automagic imports, we have renamed all our templates to comply with launchpad's guidelines but we have conflicting templates imported already, so we'd need them cleaned out from lp:elisa/1.0 to have new properly named templates imported properly.

We dislike removing templates because that means losing all the history for translations (i.e. when did a translation happen, who did it, etc. PO files can only keep track of single "last-translator" for the entire file).

Is there anything we can do to make the switch transparent? We would be happy to help with that, and that should provide better experience for translators as well.

Michał Sawicz (saviq) said : #4

Well, our goal is to have a working automatic import and approval from a bazaar branch. If you want it like that better, then we're fine with renaming the templates to match .pot and .po files in bazaar. Basically we need current state from our branch in Rosetta, possibly with as much translations migrated as possible.

We have to migrate translations from 0.5 series, too, but they require some work on migrating placeholders, so we'll have to work on them afterwards.

I'm not sure how much you can do, I wanted to ease your work - just clean up and we'd have to do the work. If there are things you want to do differently - great. For 1.0 series there're hardly any translations ready, we have all of them in-source. What do you propose?

Hi Michał, sorry for not responding sooner on this. We are pretty overwhelmed with different items, so I just went ahead and moved old 1.0 templates out of the way. You should be able to set up bzr import now.

Michał Sawicz (saviq) said : #6

Thanks a bunch for that, the templates got imported, that's great. The thing is... Our translations didn't get approved automatically... I can't find information on what should we do with the catalog (.po) files for them to be imported without the need for Your involvement...

All translations imported from bazaar landed as "need review" in Rosetta, anything we can do about it?

Yes: you need to use a layout that's actually supported. I recommend standard GNU gettext layout of

  template1/template1.pot
  template1/es.po
  template1/de.po
  ...
  template2/template2.pot
  template2/es.po
  template2/de.po
  ...

They can be nested deeper than that, but it's important that all translations for a single POT are in the same directory, and they need to be named after a language code, except in a few cases where country is also important (like pt_BR and zh_TW).

I am also sorry if this is not well documented. We are working on documentation improvements this month as well.

Michał Sawicz (saviq) said : #9

Thanks Данило Шеган, that solved my question.

Michał Sawicz (saviq) said : #10

OK one last thing, is the described scheme the only one supported? Would putting the .po files in the same dir as the .pot suffice? Like so

i18n/<domain>.pot
i18n/<language1>.po
i18n/<language2>.po

etc.?

Yeah, that would work as well. Just do not put more than one template in the same directory (you can imagine how that's hard for the system to pick up).

Michał Sawicz (saviq) said : #12

Thanks Данило Шеган, that solved my question.

Michał Sawicz (saviq) said : #13

Well... We've done as described above.... and the catalogs still landed as 'Needs Review'...

See here https://translations.launchpad.net/elisa/+imports?start=162&batch=75

All these files should've been imported automatically... Maybe all the old imports stood in the way?

Best Jeroen T. Vermeulen (jtv) said : #14

Hmm... the only ones I see now that are waiting for review are the old files with the incorrect language codes ("fr_FR" and such) and the template domain in the filename and the language code higher up in the path:

https://translations.launchpad.net/elisa/+imports?field.filter_status=NEEDS_REVIEW

So I'm guessing the new files were auto-approved soon after you asked. To get rid of the remaining entries, just mark them as Deleted and click Change Status at the bottom of the page.

Michał Sawicz (saviq) said : #15

Yes exactly, sorry for messing things up. At last we have it all working, thanks again!

Michał Sawicz (saviq) said : #16

Thanks Jeroen T. Vermeulen, that solved my question.