The Google Translate component is designed to translate any field from content to a specified target language represented by a two-letter ISO 3166-1 alpha-2 code. The translated text will be presented in the field enrichment.text_translation by default. This component supports both real-time and batch-processing workflows.

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 JSON path for the translation output. By default, this is set to enrichment.text_translation. The field can be an existing field, or the component can create a new field.
• Target Language (Required): The target language for translation (in ISO 3166-1 alpha-2 code format, e.g., en, fr, es).
• Source Path (Required): The JSON path of the text field to be translated. Any metadata field can be chosen as input. The default field is content.body.
• Source Language (Optional): The language to translate from. Leave blank to auto-detect the source language automatically.
• Filter Conditions (Optional): Filter conditions to apply before translating a document. See JSON Conditions page for more information.

Dynamic Pipeline Example Configuration

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

• enrichment.text_translation is set as the destination path for the translation output
• content.body from the input document is set as the Source Path for translation
• en is set for source language (auto-detect if left blank)
• 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 includes: