Comment 1 for bug 576661

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

I expect this to be related to a suggestion which is masked by the current translation: i.e. one having fewer plural forms, but those that are present are identical to existing ones.

After confirming this happens on staging as well, and that "dismiss suggestions" works fine, I've looked at the data there:

 potmsgset | msgid | msgstr0 | msgstr1 | msgstr2 | date_created
-----------+-----------------------+----------+----------+----------+----------------------------
...
   8159727 | %i hour | 15639594 | 7843906 | 16656767 | 2007-09-23 14:24:44.753061
   8159727 | %i hour | 7843905 | 7843906 | | 2006-12-02 23:27:17.589556
   8159727 | %i hour | 15639594 | | | 2008-01-15 11:33:27.231931
   8159729 | hour | 836448 | 836449 | | 2006-12-02 23:27:17.589556
   8159729 | hour | 843601 | | | 2008-01-15 11:33:27.231931
   8159729 | hour | 843601 | 836449 | 7312344 | 2007-09-23 14:24:44.753061
   8159730 | minute | 827884 | 820638 | 7287070 | 2007-09-23 14:24:44.753061
   8159730 | minute | 827884 | 820638 | | 2006-12-02 23:27:17.589556
   8159730 | minute | 827884 | | | 2008-01-15 11:33:27.231931

In all the cases where this happens my above assumption is correct (there are even two extra suggestions for each message: one with only one plural form translation, and one with two plural form translations, whereas we need three). The bug is not very important, imo, simply because there's a workaround as well. The way we want +translate page to work, it will display all plural form translations together as a single suggestion, when this will get resolved.

Simple workaround for you is to just use "dismiss suggestions".