Red Hat Bugzilla – Bug 1002772
Source string with translation changed plural will cause pull failure
Last modified: 2013-11-26 22:36:28 EST
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.63 Safari/537.31
A source string in plural form gets translated in a language with 2 plurals.
It then changed to singular form. The second translated string will still sit in database and when pulling, that second string will be attempted to be written out and cause an error in client (if download from UI it will silently fail and output a halfway file).
Steps to Reproduce:
1. Push a pot with one string in plural form
2. Pick a language that supports plural > 1
3. Translate the string and save
4. Change the pot and make the string singular
5. Pull from server
Caused by: java.lang.RuntimeException: plural forms not enabled for this text flow: resId=af6517b78862e0ad1739e91f2daa35ba
Ignore the unused plural translation and maybe give a warning
committed into client/master:
and into common/master:
I think the relaxed data check should be optional, only enabled when it is needed (eg server returns inconsistent data). Failing the pull process is an important sign that something is wrong.
added new option --continue-after-error or -c to enable client continue on this plural error.
maven client option will be -Dzanata.continueAfterError
VERIFIED with Zanata version 3.0.4-SNAPSHOT (20130923-0021)
Closing VERIFIED bugs for Zanata versions <= 3.1.