Handle different plural form formulae on import

Bug #70470 reported by Данило Шеган
24
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Данило Шеган

Bug Description

If we're importing a PO file with an incompatible plural form formula, we should set the fuzzy flag on all the imported plural messages, or evaluate and match the plural forms (i.e. if they are just reordered, import them, if there's a different number of them, mark them as fuzzy).

Practical example: Serbian Nautilus import has 4 plural forms; one is lost during import. Slovenian uses two different plural form formulae which have two forms interchanged.

description: updated
Changed in rosetta:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Carlos Perelló Marín (carlos) wrote :

This bug is more important, it's causing problems with Slovenian translations. See bug 121555 for that concrete case.

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

So, lets plan this for 1.1.12.

Changed in rosetta:
milestone: none → 1.1.12
description: updated
Changed in rosetta:
assignee: nobody → danilo
Changed in rosetta:
status: Confirmed → In Progress
Revision history for this message
Данило Шеган (danilo) wrote :

Fixed in RF 5356. Will be testing tomorrow, and then also changing Slovenian plural expression, and later fix existing contents in our database (that can't be perfect, though, but majority of the cases should be fixed) along with the roll-out.

Changed in rosetta:
status: In Progress → 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

Related questions

Remote bug watches

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