NVDA does not read anything.
NVDA should read previous / next character or word, as it does in other languages.
Installed and portable.
This issue also affects some system dialogs, Mozilla Firefox and the Windows console with UIA experimental support disabled.
error executing script: <bound method EditableText.script_caret_moveByWord of <NVDAObjects.Dynamic_IAccessibleEditWindowNVDAObjectEditableIndentNav object at 0x047237D0>> with gesture 'ctrl+flecha dreita'
Traceback (most recent call last):
File "scriptHandler.pyc", line 205, in executeScript
File "editableText.pyc", line 226, in script_caret_moveByWord
File "editableText.pyc", line 164, in _caretMovementScriptHelper
File "NVDAObjects\behaviors.pyc", line 175, in _caretScriptPostMovedHelper
File "editableText.pyc", line 149, in _caretScriptPostMovedHelper
File "textInfos\offsets.pyc", line 506, in expand
File "textInfos\offsets.pyc", line 485, in _getUnitOffsets
File "NVDAObjects\window\edit.pyc", line 418, in _getWordOffsets
File "textInfos\offsets.pyc", line 366, in _getWordOffsets
File "locale.pyc", line 591, in getlocale
File "locale.pyc", line 499, in _parse_localename
ValueError: unknown locale: an
Yes.
2019.2 works as expected. The problem starts in 2019.3.
Yes.
Yes.
Steps to reproduce:
Actual behavior:
NVDA does not read anything.
Expected behavior:
NVDA should read previous / next character or word, as it does in other languages.
System configuration
NVDA installed/portable/running from source:
Installed and portable.
NVDA version:
2020.1
Windows version:
Windows 10 version 1909
Name and version of other software in use when reproducing the issue:
This issue also affects some system dialogs, Mozilla Firefox and the Windows console with UIA experimental support disabled.
Other information about your system:
Relevant log fragment:
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.
2019.2 works as expected. The problem starts in 2019.3.
If addons are disabled, is your problem still occuring?
Yes.
Did you try to run the COM registry fixing tool in NVDA menu / tools?
Yes.