-
-
Notifications
You must be signed in to change notification settings - Fork 643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keys which produce a compound character spoken as separate typed characters #1428
Comments
Comment 1 by briang1 on 2011-03-24 08:05 |
Comment 2 by pvagner on 2011-03-24 10:10 |
Comment 3 by jteh on 2011-03-24 19:41 |
Comment 5 by jteh on 2014-09-25 23:08 |
CC @jcsteh |
P4 for now because even though it makes speak typed characters useless for some languages, we haven't had any complaints in many years with those communities, so we're not sure how much this actually matters to them for whatever reason. CC @dineshkaushal for any thoughts. |
@dineshkaushal your thoughts on this are very appreciated, thanks. |
@michaelDCurran is this solved by #10550? cc: @jcsteh since you created this issue years ago. |
If there are such characters in chinese as well, maybe @cary-rowen and @hwf1324 can you have a look and test if this issue is still relevant? |
#10550 is unlikely to fix this because it relates to navigating by character, whereas this relates to typed characters, which are handled differently. I suspect this bug still exists, though it doesn't seem like anyone cares any more? Chinese input is handled differently - it has an input method editor rather than keys mapping directly to characters - so it is handled by a very specific part of NVDA and probably doesn't suffer from this. |
How is it for Korean or Japanese? @nishimotz, @khsbory could you provide some updates if you still see this issue in NVDA 2024.4 Beta? |
We didn't get any updates from people who might have this issue in Japanese or Korean language upon request, I am closing as abandoned. If you are still having this issue, please comment and we can reopen. As far as I understand chinese speaker don't have this issue, but feel free to comment and we can reopen in case it still occurs. |
Reported by jteh on 2011-03-23 22:05
Some languages contain characters which do not have a single unicode character representation. Instead, pressing such a key produces a sequence of multiple unicode characters. This sequence looks like a single character and behaves like a single character in some respects; i.e. left/right arrow keys move the cursor past the entire compound character. However, the input actually contains several unicode characters.
Str:
Other letters in Tamil like this:
||= Letter =||= Key =||
|| த்ர || shift+6 ||
|| க்ஷ || shift+7 ||
|| ஷ்ர || shift+8 ||
|| ஞ்ச || shift+ஜ ||
|| ந்த || shift+த ||
|| ஃப || shift+ப ||
I haven't checked this yet, but I'm pretty sure Windows actually sends separate WM_CHAR messages for these characters; that is the only way it could work, since WM_CHAR only handles one character. Unless there's something I don't know about which indicates whether a character is a compound character and when it ends, this is going to be difficult to fix. We can't use WM_KEYUP to determine when a character ends, as this would mean we'd have to wait for the key to be released to have it announced. Using a timer would incur delay in speaking of typed characters, which is unacceptable.
Blocking #4487
The text was updated successfully, but these errors were encountered: