New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVDA fails to report system input language switching with Alt+Shift #8419

Closed
k-kolev1985 opened this Issue Jun 19, 2018 · 4 comments

Comments

Projects
None yet
4 participants
@k-kolev1985

k-kolev1985 commented Jun 19, 2018

Steps to reproduce:

  1. Update NVDA to the latest "next" snapshot (next-15324,255cb03f).
  2. Try to switch between input languages with Alt+Shift. My input languages are 2: English U.S. and Bulgarian Bulgaria.

Expected behavior:

NVDA should report the input language change.

Actual behavior:

NVDA only plays its error sound.

System configuration:

  • Operating system: Windows 10 Pro version 1803 (build 17134.112), 64-bit, in Bulgarian with all locale settings set to "Bulgarian".
  • NVDA version: next-15324,255cb03f.
  • Processor: Intel Core i5-4670 at 3.40GHz.
  • RAM Memory: 8.00GB.
  • Graphics: MSI GeForce GTX-1050TI Gaming X 4G, 4096MB dedicated memory + 4065MB shared system memory, desktop resolution set to 1920x1080.
  • Sound Card: Realtek ALC887 at Intel Lynx Point PCH - High Definition Audio Controller.

Other questions:

I'm attaching the NVDA log with the logging level set to "Debug".
NVDA_Log_2018-06-19.log

@leonardder

This comment has been minimized.

Show comment
Hide comment
@leonardder

leonardder Jun 19, 2018

Collaborator

@dkager, could you please provide a fix for this ASAP?

Collaborator

leonardder commented Jun 19, 2018

@dkager, could you please provide a fix for this ASAP?

@dkager

This comment has been minimized.

Show comment
Hide comment
@dkager

dkager Jun 19, 2018

Collaborator

The problem appears to be that the language contains non-ASCII characters. This did not show up in testing because I only used Western European layouts.

@k-kolev1985 Could you try this build to confirm if it fixes the problem?

Collaborator

dkager commented Jun 19, 2018

The problem appears to be that the language contains non-ASCII characters. This did not show up in testing because I only used Western European layouts.

@k-kolev1985 Could you try this build to confirm if it fixes the problem?

@k-kolev1985

This comment has been minimized.

Show comment
Hide comment
@k-kolev1985

k-kolev1985 Jun 19, 2018

@dkager Yes, this test build fixes the issue. Now NVDA correctly reports the names of the input languages when I switch to each of them.

And I've internally guessed correctly that the problem has something to do with text encoding, taking in consideration the error about Unicode encoding. Problems like this sometimes happen when non-latin (cyrillic) text is involved. 😀

k-kolev1985 commented Jun 19, 2018

@dkager Yes, this test build fixes the issue. Now NVDA correctly reports the names of the input languages when I switch to each of them.

And I've internally guessed correctly that the problem has something to do with text encoding, taking in consideration the error about Unicode encoding. Problems like this sometimes happen when non-latin (cyrillic) text is involved. 😀

@leonardder

This comment has been minimized.

Show comment
Hide comment
@leonardder

leonardder Jun 19, 2018

Collaborator

This was fixed by @dkager in #8401 and will be available in the next snapshot that's currently being build.

Collaborator

leonardder commented Jun 19, 2018

This was fixed by @dkager in #8401 and will be available in the next snapshot that's currently being build.

@leonardder leonardder closed this Jun 19, 2018

@nvaccessAuto nvaccessAuto added this to the 2018.3 milestone Jul 18, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment