MainInclusionReportscim

Differences between revisions 4 and 28 (spanning 24 versions)
⇤ ← Revision 4 as of 2006-01-06 07:43:11 →
Size: 1299
Editor: gnulinux
Comment:
← Revision 28 as of 2008-08-06 16:34:58 → ⇥
Size: 2421
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
  * Input method is required by CJK people. It's a critical issue for them.   * Input method is required by many Asia users, like CJK people and Indian. It's a critical issue for them because they can't input their native language without it.
Line 10: Line 10:
  * Build dependency of ...
  * 		  * Although there are a few candidates for multilingual input method framework such as IIIMF or uim, there are some critical problems in it.
    * uim lacks well supported chinese input methods.
    * IIIMF lacks well supported OSS input methods, lacks comfortable GUI. Some people pointed out security issues in its fundamental design.
  * See also MainInclusionReportScimAnthy
  * See also MainInclusionReportScimHangul
  * See also MainInclusionReportScimPinyin
  * See also MainInclusionReportScimChewing
  * See also MainInclusionReportScimTables
Line 16: Line 22:
  * Fedora, SUSE and Mandriva shipped with SCIM, no critical bugs has been found.
  * There are some binary compatibility issue arround libstdc++. Since libscim will be linked with all Gtk+ (and patched version of Qt) applications via its input method module system, and SCIM is written in C++, an application which is compiled against different version of C++ with SCIM will cause clash. This problem isn't reproduced when you use SCIM via XIM.		   * Fedora, SUSE and Mandriva shipped with SCIM, and no critical bugs has been found in them.
  * There are some binary compatibility issues related with libstdc++. Since libscim will be linked with all Gtk+ (and patched version of Qt) applications via its input method module system, and SCIM is written in C++, an application which is compiled against different version of C++ with SCIM will cause clash. This problem isn't reproduced when you use SCIM via XIM because it is a protocol based communication, not shared link.
Line 23: Line 29:
  * SCIM is just only a framework. Also some major IMEngines (language plugins for SCIM) should be included into main to realize true multilingual input. They are all in universe.
    * scim-pinyin (mainland China)
    * scim-chewing (Taiwan)
    * scim-hangul (Korea)
    * scim-anthy (Japan)
    * scim-tables (Hong Kong)
    * scim-m17n (http://www.m17n.org/m17n-lib/support_input_sum.html)
Line 25: Line 38:

MartinPitt: approved

Main Inclusion Report for sourcepackage

Requirements

  1. Availability:

  2. Rationale:

    • Input method is required by many Asia users, like CJK people and Indian. It's a critical issue for them because they can't input their native language without it.
    • SCIM supports many laungages via scim-pinyin, scim-hangul, scim-anthy scim-tables, scim-m17n and so on.
    • Although there are a few candidates for multilingual input method framework such as IIIMF or uim, there are some critical problems in it.
      • uim lacks well supported chinese input methods.
      • IIIMF lacks well supported OSS input methods, lacks comfortable GUI. Some people pointed out security issues in its fundamental design.

    • See also MainInclusionReportScimAnthy

    • See also MainInclusionReportScimHangul

    • See also MainInclusionReportScimPinyin

    • See also MainInclusionReportScimChewing

    • See also MainInclusionReportScimTables

  3. Security:

    • No security histroy.

  4. Quality assurance:

    • SCIM is well maintained by Jame Su who is employed in Novell.
    • Fedora, SUSE and Mandriva shipped with SCIM, and no critical bugs has been found in them.
    • There are some binary compatibility issues related with libstdc++. Since libscim will be linked with all Gtk+ (and patched version of Qt) applications via its input method module system, and SCIM is written in C++, an application which is compiled against different version of C++ with SCIM will cause clash. This problem isn't reproduced when you use SCIM via XIM because it is a protocol based communication, not shared link.

  5. Standards compliance:

    • The package meets debian-policy and FHS.

  6. Dependencies:

    • All in main.
    • SCIM is just only a framework. Also some major IMEngines (language plugins for SCIM) should be included into main to realize true multilingual input. They are all in universe.

Reviewers

MartinPitt: approved

MainInclusionReportscim (last edited 2008-08-06 16:34:58 by localhost)