Set fuzzy after setting content

Otherwise the Po backend is too smart and drops fuzzy flag when the
string is not translated. So creating new fuzzy translation leads to
situation when in database we have the fuzzy flag but not in the
backend.

This inconsistency in database is causing wrong behaviour when togging
fuzzy flag as seen in issue #189.

weblate/trans/models.py

@@ -2130,13 +2130,13 @@ class Translation(models.Model):
 
             # Detect changes
             if unit.target != get_target(pounit) or unit.fuzzy != pounit.isfuzzy():
-                # Update fuzzy flag
-                pounit.markfuzzy(unit.fuzzy)
                 # Store translations
                 if unit.is_plural():
                     pounit.settarget(unit.get_target_plurals())
                 else:
                     pounit.settarget(unit.target)
+                # Update fuzzy flag
+                pounit.markfuzzy(unit.fuzzy)
                 # Optionally add unit to translation file
                 if add:
                     if isinstance(store, LISAfile):