Last modified: 2011-07-11 17:38:43 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 T30482, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 28482 - Introduce "group fuzzying" or "fuzzying classes"
Introduce "group fuzzying" or "fuzzying classes"
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
Translate (Other open bugs)
unspecified
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Niklas Laxström
https://translatewiki.net/wiki/Thread...
: i18n
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-10 20:30 UTC by Purodha Blissenbach
Modified: 2011-07-11 17:38 UTC (History)
2 users (show)

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


Attachments

Description Purodha Blissenbach 2011-04-10 20:30:24 UTC
Sometimes, messages belong to each other and when one is being altered, related ones should at least be checked. Also, it is usually desirable, to have either all of a group translated together, or none at all, so as to avoid mixed language sentence whith likely often broken grammar.

For example, there are several messages of the kind: "Foo $1 bar." where $1 is another message, or one of a choice of other messages, or a link, the anchor of which is another message, or an anchor of a choice of other messages, etc.

We also have: "Foo:" [__input__] "bar." where "Foo:" and "bar." are two separate messages. There are even quite more complex cases.

Since good wording, language style and grammatical constraints make distribution of parts and pieces different between languages, we need to reconsider and reevaluate all messages when one has been altered.

Of course, when message documentation is good, correct, and up to date, fuzzying one message (and reading the message documentation!) may make translators aware of related messages. This is often not the case, however. Specifically pieces related to elsewhere, or inserted elsewhere, are often hard or impossible to detect,

Thus it may be advisable to create message groups, and fuzzy all members of them, when one is fuzzied. A helpful effect of those groups would be that on message editing pages, these related message could automacically  all be shown. This would make it easy for translators to maintain an overwiev of the messages to be treated together.

In theory, a template call listing the related messages as parameters in the message documentation could do almost the same, except that automated group fuzzying cannot be had by a template reference alone.
Comment 1 Niklas Laxström 2011-07-11 11:41:24 UTC
Seems much work for little benefit. We should try to avoid lego messages as much as possible instead.
Comment 2 Siebrand Mazeland 2011-07-11 17:38:43 UTC
Will not fix per comment 1. Feel free to submit a patch that would implement this, but it will not be roadmapped.

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


Navigation
Links