Last modified: 2014-04-15 06:22:15 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T40681, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 38681 - Highlight non-matching parts of suggestions from translation memory
Highlight non-matching parts of suggestions from translation memory
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
master
All All
: Low enhancement (vote)
: ---
Assigned To: Pau Giner
https://translatewiki.net/wiki/Thread...
: design
: 38581 (view as bug list)
Depends on:
Blocks: 46484
  Show dependency tree / graph
 
Reported: 2012-07-25 17:47 UTC by Nemo
Modified: 2014-04-15 06:22 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Nemo 2012-07-25 17:47:33 UTC 
The suggestions from translation memories already tell you how much the two (source text) strings match, but then it's left to the translator to look for the differences, to start with.

As a translator, I want to see what are the changed/removed/added words so that I can quickly change the proposed translation to match my original.

Drawbacks:
1) visual clutter,
2) [IMHO] wrongly suggesting that those are the only parts requiring check, while the whole suggestion might be wrong in the new context.
Comment 1 Nemo 2012-07-28 17:23:31 UTC 
*** Bug 38581 has been marked as a duplicate of this bug. ***
Comment 2 Siebrand Mazeland 2013-01-01 12:31:54 UTC 
Pau, can you assess if there is any benefit or this feature request from a usability perspective? I'm skeptical at first, aside from if there are algorithms that can identify which parts cause the Levenshtein distance.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links