Red Hat Bugzilla – Bug 546130
publican lang_stats counts fuzzy unmatched strings as fuzzy
Last modified: 2010-11-23 23:16:27 EST
Created attachment 377377 [details]
PO file for Publican Document Conventions in Assamese
Description of problem:
PO files sometimes contain unmatched strings at the end of the file. These are commented out with a #~ at the start of each line.
At some point before being relegated to "unmatched" and commented out, strings might have been marked "fuzzy". When they are commented out as unmatched, they retain their fuzzy tags.
Running "publican lang_stats" over a PO file that has fuzzies amongst its unmatched strings results in Publican counting these fuzzy strings in its report.
This is unexpected behaviour because other translation tools do not count fuzzies if they are unmatched (msgfmt, gtranslator, lokalize).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run publican lang_stats over a PO file that has unmatched fuzzy strings in it, but no other fuzzy strings (example attached)
Publican reports fuzzies present in the PO file.
Publican reports no fuzzies.
Added check for obsolete in lang_stats code.
publican-1.4-1.fc12 has been submitted as an update for Fedora 12.
publican-1.4-1.fc11 has been submitted as an update for Fedora 11.
publican-1.4-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.
publican-1.4-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.