speakup and garbled text

[Chuck Hallenbeck]

Hi,


>>>
>>> I doubt it, because as I say, I have never seen it in review mode.
>>
>> Even if you ask for reading the whole screen?
>
> Yes, precisely.  Reading the screen is fine.

I think I have noticed that:

1. the speech produced by one whole line of text takes a certain amount
of time, call it t1.

2. Displaying a full line of text takes a certain amount of time, call
it t2.

3. Using review mode to read  a whole screen does  not require the
screen to be redisplaye,d, so t2 is zero in that case.

4. In all other cases, t1 is much longer than t2, so that eventually the
amount displayed but not yet spoken becomes indefinitely large.

5. the solution is either:

5.1 slow down the display, so it never accumulates a large amount of
unspoken date,

or 5.2 don't be surprised if the speech gets garbled due to a buffer
overflow condition somewhere in the speech chain.

I've been writing a lot of bash scripts with lots of display and lots of
speaking, and find that I must sprinkle the code with "sleep" commands
to artificially slow down the display so it doesn't overwhelm the
translated text waiting to be spoken.

Just my observations.


Chuck