Steps to reproduce:
you just need to hear a text that must be spoken by the reader, using the portuguese BR language.
Actual behavior:
when we put the ª sign, for example, it announces female ordinal, instead of interpreting its previous character, the same as it was in the previous version.
Expected behavior:
The reader must interpret the previous character before the character, for example 2ª, the reader must pronounce primeira, and for º sign primeiro.
System configuration
NVDA installed/portable/running from source:
nvda installed
NVDA version:
2020.2
Windows version:
Microsoft Windows 10 Pro
Name and version of other software in use when reproducing the issue:
notepad etc
Other information about your system:
there is no way to send log, because it happens everywhere and there is no error
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.
With the previous version of NVDA the signal is interpreted correctly.
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
Steps to reproduce:
you just need to hear a text that must be spoken by the reader, using the portuguese BR language.
Actual behavior:
when we put the ª sign, for example, it announces female ordinal, instead of interpreting its previous character, the same as it was in the previous version.
Expected behavior:
The reader must interpret the previous character before the character, for example 2ª, the reader must pronounce primeira, and for º sign primeiro.
System configuration
NVDA installed/portable/running from source:
nvda installed
NVDA version:
2020.2
Windows version:
Microsoft Windows 10 Pro
Name and version of other software in use when reproducing the issue:
notepad etc
Other information about your system:
there is no way to send log, because it happens everywhere and there is no error
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.
With the previous version of NVDA the signal is interpreted correctly.
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