Red Hat Bugzilla – Bug 61502
freetype sbit needed
Last modified: 2007-03-26 23:52:02 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; T312461)
Description of problem:
freetype1 has already sbit functionality. but XF86 did not use this
recently I found that, there exists some freetype-sbit patch, and Mandrake
related URL: first author! (for XFree86 4.0.1)
Mandrake patch (adopted against 4.1.0)
Sat Aug 18 17:47:29 CEST 2001 - firstname.lastname@example.org
- add sbit patch to make the freetype module use embedded bitmaps
present in some unicode/cjk TrueType fonts for small point sizes
instead of rendering the outlines.
(original patch xfree-ttf-patch.tar.gz is from
I only adapted it to work with XFree86-4.1.0)
xtt module already have this functionality.
but, the xfs use freetype !!! (xfs is default for RH7.2)
then under this condition, user can't see any embedded bitmap font
with his ttf.
(people workaround this problem by using xtt module)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. a ttf with embedded bitmap fonts in it
2. xfs can't render it's sbits
Created attachment 49585 [details]
this is a mandrake patch
Yu, can you have a look at this, and let me know what you think? If you like,
I can do a test build perhaps with this patch, or at least try to apply it
for testing. Before commiting to using it though, I would want to discuss
the matter with various people in the XFree86 and font related communities to
find out why it isn't applied already.
FreeType2 can handle embedded bitmap, but our freetype-2.0.4-2 can't(bugs).
Xft2 and freetype-2.1.0 combination has no problem with embedded bitmap, but
currently, freetype-2.1.0 has bugs with .ttf files, .ttc is ok.
New X core freetype module is under redevelopment from Juliusz under FreeType2.
So, both Xft2 and core freetype module have no problem with embedded bitmap, but
I am expecting a lot debug works.
Mike Harris will include new Freetype2 backend soon.
I'm closing this as WONTFIX for now, since it is not something that we
are likely to implement or patch into our release ourselves. This type
of functionality truely needs to be done at the XFree86.org level so that
distribution vendors do not need to endlessly patch and maintain such
My understanding from the above, and from XFree86 mailing lists, is that
this will be supported one way or another in a future XFree86 release,
either 4.3.0 or later. So even though I'm closing this WONTFIX right now,
it is possible that it is already present in my CVS builds, or might
be present in 4.3.0 when it is released.
Either way, it is something upstream needs to do.