search

nvaccess / nvda

NVDA, the free and open source Screen Reader for Microsoft Windows
https://www.nvaccess.org/
Other
2.1k stars 634 forks source link

First character after the cursor is dropped for Unicode not in braille table #5077

Closed nvaccessAuto closed 4 years ago

nvaccessAuto commented 9 years ago

Reported by dkager on 2015-05-05 14:54 This issue occurs when the cursor moves onto Unicode characters that aren't defined in a braille table (#499, #537). Probably a liblouis bug.

To reproduce, use NVDA with the default braille table (en-us-comp8.ctb) and default braille settings. Open Notepad and enter the following line: French uses the letter é a lot.

In braille this is rendered as: French uses the letter '\x00e9' a lot.

The problem:

For example, if the cursor is on the charcode, the following space is removed: French uses the letter '\x00e9'a lot.

This becomes a bigger problem when the charcode appears in the middle of a word.

Finally, while on this subject, has there been a final decision on whether or not to print an arbitrary indicator instead of the hex code? I'd prefer that, especially if it was a user setting.

nvaccessAuto commented 9 years ago

Comment 1 by dkager on 2015-05-06 09:10 Just verified this also happens with other tables (nl-NL-g1.ctb) and also in NVDA 2015.1, so not to blame on liblouis 2.6.2.

nvaccessAuto commented 9 years ago

Comment 2 by jteh on 2015-05-06 11:31 Do you have "Expand to computer braille for the word at the cursor" enabled? If so, try with it disabled. While it seems counter-intuitive that this should have any effect when using this table, I suspect it's a different code path, so that setting may well matter.

nvaccessAuto commented 9 years ago

Comment 3 by dkager (in reply to comment 2) on 2015-05-06 12:16 Replying to jteh:

Do you have "Expand to computer braille for the word at the cursor" enabled? If so, try with it disabled. While it seems counter-intuitive that this should have any effect when using this table, I suspect it's a different code path, so that setting may well matter.

Correct: with this setting disabled the problem goes away. With it enabled, one character is eaten.

nvaccessAuto commented 9 years ago

Comment 4 by dkager on 2015-05-09 15:32 Reported upstream.

Adriani90 commented 4 years ago

@dkager the Liblouis issue seems fixed. Is this issue still present? cc: @Andre9642

Adriani90 commented 4 years ago

I am closing this issue since we don't have any updates since years on this and the Liblouis issue seems solved. If you are having this issue still, please feel free to comment on this one and we can reopen. Thanks.