Rosetta keeps reporting a wrong status (color bar) for translations

[Frederik Dannemare]

Hi,

take <https://launchpad.ubuntu.com/distros/ubuntu/hoary/+sources/prebaseconfig/+pots/pkgconf-prebaseconfig> for instance

Hi,

take <https://launchpad.ubuntu.com/distros/ubuntu/hoary/+sources/prebaseconfig/+pots/pkgconf-prebaseconfig> for instance.

You'll see that Rosetta indicates 9 strings as Done and 2 strings as Todo, but there are in fact no untranslated or fuzzy strings left to be translated for this .po file (can be quickly verified with e.g. kbabel).

I see this problem regularly using Rosetta.
Can people confirm?

[Carlos Perelló Marín (carlos)]

All translations I checked in that situation (missing two translations) have two messages marked as "Someone should review this translation", that means that those translations are not being used, and that's why they appear as missing.

Please, add a comment if you think I'm missing anything.

Cheers.

[Christian Reis (kiko)]

Carlos, I do think he has a point that the UI makes it a bit confusing -- it indicates 2 Todo but they already have translations. We should haul mpt in and see what he thinks; it may be that we just discount strings pending review from the Todo statistic, or we add "needs-review" feedback in some other way.

[Carlos Perelló Marín (carlos)]

If a string has the "Needs review" flag that means it's not translated so the count is working as it should work.

[Christian Reis (kiko)]

You're not listening to what I'm saying. I agree that according to Rosetta internal state it's correct. I am saying that the UI presented is confusing to the end-user and this needs assessing.

[Mark Shuttleworth (sabdfl)]

Folks, there were plenty of bugs in the old storage system. I am landing a new storage system this week, and it will fix many of them and introduce new ones, so please wait till you see the big landing (it will be obvious, the look of the suggestions system has changed entirely) and then let's see which of these bugs remain. I'm confident the stats and storage and suggestions code is substantially improved by this landing.

[Christian Reis (kiko)]

I believe the UI issue still persists posterior to this landing, we should get some traction here.

[Johan Walles (walles)]

Comment copied from bug 21, requested by Kiko:

"
It's an UI bug. I was obviously confused by this, as was the reporter of bug 351.

IMO needs-review translations should be in their own category. They obviously aren't ready for use, and thus cannot be counted as translated. OTOH, a translation obviously exists (otherwise there wouldn't be anything to review), so counting them as untranslated is wrong as well.

By the same reasoning, showing needs-review entries when asking for untranslated entries seems wrong to me. If that's what you get, the category should be named something like "untranslated and needs-review items".
"

[Matthew Paul Thomas (mpt)]

Fuzzy strings should still be represented in the graph as being "translated", because if I'm not an editor, no matter how much I translate them their status isn't going to change -- they're still going to need review.

However, I think there should be different colors for "Translated and reviewed" and "Translated but unreviewed". That way editors can see what needs review, and non-editors can understand what's going on when editors talk about reviewing.