secondlife / secondlife/viewer

Azure API cannot be entered normally

Open
#5,995 3 comments 0 reactions 1 assignee View on GitHub

@akleshchev is already working on this.

Since Jul 17, 2026.

  • #6005 by @akleshchev — merged
bug stale
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

About chat translation, I found two bugs.

Using the new Azure API will result in a 401 error. Because the current Azure API has too many characters, it exceeds the viewer’s API character limit.

https://learn.microsoft.com/en-us/answers/questions/2147198/speech-service-api-keys-too-long-to-use

Another bug was discovered earlier (at that time, the Azure API was still 32 characters). If the text sent to Azure contains emoji or other non-ASCII characters, the translation will become garbled.

I mistakenly submitted it under feature requests before, and I’m very sorry.

https://secondlife.canny.io/admin/feedback/bug-reports/p/azure-api-cannot-be-entered-normally

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.