Open surfer0627 opened 6 months ago
cc: @wmhn1872265132, @cary-rowen
In Simplified Chinese operating system, using Microsoft Pinyin input method cannot reproduce
If addons are disabled, is your problem still occuring?
Can you confirm you've tested this?
wmhn1872265132 commented:
In Simplified Chinese operating system, using Microsoft Pinyin input method cannot reproduce
Yes, I confirm this.
Furthermore, in traditional Chinese operating systems, when using the Chinese input method such as Chinese New Phonetic, the issue specifically occurs.
Clarification Regarding the Term "Chinese New Phonetic" in the Windows User Interface
In the English user interface (UI) of Windows, the term "Chinese New Phoneticn" appears as "Microsoft Bopomofo". The original term "Chinese New Phonetic" was chosen due to its usage in the NVDA user guide, particularly in the section Announce Selected Candidate".
cary-rowen commented:
Can you confirm you've tested this?
Yes. Sorry, I forgot to attach NVDA log.
line: 541, Microsoft Pinyin
line: 617, Microsoft Bopomofo
This issue has been reported on the NVDA-TW forum. The case occurs when NVDA is set to not speak typed characters, yet it still reports numbers while typing using the Chinese input method (Chinese New Phoneticn.).
Steps to Reproduce:
Actual Behavior:
NVDA continues to report each typed number (e.g., "1", "2", "3") despite the "Speak Typed Characters" setting being disabled.
Expected Behavior:
NVDA should not speak typed characters when the "Speak Typed Characters" setting is disabled.
NVDA logs, crash dumps and other attachments:
nvda log test speak typed characters.txt
System configuration
NVDA installed/portable/running from source:
installed
NVDA version:
2024.1
Windows version:
Windows 10 22H2 (AMD64) build 19045.4291
Name and version of other software in use when reproducing the issue:
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 addons are disabled, is your problem still occuring?
Yes.
Did you try to run the COM registry fixing tool in NVDA menu / tools?
No.