Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Introduction

When you run the XTM Connect – Oracle Content Management plugin, to submit content for translation in XTM Cloud, you can make other configuration settings for your XTM Cloud project. You do so in the Create Translation Job panel, on the left-hand side. Apart from selecting an XTM customer or an XTM Template, you can also select a source and target language combination.


General rule

It is important to know that the source and target languages listed and available in these dropdowns do not depend on which languages have been selected in a specific XTM project template, that has been set up in the XTM Cloud Settings of a particular Oracle Profile, in the connector administration panel, but on which languages have been selected in the Oracle CMS, in a relevant Localization Policy [Content → Localization Policies → select a relevant Localization Policy → Language).

IMPORTANT!

Take note of the Required label: this is always assigned to one language only. The default language is the language in which the source content is created, in Oracle.

XTM Connect – Locale takes whatever languages have been configured for a particular repository’s Localization Policy in the Oracle CMS, and completely ignores the languages selected in an XTM Cloud project template.

For example, if a selected Localization Policy has the following languages:

  • English (United Kingdom), Polish and German (Germany),

and a selected project template has:

  • Source: English (United States) and

  • Target: Polish, Spanish (Spain),

the only languages available in the XTM Connect – Oracle Content Management plugin will be English (United Kingdom), Polish and German (Germany). All of them can be selected either as source or target languages.

IMPORTANT!

Keep in mind that all the languages defined in the Localization Policy in the Oracle CMS must be mapped with their XTM Cloud counterparts.

Therefore, first and foremost, a language mapping needs to be performed in the Language mapping section of a particular Oracle Profile in the connector administration panel.

Otherwise, for example, if a particular target language is not mapped in the connector administration panel, when creating an Oracle translation job in the CMS and submitting the content for translation in XTM Cloud into the target language in question, you will notice that the translation job will be cancelled automatically, thus never making its way to XTM Cloud.

  • No labels