Databases Reference
In-Depth Information
Figure 5-29.
Branch to return to calling page
Don't forget to seed the translated application so that the new navbar and page 111 will be in the
translated mapped application.
And, voilà! Using this example, the user will be able to switch languages from any pages within the
application.
Care should be taken when running an application in multiple languages, as it can be confusing.
Development is always done in the default primary language application, but the translated applications
must be re-created (published) even if the changes made are not text related or do not require
translation, in order for these to be included.
Testing an application in the default language first and publishing the translated applications before
testing other languages is an essential part of debugging and testing.
Translation logs
Developer Log
To monitor the translation activities, there are new reports available in APEX 4. The developer log is
located in Translate Application Globalization section of the Shared Components of the application.
At the bottom of the page in the Translation Utilities section, you will find a link to view the
developer log.
This report, shown in Figure 5-30, displays all actions that have been performed both on the
primary application as well as on the translated applications. It is also possible to see when seeds and
publishes have been done.
Since this is an interactive report, all filtering, sorting, and other reporting capabilities are available.
Note that this report lists all the translation-related activities on all the applications of the
workspace.
