You must complete several tasks to prepare your library for translating content by using Translations and a single library.
- Create the Locale records and Service Provider Profiles in Translations.
- Ensure that the Translations user has the correct permissions to folders and objects in the library.
- Ensure that the Translations user has the correct permissions for release states in the library.
Folder, object, and release state permissions enable variant objects to be created in the library folders when the translation jobs are created. They also enable variant objects to be updated when the completed translation jobs are imported. If the Translations user does not have sufficient permissions, the translation jobs will not be created or imported successfully.
- Create variants of templates in Author for publishing to any languages requiring localized text strings or paths to locale-specific files.
Note: This job is completed after the first translation job to a locale has been created. When the first translation job for the locale is created, the variant criteria is automatically updated with the locale value. Once this locale value has been created, you can then use it create your variant templates.
When your variant template is ready for use, be sure to mark it as localized.
- Store the translated values used by your variables in the Locale records in Translations. When you publish, your locale content uses the translated values.
- Be sure you're using the latest version of your zip tool. If you are translating to double-byte languages such as Japanese or Chinese, be sure that your tool supports these languages.