Dear Danielle,

Thanks for the info.

From a programming point of view it is a pity only a series of backspaces is sent....

Given the fact we are speaking about steno, and steno is all about speed, I have following question to you:

would it be acceptable to you that individual letters are completely spoken out when they are deleted? Not very ideal from a speed perscpective (user experience), but from a programming point of view perhaps a reliable solution could be worked out.

Otherwise, I guess we would need a mechanism to detect when the sequence of generated backspaces is over (and not waiting for the next key stroke): my first simplistic idea would be using a hold-off timer going off, but that is probably not a very reliable solution. (if I remember well from your video with steno you do 300 wpm or 5 words per sec or 200 millisec per word, counting 3 or 4 syllables per word means max 50 millisec per syllable or keystroke... that is pretty tight).

An alternative would be to create a plover plugin to be plugged in into nvda, that creates a backdoor open to plover in order to let plover instruct nvda to speak the complete syllable being deleted; obviously the plover code should be modified to give nvda this instrucction via this backdoor. At the positive side, I believe it would work more reliably and simpler to implement; at the negative side, I dislike this option as it requires code on both the nvda and plover side and I am not in favour of creating backdoors.

Please let me know what your opinion as user on the above question is / what behavior you exactly would expect.

Kind regards,

Didier