Localizing a jolt applet – HP NonStop G-Series User Manual
Page 95
Since all Jolt classes belong to package bea.jolt, all Jolt class files are put in /classes/bea/jolt subdirectory (i.e., "jolt" is a subdirectory of
"bea" which is a subdirectory of "classes").
The HTML file for the Jolt applet should refer the codebase to the "classes" directory. For example:
/export/html/
|___ classes/
| |_____ bea/
| | |______ jolt/
| | |_____ JoltSessionAttributes.class
| | |_____ JoltRemoteServices.class
| | |_____ ...
| |_____ mycompany/
| |________ app.class
|___ ex1.html
|___ ex2.html
The webmaster may specify the "app" applet in ex1.html as:
<applet codebase="classes" code=mycompany.app.class width=400 height=200>
Localizing a Jolt Applet
If your Jolt application is intended for international use, you must address certain application localization issues. Localization
considerations apply to applications that execute from a client Web browser and applications that are designed to run outside a Web
browser environment. Localization tasks can be divided into two categories:
Adapting an application from its original language to a target language.
●
Translating strings from one language to another. This sometimes requires specifying a different alphabet or a character set from the
one used in the original language.
●
For localization, the Jolt Class Library package relies on the conventions of the Java language and the TUXEDO system. Jolt transfers
Java 16-bit Unicode characters to the JSH. The JSH provides a mechanism to convert Unicode to the local character set.
For information about the Java implementation for Unicode and character escapes, refer to your Java Development Kit (JDK)
documentation.