Neoview JDBC Type 4 Driver Programmer's Reference (R2.2, R2.3, R2.4, R2.5)

HPT4Messages_xx.properties
where xx is the locale name. The locale name is defined by the current default locale or by the
language property.
The Type 4 driver is shipped with an error messages and status messages property file that
contains the textual representation of errors and status messages for the English locale. The file
is named HPT4Messages_en.properties.
Localized-Message String Format
A localized message file contains strings in the form:
message=message_text
For example:
driver_err_error_from_server_msg=An error was returned from the server.
Error: {0} Error detail: {1}
where the message is driver_err_error_from_server_msg. The message_text is: An
error was returned from the server. Error: {0} Error detail: {1}
The pattern {n} in message_text, where n equals 1, 2, 3, and so forth, is a placeholder that is
filled in at run time by the Type 4 driver. Any translation must include these placeholders.
Procedure to Create a Localized-Message File
1. Extract the HPT4Messeges_en.properties file, which is in the hpt4jdbc.jar file. For
example from a UNIX prompt, use the jar Java tool:
jar -x HPT4Messages_en.properties < hpt4jdbc.jar
2. Copy the file.
3. Edit the file and replace the English text with the text for your locale.
4. Save the file, giving it a file name that meets the naming requirements described under
“File-Name Format for the Localized-Messages File” (page 32).
5. Put the file in a directory anywhere in the class path for running the JDBC application.
The new messages file can be anywhere in the class path for running the user application.
At run time, if driver cannot read the messages property file, the driver uses the message portion
of the property as the text of the message. For a description of the message portion, see the
“Localized-Message String Format” (page 33).
Internationalization Support 33