Solution for application and software localization

Software localization is a complex process

Software localization is not only about the translation; it is a more complex process of adjusting to the language as well as the legal, cultural and technical requirements of a given region. We will tell you how to get ready for the localization, what to focus on and how to best prepare your software in order to make the translation itself procedurally simple and as automated as possible.

The times have long gone when software strings had to be copied and pasted into spreadsheets for translation.
To put it more simply, we are able to handle any structured source file, whether xml, json, resx, php, or csv.

Ideally, localization consists of two phases – the first phase is internationalization followed by localization itself. Internationalization is defined as the way of writing the code so that the code can work in different language mutations without having to make any changes to the code. It includes standardized design and development procedures ensuring a simple and easy‑going localization if implemented properly. In practice, this may even mean a differing user interface design.

For example, one should be aware that the text in the new target language will have a different length, the use of plurals will be different (every language has a different number of plurals), or can be read from left to right or from right to left. This requires adjustments not only to the content itself, but also to the user interface.

Best practices include:

• using resource files – every planned language has its own file. This is a more elegant localization method ensuring that the translations themselves do not affect the master code of your application or software;
• using Unique Identifiers (IDs) for each string – this ensures clarity and better structuring, also when using Translation Memories (TMs), in particular where continual translations are required;
• using comments right in the code to ensure an understandable context for the translator;
• correct use of local languages – Canadian French is different from French used in France;
• proper encoding (character set) setup – UTF‑8 is a minimum requirement for correct target language display; UTF‑16 is more appropriate for Asian languages;
• creating the so‑called style guide, a set of special rules for the translation, such as:
  • corporate terms and/or style
  • number, date, currency and unit formatting
  • language style – formal, informal, technical, conversational, etc.
  • use of acronyms and abbreviations
  • and so on.