Differentiate fuzzy and suggestions

Totally a n00b question, but is "fuzzy" in this context, uh, where the untranslated string has been "tweaked" from a previous version with a translation, but not rewritten from the ground up? So now the translations for the previous versions "apply with fuzz" but may need similar tweaking?

keith.smith: Fuzzy is techno-speak for things like this:

You had a translation for "Create stori." but then it was fixed to be "Create story", and the gettext system (not l10n_server, but your external tools) realize this source string is very similar to the string before, so it uses your previous translation there, but marks it fuzzy, so you know it is not an exact match. Then you can go in and check whether the change in the original string changes any meaning or was just a grammar/spelling fix, which should not affect the translation.

So "fuzzy" is an automated suggestion.

meba: I think paying more attention helps more :) Maybe a flag can be used there for "automated suggestions" which we can also use later, when this capability will be built into l10n_server, if ever.

Related issue: #194141: Implement msgmerge type fuzzy matching.

I think this is a duplicate of #251327: Flag translation as 'golden' vs 'need work'. As soon as we have a "needs work" flag, we can put that on a suggestion.

I don't see how that issue will help us with separating automated (fuzzy) suggestions from people-submitted ones. And that distinction is useful because fuzzy translations are different from people-submitted ones in some important ways:

• They will have different types of errors, which the reviewer needs to be alert for. (For instance, a fuzzy suggestion may miss a small but crucial word like "not" or "un-", which completely reverses the meaning.)
• Usually, people-submitted suggestions should have higher priority than automated (fuzzy) ones, because it may be demotivating for someone to wait for a long time for their suggestions to be reviewed.
• If a reviewer sees some types of error repeated in a lot of suggestions, it may be useful to write about it on the overview page, to teach people to avoid those types of error. But if it's caused by automated suggestions, that's pointless.

I'm changing the priority to minor. I'd kind of want to keep it at normal, but there are others of normal priority that are more important in my opinion, so I'm donwgrading this one.

@zirvap: when importing a .po file, we don't know whether the fuzzy marker means "the translator wanted to tell us this is not yet final" or "the tool merged this in automatically and might be more broken then usual". Most desktop tools allow you to mark strings as fuzzy yourself, when you are not sure about it. At least the Hungarian team used this feature extensively before. So when we import a .po file, we can't tell what fuzzy exactly meant.

Aha, I didn't know that -- I thought fuzzy was used only for automated translations. In that case, I agree this is a duplicate.

When we have the "needs work" flag, we might want to put it on all strings marked fuzzy when importing .po-files, but that feature request can wait until we have the flag :-)