Globalization
Globalization is the process of creating or modifying an application so that it can use the correct GLS locale to support different languages, territories, and code sets without changing or recompiling the code.
This process makes HCL OneDB™ database applications easily adaptable to any culture and language. For a database application, you perform globalization on the application that accesses a database, not on the database. The data in a database that the application accesses should already be in a language that the user can understand.
To globalize a database application, design the application so
that the tasks in the following table do not make any assumptions
about the language, territory, and code set that the application uses
at run time.
| Application Task | Description |
|---|---|
| User interfaces | Includes any text that is visible to users, including menus, buttons, prompts, help text, status messages, error messages, and graphics |
| Character processing | Includes the following processing tasks:
|
| Data formatting | Includes any culture-specific formats for numeric, monetary, date, and time values |
| Documentation | Includes any explanatory material such as printed manuals, online documentation, and readme files |
| Debugging via tracing (HCL OneDB, DB API) | The DataBlade® API provides the application or DataBlade developer the capability of using globalized trace messages. It uses in-line code working with system catalog tables: systracemsgs and systraceclasses. For more information, see the HCL OneDB DataBlade API Programmer's Guide. |
A globalized application dynamically obtains language-specific information for these application tasks. Therefore, one executable file for the application can support multiple languages.