Braille cursor tracking confused when moving through unicode characters #499
Reported by mdcurran on 2009-12-06 07:53
The middle character in x�x is not handled properly.
(there is a 0x7f character between the two x characters).
When arrowing through the characters up to the first x, everything is fine.
Note that this problem seems to occure for any unicode character where its escape hex number is printed on the display. E.g. if I type some english but include some Chinese characters on the same line.
Guessing this is an issue with libloui and mapping input offsets to output offsets?
Comment 1 by mdcurran on 2009-12-06 08:05
Comment 6 by jteh (in reply to comment 1) on 2010-07-27 03:38
These are all due to the Python bindings not providing a large enough output buffer to liblouis. I've proposed some ideas and am awaiting feedback on the liblouis community on the best way to fix this in the Python bindings.
Comment 8 by jteh (in reply to comment 6) on 2010-08-04 17:38
I fixed this in liblouis svn !r371.
However, we also now have another option. We can specify that undefined characters be displayed with a certain character (e.g. space) instead of displaying the hexadecimal value. I think this is more user friendly for screen reader users.
All of this will be in the next liblouis release. I can try to request one, but I want to wait to see what happens regarding the proposed changes to the Danish tables, as an NVDA user has requested this.