Introduce support for plural forms. 1) Client support plural when push documents. 2) Translation editor supports of plural entry.
Current behaviour of python client: pushing source with plural forms: pushes msgid and ignores msgid_plural. pushing translations with plural forms: does not push translations for plural forms (probably because "msgstr" is not present, only "msgstr[0], msgstr[1], etc.). Translations for surrounding text flows are pushed correctly.
Please see: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes I've filled in the Technical Notes field with the information that I have to hand. Could you please verify / correct what's there, and provide what's missing?
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause In translation files, msg_plural entries provide multiple versions of a noun string. These entries allows software to present the correct singular or plural version of the noun to match a number in a message. Zanata did not support msg_plural entries (?). Consequence Zanata (???did not handle?????crashed when encountering???ignored???) files containing msg_plural entries Change What was done to implement the feature. Note: backported from upstream is not an explanation. Result What now happens when the actions or circumstances above occur. Note: this is not the same as the feature request was fulfilled.
Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,13 +1,11 @@ Cause -In translation files, msg_plural entries provide multiple versions of a noun string. These entries allows software to present the correct singular or plural version of the noun to match a number in a message. Zanata did not support msg_plural entries (?). +In translation files, msg_plural entries provide multiple versions of a noun string. These entries allows software to present the correct singular or plural version of the noun to match a number in a message. Zanata did not support msg_plural entries. Consequence -Zanata (???did not handle?????crashed when encountering???ignored???) files containing msg_plural entries +Zanata silently ignored msg_plural entries in POT/PO files Change -What was done to implement the feature. -Note: backported from upstream is not an explanation. +Plural support was added to Zanata's data model, database schema, REST API model, Maven/Python clients, webtrans editor UI and translation memory search feature. Result -What now happens when the actions or circumstances above occur. +Plurals are now accepted/returned via REST clients, accepted/displayed in the editor UI and in TM search results-Note: this is not the same as the feature request was fulfilled.
verified in Zanata version 1.6.0-alpha-3-SNAPSHOT (20120430-0019).
Actually, this should still be in MODIFIED state due to bug 814006.
oops,thanks for reminding!!
verified in Zanata version 1.6.0-beta-2-SNAPSHOT (20120523-0019).