MainInclusionReportscim
Differences between revisions 7 and 18 (spanning 11 versions)
1643
Comment:
|
2070
|
Deletions are marked like this. | Additions are marked like this. |
Line 12: | Line 12: |
* IIIMF lacks well supported OSS input methods, lacks comfortable GUI. * Build dependency of ... * |
* IIIMF lacks well supported OSS input methods, lacks comfortable GUI. Some people pointed out security issues in its fundamental design. * See also MainInclusionReportScimAnthy |
Line 20: | Line 19: |
* 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. | * 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 26: | Line 25: |
* SCIM is just only a framework. Also some major IMEngines should be included into main to support true multilingual input. * scim-pinyin (Chinese) * scim-hangul (Korean) * scim-anthy (Japanese) * scim-m17n (http://www.m17n.org/m17n-lib/support_input_sum.html) |
Main Inclusion Report for sourcepackage
Requirements
Availability:
http://archive.ubuntu.com/ubuntu/pool/universe/s/scim, available for all supported architectures
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
Security:
- No security histroy.
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.
Standards compliance:
- The package meets debian-policy and FHS.
Dependencies:
- All in main.
- SCIM is just only a framework. Also some major IMEngines should be included into main to support true multilingual input.
- scim-pinyin (Chinese)
- scim-hangul (Korean)
- scim-anthy (Japanese)
scim-m17n (http://www.m17n.org/m17n-lib/support_input_sum.html)
Reviewers
MainInclusionReportscim (last edited 2008-08-06 16:34:58 by localhost)