Steps to reproduce:
- On a system that is not set to English as the language, but has a language supported by NVDA, build NVDA from source.
- Run tests, at least the system tests.
Actual behavior:
Almost all tests fail because the NVDA test harness expects English language output everywhere, including the Chrome UI. Local tests cannot be run and fail almost 100%.
Expected behavior:
NVDA should force itself and the apps it uses to run in English if it needs that, even on non-English systems.
System configuration
NVDA installed/portable/running from source:
Running from source.
NVDA version:
Any current master that supports running tests.
Windows version:
Any supported.
Name and version of other software in use when reproducing the issue:
Chrome browser for system robot Chrome tests.
Other information about your system:
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.
No.
If NVDA add-ons are disabled, is your problem still occurring?
Yes.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
N/A.
Steps to reproduce:
Actual behavior:
Almost all tests fail because the NVDA test harness expects English language output everywhere, including the Chrome UI. Local tests cannot be run and fail almost 100%.
Expected behavior:
NVDA should force itself and the apps it uses to run in English if it needs that, even on non-English systems.
System configuration
NVDA installed/portable/running from source:
Running from source.
NVDA version:
Any current master that supports running tests.
Windows version:
Any supported.
Name and version of other software in use when reproducing the issue:
Chrome browser for system robot Chrome tests.
Other information about your system:
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.
No.
If NVDA add-ons are disabled, is your problem still occurring?
Yes.
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
N/A.