If the latest version of Notepad++ (4.8.2) is open when I open a PDF file using Acrobat Pro (7.0.9) causes Acrobat to display a dialog "Reading Untagged Document": "This 14 page document is untagged and must be prepared for reading. Whle the document is being analyzed, your assistive technology will not be able to interact with this application" and displays a Start and Cancel buttons.
If Notepad++ is not open, this dialog is NOT displayed. Only when Notepad++ 4.8.2 is open, even with a blank document, does this happen.
Thanks,
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also when Notepad++ is open without any plugins? Temporarily rename the plugins folder to check this and report here when you find out it is not caused within Notepad++ itself.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have this problem too, with acrobat reader 8.1.2, and notepad++ 4.8.2.
Disabling all plugins for acrobat solves the problem, and I think the cause is the accessibility plugin. From what I can tell, it will try to prepare a document for a screen reader if it thinks one is running.
So, acrobat thinks notepad++ is a screen reader. I don't know why.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's Accessibility.api. Removing this plugin prevents the problem. I did have to also remove ReadOutLoud.api if I remove Accessibility.api; otherwise, acrobat reader crashes. Hope this helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I should be a little more specific. After removing accessibility.api, if I start acrobat reader with notepad++ running, I get a message saying "this version of acrobat does not support screen readers." (But there's an option to never show this message again.)
So, acrobat still thinks notepad++ is a screen reader, but without the accessibility plugin, it won't start up the whole process of "reading" the document.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Seems to be w/o any plugins too. Very typical, why would adobe read a file differently if Notepad++ is open? Its probably in the same alley as adobe 8 not resizing the document when logitech setpoint is installed :).
Harry
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yep. I can confirm that even without plugins, Acrobat behaves this way. It's definitely something with the latest version, as it just started doing it after I updated (and I use Acrobat Pro daily, so would have seen it previously!)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If the latest version of Notepad++ (4.8.2) is open when I open a PDF file using Acrobat Pro (7.0.9) causes Acrobat to display a dialog "Reading Untagged Document": "This 14 page document is untagged and must be prepared for reading. Whle the document is being analyzed, your assistive technology will not be able to interact with this application" and displays a Start and Cancel buttons.
If Notepad++ is not open, this dialog is NOT displayed. Only when Notepad++ 4.8.2 is open, even with a blank document, does this happen.
Thanks,
Also when Notepad++ is open without any plugins? Temporarily rename the plugins folder to check this and report here when you find out it is not caused within Notepad++ itself.
I have this problem too, with acrobat reader 8.1.2, and notepad++ 4.8.2.
Disabling all plugins for acrobat solves the problem, and I think the cause is the accessibility plugin. From what I can tell, it will try to prepare a document for a screen reader if it thinks one is running.
So, acrobat thinks notepad++ is a screen reader. I don't know why.
> Disabling all plugins for acrobat solves the problem, and I think the cause is the accessibility plugin
Could you let me know witch plugin provokes this problem?
Don
It's Accessibility.api. Removing this plugin prevents the problem. I did have to also remove ReadOutLoud.api if I remove Accessibility.api; otherwise, acrobat reader crashes. Hope this helps.
I should be a little more specific. After removing accessibility.api, if I start acrobat reader with notepad++ running, I get a message saying "this version of acrobat does not support screen readers." (But there's an option to never show this message again.)
So, acrobat still thinks notepad++ is a screen reader, but without the accessibility plugin, it won't start up the whole process of "reading" the document.
Next release of Notepad++ should have this corrected, so just hang in tight :)
-Harry
I confirm that (thanx to Harry) ;)
Next release will be in 2 weeks.
Don
Seems to be w/o any plugins too. Very typical, why would adobe read a file differently if Notepad++ is open? Its probably in the same alley as adobe 8 not resizing the document when logitech setpoint is installed :).
Harry
Yep. I can confirm that even without plugins, Acrobat behaves this way. It's definitely something with the latest version, as it just started doing it after I updated (and I use Acrobat Pro daily, so would have seen it previously!)