Feature roadmap/SCIM: Difference between revisions
Jump to navigation
Jump to search
(Automated import of articles) |
No edit summary |
||
(4 intermediate revisions by 3 users not shown) | |||
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. 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. |
||
⚫ | |||
|Specification= |
|Specification= |
||
* 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>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 in the relevant locales |
|||
⚫ | |||
** 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 stuff |
|||
* Implementation of [[OLPC_Nepal_Keyboard]] |
|||
⚫ | |||
** Simplified Chinese: |
|||
*** The following Fedora packages provide support for the Chinese requirement: |
|||
**** scim-pinyin |
|||
**** scim-fcitx (''To be verified with the team in China'') |
|||
** Nepali support is implemented by the following Fedora package |
|||
*** m17n-contrib-nepali |
|||
|Owners=Sayamindu |
|Owners=Sayamindu |
||
|Priority=1 |
|||
|Helps deployability=yes |
|||
|Target for 9.1=yes |
|||
}} |
}} |
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 |