Fuzzy strings lost after import

Bug #312476 reported by Dirk Stöcker on 2008-12-30
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Undecided
Unassigned

Bug Description

The "fuzzy" strings of .po upload seems to be loast after import. That destroys useful work.

E.G. When I fix a typo in the original software the strings will get fuzzy, but the translation is still the same. When the fuzzy strings is not imported, then the work is lost.

This is an intentional design decision made due to nature of fuzzy messages in PO files. Supporting them requires too much effort, introduces many problems in our code and usage, and brings little value. "Fuzzy" messages are very rough "similarity matching" translations (i.e. it counts characters and uses that as a metric), and we'll instead be introducing a better similarity matching which actually takes words into consideration: https://blueprints.launchpad.net/rosetta/+spec/rosetta-fuzzy-merge

We might want to import them as "suggestions", but in most cases (when it's not only a small typo), they are usually pretty bad which is why we avoided doing that so far.

Changed in rosetta:
status: New → Won't Fix
SirVer (sirver) wrote :

The widelands project has a lot of lore which changes frequently. Fuzzy strings spare a lot of work for us... when will we get them - one way or another?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions

Related blueprints