Question

2
Replies
1458
Views
OleksandrByelyenov Member since 2016 40 posts
Sberbank
Posted: August 11, 2017
Last activity: September 4, 2017
Closed
Solved

Different default locale settings produce different key names of same rules.

Hello. I use the "Localization wizard" tool to localize my application for several locales.
My application comprised of the CompanyRuleSet, CompanyRuleSetInt and SomeRuleSet.
There are also two locale rule sets: SomeRuleSet_uk(Ukrainian) and SomeRuleSet_ru(Russian).

I want to update existing and add new translations in Russian and Ukrainian. To do so, I utilize 'Localization Wizard'.

While I was downloading a Ukrainian localization, I noticed that (look at the 'Key' column, this 15 rules are same on all screenshots):
1) If I set 'en_US' as the default localization in my Operator and 'English' in 'Designer Studio -> UI -> Localization Tools -> Locale Settings' I get such TextToTranslate.xml file:

2) If I set 'uk' as the default localization in my Operator and 'Ukrainian' in 'Designer Studio -> UI -> Localization Tools -> Locale Settings' I get such TextToTranslate.xml file:

3) If I set 'ru' as the default localization in my Operator and 'Russian' in 'Designer Studio -> UI -> Localization Tools -> Locale Settings' I get such TextToTranslate.xml file:

I you could noticed that the key names differ between 'en_US' localization and 'uk'('ru') localizations. Rows from all tables with the same row number are translations for one rule entity.

Could someone explain to me why 'key' column of 'en_US' location differs from other 'key' columns?

Thank you.

***Updated by moderator: Lochan to add Categories***

Case Management User Interface
Moderation Team has archived post
Share this page LinkedIn