CustomVocabulary does not work when combined with identify-language or identify-multiple-languages
This message is logged by WebSocket transcriber:
BadRequestException: You must specify the custom vocabularies in the vocabularyNames parameter when using language identification or multiple language identification.
On looking at API spec, when using identify-language or identify-multiple-languages, any Custom Vocabularies must be specified as VocabularyNames - not VocabularyName
To Reproduce
Steps to reproduce the behavior:
Choose identify-language or identify-multiple-languages, AND specific a CustomVocabulary.
Expected behavior
Template parameter CustomVocabulary should accept a list of vocab names for use as VocabularyNames when using identify-language or identify-multiple-languages.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Describe the bug
CustomVocabulary does not work when combined with identify-language or identify-multiple-languages
This message is logged by WebSocket transcriber:
BadRequestException: You must specify the custom vocabularies in the vocabularyNames parameter when using language identification or multiple language identification.
On looking at API spec, when using identify-language or identify-multiple-languages, any Custom Vocabularies must be specified as VocabularyNames - not VocabularyName
To Reproduce Steps to reproduce the behavior:
Choose identify-language or identify-multiple-languages, AND specific a CustomVocabulary.
Expected behavior
Template parameter
CustomVocabulary
should accept a list of vocab names for use as VocabularyNames when using identify-language or identify-multiple-languages.Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.