Not all Math symbols and equations inserted with Insert equation option are recognized.

[poonamdeo]

Summary of the issue:
In using NVDA with mathematics we have found that there are some symbols not recognized by NVDA.
Math auto-correct for inserting Math symbols in Word.
For example: To get epsilon sign if Math auto-correct enabled typing \epsilon gives ϵ, sign. \perp gives ⊥, etc.
It should read as the symbol name, instead of reading as the respective symbol number from the symbols list.

System configuration:
NVDA installed from: https://ci.appveyor.com/api/buildjobs/9kp2iwapkhtlbpx4/artifacts/output%2Fnvda_snapshot_pr11467-20720%2C12322f65.exe
NVDA version: pr11467-20720, 12322f6
TTS synthesizer: eSpeakNG
Windows 10
Word 2016
Add-ons got disabled automatically while installing this pr.

Description of how this pull request might fix the issue:
Maybe all symbols available in Math auto-correct list and Word symbols list categories Mathematical operators, Miscellaneous Mathematical Symbols–A, Miscellaneous Mathematical Symbols–B and Supplemental Mathematical Operators, and arrows are there in the symbols list as these arrows get used in writing Chemical expressions in Word if added to the NVDA dictionary it would help the user access most used format "Word" for STEM subjects without needing to rely on any of the other software.

The below-mentioned issue is linked to issue number: #4631

NVDA doesn't read Math expressions inserted in Word insert equation editor.
Even the symbols recognized so far are when inserted in equation editor NVDA do not recognize the equation or characters in it.
It announces as a character number.

[DrSooom]

@poonamdeo: Please completely fill out the bug report draft and add there your used language (OS, Microsoft Office NVDA, TTS synthesizer) and the used TTS synthesizer (incl. version) as well. Thanks.

[lukaszgo1]

the second part of this issue i.e. symbols inserted by the equation editor not being readable with NVDA is a duplicate of #4631

[poonamdeo]

Hi Daniel, I didn't fully understand your message, what I understood is I will need to add the system specifications nothing else right?

[Adriani90]

I think this will also improve significantly after #11467 has been merged.

[DrSooom]

@poonamdeo: It is always recommended to completely fill out the bug report draft for bugs in NVDA. This template also includes headlines, which improves the clarity of an issue. And it makes it easier for developers to reproduce the issue.

[Adriani90]

@poonamdeo this is now much better after unicode normalization is enabled in NVDA voice settings. Closing as works for me.
If you are still having this issue or you find symbols that are not recognized, please comment with a list of symbols that you would like to have spoken and we can reopen.