Software Localization
Software Localisation is the process of transforming software's
locale, interface and support documentation to a target language
according to its cultural context and business practices. The look
and feel of the localized software is kept identical to the parent
software. Localisation is sometimes referred to as L10N (L 10 N)
for short. The "10" is for the ten letters between the "L" and the
"N."
Software Localization Services
At Applied Language we have localized software for some of the
world's biggest companies including Sony and Caterpillar. Your
localization project will be handled by the most experienced
project managers in the industry, working only with linguists with
the relevant specialist knowledge and technical ability for your
subject area.
Our Software Localization Process
Right from the outset we'll work with you all the way to ensure
you localized software is right for your market. The first stage of
this process is to identify the type and category of the
localization:
- Localization of a typical software e.g. desktop or web
based
- Localisation on a device or hardware
- Is the software Open source or proprietary
Localization projects are usually started after the mainstream
product is complete or almost complete. Firstly the software must
be internationalized, which is the process of removing cultural
assumptions from a project.
Preparation of the Source Material as a Localization Kit
At this stage the source materials (software, online help, and
other documentation) should be made available by the software
developers as a localization kit. If appropriate, previous
translations, glossaries and translation memories may be provided
to ensure consistency between the current project and any previous
translation work.
A localization kit is a set of tools, source files, test
scripts, and instructions that are used to create the localized
version of the product.
Analysis of the Source Material
Once we have received the localization kit, our engineers and
DTP experts will identify potential problems and select suitable
tools and methods. This analysis of the source material will
provide our project managers with the information they require to
produce detailed schedules and budgets for the project.
Preparation of Terminology
A multilingual project glossary, or terminology database of
terms from the user interface and support documentation is produced
at an early stage. This will identify terms which are not to be
localized (e.g. product names and brand names) and is agreed with
the software developers before localization begins.
Preparation of Translation Kit
Following the analysis of the source material, we will prepare a
translation kit for our translators.
We will also examine any existing translations to see whether
and how these might be reused to save translation resources.
Ideally, translation memories and terminology databases will have
been provided by the software developers as part of the
localization kit, together with previous translated versions of the
files. If not, translation memories may be created from previous
translations.
The translation kit will consist of technical and linguistic
information, together with the source material for translation.
Translation of the Software
The next stage is the translation of the user interface of the
software including dialog boxes, menus and any other text strings.
The translation of the interface always precedes the translation of
online help and other supporting documentation. This helps maintain
consistency and ensures that screen shots and other examples are
relevant.
Engineering the Localized Version
Once the resource files containing elements of the user
interface have been translated, appropriate shortcut keys can be
assigned and dialog boxes and menus can be resized as
necessary.
The software can then be compiled to create an executable
version.
Testing the Localized Version
Following compilation, the translations in the localized
software can be validated in context. We can also carry out
functionality testing at this stage if required. The localized
version of the software can then be sent to the software developers
for acceptance testing.
Translation of Online Help and Documentation
Screen shots are often used to illustrate online help and other
documentation. Localized screen shots are required for each target
language.
Once a compiled version of the localized software is available,
and the terminology used in the user interface has been frozen,
work can begin to create screen shots. Localization of online help
or other documentation cannot be completed without them.
Translation of the online help and other supporting
documentation, using the terminology established during the
translation of the software, is usually done at the same time as
the collection of screen shots.
Product QA and Project Delivery
Before final delivery, we perform a QA check on the localized
files. This might include: proof-reading all translations, delivery
test of the software, completion of bug and problem reports, and a
review of the initial agreement with the software developers to
ensure that all steps have been covered.
Once the QA test is complete, all files can be delivered to the
customer.