Running Win7 64bit, Office 2007.
First of all, I ran into a case this morning, where I could not get the
Read-to-end to work properly in Word. I could put the cursor on the
first character of the first paragraph, and hit Read-to-en. The synth
would keep chattering through the first line, then go silent. I arrowed
down to the next line, and again asked it to read to the end of the
document. Now it would read the rest of that first pargraph, and then go
silent.
From here, I would have to manually move my cursor down to the
beginning of each paragraph, and then press the Read-to-end to have the
text of the paragraph read out. No chance whatsoever to have the full
document read out. OK, it was an RTF document, but I have been able to
read these documents in Word ever before. Since most of the paragraphs
in this particular document only are two or three lines in length, I
ended up simply just using my arrow-keys. Anyone else see this behavior,
and is there a setting I need to change?
Secondly, in Notepad, ever since I installed the Beta, I experience many
times the Read-to-end does not work. You can put yourself at top of the
text, press the Read-to-end keystroke wildly as many times you want -
but it will produce only silence. then, next time you open a document
and try the same procedure, the speech happily reads out every single
sylable of the text. Don't know, if my computer starts to get a
sensitive skin to the text it is to read out, but it definitely is
bothersome.
Next. In Notepad, I can write a text. If I mistype something, and
backspace, funny stuff starts to happen. That is, the first time you
press backspace, the synth will say a totally random character. I have
had times, where it would report the letter C, as if I had deleted a C.
Thing is, that there was no C, in miles distance from the cursor
position. Continuing to press the Backspace, it seems that every press
produces the right output. Which would say, the character that you are
deleting is being reported by the synth. OK, so you keep typing. Three
lines later, you again find that you need to delete some of the just
typed text. You hit the backspace, and same story goes on. The first
press of the backspace, and you can have the fun of guessing what
character it will report this time. It might be any character, you just
don't know which. The only thing that you can be just about certain of,
is that it never will be the character you actually were deleting. And,
you can rely pretty well on the fact, that from second press and further
on, you will have correct reporting.
Have tried to maximize the window, but no way that it ever helped. Sorry
to say, all of these things worked just fine in WE8.4, and definitely do
slow down productivity. It was trouble under Beta2, and it still is
trouble under Beta3. Hope for a fix in next Beta, and most definitely in
the final.
--
David
If you reply to this message it will be delivered to the original sender only.
If your reply would benefit others on the list and your message is related to
GW Micro, then please consider sending your message to [email protected] so
the entire list will receive it.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
