How Release Management Handles Existing Translated Content

When you create a new release, new product, or branch a release, Astoria can also clone existing translations of all of these assets into the same release in a target-language cabinet.

Cloned target-language translation objects are connected to the cloned source-language object via translation attributes.

Creating a New Release (or New Project) or Branching a Release

If the user specifies a snapshot label when issuing the command, Astoria checks to see if the same label exists on the baseline or selected release translated content. If it exists, the translated content is filtered using the snapshot label. If the label does not exist, the translated content is not cloned, because it has never been translated using that label.

When cloning translations, the state of the original translation is examined, to determine if it is up to date or not. The translation clone (in the release) is marked with this flag. This is used during the first translation of the clone. If the original translation was not up to date, the first translation of the clone will force translation of the full document, regardless of the Translation Package Contains option selected by the user on the Start Translation dialog.

In-Progress Translations

You can control whether translated content is cloned if a translation is currently in progress on seeded content or content in a release. In the application document, if the Allow in-progress translations when creating or branching a release check box is selected (the default value), the release will clone the most-recently translated content. If the check box is cleared, the task to create the release will fail if in-progress translations are encountered. In either case, Astoria will report the list of in-progress translations in the debug log. See Configuring the Translation Option for Release Management.

Note: If the task to create the release fails because of in-progress translations, options that were specified in the dialog to create the release are retained for the selected object. This allows the user to resubmit the task when the in-progress translations complete without having to re-enter the seed documents. The options in the dialog are cleared when the next task to create the release is invoked on the object.

Merging a Release

For each object that is merged, Astoria checks to see if it has any translations in the source release. Then it checks to see if the target release has the same translation. If the translation exists in the source release but not in the target release, the merge clones the translation to the target (and connects it via translation links). This applies to documents that are merged, and their references.

When merging a release, and the Merge tab is displayed, it does not display any translated documents or files, but displays only the source-language documents. However, when you issue the Start Merge command, Astoria clones translated documents to the target release, behind the scenes. This occurs only to translations of documents and files that are merged, and their references, and only if they don't already exist in the target release.