Feature roadmap/SCIM: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
m (fix link to User:Sayamindu)
Line 2: Line 2:
|Name=SCIM
|Name=SCIM
|Feature subcategory=Localization
|Feature subcategory=Localization
|Requesters=Sayamindu
|Requesters=User:Sayamindu
|Requirements=
|Requirements=
* We need to migrate to SCIM for our input method needs. Our current input method (XKB with XIM) does not work with languages like Chinese, and there are enhancement requests from existing deployments (eg: <trac>8494</trac>) which can only be handled via SCIM.
* We need to migrate to SCIM for our input method needs. Our current input method (XKB with XIM) does not work with languages like Chinese, and there are enhancement requests from existing deployments (eg: <trac>8494</trac>) which can only be handled via SCIM.

Revision as of 05:17, 21 December 2008

Feature subcategory Is part of::Category:Localization
Requesters {{#arraymap:User:Sayamindu|,|x|Requested by::x}}
Requirements * We need to migrate to SCIM for our input method needs. Our current input method (XKB with XIM) does not work with languages like Chinese, and there are enhancement requests from existing deployments (eg: <trac>8494</trac>) which can only be handled via SCIM.
  • Must completely support Simplified Chinese, Nepali and Amharic.
Specification * Conversion of all existing layouts to m17n db format , along with refinements and better support for modifiers whenever possible (<trac>6280</trac>
  • Modification of relevant startup and configuration scripts for SCIM support
  • User experience for keyboard layout switching should not change
  • Proper handling of Amharic characters (<trac>8494</trac>)
  • Implementation of OLPC_Nepal_Keyboard
Owners {{#arraymap:Sayamindu|,|x|Contact person::User:x}}
Priority Priority::1
Helps deployability? Helps deployability::yes
Target for 9.1? Target for 9.1::yes