Reported by kevinchao89 on 2012-03-18 19:22
when a phrase, sentence, word, and/or character contains formatting
attributes, e.g. bold, italic, and/or underline, NVDA should be able
Comment 1 by jteh on 2012-03-19 03:25
There is definitely code to support this and it does work in Adobe Reader 9. However, Reader X no longer seems to be reporting any formatting information; everything is just blank. We will report this to Adobe.
Attachment underlined text.pdf added by kevinchao89 on 2012-03-19 21:02
Comment 2 by kevinchao89 on 2012-03-19 21:03
The underlined text is in the paragraph that starts with “The causes of the school dropout problem have received…”. Dropout is underlined. Continue on in the paragraph and “effects” is underlined. “Important” is italicized. “Obvious” is italicized.
Comment 3 by jteh on 2012-03-26 01:59
The issue has been reported to Adobe and they are investigating. This worked correctly in Reader 10.0.1 and earlier, but is broken in Reader 10.1 and later.
The problem is that IPDDomNode::!GetFontInfo() is returning FontInfo_NoInfo when it should return FontInfo_MixedInfo or FontInfo_Valid as fontStatus. Therefore, when NVDA sees FontInfo_NoInfo, it treats this as an indication that there is no font info and does not descend any further.
Interrogating the tree myself, I see that there is valid font info on the word nodes. However, the node above says FontInfo_NoInfo, so NVDA never sees this.
Comment 4 by jteh on 2012-06-05 00:45
Note that NVDA was never able to detect underline, as it isn't exposed in the same way as other font info. I've filed #2410 to cover this issue and narrowed the scope of this ticket to the regression in Reader 10.1.
Changed title from "Adobe Reader X: formatting info (bold/italic/underline) should be automatically reported or allow querying" to "Font info not detected in Adobe Reader 10.1 and later"
Comment 5 by jteh on 2012-09-04 23:51
This won't be fixed in Reader in the near-term, so we'll need to work around it in NVDA.
Milestone changed from None to 2012.3
Comment 6 by jteh on 2012-09-05 00:46
Worked around in ebd3a11.