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 is tagged, Reads with "Read Out Loud" but not with NVDA or Jaws #7021

Closed
raebened opened this Issue Mar 27, 2017 · 17 comments

Comments

Projects
None yet
7 participants
@raebened

raebened commented Mar 27, 2017

I have a series of PDFs made with Indesign that are tagged. I'm cleaning them up and completed one that passes all checks (Acrobat, PAC and CommonLook) and yet will not pass a simple screen reader test. It never loads and reads as "blank."

This document came to me already tagged, but needed significant cleanup. However, it won't read at all even before I work on it, so I don't believe it's anything I'm doing.

I've tried various techniques none of which work:

  • removing all the form fields
  • removing graphics
  • removing tags and retagging automatically
  • saving as Word and remaking PDF with tags (even this did not work!)
  • using Acrobat to create PDF from file -- this results in a "screen-readable" document but the text is scrambled and meaningless as if the document were encoded.

This file is using embedded Truetype (CID) fonts. The file was originally created in 2013 on a Mac. The other files in this set that do not have this problem were originally created in 2014.

I'm quite puzzled and cannot resolve this problem.

@Brian1Gaff

This comment has been minimized.

Show comment
Hide comment
@Brian1Gaff

Brian1Gaff Mar 27, 2017

Brian1Gaff commented Mar 27, 2017

@josephsl

This comment has been minimized.

Show comment
Hide comment
@josephsl

josephsl Mar 27, 2017

Collaborator
Collaborator

josephsl commented Mar 27, 2017

@raebened

This comment has been minimized.

Show comment
Hide comment
@raebened

raebened Mar 27, 2017

Thanks josephsl but there is text in the document. I know "blank" is the kind of error you get when a document is just a scanned file but this file has text, I've tagged it. I can select it in the PDF, I can save it as a Word file and the text is all there.

Just for the heck I did run OCR and it says it can't do it because there is text on the page. I continued anyway to see if it would change something but it did not.

raebened commented Mar 27, 2017

Thanks josephsl but there is text in the document. I know "blank" is the kind of error you get when a document is just a scanned file but this file has text, I've tagged it. I can select it in the PDF, I can save it as a Word file and the text is all there.

Just for the heck I did run OCR and it says it can't do it because there is text on the page. I continued anyway to see if it would change something but it did not.

@josephsl

This comment has been minimized.

Show comment
Hide comment
@josephsl

josephsl Mar 27, 2017

Collaborator
Collaborator

josephsl commented Mar 27, 2017

@jcsteh

This comment has been minimized.

Show comment
Hide comment
@jcsteh

jcsteh Mar 27, 2017

Contributor
Contributor

jcsteh commented Mar 27, 2017

@raebened

This comment has been minimized.

Show comment
Hide comment
@raebened

raebened Mar 28, 2017

SAFER_Contingency_Planning.pdf

Here is the original file before I added read only form fields for the body text on form pages. It's the simplest version I have that should help eliminate the source of the problem. Thank.

raebened commented Mar 28, 2017

SAFER_Contingency_Planning.pdf

Here is the original file before I added read only form fields for the body text on form pages. It's the simplest version I have that should help eliminate the source of the problem. Thank.

@jcsteh

This comment has been minimized.

Show comment
Hide comment
@jcsteh

jcsteh Mar 29, 2017

Contributor

I get a crash when I try to open this PDF in Adobe Reader DC with NVDA running. A colleague sees the same issue. I'll investigate.

Contributor

jcsteh commented Mar 29, 2017

I get a crash when I try to open this PDF in Adobe Reader DC with NVDA running. A colleague sees the same issue. I'll investigate.

@jcsteh jcsteh self-assigned this Mar 29, 2017

@raebened

This comment has been minimized.

Show comment
Hide comment
@raebened

raebened Mar 30, 2017

raebened commented Mar 30, 2017

@PratikP1

This comment has been minimized.

Show comment
Hide comment
@PratikP1

PratikP1 Mar 30, 2017

