My SugarCE 5.5.1 has Russian language pack installed that works fine all over the Sugar. I create new custom module in Module Builder. That Sugar instance will be used only by Russian-speaking people.

Firstly I thought it's more convenient to create module with native English labels, strings, etc. and then translate some into Russian when needed.

But I found out that if I set Label in Module Builder → package_name → module_name page into English (“Visits” in my case) it became “hardcoded” and could NOT be overridden after that neither in Label editor in Module Builder (only fields related labels for custom module are accessible through Studio) nor manually in files located in custom/modulebuilder/packages/<package_name>/modules/<module_name>/language/. Yes, I can edit those file manually but after module deployment they turn back to English labels. Moreover it affects on many labels such as 'LBL_LIST_FORM_TITLE', 'LBL_MODULE_NAME', 'LBL_MODULE_TITLE', 'LBL_HOMEPAGE_TITLE', 'LNK_NEW_RECORD', 'LNK_LIST' and so on.

Considering using my Sugar mostly in Russia I use a workaround for that: I switched custom module label into Russian. Now while logging into Russian interface everything looks fine: my Russian-only-speaking users are happy with existing labels and so on. But what if I would like to add in the future users from Czech or Hungary for example?

So, the question is: What is the proper way to set multilingual labels for custom module? Could it be the problem of exact langpack but not Sugar issue or my misunderstanding, of course?

Thank you!