Launchpad itself

This change on .po files is fine?

Asked by Luiz Augusto

I've done some translations using the web interface years ago. Now I've done some using .po files for the first time.

Since I'm very curious, I've explored some features of the Poedit tool, such as creating a translation memory database. Then I've run the automated translation tool, that generated some correct phases and some nonsense ones. I've fixed some of then and translated by hand some others.

I wanted to send my work-in-progress to avoid to someone translating the exactly same messages that I've translated, but without flooding with phrases not reviewed (I known that those will get a "needs review" flag on the web interface, but some of the phases really don't have nothing related to the ones in the English language). I've run the command

msgattrib --translated --no-fuzzy [original.po]>[new.po]

and uploaded the .po files to the "biblio" and "calibre projects". But now I'm worried if it is ok.

This may cause some kind of problem to the script that automatically merges the .po files? If reviewed by hand it will makes problems to the reviewer? What do you recommend to do in the next time?

Best regards,
Luiz Augusto

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Jeroen T. Vermeulen
Solved:
Last query:
Last reply:
Revision history for this message
Luiz Augusto (lugusto) said : 		#1

lol in the meantime all of my translations have successfully imported. But I will keep this question open since I need to known if is fine to run the command mentioned above.

Revision history for this message
Best Jeroen T. Vermeulen (jtv) said : 		#2

Hi Luiz,

Launchpad ignores fuzzy messages anyway. So --no-fuzzy should be harmless (and also useless). I can't say off the top of my head whether removing untranslated messages from the PO file will change anything, but it's not likely to cause any problems either.

Of course it would be bad if you use --translated on the template, but that would be a bad idea and I'm assuming you didn't do that. :-)

Revision history for this message
Luiz Augusto (lugusto) said : 		#3

Thanks Jeroen T. Vermeulen, that solved my question.