Creating a Translation Job

Translation Jobs serve as packages for the content that are sent to a translation management system for translation. You can quickly create translation jobs with minimal steps.

Before you begin

To create a Translation Job you must have Translation Management rights and one other Content Manager right to a Publication (or Publications) that is a target for the translated content.

About this task

In Experience Space, you create translation jobs and send to translation all in one step. If you need to do these things in separate steps and potentially add more items to the same job before sending it, you should use Content Manager Explorer.

Procedure

  1. Go to a Publication that is configured either as a translation source or target, and in the Content area, do one of the following:
    • If initiating the translation job from a target Publication, select one or more translatable items and then select Translate. This type of translation job is sometimes called a "pull" translation because you are initiating the translation from a target Publication and you are pulling down the translation from the source Publication, which is higher up in the translation BluePrint.
    • If initiating the translation job from a source Publication, select one or more translatable items and then select Translate children. This type of translation job is sometimes called a "push" translation because you are initiating the translation request from the source Publication and are pushing the translations down to the target (one or more) Publications, which are lower down in the translation BluePrint.
  2. On the General tab, add the following basic details for the job:
    Translation job name
    Enter something that will describe the job and will distinguish it from other jobs in the translation queue.
    Date required
    Select the date by which the translation should be returned from the translation management system. If you do not specify a value, the translation management system sets the due date based on configuration settings in that system.
  3. Select the check boxes, as needed, to control which items get translated:
    • Include previously translated itemsSelect this option if you want to send previously translated items even if the source has not changed. By default, jobs do not include previously translated items unless the items have changed since they were last translated, making the translation out of date.
    • Translate components and keywords—Select this check box if the selection includes pages or organizational items and you want to translate all nested components and keywords.
    • If only this check box is selected, then only the nested content items will be sent for translation, and not pages or organizational items. Nested content items can include the following:
      • components that are contained on directly on pages
      • linked components and keywords contained in metadata fields of pages or organizational items
      • components nested in folders, bundles and virtual folders
    • Translate pages and organizational items—Select this check box to translate any selected pages any organizational items, including all nested container items regardless of how deep they are in the hierarchy.
    If both Translate components and keywords and Translate pages and organizational items are selected, then the translation job will include all levels of the organizational structure and all item types.
  4. In the list of publication targets, select one or more targets for the translation.
  5. On the Workflow tab, specify the Workflow to use. if the field is read-only, the Workflow has been configured for you.
  6. When you are finished with the translation job and ready to send it, select Send to translation.

Results

Experience Space sends the job to the translation queue, which you can view by selecting the (Translation jobs ) button on the Action menu. Note that the queue opens in the Classic user interface.