The ebuild depends on media-fonts/intlfonts, and in addition on several more fonts, if some LINGUAS are enabled. All of these fonts are bitmap fonts, for which there are truetype alternatives. Moreover, LINGUAS are used only to decide the fonts to depend on. I think that uim ebuild shouldn't decide which fonts are required - especially as none of the fonts in the ebuild are actually required (I am running a system without bitmap fonts without issues). A suggestion: - drop all font dependencies - drop linguas_* use-flags - drop the xft use-flag, and supply --with-xft unconditionally (libXft is already an unconditional dependency) - write fonts recommendations in pkg_postinst()
Sorry, "intlfonts" above should be "font-sony-misc".
I've considered font removal and try to check the code. I think it's difficult (or too early) to remove fonts dependss. uim/xim/convdisp.cpp has the follwoing lines to hardcode font names: > const char *fontset_zhCN = "-sony-fixed-medium-r-normal--16-*-*-*-c-80-iso8859-1, -isas-fangsong ti-medium-r-normal--16-160-72-72-c-160-gb2312.1980-0"; > const char *fontset_zhTW = "-sony-fixed-medium-r-normal--16-*-*-*-c-80-iso8859-1, -taipei-fixed-medium-r-normal--16-150-75-75-c-160-big5-0"; > const char *fontset_ja = "-sony-fixed-medium-r-normal--16-*-*-*-c-80-iso8859-1, -jis-fixed-medium-r-normal--16-*-75-75-c-160-jisx0208.1983-0, -sony-fixed-medium-r-normal--16-*-*-*-c-80-jisx0201.1976-0"; > const char *fontset_ko = "-sony-fixed-medium-r-normal--16-*-*-*-c-80-iso8859-1, -daewoo-gothic-medium-r-normal--16-120-100-100-c-160-ksc5601.1987-0"; and without font-jis-misc, uim-xim output "Critical: XCreateFontSet failed!". (Actually, it's not so critical.. it works fine even this "critical" output.) Also notice that even if USE="xft" (and so --with-xft), /usr/share/uim/im-custom.scm set xft font future default to be disabled: > (define-custom 'uim-xim-use-xft-font? #f > '(xim xim-preedit) > '(boolean) > (N_ "Use anti-aliased fonts for Over-the-Spot/Root-Window preedit") > (N_ "long description will be here.")) When it came to default to be enabled, I'd agree to drop font deps, but not now.
(In reply to comment #2) > and without font-jis-misc, uim-xim output "Critical: XCreateFontSet failed!". > (Actually, it's not so critical.. it works fine even this "critical" output.) I can't reproduce this message, did you just run uim-xim? I tried running LANG=ja_JP.UTF-8 uim-xim --direct, and also running midori with same LANG, selecting xim input afterwards, and typing some Japanese input. No message from uim-xim. I set uim-xim-use-xft-font? to #f before doing all that. > When it came to default to be enabled, I'd agree to drop font deps, but not > now. Non-default Xft looks like legacy to me, maybe ask upstream?
(In reply to comment #3) > (In reply to comment #2) > > and without font-jis-misc, uim-xim output "Critical: XCreateFontSet failed!". > > (Actually, it's not so critical.. it works fine even this "critical" output.) > > I can't reproduce this message, did you just run uim-xim? I tried running > LANG=ja_JP.UTF-8 uim-xim --direct, and also running midori with same LANG, > selecting xim input afterwards, and typing some Japanese input. No message > from uim-xim. I set uim-xim-use-xft-font? to #f before doing all that. strange... $ vi ~/.uim.d/customs/custom-uim.scm (set uim-xim-use-xft-font? to #f) $ sudo emerge -C font-jis-misc $ env -i HOME=$HOME DISPLAY=$DISPLAY LANG=ja_JP.UTF-8 uim-xim $ (another shell) XMODIFIERS=@im=uim xterm Turn on uim and type something arise this result: uim <-> XIM bridge. Supporting multiple locales. Using full-synchronous XIM event flow Supported conversion engines: direct (*) tutcode (ja) anthy-utf8 (ja) XMODIFIERS=@im=uim registered, selecting anthy-utf8 (ja) as default conversion engine Critical: XCreateFontSet failed! Critical: XCreateFontSet failed! Critical: XCreateFontSet failed! ..and "uim-xim --engine=direct" didn't show the critical message above. > > When it came to default to be enabled, I'd agree to drop font deps, but not > > now. > > Non-default Xft looks like legacy to me, maybe ask upstream? Yes. This part is upstream issue.
Still cannot reproduce the error. Oh well, I guess that one needs an actual legacy X application for that, like xterm.
(In reply to comment #5) > Still cannot reproduce the error. Oh well, I guess that one needs an actual > legacy X application for that, like xterm. aha, may be yes. The code is in xim/*.c Since midori is gtk based application, it might use gtk im module instead of xim...
