Use
A language resource contains all of the language-specific elements of an Internet service and enables you to make your application multilingual. Compared with hard-coded text in the HTML template, it also makes it easier for you to understand and maintain your source code.
For each language-specific text in your Web interface, you insert a placeholder into the HTML template (similarly to text elements in an ABAP program). The actual texts are maintained through the theme parameters with the same name. At runtime, the ITS recognizes the placeholders for each template and replaces them with texts in the appropriate language.
Prerequisites
You must already have created the HTML templates for your Internet service.
Procedure
Adding Placeholders to an HTML Template
Use the following syntax:
Suppose we defined three placeholders
Entering Language-Specific Texts
The system displays the theme parameters.
Those place-holders for all the templates used by the service that have already been maintained are added to the parameter list.
Result
The theme parameters are now part of the service. They are translation-relevant parts of the R/3 Repository object, and as such will enter the translation workflow when you release the service.
When you start the service in the original language, the texts appear in the relevant language.
If there is no translation of the language-specific texts in the logon language, no text is displayed when the user executes the service.