Re: Protocol for speaking daemon (comments expected)

[Jan Hubicka <hubicka@atrey.karlin.mff.cuni.cz>]

> Say commands should also have some kind of priority indicator.  For
> example, status messages should be given a higher priority than just
> regular text.  E.G. While reading a document, status messages should be
> spoken as soon as they are available (perhaps using a different
> 'personality' -- see below).
Yes, priority is quite significant, I think. IMO there should be defined
something as following priorities:
urgent
normal
low
optional (say just in case nothing else is spoken....)
> Similar to the query command (or perhaps part of it), you should be able to
> not only learn the status of a message, but determine the currently
> speaking message, and, if possible, obtain more definitive information with
> regards to your exact position in the message.  This would make things
> similar to indexing on the Dec-Talk possible.
Well, determining possition in messge should be quite complex at non-dectalk
stuff (like software syntetizers...) so it should be made as optional or
something...
> 
> Finally, it may be useful to put all of the synthesizer definitions in a
> 'synthcap' or similar file.  This would provide something analogus to the
> SSIL standard system under Windows.
Very interesting idea :)
Please can you send me some docs about SSIL standard?

Honza
> 
> Bryan
> 
> 
> 
> --
> Bryan R. Smart
> Email: bsmart@pobox.com
> 
> 
> ---
> Send your message for blinux-list to blinux-list@redhat.com
> Blinux software archive at ftp://leb.net/pub/blinux
> Blinux web page at http://leb.net/blinux
> To unsubscribe send mail to blinux-list-request@redhat.com
> with subject line: unsubscribe

-- 

---
Send your message for blinux-list to blinux-list@redhat.com
Blinux software archive at ftp://leb.net/pub/blinux
Blinux web page at http://leb.net/blinux
To unsubscribe send mail to blinux-list-request@redhat.com
with subject line: unsubscribe