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
pdf: NVDA skips private use areas characters #5562
Comments
Sorry, I don't know how to attach files. |
According to the investigation from users, now, NVDA reads pdf files and skips "private use areas" characters. notes: definition resources: |
Because this is the private use area, it is by definition impossible to have standard mappings for them. Therefore, there's nothing useful we can do here. |
Is it possible that NVDA could detect the character like NVDA2012.2 do? If users know that there is a private use area character. They could find one sighted person for help. |
Sorry. I misunderstood what you were asking for. I thought you were expecting these symbols to have proper names, which is impossible. However, the fact that they aren't present at all recently is another issue entirely. |
I can confirm this. Change was introduced by 788cefb (#2963, NVDA 2014.1). @michaelDCurran: This commit does two things:
|
I guess it was that when we fall back to a label, it is appended, rather However, if it breaks something, then there is no technical reason I can |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@jcsteh #5562 (comment) suggests that you are able to successfully reproduce the reported issue and are aware of the causative factors of this regression. Could you and @surfer0627 please check if this bug still stands in the latest version of Acrobat Reader? |
@bhavyashah: |
I can still reproduce this issue in NVDA alpha-16768,a6f7fb40 with Adobe reader 19.010.20091 |
Now, NVDA 2019.3.1 released. Then, we still need to use version 2013.3 to read private use area characters in pdf while using acrobat reader. Is it possible to have a try build to fix this issue temporarily? Actually, I do not know how to do. (git revert 788cefb) or something else. Thank you for all of your help. |
This is more complicated than just reverting the change. It's hard to say whether this is a regression or not, since this was initially changed for #2963. I found the description of this issue hard to follow, I'll attempt to describe it in my own words:
However it seems that if we fixed this in the way suggested by jcsteh's comment we will end up with noise being added to cases where a label exists. Ideally there is a label that should replace these characters, and they don't have to be rendered. |
Suggestion: use speech refactor feature to add a beep or a short sound that indicates a PUA symbol. However, this should apply only in the PDF virtual document, in MS Word PUA bullets for example are mapped to unicode, so NVDA would not report these anymore if we change the behavior for Microsoft word as well. |
NVDA skips some symbols: the numeric values are (e18c, e18d, e18e, and e18f)
This case occurs in NVDA 2014.1 and later version.
Please use the attachments to test it.
symbols.docx
symbols.pdf
case1:
environment:
NVDA2015.4 installed
interface language: English
Synthesizer: eSpeak
Adobe Reader: XI
STR:
(NVDA skips a symbol e18d.)
notes: In NVDA2012.2, the symbols could be detected.
case2:
environment:
NVDA2012.2 portable
interface language: English
Synthesizer: eSpeak
Adobe Reader: XI
(This is because here is a symbol e18c)
notes:
• I could not find NVDA2013.x, so I'm not test it.
• NVDA_2012.2 (portable) could be downloaded at
https://dl.dropboxusercontent.com/u/90288447/nvda2012.2.1.rar
The text was updated successfully, but these errors were encountered: