Feature roadmap/SCIM: Difference between revisions
Jump to navigation
Jump to search
(Some polish) |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 4: | Line 4: | ||
|Requesters=User: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. Having SCIM ready and integrated into our builds offer us the possibility to add support for almost any script relatively easily |
||
(and at a short notice), since it is much more flexible and powerful than what we have been using till now (XKB). |
|||
* Must completely support Simplified Chinese, Nepali and Amharic. |
* Must completely support Simplified Chinese, Nepali and Amharic. |
||
* User experience for keyboard layout switching should not change |
* User experience for keyboard layout switching should not change |
||
Line 11: | Line 12: | ||
* <s>Conversion of all existing layouts to [http://www.m17n.org/common/m17n-docs-en/m17nDBFormat.html m17n db format ], along with refinements and better support for modifiers whenever possible (<trac>6280</trac></s> (Postponed due to uncertainty wrt the future of SCIM, as detailed on [http://sourceforge.net/mailarchive/forum.php?thread_name=49123FC0.7080306%40users.sourceforge.net&forum_name=scim-devel this thread] ) |
* <s>Conversion of all existing layouts to [http://www.m17n.org/common/m17n-docs-en/m17nDBFormat.html m17n db format ], along with refinements and better support for modifiers whenever possible (<trac>6280</trac></s> (Postponed due to uncertainty wrt the future of SCIM, as detailed on [http://sourceforge.net/mailarchive/forum.php?thread_name=49123FC0.7080306%40users.sourceforge.net&forum_name=scim-devel this thread] ) |
||
* Modification of relevant startup and configuration scripts for SCIM support |
* Modification of relevant startup and configuration scripts for SCIM support |
||
** Patches in olpc-utils ensure that SCIM starts up automatically |
** Patches in olpc-utils ensure that SCIM starts up automatically in the relevant locales |
||
** A separate script pre-configures SCIM, based on the mfg-data. This also ensures that SCIM recognises |
** A separate script pre-configures SCIM, based on the mfg-data. This also ensures that SCIM recognises the XO's language switching key as the trigger to change layouts |
||
* Language/script specific |
* Language/script specific stuff |
||
** Proper handling of Amharic characters (<trac>8494</trac>) requires implementation of a new Amharic input method |
** Proper handling of Amharic characters (<trac>8494</trac>) requires implementation of a new Amharic input method (in progress) |
||
** Chinese: |
** Simplified Chinese: |
||
*** The following Fedora packages provide support for the Chinese requirement: |
*** The following Fedora packages provide support for the Chinese requirement: |
||
**** scim-pinyin |
**** scim-pinyin |
||
**** scim-fcitx (''To be verified'') |
**** scim-fcitx (''To be verified with the team in China'') |
||
** Nepali support is implemented by the following Fedora package |
** Nepali support is implemented by the following Fedora package |
||
*** m17n-contrib-nepali |
*** m17n-contrib-nepali |
Latest revision as of 17:11, 28 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. Having SCIM ready and integrated into our builds offer us the possibility to add support for almost any script relatively easily
(and at a short notice), since it is much more flexible and powerful than what we have been using till now (XKB).
| |
Specification | *
| |
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 |