[BRLTTY] Improving the speech support of brltty

Dave Mielke dave at mielke.cc
Wed Apr 25 16:09:08 EDT 2012


[quoted lines by Sebastian Humenda on 2012/04/25 at 21:41 +0200]

>* a speech cursor which follows the braille cursor, until some special
>  speech-only navigations are made. In this case the display stays at the
>  current position until the speech cursor gets out of the text area which is
>  displayed on the display. So the braille display would scroll with the speech
>  cursor when e. g. naviggating word-by-word. The motion would be like the
>  braille left-and-right motions with a fixed length.

>* same as above, but the display scrolls so that the speech cursor is always
>  approximately in the middle of the display so that you can see the context
>  left and right of the word / character beeing spoken (I don't like that, but
>  other people do prefer it) (and it's not so simple to implement, I guess)

Both are equally easy. I suppose there's a third alternative where the speech 
cursor would drag the braille display. In other words, the braille display 
would only move just enough to bring the speech location back into view.

Should navigation of the braille display location always move the speech 
cursor? If so, where should the speech cursor go: the leftmost character, the 
rightmost character, the middle, or where?

>A separate speech cursor would also allow to to "clicks" like the cursor routing
>does.

Do you mean a key which means route to the current speech location?

>What I also like to have, but this is harder to implement is that updates on 
>the screen are spoken, even when you are not on the line with the system 
>cursor. This is of course a setting which has to be selectable only for some 
>circumstances and it should be activated via a key stroke. If this setting is 
>enabled, you can e. g. enter "date" on the shell and you get the date and the 
>prompt spoken. And one would turn of this mode in Vim since the update of the 
>cursor would be spoken while navigating (since it's in the status line).

This would be much harder to implement so please remember it and remind me 
about it after we get the speech cursor working.

Is it okay for the speech functions to be bound to keyboard key combinations 
rather than to braille display key combinations? This isn't an implementation 
detail. I'm asking, rather, because I'd like to know where to define the 
default bindings.

-- 
Dave Mielke           | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario   | 2011 May 21 is the End of Salvation.
EMail: dave at mielke.cc | Canada  K2A 1H7   | http://Mielke.cc/now.html
http://FamilyRadio.com/                   | http://Mielke.cc/bible/


More information about the BRLTTY mailing list