feature request: search for fuzzy messages

[GoogleCodeExporter]

It seems, that mo files created with compilemessages doesn't use fuzzy
messages. It would be great to be able to filter to that, and optionally, a
checkbox should be used to explicitly state fuzzyness.

Original issue reported on code.google.com by pihentagy on 15 Oct 2008 at 4:22

[GoogleCodeExporter]

I wonder if this is something worth implementing, i.e. I'm not even certain why 
one
would want to force fuzzy messages in the first place. Feel free to reopen or 
submit
a patch, though.

Original comment by mbonetti on 8 Jan 2009 at 3:05

• Changed state: WontFix

[GoogleCodeExporter]

Suppose you have written _(u'asdf') somewhere.

Then, you translate it with rosetta to 'qwer'

Then, for some reason, the code changed to:
_(u'asdfe')

If you change it to a similar string, then you will still get the translation 
'qwer',
which may be incorrect. Fuzzy messages are not used (AFAIK), so you have just 
lost
your work.

If the fuzzy translations are used, then you may still considering this case:
If I change the original text, I definitely have to look at 'outdated' 
translations,
because they are not up to date.

Original comment by pihentagy on 8 Jan 2009 at 5:59

[GoogleCodeExporter]

+1 on this also for me. I'm having this issue with django-rosseta actually. Even
more, if you extract and compile initially with poedit, and some strings get 
marked
as fuzzy you'll have no way to know it in rosseta.

Original comment by antoni.aloy@gmail.com on 11 May 2009 at 11:19

[GoogleCodeExporter]

By popular demand, this is implemented as of r66. Feedback is welcome.

Original comment by mbonetti on 26 May 2009 at 11:27

• Changed state: Fixed

[GoogleCodeExporter]

Works very nice. I added some new translation strings to my code, that looked a 
lot
like already translated ones. Result in Rosetta: prefilled translations with 
fuzzy
checkbox on. Only had to make a few corrections and uncheck fuzzy.

Maybe this would make it even better: unchecking can be done with JavaScript 
when you
change the input of a fuzzy translation (on 'change' event of the input field
triggers unchecking of the fuzzy checkbox).

Original comment by wou...@dynora.nl on 26 May 2009 at 3:23

[GoogleCodeExporter]

@Wouter I'd rather not do that as users might want to flag a hand-written 
translation
as fuzzy, if they are unsure and want it checked by QA (actual feedback I had
concerning this issue)

Original comment by mbonetti on 26 May 2009 at 3:43