Skip to content
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

Reporting of characters in input help mode is unreliable if the current input language is not english #14793

Open
k-kolev1985 opened this issue Apr 5, 2023 · 0 comments
Labels
blocked/needs-product-decision A product decision needs to be made. Decisions about NVDA UX or supported use-cases. blocked/needs-technical-investigation Issue is blocked. A technical investigation is required to progress the issue. p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.

Comments

@k-kolev1985
Copy link

Steps to reproduce:

  1. Add another (preferably - non-latin) input language to Windows (in my case it is bulgarian), so you have two - english and the additional one.
  2. Switch to the newly added input language.
  3. Preferably, switch to a multilingual speech synthesizer (e.g. eSpeak), which can read the letters from both english and the additional input language added in step 1.
  4. Enable input help mode in NVDA.
  5. Press each key with a letter/character from the main part of the keyboard.
  6. Observe what will NVDA report for each pressed key.

Actual behavior:

In most cases, NVDA reports the letters from the english input language. Exceptions are the keys where for the english input language/layout there are symbols/punctuation characters instead of letters - there NVDA reports the corresponding characters from the additional input language.

Expected behavior:

NVDA reports the characters (symbols/punctuation/letters) for the currently active input language (e.g. in my case - bulgarian).

NVDA logs, crash dumps and other attachments:

NVDA_InputHelp.log

System configuration

NVDA installed/portable/running from source:

Installed.

NVDA version:

NVDA version alpha-28022,5f340be5

Windows version:

Windows 11 Pro version 22H2 (build 22621.1413), 64-bit, in Bulgarian with all locale settings set to "Bulgarian".

Name and version of other software in use when reproducing the issue:

N/A

Other information about your system:

N/A

Other questions

Does the issue still occur after restarting your computer?

Yes.

Have you tried any other versions of NVDA? If so, please report their behaviors.

NVDA 2023.1 - the behavior is the same.

If NVDA add-ons are disabled, is your problem still occurring?

Yes, it is.

Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?

N/A.

@seanbudd seanbudd added p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation. blocked/needs-product-decision A product decision needs to be made. Decisions about NVDA UX or supported use-cases. blocked/needs-technical-investigation Issue is blocked. A technical investigation is required to progress the issue. labels Apr 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked/needs-product-decision A product decision needs to be made. Decisions about NVDA UX or supported use-cases. blocked/needs-technical-investigation Issue is blocked. A technical investigation is required to progress the issue. p3 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority triaged Has been triaged, issue is waiting for implementation.
Projects
None yet
Development

No branches or pull requests

2 participants