I have designed a text table for arabic and persian. But just characters that I have defined using "\x##" string operand, can be typed using braille keyboard. When Dot keys that are mapped to a unicode character using "\u####" or "\U########" string operands, are pressed nothing happens in the text editor.
I have checked the output of xbrlapi and for these keys it says : couldn't translate keysym "########" to keycode, and this keysym is different from what I have defined in text table. For example, I have defined the following mapping in text table for ARABIC COMMA : char \u060C ( 5 ) and when I press Dot5 key, xbrlapi says : couldn't translate keysym "0100060C" to keycode. Is it anything wrong with this char directive or some configuration needs to be done with xbrlapi or OS? On Mon, Jan 18, 2016 at 5:22 PM, Samuel Thibault < samuel.thiba...@ens-lyon.org> wrote: > Dave Mielke, on Mon 18 Jan 2016 07:47:29 -0500, wrote: > > What has been done for a number of languages, and which I actually do for > > Canadian English (because, as you may know, Canada also has French), is > add dot > > 8 to what we might call the non-lcoal symbols. > > Just wondering a crazy idea: wouldn't it be convenient to have some > include_plus8 keyword, equivalent to include except that it adds the > 8th dot to all patterns? That way people can include various existing > tables, using the 8th dot to determine it's not their usual language. > > Samuel > _______________________________________________ > 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 >
_______________________________________________ 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
