nvda.log
Steps to reproduce:
with MathCAT installed, open the attached PDF in acrobat and read-all
Actual behavior:
speak command keys on
NVDA+down arrow
Illegal MathML found: see NVDA error log for details
a is less than b
The issue here is that the marked content is not being quoted for XML special characters so the < is tagged with a PDF mo structure element but being linearised as <mo><</mo> rather than <mo><</mo> so MathCat is handed non well formed xml that can not be parsed.
Expected behavior:
It should read the math as a is less than b
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed
NVDA version:
nvda 2025.1.2
Windows version:
11
Name and version of other software in use when reproducing the issue:
MathCAT 0.6.10
less.pdf
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Have you tried any other versions of NVDA? If so, please report their behaviors.
If NVDA add-ons are disabled, is your problem still occurring?
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
nvda.log
Steps to reproduce:
with MathCAT installed, open the attached PDF in acrobat and read-all
Actual behavior:
speak command keys on
NVDA+down arrow
Illegal MathML found: see NVDA error log for details
a is less than b
The issue here is that the marked content is not being quoted for XML special characters so the < is tagged with a PDF mo structure element but being linearised as
<mo><</mo>rather than<mo><</mo>so MathCat is handed non well formed xml that can not be parsed.Expected behavior:
It should read the math as a is less than b
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed
NVDA version:
nvda 2025.1.2
Windows version:
11
Name and version of other software in use when reproducing the issue:
MathCAT 0.6.10
less.pdf
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Have you tried any other versions of NVDA? If so, please report their behaviors.
If NVDA add-ons are disabled, is your problem still occurring?
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?