Accept invalid nplurals if no plurals translated

Bug #187647 reported by Jeroen T. Vermeulen
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

The fix for bug 181707 turns invalid nplurals specifications in a PO header into parse errors.

If there are a few common mistakes, we could quietly accept bad plural-form specifications in translations that don't contain any plurals at all.

Changed in rosetta:
importance: Undecided → Low
Changed in rosetta:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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