Description of problem:
The fuzzies entries from an imported PO file appear as translated in the zanata workspace. I used the python client
Version-Release number of selected component (if applicable): 1.3
How reproducible: Always
Steps to Reproduce:
1. Go to a project with existing PO files. The project should have some Fuzzy entries.
2. Run $zanata publish push --import-po
3. Go to project in the zanata instance
The entry that appear as fuzzy in the local PO file, now appear as translated in the zanata workspace!
It should appear as Fuzzy in the zanata workspace. The fuzzy should be kept.
I think this bug is same to "Bug 728821 - Fuzzy strings are not shown on web interface after uploading", sorry, it's my fault, when i parsing the po file to json, i didn't consider the fuzzy entry (processing "#, fuzzy" flag in each entry), i will add this processing and fix it in soon.
*** Bug 728821 has been marked as a duplicate of this bug. ***
I have modified source code of python client to fix this issue, changes in
The fuzzy messages will be imported and displayed as Fuzzy in the zanata workspace. I have test and verify this on my locale machine.
There is one make me confused. I compare the status between zanata instance on
my locale machine with 'publican lang_stats', The number is different. I am not
sure which one is correct, or both is correct, just because using different
VERIFIED with zanata-python-client-1.3.1-1.el5
and Zanata version 1.4.2-SNAPSHOT (20111014-1722