You can use Oracle TranslationHub to assist with translation for almost all multilingual Oracle Forms applications. Unless your application requires end users to toggle between languages at runtime, you can use Oracle TranslationHub and then generate separate binary files for each language.
The Oracle Forms Listener Servlet determines the language environment by reading the NLS language setting from the environment file that is configured for a requested Forms application. This servlet has a Browser language detection feature that allows an application to start in the preferred language that is registered with the Forms Listener Servlet. When a user needs to switch to a different translation, the user can stop the Forms application and change the preferred language that is configured in the Browser setting.
Using the Oracle TranslationHub approach, you develop your application in the following stages:
This is the simplest way to implement multiple language applications quickly. With this approach, you can use Oracle TranslationHub for maximum efficiency. If you have a stable application, this approach will work well for you.
For example, if you created an application in four languages and then needed to change the text of a field label, you would make the change in Developer, save the change in the definition file, use Oracle TranslationHub to translate the new field label, and then insert the new messages into the definition file and regenerate to create a binary file containing the new label.
If your applications must support multiple languages simultaneously, you must use the runtime language switching approach instead.