Red Hat Bugzilla – Bug 1002774
Source string with translation changed plural will cause incomplete download file
Last modified: 2013-11-26 22:35:18 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. download from server
Downloaded file will stop at that string
When server generating the file it should ignore the unused plural translation and continue so that a complete po file gets written out. Meanwhile somehow inform the user this issue.
When this situation happens, editor will not display the extra leftover translation, but the underlying model will still store it and thus when launching translation history, it will always have an unsaved entry at the top. We need to make sure server never return inconsistent (plural in source and target) DTO like this.
Pull request: https://github.com/zanata/zanata-server/pull/150
The PR was merged. Can we put this ON_QA?
VERIFIED with Zanata version 3.1-SNAPSHOT (20130923-0037)
Closing VERIFIED bugs for Zanata versions <= 3.1.