Thanks, Jungshik Shin.
I'v been watching this talk with care :) because nobody gave me an answer, so I think it's a system- or environment-specific problem. > On Sat, 17 Nov 2001, Keith Packard wrote: > > Around 16 o'clock on Nov 17, Tomohiro KUBOTA wrote: > > > Unicode truetype Japanese fonts. I found that > > > XftDrawString*() cannot display characters if these > > > fonts are used in XFT_PIXEL_SIZEs of 10, 11, 12, 13, > > > 14, 15, 16, 17, 20, and 21. Curiously enough, the > > > Kochi fonts include built-in bitmap fonts for these > > > sizes. I imagine > > > > Sorry, it's an easy bug to fix (once I had a font with > > bitmaps to try it out). It doesn't make Xft use the > > embedded bitmaps, but at least it displays the glyphs > > now. I've already committed this fix to CVS so it will > > be in XFree86 4.2. I'll make the new Xft library use > > embedded bitmaps when not rendering with anti-aliasing. It sounds strange to me. Is it a bug of XFT module (XFree4.1.0)? Is freetype (or xft) module irrelevant with this problem? I think the bug could be inside of freetype2 module. Currently I'm using both Linux(Mand8.1 distro) and FreeBSD on single machine. With default installation of Mand8.1, all fonts on KDE(2.2.1)/Qt(2.3.1) are rendered ugly (really ugly) with AA, but (I was surprised) the invisible range of some TTC fonts are visible without any modification. After the first installation, I visited some sites and found an interesting article. <QUOTE> ... There is a problem with some anti-aliased true type font, they are ugly. It is not the fault of Mandrake: the bytecode interpreter has been deactivated in freetype2 by its developers, for patent infringement reasons, since 2.0.3 version. However, you can reactivate it by hand : 1. Install freetype2-2.0.4-1mdk.src.rpm (all files are then in /usr/src/RPM subfolders) 2. Unpack freetype-2.0.4.tar.bz2 3. Edit the include/freetype/config/ftoption.h file 4. Search the line containing TT_CONFIG_OPTION_BYTECODE_INTERPRETER and replace the #undef by #define 5. Retar and bzip2 the folder freetype-2.0.4 5. Recompile using the same freetype2.spec file (in /SPECS folder, type rpm -ba ./freetype2.spec). Before you can edit the spec file to change the compile version number to 2mdk. 6. Reinstall the generated rpm files and restart X server 7. Say : OOOhh, how beautiful it is ! (http://elektron.its.tudelft.nl/~rbos36/mdkfreetype2.html) ... </QUOTE> Of course I reinstalled freetype2 and got expected AA effect as on FreeBSD4, BUT with the bug. After that, with more experiments I got convinced that freetype modules make the problem. My guess is TRUE? -- Jaewoo Kim _______________________________________________ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
