NuGet / Home

Repo for NuGet Client issues
Other
1.5k stars 253 forks source link

[Localization] Narrator doesn’t localize the string “press Alt+Down to navigate any recent search terms” when the focusing is on search-filter of PM UI #13790

Open v-luzh opened 1 week ago

v-luzh commented 1 week ago

NuGet Product Used

Visual Studio Package Management UI

Product Version

Dev\6.12.0.82

Worked before?

It is not a regression since it also reproes on D16.11\34601.136.

Impact

None

Repro Steps & Context

Details about problem

NuGet Version: Dev\6.12.0.82 VS Version: D17.12\35312.88 OS: Windows-11-Enterprise-22H2 with loc languages pack CHT

Installation:

  1. Create a clean VM with loc OS (such as Windows-11-Enterprise-22H2-ZH-TW)
  2. Install VS D17.12\35312.88 from: Pipelines - Run rel.d17.12-35312.88 (visualstudio.com) with loc language pack (such as CHT)

Repro Steps:

  1. Turn on Narrator from ‘Settings->Accessibility->Narrator’ on the VM.
  2. Create a C# Console App (.NET Core 9.0) in VS after setting a loc language (such as CHT) through menu “Tools->Options->Environment->International Settings->Language”.
  3. Go to “Browse” tab and press ‘Tab’ key on the keyboard to focus on the search-filter.
  4. Listen to the reading from Narrator.

Expected Result:

Narrator should read the string “press ‘Alt+Down’ to navigate any recent search terms” into loc languages.

Actual Result:

Narrator doesn’t read the string “press ‘Alt+Down’ to navigate any recent search terms” into loc languages. image

Notes:   

1.The repro rate is 100%. 2.It reproes on all the local languages: CSY, CHS, CHT, DEU, ESN, FRA, RUS, KOR, ITA, JPN, TRK, PTB, PLK.

Verbose Logs

No response

donnie-msft commented 1 week ago

Since we don't own the search control, the best approach would be to check for known issues and dupe this to that bug. There also may be known workarounds we can implement on our side.

jgonz120 commented 1 week ago

image

Can confirm that the language being read is in English even though the UX is in Spanish, though it looks like a lot of items aren't being translated. I'm going to try changing my whole windows instance to Spanish and see if that makes a difference.

I wasn't able to find an existing bug in VS.