Creating
Texts for the Original Language
A central aspect of internationalization is the translatability of the texts that are displayed on the user interface. For this reason, an international application must not contain any language-specific text elements in its source code. You must define these texts in the Message Editor.
To make the translation process smoother, we recommend that you store any frequently used language-specific texts that you have defined in the Layout editor, such as labels or table headers, in Simple Types.
This tutorial is concerned with the following language-specific texts:
- Language-specific resources that you define at design time in the NetWeaver Developer Studio, such as the following
§ Labels for interface elements
§ Error messages
- Language-specific resources that you use dynamically in the source code
In Web Dynpro, the text elements that you create at design time are isolated and grouped automatically in *.xlf files.
Web Dynpro is not currently linked to an SAP translation system that can extract the automatically generated *.xlf files and import them into an existing R/3-based translation system. For this reason, the following procedure includes a workaround for the internationalization and translation of the application.
Process Flow
In the following tutorial, you add all texts to the application that you want to display on the user interface. In the next step, you internationalize these texts. The procedure Defining Language-Specific Application Properties describes how the language display of the QuickCarRental application is determined.
Structure of the tutorial:
- Create texts for the original language
a. Create the simple types
b. Create the context and action
c. Complete the layout of the application
d. Create the warning message and implement onActionRent()
e. Create dynamic texts and complete the application
- Translate text resources into other languages
- Define language-specific application properties
Next step: