Azure / azure-sdk-for-net

This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at https://learn.microsoft.com/dotnet/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-net.
MIT License
5.25k stars 4.59k forks source link

[QUERY] CLU Punjabi #43631

Closed nkoriath-motive closed 4 months ago

nkoriath-motive commented 4 months ago

Library name and version

Azure.AI.Language.Conversations 1.1.0

Query/Question

I have a general query about using Punjabi audio with an Intent Recognizer.

Background

We are using CLU and intent recognition and making use of Multi-lingual option on our project. We have a trained model that was produced with this option enabled and have a deployment using that trained model. We have a simple test where we run continuous recognition and feed it audio.

In our testing we see successful speech recognition and intent results for the following language codes: en-US, fr-FR, hi-IN

This all works great!

Problem

However, we cannot seem to get this working with Punjabi. We get an error that the locale is not supported. ErrorDetails=Connection was closed by the remote host. Error code: 1007. Error details: Recognition is not supported for the requested language.

We have tried the following locales: pa-IN, pa-PK, pa-Guru, pa-Arab, pa

It is listed in the documentation as a supported locale: https://learn.microsoft.com/en-us/azure/ai-services/language-service/conversational-language-understanding/language-support

Furthermore, I can get results when experimenting in Language Studio and sending it Punjabi text.

Questions:

What language code should we be sending for this? Is the documentation incorrect/is this supported or am I missing something?

Environment

No response

jsquire commented 4 months ago

Hi @nkoriath-motive. Thank you for reaching out and we regret that you're experiencing difficulties. The behavior that you're inquiring about is a rejection from the Conversations service and not something that the Azure SDK package has insight into nor influence over. As a result, the maintainers of the Azure SDK libraries are unable to assist.

To ensure that the right team has visibility and can help, your best path forward for would be to open an Azure support request or inquire on the Microsoft Q&A site.

I'm going to close this out; if I've misunderstood what you're describing, please let us know in a comment and we'd be happy to assist as we're able.