Last modified: 2013-06-03 18:22:31 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 T49177, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 47177 - Confirming a fuzzied translation should be logged
Confirming a fuzzied translation should be logged
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
master
All All
: Lowest normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-12 18:14 UTC by Nemo
Modified: 2013-06-03 18:22 UTC (History)
5 users (show)

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


Attachments

Description Nemo 2013-04-12 18:14:35 UTC
With the new system (without !!FUZZY!!), it's impossible to tell that a user has confirmed a fuzzied translation, because there's no edit to the translation and there's no log. This produces mysterious summaryless diffs to translation page when all goes well and nothing at all when something goes wrong or it's not page translation (with all sorts of problems for attribution and understandable histories), see bug 46716 comment 4.

A log entry should be added.
Comment 1 Siebrand Mazeland 2013-06-03 18:22:31 UTC
This also causes https://gerrit.wikimedia.org/r/#/c/66574/1/AccountAudit.i18n.php where doing a full export of an extension finally removed the # fuzzy comment, even though the actual unfuzzy had possibly taken place a long time ago.

Two expected behaviors based on this issue:
I. Marking unfuzzy should make the message group qualify for export if it's a file based message group.
II. Marking unfuzzy should be visible in the page history of the translation.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links