Hi, On Sun, Dec 18, 2011 at 12:26:51PM +0800, Yao Wei wrote: > Package: im-config > Version: 0.7 > Severity: wishlist
Sure. > Tags: l10n This is usually used for marking translation patch/bug. > Please help us adding HIME input method editor as another engine. This > package will be uploaded soon. (#652022) Checked http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=652022 I do not understand "some arguments happened". Who was involved? gcin upstream? HIME upstream, QA team, previous gcin maintainer? > It is a Chinese input method framework forked from gcin. Although it > supports anthy IM, its name does not mean that it is a Japanes-only > input framework. I did not even realize "Hime (姫) is the Japanese word for princess." > By the way, I would like to know why GTK2 immodule and GTK3 immodule > needs to be co-exist to change GTK_IMMODULE to its IME. It is unfortunate result of GTK decision to use the same environment variable to enable GTK immdule for GTK2 and GTK3. If they had chosen the similar choice like Qt4, I did not need to do this. If one exists but not the other one, then you enable GTK immdule without supporting immdule. Since we do not expect GTK2 apps to be purged for wheezy (unlike Qt3), I should not create situation with likely breakage. People can override it by manual configuration but default should serve most people without much tweaking. Whoever install these system, the added space for additional package is small. We are talking desktop even for LXDE. > # vim: set sts=4 expandtab: > IM_CONFIG_SHORT="activate Chinese input method (hime)" > > IM_CONFIG_LONG="Recommended for Gnome: hime, > hime-gtk3-immodule\n\nRecommended for KDE: hime-qt4-immodule" I am rephrasing these now. So I will make it consistent. One big question is the order of these IMs. Currently 20 ibus 22 fcitx 24 uim 48 scim missing Qt4 support etc. (Well there is via bridge ...) 50 gcin it was Chinese only but now I know it has some anthy usage. ... If gcin maintainer asks with explanation, I think I need to move gcin between uim and scim. Question is where should HIME should go in this order. (I am thinking 26, it is still new but there is someone caring it. gcin should be 28 if new maintainer asks.) As for your ITP, package description needs to be revised. This is substandard. You have to provide proper short and long description. http://www.debian.org/doc/manuals/developers-reference/best-pkging-practices#bpp-desc-basics “If you are having problems writing your description, you may wish to send it along to <debian-l10n-engl...@lists.debian.org> and request feedback.” Also, you need to explain upstream situation and difference to me separately so I have better understandings. Once you finish all these, let me know. I will update package. Osamu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
