Translate a multilingual model
Add a language to an existing NLU model by translating it. Use one of several translation options to add a secondary model in a supported language.
Avant de commencer
- Activate the Localization Framework (com.glide.localization_framework.installer) plugin. See Localization Framework.
- In your target application scope, create a primary language model, or use an existing primary model.
- Multilingualism is available for Virtual Agent and AI Search models.
- Role required: nlu_admin or admin.
Pourquoi et quand exécuter cette tâche
Translating a model creates a secondary model of the language you choose, in the same application scope as the primary model.
The secondary model contains the same content as the primary. However, the intents of the secondary model are disabled and must be reviewed prior to publishing the secondary model.
To translate a primary model and create a secondary model, you must choose a translation mode. The modes appear in the user interface as individual cards that you use in Step 4 of this procedure. Activated cards appear surrounded by a thin green border. Only activated cards can be selected as your translation mode. For the Use AI and Use a third party modes, selecting the Add button on an activated card starts the translation.
| Translation mode | Description |
|---|---|
| Use AI | Translate using machine-intelligence providers such as Google. Selecting the card creates a translated secondary model. Machine translations may be incorrect or too literal, so review the translated content for accuracy. For more information, see Dynamic Translation. To activate the Use AI mode, Localization Framework must be configured and activated. |
| Use a third party | Request translation by a professional translation team. When you select this mode, an LF task is created per the LF language group settings for the secondary language. When the translations are completed, the translated model is created and ready for review. For more information, see Localization Framework and Translation modes. |
| No translation | Default. Manually translate your primary language into a secondary language. Selecting this mode creates a draft secondary model with the intent names the same as that of the primary model. These intents are disabled by default, and you must enter your utterances manually. Names of intents and names of entities imported from the primary model aren't editable. Names of entities that you create directly in the secondary model are editable. This mode is also helpful if you want to draft and save the primary model first, and then translate your utterances later. |
In this example scenario, your primary model uses the English language and you're adding a version in the French language, without translating utterances.
Procédure
Que faire ensuite
If you chose to enable the model without translation, you must manually enter training utterances for each intent. If you choose to use software or a third-party translator, you must review the translations before you can continue working on the model.
Entering training utterances and reviewing secondary models can be delegated to users who have the nlu_editor role. For more information, see Assign an NLU editor to a model and Resolve intent issues.