#Dialogflow translator bot code

If you later want to add other languages to the skill and one or more of the desired languages isn't supported natively, you would need to create a new skill from scratch and set English as the primary language in the new skill.Then, if you later need to add other languages that are natively supported, you will be able to optimize intent resolution for each language (in addition to having more control over the output messages). If the target language of your skill is among the natively-supported languages, consider using the native language approach.Create resource bundles for the skill responses.(For non-English skills that rely on a translation service, the underlying training model of the skill is in English.)

#Dialogflow translator bot code

Add code to the dialog flow to detect the language of the user input and to translate it behind the scenes.Create intent utterances and entity values in the language that you are supporting.When creating the skill, designate the target language as the primary language (and in translation mode).You have configured a translation service (either Microsoft Translator or the Google Translation API).However, if that language is not supported natively, you can use a translation service. Typically, if the language you are targeting for a skill is supported natively in Oracle Digital Assistant, you would use that native language support for the skill. To realize the potential of this approach, be sure to allocate adequate resources for multi-language intent training and formulating effective output messages in all of the target languages.In terms of user experience, this approach gives you the best opportunity to satisfy user expectations in multiple languages.Create resource bundles for each of the skill's output strings, provide entries for each language, and reference the resource bundle keys from the appropriate places in the dialog flow and the skill's settings.For any value list entities that you create in the primary language, add values in the additional language that correspond to each of the values in the primary language.For each additional language, augment the training corpus as necessary.Build the training corpus in the primary language.

On the skill's Settings, Intents, or Entities page, add any additional natively-supported languages that you want to target.Once you have set it, you can not change it. This language will serve as the default language in the skill.

When creating the version (or clone) of the skill, designate one of the natively-supported languages as the primary language.

The Platform Version of the skill is 20.12 or higher.

The languages you are targeting all are on the list of Natively-Supported Languages.

This includes example utterances for intents and custom entity values. For skills that you target to the languages that Oracle Digital Assistant supports natively, you can add training data for all of the target languages.