Dave Mielke <[EMAIL PROTECTED]> writes: > Now, of course, it must be one of them since brltty simply calls > SD. Someone with SD expertise is going to have to figure this > out. All I can do is ensure that brltty is calling the correct SD > functions. The code is simple enough for anyone to verify this.
I am not an experience SD user, but I still had to take a look. First of all, I can confirm the bug. The SD driver in general seems to work, autospeak speaks inserted multiletter strings, but does not do key echo. I just got the following message in speechd.log: [Thu Nov 27 17:14:30 2008 : 489666] speechd: ERROR: Invalid character encoding on event input (failed UTF-8 validation) Could it be that in general the call is OK, but what is expected in the string buffer is not correctly encoded for some reason? -- CYa, ⡍⠁⠗⠊⠕ | Debian Developer <URL:http://debian.org/> .''`. | Get my public key via finger mlang/[EMAIL PROTECTED] : :' : | 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44 `. `' `- <URL:http://delysid.org/> <URL:http://www.staff.tugraz.at/mlang/> _______________________________________________ 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
