[quoted lines by Nicolas Pitre on 2012/05/17 at 21:48 -0400] >What I don't understand is why the TTS is given that line, then stopped >and given the same line again once the length is enlarged.
It's because the core queries the screen dimensions before it reads the screen content. The two operations are entirely separate. >Worse, the longer line is sent long after the truncated one, long enough that >the synthesizer has time to start saying the first word. Why such a delay? >My computer isn't that slow... I'm guessing here because I know the path in the core is very short. My guess is that the speech driver and/or synthesizer may have a somewhat expensive path for getting the synthesis started. >I don't know how this is implemented, but surely the code can figure out >that the line length is not sufficient for the new content, and enlarge >it before speaking it? The short answer is that it's never been addressed for at least two reasons. One is that this is the first time we've had a dynamically growing screen width. The other is that it's not noticeable to a braille user. A possible third reason is that I myself don't use speech so I end up only ever reacting to speech issues which others take the time to bring to my attention. In any event, I now have an idea as to how to fix the problem without changing the menu pseudo-screen code. I should be committing a potential fix fairly soon. -- 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: [email protected] | Canada K2A 1H7 | http://Mielke.cc/now.html http://FamilyRadio.com/ | http://Mielke.cc/bible/ _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty
