Translator credits on user uploads

Bug #695033 reported by Данило Шеган
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Launchpad itself

Bug Description

When we import user uploaded PO files today, we want to treat them as if they were done inside Launchpad. However, there are a few problems with that:
 1. We attribute translations to the Last-Translator as listed in the PO file
 2. People forget to update Last-Translator field before re-uploading
 3. If upload is done by a reviewer on behalf of a translator, we lose information on one of them

What we should do:
 1. drop Last-Translator on PO file export (so translators have to fill it in or we'll use the uploader, but it will be explicit on our side) when only a single PO file is requested (we want last-translator to be present on bzr exports, tarball exports and such)
 2. use uploader as the "reviewer" for any new translations, but only for user uploads; we should keep the behavior for maintainer uploads the same as it is today (iow, set only the submitter to last-translator)

This is a follow-up bug from bug 118527.

tags: added: translation-credits
Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 695033] [NEW] Translator credits on user uploads

As an alternative, consider signing the last-translator; that will let
you detect updated translations that have not had the translator
updated. A simple few-character hash (e.g. the first 16 bits of
md5(translation).update(translator)) would be plenty sensitive, and
easy for tools that want to support last-translator externally.

That way the export process will be identical, so that folk using
external tools on bzr branchs and then uploading the results via a
reviewer will still be served better than they are today.

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

It is not uncommon for the last-translator to be the same. We wouldn't want to lose that (and if we did, we wouldn't even have to worry about hashes or anything: we'd have both a DB value and an actual value from a PO file at hand, which we could easily compare).

Also, external tools already support Last-Translator (any good PO file editor will set it automatically, but people sometimes update PO files in bare text editors or "bad" PO editors).

Changed in launchpad:
importance: Medium → High
Changed in launchpad:
importance: High → Low
Revision history for this message
Nicolas Delvaux (malizor) wrote :


I understand that this bug may be difficult to solve but, meanwhile, is it possible to at least add a warning on the PO upload page to inform that the translation will be attributed in accordance to the last-translator field?

Because, currently, this is not documented anywhere. And one can only find this bug report when it's too late.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

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