On Tue, Aug 31, 2021 at 03:16:14PM -0400, Nicolas Pitre wrote: >I use autospeak all the time. That is, whenever the braille window moves >to a different line then the TTS immediately reads the content of the >whole line. This allows me to read the line in braille simultaneously >with the TTS if I need a "visual" appraisal, or just let the TTS read it >on its own. This is very efficient as no additional commands on top of >braille navigation are needed to trigger speech output.
Agreed. But there is a terible bug which makes working with speech only very difficult in some situations. Lets say you have the following lines in a file: test123 test234 test567 In some situations, and I think it is when such lines that differ only im some characters on the beginning of a line and if those lines are at the end of a screen, the content of the first line is spoken fully and the second and third line is spoken only partialy (in the example test is not longer spoken for the second and third line). This is no big problem when also a braille display is used, allthough it is annoying. And I know such behaviour only with brltty, e.g. sbl does not have the described problem. However, it would be nice if this behaviour could be fixed or at least researched. Maybe it is not brltty releated and it is a problem of espeak-ng or speech-dispatcher. Without this behaviour it would be much more easier only to work with speech and not move the fingers from the keyboard to the brailledispay to get sure whats the real content of the current line, that would speed up working in some situations very much. Let me know if you need more infos about the problem or if I can help anynow to get it fixed. Cheers, Schoepp _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: BRLTTY@brltty.app For general information, go to: http://brltty.app/mailman/listinfo/brltty