CTSX Translations.com
Edition |
Incubator (services) |
||
Issues |
|||
Git |
|||
Latest |
3.4.9
|
The CTSX Translations.com module performs translations using the Translations.com APIs. Translations are handled asynchronously.
Installing with Maven
Maven is the easiest way to install the module. Add the following to your bundle:
| In order to start the Translations.com translation process, please make sure that the core and apps modules in the Content Translation Extended have already been installed. |
<dependency>
<groupId>info.magnolia.translation</groupId>
<artifactId>magnolia-content-translation-support-ext-translations-com</artifactId>
<version>3.4.9</version>
</dependency><dependency>
<groupId>com.translations.globallink</groupId>
<artifactId>globallink-connect-api</artifactId>
<version>4.18.4</version>
</dependency>Configuration
Configuration of the Translations.com service provider is handled in the module config. This provider can be configured with the following properties.
Please use JCR for module configuration. When using yaml, translation provider definitions are not loaded and the connector is unusable.
|
| Property | Description |
|---|---|
|
optional Translation agent name. |
|
optional , default is When true the content review process (workflow) is bypassed. |
|
required Definition class for the translator to be used. See |
|
required Identifies the client application with Translations.com. |
|
required Identifies the configuration within Magnolia. |
|
required Number of days system continue to listen to GlobalLink PD (calculated from last modified date of a submission). |
|
optional The default configuration used by the system in the case of multiple translation services being used. |
|
required Enable or disable the configuration using this flag. |
|
required Depends on the version of GlobalLink PD you use. For version 5 use "Magnolia". For version 4 use "xliff". |
|
required Implementation class for interfacing with TranslationsCom. See |
|
required Name of the project setup with Translation.com. |
|
optional Prefix added to submitted documents. Example: |
Sample configuration
'config':
'jcr:primaryType': 'mgnl:content'
'translationsComConfig':
'agentName': 'xxx'
'autoTranslationAllowed': 'false'
'class': 'info.magnolia.translation.ext.provider.translationscom.definition.TranslationsComProviderDefinition'
'clientId': 'xxx'
'clientPassword': 'xxx'
'configName': 'translations.com'
'daysListen': '1'
'defaultFlag': 'false'
'enabledFlag': 'true'
'fileFormat': 'xxx'
'implementationClass': 'info.magnolia.translation.ext.provider.translationscom.translator.TranslationsComTranslator'
'projectCode': 'xxx'
'submissionPrefix': 'xxx'
'url': 'xxx'Usage
After registration and starting, The Content Translation Support Extended (CTSX) module will bind the Translations.com translator to Configuration field.
| You can test the connection to the translator api before using. |
How it works
Use the same steps outlined with CTSX Google Translator but you will choose Translations.com instead of Google.com in the Configuration.
| In additional, at the Step 2 after submitting the batch you must to wait for the response from Translations.com’s GlobalLink Project Director app (PD). |
| You would be able to see the Pulse notification for translation result as soon as the submission has been delivered on PD. |
