Apex: XLIFF Translator
We like the Apex solution to make multi-lingual applications; especially the idea of “one master-source, but multiple instances of the applications (one per language)”.
This approach reminds me of “Oracle Translation Builder”, the solution to translate the good-old Oracle Forms …
We explained already in another blog (entry of December 13th) how you have to deploy such a multilingual application. With the current version, there is one special point you should be aware of: when importing a translated application, use the same APPLICATION_ID. Hopefully Oracle will do something about this in future releases (see also this entry on the forum).
Following screenshot gives the main steps for translating an application, especially steps 1 till 4 are always necessary.
Don’t let you misguide by the hyperlink for step 3: the translation of the text is not (yet) part of Oracle Application Express. The real translation work from a source to target language happens outside apex.
You have to edit the XLIFF-translation file by yourself; either by using a simple text-editor, MS-Word or an XML Editor (XML Spy or JDeveloper).
We didn’t like those editors, because there is a lot of repetitive work.
Therefore we decided to build are own tool to help us in doing this work, a tool developed in Apex … of course !
What should be possible with this tool:
3.1. upload an xliff-file and analyze/seed the content to internal tables
3.2. make a translation for every source element
3.3. regenerate the xliff file with the entered translations.
The idea is also to provide a kind of dictionary ; so it will be possible to automate a part of the translation process for words that are repeatedly used.
A new tool is born: “The XLIFF Translator for Oracle”.
In the near future, we will put this application on-line.
Here you can see already a preview of the utility…
(will be continued …)