on 02-08-2009 9:59 AM
Plz explain me Internationalization concept in webdynpro java applications//////////////////
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi niru,
The goal of Internationalization is to provide the technical foundation for enabling programs to support multiple scripts and languages without redesign or modification. Once a user has selected a logon language, all programs must transparently alter their run-time behavior to meet the expectations of the user. Internationalization furthers generic programming, because hard-encoded search strings, error messages, etc. may work in one language, but not in another.
Internationalization interacts with every face of the system: logon language, language input, menu texts, sorting, character conversion, printing, data transfer - simply put, it is the technical underpinning of global business software
Within Web Dynpro, the language-specific text elements are divided into three types:
Texts that are defined when you create simple data types such as Simple types
Language-Specific Resources that you specify declaratively at design time These include texts that you assign to the UI element properties or define when you create actions, methods, or simple data types.
Messages
Language-dependent resources of the message type text that are used in dynamic programming You can create these text elements also at design time using the message editor.
Furthermore, the SAP NetWeaver Developer Studio supports the following:
· The creation of texts and messages that are added to the properties file using the Message Editor
· The modification of S2X files already created using the S2X Document Editor
· The conversion of properties files into S2X files and vice versa The S2X Editor also allows you to add context information to S2X files that is essential for the correct translation of the text elements.
These Web Dynpro tools simplify the process of the creation of international applications and hence the translation process of the language-specific resources.
You can therefore develop applications that suit different languages without having to recompile an application for each individual language when a new language is to be supported.
The Internationalization Service of the Web Dynpro Runtime Services supports this PropertyResourceBundle concept and allows easy access to the classes java.util.ResourceBundle and java.text.format. With the class com.sap.tc.webdynpro.services.sal.localization.api.WDResourceHandler, you can read the language-specific text elements using the following source code:
// Load the resource bundle u201CMyResourceBundle.propertiesu201D located
// in the package u201Ccom.sap.testu201D for locale set in the resource handler.
// Therefore, the resource handler also needs the classloader that has
// the package u201Ccom.sap.testu201D in its scope
resourceHandler.loadResourceBundle(u201Ccom.sap.test.MyResourceBundleu201D, this.getClass() );
// get the message of the u201Cpress saveu201D button
String saveMessage = resourceHandler.getString( u201Cpress_saveu201D );
For further help you can refer following link:
http://help.sap.com/saphelp_nw04s/helpdata/en/2d/e7381138a8d2458f1f4fac32614f71/content.htm
Regards,
Anu
Hi Niru,
Internationalization or i18N is built into Webdynpro for Java application. The UI's generated using Webdynpro will have all the text, labels, heading etc... in an .xlf file.
Once the application is developed then the translation team will create .xlf files for different languages. At runtime the webdynpro framework will read the text from the translated .xlf file based on the users logon languange.
As a developer you need not worry much about Internationalization. Most of the parts are automatically taken care by the framework. If the UI elements are created at design time then the labels and what ever text that is visible from the UI will automatically get inserted in to the .xlf file. If the UI's are generated at runtime then the lables and texts should be added to the message pool and retrieved to be used in the UI from there. All message pool texts will also get translated.
You can go through additional documents in SDN. Links are there in other posts.
Regards,
Sanyev
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
You can find all the concepts related to internationalization in webdynpro java at the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/e7381138a8d2458f1f4fac32614f71/frameset.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/0f/868589c3b5cf44b45d527d70631f6d/frameset.htm
(Deals with how to internationalise the webdynpro application)
Regards.
Rajat
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
Internationalization is to adapt existing applications so that they can be used in several languages without the need for changes to the source code.
1) It is the process for separating language-specific parts of a program from the other parts.
2) classes used for this purpose
*java.util.ResourceBundle
*java.text.format
3) The Java class PropertyResourceBundle (derived from the ResourceBundle )
separates language-specific parts of a program and stores them in properties files.
4) Processing the properties files
files are converted into the S2X format using S2X Document Editor
The properties files can be passed to the translation backend as S2X files.
After the translation , the translation backend returns a localized S2X file for each S2X source file and
target language to the NWDS.
text elements created in webdynpro are stored in.xlf files. these can be translated to any language.
use th following link,
Regards
Jayapriya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A simple search on SDN will show you desired results -
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
94 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.