NeonGeckoCom/NeonCore

Language Handling in Intent Service

Opened this issue · 3 comments

Objective

Improve Intent Handling Language Support

Initial Implementation Goals

  • Handle intent matching in the user input language
  • If no intent matched, handle translation to core language and intent match again

Open Issues

  • How should fallback intents be handled (all but unknown use input language, some confidence level before trying in core language?)
  • Should language fallback order be configurable?

Language detection can be disabled by default for single-user use cases (i.e. Mark2)

#502 handles a configured supported_langs parameter, where configuration defines which languages to handle natively vs via translation to the default language (en-us)