Creating the language objects using the publication

The web interface Translation option can be used to manually specify the language objects to create.

Before you begin

Objects must be in Released status. Language objects are not created for objects that are not released.

About this task

You can manally choose the language objects to create and base it on the publication's language requirements. To do this, it does not require that Requested Languages be specified for the map or any topics.

  • Make sure the publication was saved.

    In Publication Manager, select the publication then click Publication > Save.

    If Save is not available, it means the publication was already saved.

  • The procedure that follows may be combined with the next procedure for sending the language objects (out) for translation, but for clarity, they are described separately.
  • If the workflow is configured for translation and users were assigned to the status for translation, this procedure can also be used to forward the language objects to the user's translation inbox.
  • Language objects are only created for source language objects that are released.

Procedure

  1. In Content Manager web client, select the Repository view and navigate to the folder containing the publication.
  2. Select the publication in the upper pane of the window.
  3. Select the version in the lower pane of the window.
  4. Click Translation in the toolbar in the lower pane.
  5. In the Generate Target Languages pane of the translation management window, select Generate the following languages.
  6. Select the language(s) to be generated from the list.

    The list is comprised of languages that are specified for the publication in the metadata field, Requested Languages. By default, all of the requested languages specified for the publication are selected.

    In this scenario:
    • If you selected the User Guide publication, German and Dutch are available and selected.
    • If you selected the Administration Guide publication, only Dutch is available and selected.
  7. To automatically have the language objects appear in a translator's inbox (this is a translator that can access their inbox in the Content Manager web client), in the Generate Target Languages pane select a Translator.
    Note when language objects are created, they are put into the status of To be translated and automatically appear in the user's Translator inbox if:
    • The Inbox configuration specifies that the Translator is assigned to the To be translated status.
    • You have selected a user as the Translator for the topic(s).
  8. Click OK.
    The language versions are created for objects whose metadata Enable translation management is checked.

    In this scenario, if you selected the User Guide publication:

    • The Dutch and German language objects are created for the Map, and the Introduction and How to use the product topics.

      Since these topics are included in the publication and Dutch and German were selected in the Translation window for the publication, these language objects are created.

    • Since the Notice topic did not have Enable translation management checked, no language version is created.
    • The How to install and configure the product topic has a condition set that is excluded for this publication however, the language version(s) is created.

    If you selected the Administration Guide publication:

    • The Dutch language objects are created for the Map and the Introduction, How to use the product and How to install and configure the product topics.

      Since these topics are included in the publication and Dutch was selected in the Translation window for the publication, these language objects are created.

    • Since the topic, Notice, did not have Enable translation management checked, no language version is created.

Results

If you selected a Translator, the language objects appear in the user's Translator inbox.

Example

The order in which you release the publications affects the language object creation. If you follow this procedure for both publications, only the language objects that are not available are created. For instance:
Release firstRelease next
User Guide

Dutch and German language objects are created for the objects.

Administration Guide

Dutch language objects for the map and topics already exist so no other language objects are created.

Administration Guide

Dutch language objects are created for the map and all topics.

User Guide

German language objects that are needed for the Map, the Introduction, and How to use the product are created.

These language objects do not currently exist.

If language object is not created, the language report states:
No action required for GUID-<number> v
<n> because Translation Management is disabled, or there are no
released source objects or all target objects already exist.