This appendix describes the language support in Oracle iSetup.
This appendix covers the following topics:
The same database character set is used for the Source, Central (Migrator), and Target instances.
Extract languages of the source instance must be a subset or same as the Target instance.
Extract languages of the source instance must contain "US" or the Target base language for INSERT processing. (Otherwise, a warning message will be shown).
The Oracle iSetup user interface is US English only.
BC4J APIs (.xml) : Language data can be extracted according to the AZ: Export Languages profile setting.
Generic Loader APIs (.ldt and .wft): For extracting, language data can be extracted only in the current session language until Release 12.2.5. Since 12.2.6, language data can be extracted according to the AZ: Export Languages profile setting.
For loading, language data cannot be loaded properly through Release 12.2.4. To work around the limitation, either of the following workarounds should be used before Release 12.2.5:
Use the Oracle iSetup Load function by updating one day forward in (LAST_UPDATE_DATE) field in the language LDT file, or
Use FNDLOAD with the upload_mode=NLS parameter from the command line.
Since Release 12.2.5, language data can be loaded using the upload_mode=NLS option of the Generic Loader API via the Oracle iSetup UI.
Oracle Application Framework Personalization APIs (.xml and .xlf): Only translations in the session language at the time of creating the personalization for the first time will be extracted, even though other language translations exist in the source instance.
Workflow Business Event System Objects Definitions API (.wfx): Language data can be extracted in the language specified as a Filter.
XML Publisher APIs (.xsl, .xlf, .rtf, and so on): All language data can be extracted at once.