Changed translations remarked as "packaged" are not reflected in graphs

Bug #126963 reported by Timo Jyrinki
12
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Данило Шеган

Bug Description

Sorry for complicated subject.

1. Thanks for the "changed in Launchpad" filter, and especially the ability to set such strings back to the upstream version, marked with "Packaged", and so that they'll then continue getting upstream changes instead of being fixed to the changed Launchpad versions. This was a very needed change.

2. The problem: I marked all but one translation in gnome-desktop-2.0 / gutsy as Packaged (also one untranslated). They're now not anymore shown when searching with "changed in Launchpad", but the graph in https://translations.launchpad.net/ubuntu/gutsy/+lang/fi is not updated to reflect the fact that almost all strings are now upstream - the bar should be mostly green.

I think it's the definition of the green bar in the Rosetta that might be the problem, since it's "Translation unchanged since last synchronized". It should be checked whether a change was done to reuse the upstream translation, and mark it as "unchanged from synchronization" as well.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

On the other hand, do not overfix this, since strings changed in this way have to be included in the language pack updates :)

Changed in rosetta:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Данило Шеган (danilo) wrote :

Should be fixed with RF 5199 and RF 5203.

Changed in rosetta:
assignee: nobody → danilo
milestone: none → 1.1.11
status: Confirmed → Fix Committed
Changed in rosetta:
status: Fix Committed → Fix Released
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

This is not fixed, the gnome-desktop-2.0 example still applies. Another example is Kaffeine: https://translations.launchpad.net/ubuntu/gutsy/+lang/fi?start=300
There are no "Changed in Launchpad" strings in kaffeine anymore since all has been reverted to Packaged, but graph shows a lot of blue and "Changed" column claims 165.

Changed in rosetta:
status: Fix Released → Confirmed
Changed in rosetta:
milestone: 1.1.11 → 1.1.12
Revision history for this message
Данило Шеган (danilo) wrote :

Timo, thanks for catching this. I've did some further digging up after others have reported similar bugs, and this should finally be fixed when I land a fix for #173527. If that happens (in 1.1.12, which is due in a couple of weeks), I'll mark this one as fixed or a duplicate of that bug (just because I added more debugging info there, not because this bug report is any worse that that one :).

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

Looking at https://translations.staging.launchpad.net/ubuntu/gutsy/+lang/fi/+index (staging, our demo server), it seems this has been fixed with bug 173527 fix: eg. obvious example is debian-installer which lists 36 untranslated and 129 changed-in-LP entries on production (yet untranslated and needs-review filters show no entries), and staging lists 0 untranslated and 93 changed-in-LP (the difference in changed-in-LP count is that we are now not considering upstream fuzzy translations as "translated").

Timo, can you please confirm if there are no more problems on staging (except perhaps bug #128324, but that's a different matter)?

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Hi! Yes, the issue I described in this bug seems to be fixed in staging! The numbers in changed in Launchpad column match the real values, and for those "reverted" translations they are correctly now shown as "translation unchanged" (ie. green).

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

Wonderful, Timo, thanks for checking this. This should become live next week.

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

So, marking as fixed in RF 5349.

Changed in rosetta:
status: Confirmed → Fix Committed
Changed in rosetta:
status: Fix Committed → Fix Released
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.