Software localization is the process of adapting software to the national and cultural features of another country. This includes translation of the user interface, documentation and accompanying files of the software. The most important role here is played by combining the features of the software and the subtlest cultural features of the language (for example combinations of hotkeys etc.)
For example, in localization into Asian languages (such as Chinese), the Double Byte Character Set (DBCS) is used, which is connected with the way that symbols are stored in the Chinese language system. A complex situation also arises in using other languages such as Hebrew or Arabic, as they are written from right to left, unlike European languages. So in localizing a product in another language of this kind, preparation of software is first required. Most frequently, software is translated into English, but this is not an absolute standard. In a number of countries such as Spain and France, the sole use of an English version of software is prohibited by law.
Software localization is a complex and elaborate process.
Firstly the user interface of the product, operational reference elements, and additional documentation are divided into component elements. Then the entire text is translated, and finally the translated elements are assembled once more in a programming product, which will now work in a completely different language.
After the software localization process is completed, the software user interface must be tested. All types of menus, hotkeys, dialog windows, popup hints and many other things must be tested, so it becomes clear how precisely and correctly they are displayed on screen. Additionally, the function of these components is tested taking into account the features of the localization language.
We are prepared to carry out all stages of localization for your software.
We request that you provide:
- All files to the specialists at our company (this is required so specialists can be certain that they will be able to assemble the entire user interface again, and also to reconstruct documentation and re-compile files of operational reference);
- A printed set of documentation (primarily for the page layout, so that there is full correspondence between the pages of the original and localized version);
- The codepage, and also information about fonts used (not compulsory in localization into English).