Based on the project, the translation workflow process will notify respective translation vendor(s)

Once translation is completed by translation vendor(s), user will be notified on the translated zip package(s)

User can upload the translated zip package(s) into SDL Tridion via the Import command on the Cloudwords ribbon toolbar

3. Translatable Fields

The GUI extension enables users to exclude specific fields for translation. By default, all text or embedded fields will be included for translation unless either of the following options is checked:

Exclude from Translation

Values will be Selected from a List

3.1. Exclude from Translation

The Exclude from translation checkbox option is now available in schema for content and metadata fields. For an embedded schema, the same rule applies. Nested embedded schemas are also taken into account. As specified in the Source tab, the tcm:ExtensionXml element is included where Cloudwords:exclude will be set to true for any excluded field.

3.2. Values will be Selected from a List

If the option of Values will be Selected from a List is checked for a text field, it will not be excluded from translation, regardless whether Exclude from translation is checked. This is due to scenarios where schemas already contained hardcoded list of values (e.g. Yes, No) or keyword values.

3.3. Translation of Keywords

For translation of keyword values used by components, users will need to send the respective category or keywords to be translated and localized in SDL Tridion before sending the components using the translated keywords.

4. User Interface

4.1. Export

4.1.1. Export Command

Includes linked component(s) of component based on link level configuration.

Includes child folder(s) and component(s)

Include all keyword(s) under category

Structure Group. Include child structure group(s) and page(s)

Include all embedded component(s) and linked component(s) based on link level configuration.

User can also choose to use the Export option on selected item(s) from the context menu

4.1.2. Export Package

Note that the exported package contains no folders but the XML files of exported items. Name of XML file uses the title of SDL Tridion item. For items with the same title, the TCM id (e.g. -40-52175-1024) will be appended to the file name of the subsequent item: -

4.1.3. Content and Metadata Fields

All content fields of the components are included in the export XML file. If metadata is defined on the SDL Tridion item, it will be included as part of the export XML file.

4.1.1. Managing Keyword Fields

SDL Tridion BluePrinting requires keywords to be localized in respective publications to allow the localized content using the referenced translated keywords to be saved. As such, it is recommended for editors to export respective categories and have the respective keywords translated before importing items referencing the translated keywords.

4.2. Import

4.2.1. Import Command

User can select the Import command from the ribbon toolbar without the need to be at a specific location context (e.g. publication, folder, structure group). The following popup window will appear: -

Language – Select the target language for the import file. Contact your system administrator or Cloudwords team if there is a missing language.