Professional Services

Page tree
Skip to end of metadata
  • Created on 2018-07-03, last edited by Cass Weber on 2019-06-26
Go to start of metadata

The CTSX Microsoft module performs translation via.

Installation

Maven is the easiest way to install the module. Add the following dependency to your bundle:

<dependency>
    <groupId>info.magnolia.translation</groupId>
    <artifactId>magnolia-content-translation-support-ext-microsoft</artifactId>
    <version>${CTSExtendedVersion}</version>
</dependency>

In order to start the Microsoft translation process, please make sure that the core and apps modules which mentioned in Content Translation Extended have already been installed.

Configuration

Configuration of the Google service provider is handled in the module config. This provider can be configured with the following properties.

autoTranslationAllowed

optional, default is false

When true the content review process (workflow) is bypassed.

class

required

Definition class for the translator to be used.

See info.magnolia.translation.ext.provider.microsoft.definition.MicrosoftProviderDefinition

clientId

required

Identifies the client application with Google.

clientToken

required

Client secret for the client ID.

configName

required

Identifies the configuration within Magnolia.

defaultFlag

optional

The default configuration used by the system in the case of multiple translation services being used.

implementationClass

required

Implementation class for interfacing with Google.

See info.magnolia.translation.ext.provider.microsoft.translator.MicrosoftTranslator

Usage

After registration and starting, The Content Translation Support Extended (CTSX) module will bind the Microsoft translator to Configuration field.

You can test the connection to the translator api before using.

How it works

The same steps with CTSX Google Translator but you will choose Microsoft.com instead of Google.com in the Configuration. 

Known Issues

Text Too Large

In case of submitting many contents (such as the whole /travel page includes dependences), an error will be thrown as below. This is known issue as number of submitted segments is over microsoft's threshold. 

ERROR info.magnolia.translation.ext.provider.microsoft.translator.MicrosoftTranslator: Error occurred while translating
java.lang.RuntimeException: TEXT_TOO_LARGE - Microsoft Translator (Translate) can handle up to 10, 240 bytes per request

5 Comments

  1. Christopher Zimmermann

    Which Magnolia versions are supported?

    1. Trung Luu

      Hi Christopher Zimmermann, It works for Magnolia 5.6 and 5.7. This info mentioned in the parent page Content Translation Extended, Should we add it here as well? 

    2. Richard Gange

      We can add versions to this page. Do you think it's really that confusing though? This is a child page of CTSX. I feel like that would imply submodule or subconfiguration. What I would rather do is change the description to say that explicitly. Then we do not need to manage the versions on these pages. 

  2. Hugo Venancio

    Hi Richard,

    What exact Microsoft Translator service is this CTSX using ? Is it the Microsoft Azure Translator Text API (https://azure.microsoft.com/en-us/services/cognitive-services/translator-text-api/)?

    If not, which one exactly ?

    Tx

    Hugo

    1. Richard Gange

      Hello Hugo-

      Exactly. The MicrosoftTranslator class is responsible for doing that. You can see it uses MicrosoftTranslatorAPI class. 

      HTH