One of the many good things about Oracle APEX is the builtin capability to create multilingual Applications. It gives you a set of tools to translate your Application and provide it in multiple languages at the same time.
One of the Key Components of this Translation Mechanism is the creation of an XLIFF File. This File contains all text strings of your Application (that is all your UI Strings, not your Data) and from which to which language it should be translated.
Sometimes you want a user to enter an address which later on can be used to display it on a map. Now you want to make sure, that the user sees what the the map will look like and where his entered address is shown on the map.
This comes in very handy for those users who always seems to forget to enter the whole address.
When that little box on that web form you need to fill in is simply too small to show all your information at once, you wish to make the box bigger.
A couple of days ago i got an emergency call from someone who attended my presentation at DOAG 2010 about APEX Translations.
Apparently they deleted (by accident) their APEX Translations (which reside in WWV_FLOW_TRANSLATABLE_TEXT$) and have neither a DB-Backup of this table nor a Backup of the XLIFF Files. Continue reading →