Truncated plural forms

[Dan Damian]

In ubuntu-doc/aboutubuntu, the Romanian plural forms expression seems to be truncated:
" (n == 1 ? 0: (((n %"
instead of
" (n == 1 ? 0 : (((n % 100 > 19) || ((n % 100 == 0) && (n != 0))) ? 2 : 1))"

In the exported .po file, the plural forms is splitted on two lines:
"Plural-Forms: nplurals=3; plural=(n == 1 ? 0: (((n %\n"
"100 > 19) || ((n % 100 == 0) && (n != 0))) ? 2: 1))\n"

...which results in a gettext error:
$ msgfmt -c ro.po
ro.po:7: invalid plural expression

See:
https://launchpad.net/distros/ubuntu/breezy/+sources/ubuntu-docs/+pots/aboutubuntu/ro/+translate

[Dan Damian (dand)]

Due to uploading a corrected po file, aboutubuntu was fixed.

The problem can be seen at the moment in faqguide:
https://launchpad.net/distros/ubuntu/breezy/+sources/ubuntu-docs/+pots/faqguide/ro/+translate

[Carlos Perelló Marín (carlos)]

This seems to be a bug caused by a bad .po upload.

We should try to fix/detect those problems on import time.

[Dafydd Harries (daf)]

It's possible that these bad uploads happen when users upload a file that was exported from Rosetta. Hence it might be an export problem rather than an import problem.

This bug seems a bit similar to #1786.

[Michael Vogt (mvo)]

We have seen this on edgy recently and it breaks update-manager. It would be really good if this could be fixed/worked around before the release.

[Michael Vogt (mvo)]

Bug #64132 is the ubuntu bugreport for this problem.

[Carlos Perelló Marín (carlos)]

I just fixed the import to export valid plural forms, this is not the right fix because this bug is produced by our import code that stores broken headers when it's too long (the case with the plural form expression). Anyway, exports should have the right value now. This only applies to language packs to have it fixed before Edgy release, it will apply too to manual export request from the web UI once it passes our QA process.

[Carlos Perelló Marín (carlos)]

The problem is fixed for Edgy, I'm going to ask for a review of this fix and move it into production to apply it with manual export requests.

Just as a note, this bug was introduced by bug #66958