Translate documents from the Web Editor id21BKF0Z0YZF

In the Repository panel, open the DITA map file in map view.

Click the Manage tab. The Translation panel displays the available language groups.

As a user, you can view the language groups configured to your folder profile. The language groups display the language folders along with their language codes. For example, the language group named G1 contains Italian (it), German (de), French (fr), and English (en) language folders.

{width="300"}

Select the language groups or languages in which you want to translate your documents.

You can select any language group as a target for the translation. If you Select all, the selected files are translated into all the available languages within the existing language groups.

The language folder option appears grayed out and shows a warning sign:

• If the target folder for a language is missing.
• If the target language is the same as the source.

If you choose a particular language, it appears as selected under all language groups you have selected. So, when you translate to any language, it’s translated in one go for all the language groups. For example, if German is present in both G1 and G2 language groups, it’s selected for both.

From the Other languages, you can choose any language for which you have created the target folder but isn’t a part of any language groups.

You can also select one the following options to translate your project:

None Select this option to translate the default versions of the files. This option is selected by default.

Use Baseline: You can select a baseline to translate your project. Click Use Baseline and choose a baseline created on the map. All files that are a part of the selected Baseline are shown in the Translation page. Once your content is translated, you can export the translated Baseline. For more details about exporting the translated Baseline, see Export translated Baseline.

Use Latest Version as on: Choose to filter the version of topics based on their creation date and time. When you select a date and time only the latest version of the files created on or before the selected date and time are shown.

Click Apply. A list with details of topics and associated assets is shown.

Select the topics that you want to send for translation. You can also use the topic filtering options for the following columns:

• Title: Title of the source file. Hover over the title of the source file to view the title of the target or translated file.
• File Name: Name of the source file
• File Type: Type of the source file. The available options are Map, Topic, and Image.
• Reference Type: Direct or Indirect references
• Version: Version number of the source file
• Version Label: Label for the selected version of the source file
• Target Version: Version number of the target file
• Document State: State of the source file. The available options are Draft, In-Review, and Reviewed.
• Target Language: The language to which you want to translate the source file
• Translation Status: The available options are: Out of Sync, Missing Copy, In Progress, and In Sync.
• Target Label: Label for the selected version of the target file

Click Send for Translation on the top right corner.

{width="800"}

From the dropdown, select Create a New Translation Project.

{width="350"}

Besides a new translation project, you also can select from the following options:

• You can choose to Create a structure only for the translation project.

• You can choose to Create a new XLIFF translation project to convert the XML content into the XML Localization Interchange File Format (XLIFF). XLIFF is an open XML-based format that is used to standardize the data transfer between various tools used in the content translation process. AEM Guides supports XLIFF version 1.2.
  In an XLIFF project, the content is exported to the industry standard XLIFF format, which can be provided to Translation vendors. XLIFF format empowers potential reuse of segments that you have already translated during the translation phase.
  After the XLIFF content is translated, it can be imported into AEM Guides, creating a translated version of the original DITA project.

  note note
  NOTE
  XLIFF export only works with human translation configuration.

• You can select Create a new multi-lingual translation project which will include translation jobs for all languages that you have selected for translation. For example, if you have selected French, German, and Spanish it will create a project which contains translation jobs for all three languages.

• If you already have a translation project, you can add topics to that project. Select Add to Existing Translation Project option from the Project list and choose a project from the Existing Translation Project list. You can sort these projects by most recent, ascending, or descending order.

  note note
  NOTE
  If your existing project is a scoping project, it has ‘(Scoping)’ appended in its name.

• If you need to create the scope for a project to be translated, you can select Create a new scoping translation project. This will not send the copies for translation and the original translation status of the files is maintained. There is no impact on the destination language copy of the referred topics which are sent for scoping.

In the Project Title field, enter a title for the project.

Click Create to create a new translation project.

A new translation project is created with the selected version of the topics. At this time, a pop-up message is displayed confirming that the translation project has been created. Once all target language copies are available in the translation project, you get a notification in the Inbox. Once the target language copies are available in the translation project, you can then go ahead and start the translation job. For details see, Start the translation job.

Select the out of sync assets for which you want to change the status.

Select the Mark In Sync button ( ) on top. The Mark In Sync dialog appears.

{width="550"}

Click Force Sync. It sets the status to In sync for the selected Out of sync assets.