Steps to reproduce:
- type the Chinese character "香" into somewhere like a notepad
- make sure the nvda locale is set to tw
- pressthe numpad 2 twice to hear the character description
- the generated character description is "香 香港 香蕉 香煙 蚊香 香味 香料 香水 芳香 檀香 中國香港 在香港以外"
But according to the tw character description file the character description for the character 香 should be
香 香水 香港 香味 芳香 百里香 焚香頂禮
Actual behavior:
Expected behavior:
nvda should refer to the character description dic file of the respective chinese locale
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
portable
NVDA version:
nvda 2022.3 beta 1
Windows version:
windows home ed 21h2
Name and version of other software in use when reproducing the issue:
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.
this problem does not exist in previous nvda, e.g. nvda 2022.2
If NVDA add-ons are disabled, is your problem still occurring?
not using any addon
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
not tried
Steps to reproduce:
But according to the tw character description file the character description for the character 香 should be
香 香水 香港 香味 芳香 百里香 焚香頂禮
Actual behavior:
Expected behavior:
nvda should refer to the character description dic file of the respective chinese locale
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
portable
NVDA version:
nvda 2022.3 beta 1
Windows version:
windows home ed 21h2
Name and version of other software in use when reproducing the issue:
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.
this problem does not exist in previous nvda, e.g. nvda 2022.2
If NVDA add-ons are disabled, is your problem still occurring?
not using any addon
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
not tried