Locale imports fuzzy strings

When doing translations, translators have the option of marking a string fuzzy - ie., that the string is probably not ready for being shown live just yet. This is used for strings that might need someone else to look at it, for strings that were machine translated and thus need a human to check it, or for a myriad of other reasons. The case in point being that they're only there for the eyes of other developers. However, in spite of this, Locale still imports without consideration for this, and thus people may end up with funny translations when they import .po files with fuzzy strings. Another thing that adds to the damage is that Drupal's default behaviour is to "add new, and not replace old" translations, meaning that those fuzzily translated strings will not be updated unless you actively import the selection with "override old" or update the strings manually on the site.

I haven't tested the behaviour in 7.x (yet), but I'm fairly sure it is the same.