Internationalizing Environments
A translated custom string can be used in the Development environment, Test environment, and Production environment.
You can use the "XLIFF" file across the two environments using the export and import functions.
Workflow
First, export the custom string (translated) using the Export option out of one environment. Then, using the Import option, import the exported custom string (translated) into the other environment.
Notes:
- The transfer of translated custom strings can be done one language at a time.
- If a custom string does not exist in the destination environment, then that custom string cannot be used; however, the custom string will be available in the Internationalization Log.
- If you add a source string to your source type in the Development/Test environment, but this source string does not exist in the Production environment, upon exporting the XLIFF file to the Production environment, the source string will carry over.
See Also
Translating Custom Strings (Internationalization)
Internationalization Node Properties
Displaying Custom Strings and System Strings
Internationalization and CSV Files
Internationalization and Web Services
Internationalization (Email Notifications)
Internationalization (Support for Tools)
Internationalization (BI Publisher/Oracle Analytics Publisher Custom Reports)
Internationalization (Dashboards)
Internationalization (Help Files)
Internationalization (Spell Check)
Internationalization (Date and Time Zone Formats)
Internationalization (Audit Log)
Last Published Tuesday, December 12, 2023