1C:Enterprise – the localization issues
Localization of business applications
Business applications (applied solutions) have their part of interface and business logic in the software product.
 |
Additional applied solution interface languages |
 Interface of multilingual applied solutions
Using
a single localized platform, one can create multilingual applied
solutions due to the possibility to use additional localized
interfaces. After installation of the following localized interface
items are available:
- system menu,
- dialogs,
- messages,
- help system.
Selection
of one or other localized interface implies no restrictions to
operations on an information base, therefore several users with
different interfaces can operate with one the same database at a time.
It's also possible to run several instances of 1C:Enterprise with
different interfaces on one PC. |
Languages
|
Creation of multilingual applied solution interface |
An applied solution can include several different interface languages.
Since
all strings are stored in a database in UNICODE format, a developer is
allowed to enter several variants of spelling in different languages
for one string.
Besides, if a multi-lingual applied
solution is developed, one can quickly switch from one language into
other. This is very useful when developing forms: one can preview a
form in English first, and then – in Russian.
Localization of interface texts
Localization
of interface texts is one of the most difficult tasks and it implies
looking for places to enter texts in other languages. Therefore,
localization of applied solutions' interface implies forming string
values in required languages, for them to be displayed in user
interface.
There is a mean for rapid applied solution
interface localization in 1C:Enterprise platform. It allows locating,
grouping and translating all occurrences of a string in an applied
solution configuration, replacing it or just adding a translation into
the configuration “in one click”.
First, one specifies an applied solutions to look at:
This
search can be performed for an applied solution entirely, across
external files, opened documents or through particular applied
solution's parts.
Result of this search is represented as a
list items, containing locations of the text found and its meaning in
different languages.
By
mouse click one can jump to the applied solution item containing the
string, to edit it; the string values can be also edited right in this
list, too.
As a result of defining required values for all
strings in each language, the applied solution is localized for using
with interface in these languages. If any string is not localized, it
shows nothing (empty string) at corresponding text fields.
Creation of a business application localized for a certain country
In
order for a business application to be applicable in a certain country
business conditions its business logic should be localized for these
conditions, too.
Providing 1C:Enterprise business
applications for other countries (such as Ukraine or Lithuania), 1C
Company's partners there have a good experience in creation of business
applications for local markets. At present, there are localized
versions of applied solutions for Ukraine, Kazakhstan, Byelorussia and
Baltic States, more are expected to come.
Some parts of
business logic are moved to localized applied solutions without
modifications, as there are no special requirements (like CRM, for
example), while other parts require adaptation and there are examples
of such adaptations.
'To localize' here doesn't means 'to
translate into other language'. In fact, it means 'to adapt for
operation in other locale's conditions'.
It's
not possible immediately to translate business logic in modules (i.e.
lines of the code implementing application business logic).
One
of the advantages of the product is its ability to be easily
customized, even by end-users. Therefore, we cannot allow incorrect
lines of the code (or comments) to be shown in the designer window.
Furthermore, there were attempts to translate business logic of some
business applications. Results were far from being good.
In
other words, adaptation includes not only translation of the interface,
but also re-working of the business logic. It's closer to development
process, than to 'translation'.
Some parts of an applied solution's business logic can be localized easier, while some parts are more difficult than others.
1C
usually provides a real business application as an example, on
development 'stage', for its partners. Our experience shows that
adaptation of a business application takes 50% of the time spent for
initial development of it (i.e. from scratch). For example, for an
applied solution like Trade Management it takes approximately 6
men/months work (usually 2 – 3 developers work for 3 - 2 months).
From
point of view of adaptation of a business application for a certain
economic conditions, generally, modules responsible for the
application's business logic are usually re-written from scratch, since
economical conditions and standards are different in different
countries.
In case with 1C:Enterprise business
applications, most business logic modules need only some modifications,
due to special means provided by the platform and 1C:Enterprise
Designer. For example, there is Payroll Calculation module that can be
adjusted by standard visual tools for almost any economic requirements.
So, a developer does not need to re-write the whole module, he just
needs to 'adjust' it. In cases like this, the core of the code
implementing the business logic is generated by the platform, according
to the interface language selected (i.e. English operators, with
relevant comments inserted, etc.).
Boxed business
applications from 1C company, including accounting business logic, are
developed in close cooperation with PricewaterhouseCoopers and provide
methodological basis for arranging accounting according with IAS
(International Accounting Standards). So the mentioned above is
applicable to many areas of creation of business logic of applied
solutions.
To the top
