I have found that Windows.UI.Text.Core.CoreTextServicesManager.InputLanguage.LanguageTag may return wrong input language that is not the same as returned from Windows.Globalization.Language.CurrentInputMethodLanguageTag. It is wrong in case of sometransient input languages (that doesn't have LCID).
It seems there is same issue as I have already reported with LCIDToLocaleName API. LCIDToLocaleName returns same wrong language tags when I tried to convert transient LCID to a language tag.
I have found that
Windows.UI.Text.Core.CoreTextServicesManager.InputLanguage.LanguageTag
may return wrong input language that is not the same as returned fromWindows.Globalization.Language.CurrentInputMethodLanguageTag
. It is wrong in case of some transient input languages (that doesn't have LCID).It seems there is same issue as I have already reported with LCIDToLocaleName API. LCIDToLocaleName returns same wrong language tags when I tried to convert transient LCID to a language tag.
It could be easily reproduced like this:
What Get-WinUserLanguageList PowerShell cmdlet returns:
Also reported here: https://github.com/dotnet/runtime/issues/82367
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.