|
I suspect that I have either forgotten something simple or something on my machine has gone wack-a-doodle that I need to fix. If I open a PDF document in Adobe Reader DC, I get the usual message about a screen reader being detected and asking if I want to prepare the file for reading. I've answered in the affirmative and that occurs. However, when that processing is going on I often get a "Not Responding" from Adobe Reader for an extended period of time (and I've got the 64-bit version). In addition, I cannot seem to reliably make NVDA do a say all no matter what I do. While I'm not getting any "Not Responding" if I open in Edge, I am still finding it well nigh impossible to get NVDA to read the PDF that is open in the browser. I seldom deal with PDFs with the screen reader, so I may be forgetting something simple as well. Is there a secret trick or several secret tricks that I need to do in advance of hitting INSERT + Down Arrow to get NVDA to read a PDF in Adobe Reader or Edge. As an aside, if you have alternative PDF readers (or editors) that you prefer when dealing with PDF files please offer their names. --
Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit
It is much easier to be critical than to be correct.
~ Benjamin Disraeli, 1804-1881
|
|
|
I now also suspect this is due to the "funky file" I was trying to play with, more than anything else. Those on the Chat Subgroup are aware of said file. However, any pointers about working with Adobe Reader and/or Microsoft Edge and/or other PDF readers would be welcome. It's not like PDF reading using NVDA doesn't come up as a cyclic topic, and I'm triggering this cycle. --
Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit
It is much easier to be critical than to be correct.
~ Benjamin Disraeli, 1804-1881
|
|
|
I have checked the box that says to not show that dialog again. I'm
not sure how customizing the reading order every time is supposed to
help. I've had very few issues leaving this checked. I have found that
the larger the PDF, the longer it takes to load. I can't remember what
NVDA says, but it will start speaking when it's ready to go.
toggle quoted message
Show quoted text
On 1/23/23, Brian Vogel <britechguy@...> wrote: I suspect that I have either forgotten something simple or something on my
machine has gone wack-a-doodle that I need to fix.
If I open a PDF document in Adobe Reader DC, I get the usual message about a
screen reader being detected and asking if I want to prepare the file for
reading. I've answered in the affirmative and that occurs. However, when
that processing is going on I often get a "Not Responding" from Adobe Reader
for an extended period of time (and I've got the 64-bit version). In
addition, I cannot seem to reliably make NVDA do a say all no matter what I
do.
While I'm not getting any "Not Responding" if I open in Edge, I am still
finding it well nigh impossible to get NVDA to read the PDF that is open in
the browser.
I seldom deal with PDFs with the screen reader, so I may be forgetting
something simple as well. Is there a secret trick or several secret tricks
that I need to do in advance of hitting INSERT + Down Arrow to get NVDA to
read a PDF in Adobe Reader or Edge.
As an aside, if you have alternative PDF readers (or editors) that you
prefer when dealing with PDF files please offer their names.
--
Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621;
Office 2016, Version 16.0.15726.20188, 32-bit
*It is much easier to be critical than to be correct.*
~ Benjamin Disraeli, 1804-1881
|
|
|
I have found that something Adobe does does make the programme appear unresponsive while it is processing. This is at its worst when Acrobat is performing OCR, where it seems to use resources in such a way that the computer appears to lock up while the processing is happening. I now use Abbyy and it’s better. If you change the setting in Adobe to show single page or something like that, it will open a lot faster, but then some key features will simply not work, so I prefer not to do this. I generally don’t use Adobe at all unless I have to fill something out, now. I just convert to another format that imo is better to read. For me, .txt is fine most of the time actually, especially as I dump stuff into my old braille notetaker to avoid having to listen to speech.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: January 23, 2023 1:46 PM
To: nvda@nvda.groups.io
Subject: **** [SUSPECTED SPAM] ****[nvda] NVDA and reading PDF files, whether in Adobe Reader DC or Edge (or another reader of your choosing) I suspect that I have either forgotten something simple or something on my machine has gone wack-a-doodle that I need to fix.
If I open a PDF document in Adobe Reader DC, I get the usual message about a screen reader being detected and asking if I want to prepare the file for reading. I've answered in the affirmative and that occurs. However, when that processing is going on I often get a "Not Responding" from Adobe Reader for an extended period of time (and I've got the 64-bit version). In addition, I cannot seem to reliably make NVDA do a say all no matter what I do.
While I'm not getting any "Not Responding" if I open in Edge, I am still finding it well nigh impossible to get NVDA to read the PDF that is open in the browser.
I seldom deal with PDFs with the screen reader, so I may be forgetting something simple as well. Is there a secret trick or several secret tricks that I need to do in advance of hitting INSERT + Down Arrow to get NVDA to read a PDF in Adobe Reader or Edge.
As an aside, if you have alternative PDF readers (or editors) that you prefer when dealing with PDF files please offer their names.
-- Brian - Virginia, USA - Windows 11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016, Version 16.0.15726.20188, 32-bit It is much easier to be critical than to be correct. ~ Benjamin Disraeli, 1804-1881
|
|
|
Yeah alt tabbing about after its done eventually gets it
working.
No idea why this is the case.
On 24/01/2023 8:39 am, JM Casey wrote:
toggle quoted message
Show quoted text
I have found that
something Adobe does does make the programme appear
unresponsive while it is processing. This is at its worst
when Acrobat is performing OCR, where it seems to use
resources in such a way that the computer appears to lock up
while the processing is happening. I now use Abbyy and it’s
better.
If you change the
setting in Adobe to show single page or something like that,
it will open a lot faster, but then some key features will
simply not work, so I prefer not to do this.
I generally don’t use
Adobe at all unless I have to fill something out, now. I
just convert to another format that imo is better to read.
For me, .txt is fine most of the time actually, especially
as I dump stuff into my old braille notetaker to avoid
having to listen to speech.
I suspect that I have either forgotten
something simple or something on my machine has gone
wack-a-doodle that I need to fix.
If I open a PDF document in Adobe Reader DC, I get the usual
message about a screen reader being detected and asking if I
want to prepare the file for reading. I've answered in the
affirmative and that occurs. However, when that processing is
going on I often get a "Not Responding" from Adobe Reader for
an extended period of time (and I've got the 64-bit version).
In addition, I cannot seem to reliably make NVDA do a say all
no matter what I do.
While I'm not getting any "Not Responding" if I open in Edge,
I am still finding it well nigh impossible to get NVDA to read
the PDF that is open in the browser.
I seldom deal with PDFs with the screen reader, so I may be
forgetting something simple as well. Is there a secret trick
or several secret tricks that I need to do in advance of
hitting INSERT + Down Arrow to get NVDA to read a PDF in Adobe
Reader or Edge.
As an aside, if you have alternative PDF readers (or editors)
that you prefer when dealing with PDF files please offer their
names.
--
Brian - Virginia,
USA - Windows
11 Pro, 64-Bit, Version 22H2, Build 22621; Office 2016,
Version 16.0.15726.20188, 32-bit
It is much easier to
be critical than to be correct.
~
Benjamin Disraeli, 1804-1881
|
|
|
Hello,
I am also interested in this.
Thanks.
Dave.
toggle quoted message
Show quoted text
On 1/23/23, Shaun Everiss <sm.everiss@...> wrote: Yeah alt tabbing about after its done eventually gets it working.
No idea why this is the case.
On 24/01/2023 8:39 am, JM Casey wrote:
I have found that something Adobe does does make the programme appear
unresponsive while it is processing. This is at its worst when Acrobat
is performing OCR, where it seems to use resources in such a way that
the computer appears to lock up while the processing is happening. I
now use Abbyy and it’s better.
If you change the setting in Adobe to show single page or something
like that, it will open a lot faster, but then some key features will
simply not work, so I prefer not to do this.
I generally don’t use Adobe at all unless I have to fill something
out, now. I just convert to another format that imo is better to read.
For me, .txt is fine most of the time actually, especially as I dump
stuff into my old braille notetaker to avoid having to listen to speech.
*From:*nvda@nvda.groups.io <nvda@nvda.groups.io> *On Behalf Of *Brian
Vogel
*Sent:* January 23, 2023 1:46 PM
*To:* nvda@nvda.groups.io
*Subject:* **** [SUSPECTED SPAM] ****[nvda] NVDA and reading PDF
files, whether in Adobe Reader DC or Edge (or another reader of your
choosing)
I suspect that I have either forgotten something simple or something
on my machine has gone wack-a-doodle that I need to fix.
If I open a PDF document in Adobe Reader DC, I get the usual message
about a screen reader being detected and asking if I want to prepare
the file for reading. I've answered in the affirmative and that
occurs. However, when that processing is going on I often get a "Not
Responding" from Adobe Reader for an extended period of time (and I've
got the 64-bit version). In addition, I cannot seem to reliably make
NVDA do a say all no matter what I do.
While I'm not getting any "Not Responding" if I open in Edge, I am
still finding it well nigh impossible to get NVDA to read the PDF that
is open in the browser.
I seldom deal with PDFs with the screen reader, so I may be forgetting
something simple as well. Is there a secret trick or several secret
tricks that I need to do in advance of hitting INSERT + Down Arrow to
get NVDA to read a PDF in Adobe Reader or Edge.
As an aside, if you have alternative PDF readers (or editors) that you
prefer when dealing with PDF files please offer their names.
--
Brian *- *Virginia, USA*- *Windows 11 Pro, 64-Bit, Version 22H2, Build
22621; Office 2016, Version 16.0.15726.20188, 32-bit
/*It is much easier to be critical than to be correct.*/
~ Benjamin Disraeli, 1804-1881
|
|
|
Carlos Esteban Martínez Macías
Hi all.
In 2020, I had the same problem with Adobe Reader in another machine. I used Foxit Reader, and it is worked fine.
Regards.
|
|
|
Wow! So what do android users do? Most of them do NOT own
iPhones.
Its great that you can update using a phone or iPad, but I'm
surprised they dumped the pc tool altogether.
mary
On 1/24/2023 9:46 AM, Carlos Esteban
Martínez Macías via groups.io wrote:
toggle quoted message
Show quoted text
Hi all.
In 2020, I had
the same problem with Adobe Reader in another machine. I used
Foxit Reader, and it is worked fine.
Regards.
|
|
|
OOps. Sent this to the wrong list. Having a bit of a focus issue
in my email client at present.
mary
On 1/24/2023 9:51 AM, Mary Otten wrote:
toggle quoted message
Show quoted text
Wow! So what do android users do? Most of them do NOT own
iPhones.
Its great that you can update using a phone or iPad, but I'm
surprised they dumped the pc tool altogether.
mary
On 1/24/2023 9:46 AM, Carlos Esteban
Martínez Macías via groups.io wrote:
Hi all.
In 2020, I
had the same problem with Adobe Reader in another machine. I
used Foxit Reader, and it is worked fine.
Regards.
|
|
|
