Open nvaccessAuto opened 13 years ago
Comment 1 by briang1 on 2011-03-24 08:05 Not that I know a lot about this, but has anyone tried narrator to see what it does for such characters?
Comment 2 by pvagner on 2011-03-24 10:10 I don't seem to be able to install tamil keyboard layout on my windows xp. Are there some extra steps needed?
Comment 3 by jteh on 2011-03-24 19:41 Check the "Install files for complex script and right-to-left languages (including Thai)" checkbox.
Comment 5 by jteh on 2014-09-25 23:08 See also #2791, which will affect the same characters in some (but not all) applications when navigating by character.
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?
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?
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