pseudo translation tool creates uncompilable PO files

[Doug Fish]

Attempting to compile PO files generated by the pseudo translation tool results in the following error

CommandError: Execution of msgfmt failed: /opt/stack/horizon/openstack_dashboard/locale/tr_TR/LC_MESSAGES/django.po:10595: a format specification for argument 'req' doesn't exist in 'msgstr[0]'
msgfmt: found 1 fatal error

The problem message appears to be
#: openstack_dashboard/dashboards/project/instances/workflows/create_instance.py:213
#, python-format
msgid ""
"The requested instance cannot be launched as you only have %(avail)i of "
"your quota available. "
msgid_plural ""
"The requested %(req)i instances cannot be launched as you only have "
"%(avail)i of your quota available."
msgstr[0] ""
"[~0:The requested instance cannot be launched as you only have %(avail)i "
"of your quota available. ~您好яшçあ~~~~~~~~~~~~~~~~~~]"

It seems that that Babel really wants the translated string to have the substitution variables from msgid_plural, but the string is based on msgid

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/298379

[Doug Fish (drfish)]

This is broken in Mitaka right now. It would be nice to have to support debugging translation issues.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Rob Cresswell (<email address hidden>) on branch: master
Review: https://review.openstack.org/298379
Reason: Abandoning for now, hasn't been updated in 4 months. Feel free to restore and update if you get time to work on the patch. Thanks!

[Rob Cresswell (robcresswell-deactivatedaccount)]

Removed assignee and reset status due to inactivity

[Akihiro Motoki (amotoki)]

After investigating the detail, this is caused by the same reason as for bug 1630507.

In the format of PO, theoretically we accept different substitution for a singular and plural forms. However, GNU gettext implementation does not allow this. The error reported in this bug is caused by GNU gettext implementation details.

We already changes the string to have the same substitution for all plural cases including a singular form as a fix of bug 1630507, so I believe this bug no longer exists.