Info: in case translation text contains both text and variables we want to use parameterized translations instead of joining multiple words manually which might result in incorrect sentence when language isn't English.

Steps to reproduce:

1. Open Alters > Actions >Trigger actions
2. Create new condition: 
3. 
4. Observe generated text "Value of tag aa does not contain bb"
5. Save record.
6. Switch language to Japanese and navigate to same section

 

Result:

Japanese is one of the languages where word order is different than most of the languages. Text will be "タグの値 aa 含まない bb" (as translation is done in parts and text is just joined together) which based on auto translate to english means "Tag value does not contain aa or bb". Based on Google translate text for such case should be "タグ aa の値に bb が含まれていません"

Expected:
Translation generation for operations and conditions should be updated to include full sentence., that is, instead of translating each part, we should have translation string like: "Value of tag %1$s %2$s $3%s" where:

• %1$s is tag  name
• %2$s is operator
• %3$s is tag value

I am not sure about linguistic constrains in other languages therefore maybe operator cannot be place as parameter too. 

 

Occurrences in Zabbix where translation texts are concatenated:

1. Alters > Actions: Condition definition.
2. Data collection > Event correlation > Conditions.
3. Discovery rule > Override > Operations. Text uses template with pre-defined text order: "condition operator value"
4. In development: from ZBXNEXT-10353 generating condition and operation descriptions. Issue was noticed here.