Person incorrectly listed as a translator

Bug #118527 reported by Elxan İsmayılov
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

Revision history for this message
Matthew Paul Thomas (mpt) wrote : Re: author of translations is changed while updating to new releases

Elxan, can you give one or two examples of strings that are wrongly labelled as being yours? Please also give the URL of the pages in Launchpad where you see them.

Changed in rosetta:
importance: Undecided → High
status: Unconfirmed → Needs Info
Revision history for this message
Elxan İsmayılov (elxan) wrote :

Hi, sorry for not providing additional information.
here I am shown as a contributor but, I am sure that I haven't done any contribution there.
and here there are some translations that I have not done. May be I have done them somewhere else but not here.
And I think 2 months ago I realized that there were translations that I haven't done in gnome-game(feisty) package I think it happened while merging translations. (I edited some of them so I don't provide any link for this one)
These are all that I have seen.
Thanks and sorry for my poor English.

description: updated
Changed in rosetta:
status: Needs Info → Confirmed
Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

When people upload translation files, they don't always update the Last-Translator field, even when the header is copied from an unrelated translation. Then, when the file is imported, it is attributed to the wrong person.

We can make this less likely to happen by omitting the Last-Translator fields from exports. Then, if those same files are later re-imported without the field added, Launchpad will consider the uploader the author of any changes.

Revision history for this message
Jeroen T. Vermeulen (jtv) wrote :

In fact, it may be best to ignore the Last-Translator field on non-published uploads altogether. If we leave out the field on export, and a translator adds it back in while editing, the translator should be the same person as the uploader anyway.

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

I think the best way to fix this problem is by ignoring the last-translator field in the case of user uploaded files.

There is also a blueprint talking about this issue

Revision history for this message
Данило Шеган (danilo) wrote :

At the moment, it's impossible for non-reviewers to upload PO files. When a non-reviewer downloads a PO file, fills in some translations and passes it to a reviewer for review and upload, the only way they can tell Launchpad who the actual translator is is by last-translator field. We should probably just set submitter to the last-translator (like we do for published uploads), and on user uploads, set a reviewer to the uploader. However, that doesn't have much to do with this bug (filed as bug 695033).

We can't reconstruct what has led to the buggy behaviour in the first place 3 years later, and if we haven't fixed the data for Elxan in this time, we probably will never find time to do it. So, let's call the bug "Invalid" because we don't know what might be there to fix. Elxan, if you have a problem with that and want the data to be cleaned up, please do let us know through a question on

Changed in launchpad:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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