Page MenuHomePhabricator

Introduce "group fuzzying" or "fuzzying classes"
Closed, DeclinedPublic

Description

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.


Version: unspecified
Severity: enhancement
URL: https://translatewiki.net/wiki/Thread:Support/Toolserver:Tsintuition-bl-promo/en

Details

Reference
bz28482

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 11:37 PM
bzimport set Reference to bz28482.

Seems much work for little benefit. We should try to avoid lego messages as much as possible instead.

Will not fix per comment 1. Feel free to submit a patch that would implement this, but it will not be roadmapped.