Handle custom language policies per recognizer type (LUIS/QnA Maker) and for language generation

Use this query to search for the most popular feature requests.

Is your feature request related to a problem? Please describe. When creating multilingual bots with unsupported LUIS locales in Composer the recommended solution is to create a customized language policy and then use a translation middleware. However, it’s pretty easy to have “hand translated” templates that perform much better, from a user language POV, than what can be achieved on-the-fly with a translation middleware.

And it can even become more complicated, because QnA maker supports more locales than LUIS.

The above scenario is relatively easy to solve when creating a code-based bot, because you can create a “MultilanguageTranslatingRecognizer” that can be completely customized. However solving this with Composer has not been possible, mainly because the LanguagePolicy kind of gets in the way. Because a single LanguagePolicy, that applies both to user and bot messages is too restrictive.

Describe the solution you’d like The possibility to define separate language policies per recognizer on one side and another for LG.

Describe alternatives you’ve considered

• Creating a “TranslatingRecognizer” to replace the standard LUIS recognizer. Result: by the time the recognizer is about to do its job the LUIS app has already been selected as per the language policy.
• Defining a custom LG policy on the MultiLanguageGenerator produces an error.

Additional context Add any other context or screenshots about the feature request here.

[mvelosop]

You should 've received the invitation already.

[mvelosop]

Thanks @carlosscastro just let me know if you need any more info or details 😊