Fuzzy strings lost after import
Bug #312476 reported by
Dirk Stöcker
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
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.
Revision history for this message
| Данило Шеган (danilo) wrote | #1 |
| Changed in rosetta: | |
| status: | New → Won't Fix |
Revision history for this message
| SirVer (sirver) wrote | #2 |
To post a comment you must log in.
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:/
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.