Internationalization (i18n) issues
An internationalization issue caused by the way the software is implemented.
Language testers can report internationalization issues.
Thereby, they enter the required fields as specified in the selected quality profile.
It determines the available categories for the i18n errors.
Internationalization issues are usually corrected by developers.
Most i18n issues are caused by assumptions that developers make.
How to avoid i18n issues?
Simple: as a developer do not make any assumptions.
If something works in your language, then it may not work other languages.
i18n error categories
We will provide an overview of all i18n issues + examples + tips how developers can resolve them here.
Examples of i18n issues are:
Hardcoded strings in the user interface cannot be translated.
- How to fix: developers need to externalize the string in a resource file and assign a string id.
Setting a string to uppercase or lowercase programmatically can also be considered as an example of hardcoding.
Concatenation of strings can come in various forms, for example:
- two strings are concatenated to form a new string.
How to fix: developers need to define a separate string with a unique string id.
- a colon is 'glued' to a string. However in some languages (like French), there must be a space before a colon: "name:" will be translated as "nom :".
How to fix: developers must include the colon as part of the string, or use a different design that does not require colons.
Concatenation of punctuations can change the meaning of a string. Here is an interesting example for the Japanese translation for "search":
The second option was the original string.
- SEARCH: To create this string, the developers implemented a method to display the string in UPPERCASE. However, this requires a completely different translation in Japanese.
- Search...: To create this string, the developers concatenated "..."after Search. However, in Japanese this changes the context of the string, which requires a completely different translation.
Translation and non-translation issues
Language testers review translations in context and report translation and non-translation issues they spot. Rigi has the following QA profiles: Default DQF MQM Each profile (except Default) has additional error categories that fit within a strict ...
A translation issue is simply a wrong translation. Language testers report translation issues. They enter the fields as specified in the selected quality profile. A quality profile is derived from a quality framework (e.g. DQF or MQM). It specifies ...
LAT main window
Each LAT task has a main window with a main menu and action buttons. Intended audience Language Testers SAP users Please refer to the SAP Help Portal. The steps to execute a preview-based review tasks are described in this article. It will bring you ...
Execute preview-based LAT
This section applies to a preview-based LAT, where you need to review translations for pre-defined set of previews. If you need to review the live application, please visit the instructions for a live LAT. This guide describes the steps how to review ...
Execute live LAT
This section only applies when you need to review translations for the live application. If you need to review a set of previews, please visit the instructions for a preview-based LAT. This guide describes the steps how to review translations on a ...