Update langauge value of Korean in API docs #215
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aromahyang
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello, I am using your library well.
To use speech recognition in Korean, I set the parameter
languageofstartListening()tokoas guided in the API documentation.Before November 12, 2024, speech recognition results were properly displayed in Korean.
However, on November 14, when using Android browsers and Android apps, the results were displayed in English even when speaking in Korean.
On desktop Chrome and iOS browsers and apps, Korean results are displayed correctly.
It is unclear whether this issue is related to Chrome 131 release (November 12, 2024), but it is certain that
language: 'ko'does not work properly in Android.Upon checking an attribute
langofSpeechRecognitionin MDN documentation, it is recommended to use the BCP 47 language tag.After changing
language: 'ko'tolanguage: 'ko-KR', Korean speech recognition works well across all OS environments.So I would appreciate it if you could update the language value in the API documentation.