MainInclusionReportscim

Differences between revisions 3 and 15 (spanning 12 versions)
⇤ ← Revision 3 as of 2006-01-06 07:33:50 →
Size: 1020
Editor: gnulinux
Comment:
← Revision 15 as of 2006-01-06 10:22:27 → ⇥
Size: 1786
Editor: gnulinux
Comment:
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
  * Input method is required by CJK people.
  * Build dependency of ...
  * 		  * Input method is required by CJK people. 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
Line 14: Line 17:
  * SCIM is well maintained by Jame Su who is emproyed by Novell.
  * 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.		   * 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.
    * http://www.scim-im.org/wiki/faq/gtk_gnome/why_firefox_mozilla_acrobat_reader_7_other_gtk_2_based_apps_can_not_be_installed_started

Main Inclusion Report for sourcepackage

Requirements

  1. Availability:

  2. Rationale:

    • Input method is required by CJK people. 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

  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.

Reviewers

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