https://bugzilla.novell.com/show_bug.cgi?id=259718 mfabian@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cfarrell@novell.com, jw@novell.com ------- Comment #1 from mfabian@novell.com 2007-04-02 03:30 MST ------- No, this has nothing to do with fontconfig. The reason is that sub-pixel hinting is not compiled into freetype2. See the freetype2.spec file: %define enable_subpixel_rendering 0 Set this to 1 and rebuild the freetype2 package if you want sub-pixel hinting. The reason why it is not enabled can be seen in include/freetype/config/ftoption.h: /*************************************************************************/ /* */ /* Uncomment the line below if you want to activate sub-pixel rendering */ /* (a.k.a. LCD rendering, or ClearType) in this build of the library. */ /* */ /* Note that this feature is covered by several Microsoft patents */ /* and should not be activated in any default build of the library. */ /* */ /* This macro has no impact on the FreeType API, only on its */ /* _implementation_. For example, using FT_RENDER_MODE_LCD when calling */ /* FT_Render_Glyph still generates a bitmap that is 3 times larger than */ /* the original size; the difference will be that each triplet of */ /* subpixels has R=G=B. */ /* */ /* This is done to allow FreeType clients to run unmodified, forcing */ /* them to display normal gray-level anti-aliased glyphs. */ /* */ /* #define FT_CONFIG_OPTION_SUBPIXEL_RENDERING */ If sub-pixel rendering is not compiled into freetype2, the results you get when you enable or disable sub-pixel hinting in the runtime configuration (fontconfig) are identical. I cannot do anything about this now → WONTFIX. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.