Samuel Thibault <[EMAIL PROTECTED]> writes: > Samuel Thibault, le Sat 19 Jan 2008 21:13:46 +0000, a écrit : >> > have brltty map them correctly to the associated dot combination? >> >> Unfortunately the screen driver model still does't take unicode into >> account and thus brltty will still show question marks for now. > > Maybe we could extend it temporarily without having to revamp everything > right now by just adding a SCR_DOTS request that returns dots, if any? > For 0x28uv, the screen driver would return ' ' for SCR_TEXT and 0xuv for > SCR_DOTS, which the main loop of brltty.c could mix just before the call > to writeWindow.
Could you elaborate a litte bit on this? As far as I see, the vcsa device only uses a 16 bit value for each character on the screen to mix attribute and character values. How does an application actually see the character at a certain position is unicode 0x2800? Or did I miss something here? -- CYa, Mario | Debian Developer <URL:http://debian.org/> .''`. | Get my public key via finger [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: BRLTTY@mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
