Launchpad itself

How to locate translations with problems?

Asked by Susanna Björverud

When pressing Save & Continue after translating a set of strings, I have at 2 occasions been greeted with a red box stating that there were errors in my translations and that I should correct them before proceeding.

But I can find no way to locate these erroneous translations :( How do I go about to locate translations with errors within a package?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Adi Roiban
Solved:
Last query:
Last reply:
Revision history for this message
Best Adi Roiban (adiroiban) said : 		#1

Hi Susanna,

The reason while a translation is considered to contain errors is listed for each translation string part.

For example if I go at the following link:
https://translations.edge.launchpad.net/ubuntu/intrepid/+source/gnome-power-manager/+pots/gnome-power-manager/ro/244/+translate

And for the "New translation" I will enter "%d" and try to save and continue in the top of the page I will see a message saying

"There is an error in the translation you provided. Please correct it before continuing."

and somewhere in the page near the translation zone I see

"Error in Translation: format specifications in 'msgid' and 'msgstr' for argument 1 are not the same ".

Erroneous translations are not saved in the package and you can see them only in the page loaded after an errorneous translation was summited.

Hope this will help.
If not, can you write the steps to reproduce this error?

Many thanks!

Revision history for this message
Susanna Björverud (sanna) said : 		#2

Hello,

I do understand why the errors occur, however it seems to me that when this red box occurs I have already been moved on to the next page, and I can no longer see the message where the error was found - that is I can not find which string contained the error. However I will pay more attention next time it occurs.

At least it is comforting to know that the error has not been saved, I was afraid that my mistakes would corrupt the translation. That I will need to retranslate the other strings on the same page (if indeed that is the case) is a small price to pay to keep the translation usable.

Thank you for your prompt reply, if the problem is indeed in the ui (and not in the chair ...) I will reopen the problem, but so far I will consider it solved.

Revision history for this message
Susanna Björverud (sanna) said : 		#3

Thanks Adi Roiban, that solved my question.

Revision history for this message
Adi Roiban (adiroiban) said : 		#4

When translating in batch of 10 strings and no filters are applied and you click „Save and continue” you will see the same set of 10 strings but the erroneous strings should be highleded by the red marked.

If for example the „show untranslated” filter is applied and you entered an error in an newly translated string and the click „Save and continue” the erroneous string should be displayed in the top of the list and then page will contain the remaining untranslated strings.

I don't know if this is a problem in the UI, but if you managed to reproduce the problem please open a new bug in the "bugs" section describing how to reproduce the error.

I wish you a Happy new year!

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

Some late-arriving notes:

The UI tries to show you the same batch of messages again in this case. But all it can really do is try to remember how far along you were in the displayed list of messages. For example, if you were at page #3, a successful submission moves you on to page #4 but an error keeps you at page #3 so as to display the messages. But if a new template is imported while you're translating, there might be very different messages there. Or if you're using a view filter, such as "Untranslated" to show only untranslated messages: if somebody else approves or imports translations for the first page of untranslated messages, the messages you'll see on page #3 now will be the ones that would have been on page #4 before.

In fact we used to have a problem where your own translations could have this effect! So if you were reviewing a translation using the Untranslated view filter, approving full translations for page #1 would take you to the translations that were previously page #3. It's always possible that there is some nasty interaction with the error display.

So if you see this happen again, please file a bug with such information as what translations you were editing and when; what view filter you're using; and whether you're on the first batch, or the last, or somewhere in the middle.