Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MSWord: some mathematical symbols are not read by NVDA. #3752

Closed
nvaccessAuto opened this issue Jan 7, 2014 · 4 comments
Closed

MSWord: some mathematical symbols are not read by NVDA. #3752

nvaccessAuto opened this issue Jan 7, 2014 · 4 comments
Labels
bug close/duplicate

Comments

@nvaccessAuto
Copy link

Reported by sumandogra on 2014-01-07 12:28
Certain mathematical symbols are not read by NVDA when present in a Word document. These mathematical symbols are common and very used ones.

These symbols are:pi symbol
Estimation
Partial derivative
Right angle
Intersection
Therefore in Mathematics
Congruence used in geometry

pls see the attachment.
Blocked by #3805
@nvaccessAuto
Copy link
Author

Attachment mathematical symbols.docx added by sumandogra on 2014-01-07 12:28
Description:

@nvaccessAuto
Copy link
Author

Comment 1 by blindbhavya on 2014-07-26 08:01
Hi.
Yes, not only these but there are many more mathematical and scientific symbols that NVDA doesn't read.
Please could someone clarify whether NVDA devs can fix this or the ESpeak dev.

@nvaccessAuto
Copy link
Author

Comment 3 by dineshkaushal on 2014-08-22 12:00
This issue can be fixed by NVDA developers. We need to edit symbols.dic found in locale\en folder. If symbols need to be modified for a specific language, then modify or add symbols.dic in the language folder found within locale folder.

For more information, check out section 2.2 of NVDA developer guide.

@nvaccessAuto
Copy link
Author

Comment 4 by jteh on 2014-08-23 03:42
Marking as a duplicate of #3805, since there is ongoing work there.
Changes:
Added labels: duplicate
State: closed

@nvaccessAuto nvaccessAuto mentioned this issue Nov 10, 2015
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug close/duplicate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nvaccessAuto