PratikP1 commented Mar 30, 2017

@jcsteh

This comment has been minimized.

Show comment
Hide comment
@jcsteh

jcsteh Mar 30, 2017

Contributor
Contributor

jcsteh commented Mar 30, 2017

@jcsteh

This comment has been minimized.

Show comment
Hide comment
@jcsteh

jcsteh Mar 30, 2017

Contributor

The null pointer check is in the branch i7021ReaderCrash.

Contributor

jcsteh commented Mar 30, 2017

The null pointer check is in the branch i7021ReaderCrash.

@jcsteh

This comment has been minimized.

Show comment
Hide comment
@jcsteh

jcsteh Mar 31, 2017

Contributor

I've fixed the first crash in #7035, as #7034 reported the same crash (and it does fix that one).

Regarding the second crash in Reader itself that occurs with the PDF you provided, I've reported this to Adobe with a crash dump. Hopefully, they'll be able to track it down.

Contributor

jcsteh commented Mar 31, 2017

I've fixed the first crash in #7035, as #7034 reported the same crash (and it does fix that one).

Regarding the second crash in Reader itself that occurs with the PDF you provided, I've reported this to Adobe with a crash dump. Hopefully, they'll be able to track it down.

@raebened

This comment has been minimized.

Show comment
Hide comment
@raebened

raebened Mar 31, 2017

raebened commented Mar 31, 2017

jcsteh added a commit that referenced this issue Apr 4, 2017

@jcsteh

This comment has been minimized.

Show comment
Hide comment
@jcsteh

jcsteh Apr 12, 2017

Contributor

@jcsteh commented on 31 Mar. 2017, 3:49 pm AEST:

Regarding the second crash in Reader itself that occurs with the PDF you provided, I've reported this to Adobe with a crash dump. Hopefully, they'll be able to track it down.

Adobe have logged this internally as bug ADC-4210565. I don't have any further info at this stage.

Contributor

jcsteh commented Apr 12, 2017

@jcsteh commented on 31 Mar. 2017, 3:49 pm AEST:

Regarding the second crash in Reader itself that occurs with the PDF you provided, I've reported this to Adobe with a crash dump. Hopefully, they'll be able to track it down.

Adobe have logged this internally as bug ADC-4210565. I don't have any further info at this stage.

@raebened

This comment has been minimized.

Show comment
Hide comment
@raebened

raebened Apr 12, 2017

raebened commented Apr 12, 2017

jcsteh added a commit that referenced this issue May 2, 2017

Adobe Acrobat Reader no longer crashes in certain PDF documents (spec…
…ifically, those containing empty ActualText attributes). (PR #7035; issues #7021, #7034)

* Adobe Acrobat Reader no longer crashes in certain PDF documents (specifically, those containing empty ActualText attributes).

adobeAcrobat vbuf backend: get_PDDomNode can fail and return null, so check for a null pointer before trying to use it.

* Address review comments.

@jcsteh jcsteh removed their assignment Sep 5, 2017

@michaelDCurran

This comment has been minimized.

Show comment
Hide comment
@michaelDCurran

michaelDCurran Oct 2, 2017

Contributor

Testing with Adobe Reader 2017 Release | Version 2017.012.20098 I can no longer reproduce the crash with that pdf.
@raebened: can you still reproduce it?

Contributor

michaelDCurran commented Oct 2, 2017

Testing with Adobe Reader 2017 Release | Version 2017.012.20098 I can no longer reproduce the crash with that pdf.
@raebened: can you still reproduce it?

@feerrenrut

This comment has been minimized.

Show comment
Hide comment
@feerrenrut

feerrenrut Oct 17, 2017

Contributor

Given that we have had no response, we will now close this issue. Please comment or re-open if this can still be reproduced.

Contributor

feerrenrut commented Oct 17, 2017

Given that we have had no response, we will now close this issue. Please comment or re-open if this can still be reproduced.

@feerrenrut feerrenrut closed this Oct 17, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment