Re: uim modules in SUSE 10.1
Mike FABIAN <[email protected]>
| Newsgroups | gmane.linux.suse.m17n |
|---|---|
| Message-ID | <[email protected]> |
UTUMI Hirosi <[email protected]> : > Mike FABIAN <[email protected]> wrote: >> https://bugzilla.novell.com/show_bug.cgi?id=113081 >> +uim-module-manager --register pyload anthy canna skk >> tcode tutcode hangul viqr ipa-x-sampa latin > > Canna is a server and I don't want to run unused servers. You don't need to run it of course. If you don't run canna, the entry "uim-canna" which appears in the scim input method selection menu doesn't work if you select it. But apart from that there is no problem. > There is scim-canna for Canna users, so I want to remove > canna from UIM. > I know most users choose Anthy for Japanese input, > and they don't want to install Canna for UIM. > uim-{pinyin,hangul,viqr} are not well tested. > I think they should be covered by uim-m17nlib. > You know m17nlib includes pinyin/hangul/viqr engines, and > Handa-san (the author of m17nlib) is a cool developer. But that is the same argument as "disable m17n support in uim because m17n support in scim is better". Usually I try to enable *everything* in the hope to make everybody happy. > I think this one is better for SUSE 10.1: > uim-module-manager --register anthy m17nlib skk I think for SuSE 10.1, I'll split several new sub-packages out of the main uim package: uim-anthy uim-m17n uim-canna If we do it this way, uim-m17n can have uim-module-manager --register m17nlib in the %post script and uim-module-manager --unregister m17nlib in the %postun script. Same for "uim-anthy" and "uim-canna". This will avoid that the main uim package requires m17n and canna. Currently the main uim package requires libcanna.so.1 but not the canna server itself. When uim-canna is a seperate package, it is no problem for uim-canna to require the complete canna server. And the user can choose which modules of uim he wants to install and use. -- Mike FABIAN <[email protected]> http://www.suse.de/~mfabian -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]