You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by orcauser on 2009-12-16 23:12
install arabic as a writing language, open word/wordpad, switch to arabic braille table and arabic writing and start typing, the braille does not display until we go down to the next line and then up again, cant be sure at the moment, but i think cursor movement is also wrong.
The text was updated successfully, but these errors were encountered:
I wonder whether there Arabic users who can confirm this. Since there haven't been comments on this issue for seven years, I think it's safe to close this. People who still experience this can request to reopen it, or open a new issue themselves.
I don't quite understand the problem here, but there's no computer Arabic braille table yet, so of course you can't input Arabic text using a braille display. Since the lack of such a table isn't NVDA scope I would vote to close as needs external fix.
If I understand correctly, I think the reporter meant switching to Arabic braille output and the Arabic PC keyboard layout. So, the question is: if you open Wordpad and start typing in Arabic, do you see braille output?
@mohdshara Thanks for investigating, just to confirm its not a more general bug: if you follow the same steps with English input on your setup, then the braille is output character by character as you type?
This is the behaviour I get (for English keyboard input, and Arabic keyboard input) in next Version: next-14098,66f26bb2 regardless of the state of the Speak typed characters check box in the Keyboard Settings dialog
Hi. yes, if you type English, characters will appear instantly as soon as you type them. This behavior only happens if you type Arabic text. I tried this with 2 Braille displays just to be sure it's not a hardware issue. Is there anything else you want me to do to help track down this bug?