About

The Google text translation component is designed to translate any field from content to a specified target language represented by two-letter short form (ISO 3166-1 alpha-2 code). The translated text will be presented in the field enrichment.text_translation by default. It should be noted that we can use this component in both real-time and batch-processing manner.

Adding to your Dynamic Pipeline

This Component can be added to your Dynamic pipelines through the "Google Translate" component. It requires the following fields for configuration:

• Destination Path (Required): the metadata field for the output of the translation. By default, it is set to enrichment field. The field can be an existing field, or the component can create a new field for this functionality.
• Target language (Required): the target language for translation (in the form of ISO-3166-1 alpha-2 code)
• Target Text (Required): This is the input text field to be translated. Any metadata field can be chosen as an input based on data sources. The default field is content.body in this component.

The following example shows a dynamic pipeline configuration for the Google Translate component. In this example:

• enrichment is set as the destination path for the output of the translation and outputted asenrichment.text_translation
• content.body from the input document is set as the input “Text” for translation
• EN is set for input language
• FR is set for target language

Compatible Languages

The language coverage is continuously improved as this component uses Google Translate in the back end. Referring to https://cloud.google.com/translate/docs/languages the language coverage is: