| Summary: | Ctrl-Space cannot be used on Simplified Chinese | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Tod Creasey <Tod_Creasey> |
| Component: | UI | Assignee: | Kai-Uwe Maetzel <kai-uwe_maetzel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P4 | CC: | loyah, n.a.edgar, simon_arsenault |
| Version: | 2.0 | Keywords: | accessibility |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | |||
|
Description
Tod Creasey
Configurable key binding support will allow the user to change the key. Is the suggestion to add a locale specific key binding for code assist? This doesn't seem to be right solution. There might be other key bindings that should be locale and platform specific. No action required at this stage, but we should keep this in mind. It's only a problem on Simplified Chinese, which although it may be an important locale, is not an officially supported locale for 2.0. We should wait for the key binding story. In general, though, we currently try to use keys that work in all locales and platforms, for consistency, and because we don't currently have a good story for locale- and platform-specific key bindings. This locale is supported on 1.0 - we ship fragments for traditional and simplied Chinese (code zh_CW). I would expect the same 2.0. Ctrl+K was used in 1.0. for Chinese. Does not affect section 508. With the keybinding support, it may suffice to define a secondary keybinding for code assist. This will work as long as our use of Ctrl+Space does not block the IME from being activated. This will be fine - the IME is activated before Eclipse so it is Eclipse that loses the Ctrl-Space. Build F2. Kai, how did you fix this? By adding a second key binding? There are duplicate key bindings for content assist in org.eclipse.jdt.ui's plugin.xml. Ctrl+2 for Content Assist (usually Ctrl+Space). Ctrl+Shift+2 for Parameter Hints (usually Ctrl+Shift+Space). These only take effect when in the zh_CN locale. |