[BRLTTY] xbrlapi cannot translate unicode characters defined in text table

[Samuel Thibault]

Hello,

Answering this old mail, just for the record.


Dave Mielke, le mer. 27 avril 2016 06:02:30 -0400, a ecrit:
> [quoted lines by payman shaykhmehdi on 2016/04/27 at 11:25 +0430]
> 
> >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.
> 
> That's not actually different. In a keysym, the bit 0X01000000 is a flag 
> meaning that the low-order three bytes are a Unicode value. It looks to me, 
> therefore, like brltty did indeed map the character correctly.

Yes.

> >Is it anything wrong with this char directive or some configuration needs
> >to be done with xbrlapi or OS?
> 
> It's a problem somewhere within the X session's configuration. xbrlapi logs 
> this warning when the function XKeysymToKeycode() fails.

Yes. That was when the character couldn't be typed directly on the
keyboard.

In the meanwhile, xbrlapi was made to map them dynamically in such a
case, this is available since brltty 6.0.

Samuel