Сергей, сама по себе мультиязычность обеспечивается механизмом схем с хранением данных на разных языках в отдельных записях специальных служебных таблиц (Sys...Lcz).

А по поводу того, как это интегрировать с актуализацией, всё зависит от конкретной системы, откуда берутся данные. Обычно у каждой страны есть свой стандарт, своя база, как правило, только на государственном языке, но есть и универсальные для нескольких стран. В маркете есть примеры таких коннекторов: Address database (для России, Украины, Казахстана), FIAS address hints (только РФ).

Спасибо) Не совсем то, что нам нужно. Когда сделаем - отпишусь.

We have the same situation with multi-language. Many our clients also ask for such solution, but after short discussion they understand, that 1 language is much better for them.

Besides, there are just 10-20 new words in their life, so there is no problem to learn them.

Technically it would be interesting solution, but no so many companies really need this, IMHO.
As I know, this can be done in Terrasoft

Thank You, Владимир,
We are trying to convince customers they need only one language as well, but sometimes it is not enough arguments for that :). It is difficult for a user to start to use a new program, but if a program is in language, he does not know, he may reject of using it, especially when using many modules.

Владимир, what are Your general arguments when You talk to customer according this question? Maybe we will try them as well.

Aurimas Lacitis

If 2 offices (or even people in the office) have different interface language, this will make difficulties in communications between them.
One tells 'Accounts', another - "Контрагенты" and it will give more troubles.

Really, for most new users 'Pipeline' has no more sense, then "Воронка продаж" :)
So, in some months it will be like a slang of the company.

You are right, some concepts of the system really becomes a slang of the company. :) Multilanguage in this case can become a trouble.
Thank You.