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
Japanese input method is not reported correctly #2730
Comments
Comment 1 by nishimotz on 2013-02-23 07:45
Regarding Japanese IME, diffEnd is not necessary as far as I know. |
Comment 2 by mdcurran on 2015-01-08 06:15 |
Comment 3 by nishimotz on 2015-01-08 09:18 Technically, we should obtain information regarding TF_DA_ATTR_INFO (for TSF) or GCS_COMPATTR (for IMM32) from Japanese input method editor. http://msdn.microsoft.com/en-us/library/windows/desktop/ms629063%28v=vs.85%29.aspx http://msdn.microsoft.com/en-us/library/cc195099.aspx Just after pressing space key and first candidate appears, the results may differ depending on the configurations or previous usage of the system. If all the characters are 'target_converted' characters (we also say that characters are converted as single clause), the user want to hear the explanations for all of the characters as the feedback of conversion. If some characters are 'target_converted' and other characters are just 'converted' (we say that characters are converted as multiple clauses), the user should know what portion is 'target' (or 'selected'), because we must use left/right arrow keys to choose the 'target' portion and press space key to select alternatives for the target portion. In Japan, implementations regarding this differs among screen readers:
Anyway, it is not just the matter of string comparisons. NVDA-JP has been worked around GCS_COMPATTR and we added TF_DA_ATTR_INFO support since 2014.3jp, so we should contribute regarding this. |
@michaelDCurran Since you were assessing the reported issue earlier, could you please share any thoughts/inputs you may have in response to @nishimotz's #2730 (comment)? |
Let me continue the discussion of #8621 regarding Japanese IME here. The first candidate issue is still open for Japanese as well, however, it is different from Chinese. When the space key is pressed, first candidate is shown, without candidate window. |
Auto focus means announce the prediction window under Windows 10. Am I right? |
As far as I have seen, the first candidate in Japanese IME shown after pressing space is treated as a reading string. That is why the first candidate is not announced as character description. |
Reported by nishimotz on 2012-10-19 07:24
Japanese input method is reported as follows:
Example:
Three syllabic (kana) characters (transliterated from Latin 'k a w a n o')
are translated into three (ideographic and syllabic) characters:
When the space is pressed, first candidate 'kawa no' is shown (without opening candidate window), so it should be reported using character descriptions.
It also should include the last (syllabic) character 'no'.
The text was updated successfully, but these errors were encountered: