Hi folks,
On Thu, 7 Sep 2000 14:04:21 +0100, Neil Smith wrote:
> That 'old' chestnut! Back to what karen wanted: I don't know a lot about
> customising arachne in this way, but if we can specify 'talk.sys' driver as
> below ($$talk$$), then is there any reason why that cfg line couldn't be
> adapted
> to send the output to karen's speech program, and / or on to the printer
> port?
Of course can You send _4prt.txt to printer, printing the page does
exactly that :-). But the problem is that both the printer port and
talk.sys is a device which can be accessed in DOS like a file with
simple commands. If the speech program can't be accessed this way, it
will be tricky to use it with Arachne 'cause she is not speech friendly.
The reason why talk.sys works is the existence of _4prt.txt, which is
ascii. I'm afraid there is no screen reader capable to read a graphics
screen from video memory.
<snipped>
> This still doesn't solve the basic problem of extracting specific chunks of
> text (specifically chat responses or text box contents) to the reader when
> an update
> occurs. How to do this?
You are right, this is only a temporarily solution. For real speech
support, everything that goes to the screen must be sent to speech
driver as ascii, too. This includes messages in the status line, except
the time display and similar things like byte counters... But messages
appearing if the mouse cursor touches a butten or a link are to be read, too.
And of course it's not good if the reader starts after several key
presses :-).
Regards Joerg
-- This mail was written by user of Arachne, the Ultimate Internet Client
-- Arachne V1.65, NON-COMMERCIAL copy, http://arachne.cz/
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
