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):
Publican 1.3

How reproducible:
100%

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)

Actual results:
Publican reports fuzzies present in the PO file.

Expected results:
Publican reports no fuzzies.

Additional info: