Bug 77 - XftGlyphFontSpecRender assumes that all fonts have the same format
Summary: XftGlyphFontSpecRender assumes that all fonts have the same format
Alias: None
Product: xorg
Classification: Unclassified
Component: Lib/Xft (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Keith Packard
QA Contact:
Depends on:
Reported: 2003-04-25 11:46 UTC by Nalin Dahyabhai
Modified: 2011-10-15 17:14 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Nalin Dahyabhai 2003-04-25 11:46:06 UTC
If XftGlyphFontSpecRender() (called via XftDrawCharFontSpec()) is given a set of
glyphs which specifies multiple fonts, it assumes that each font has the same
format as the font used for the first glyph, and uses the first font's format
when making the composite request using XRenderCompositeText().

If you mix bitmap (or monochrome) fonts with antialiased fonts, this causes
glyphs to be rendered incorrectly when the font's glyph set is passed to XRender
with the wrong format.
Comment 1 Keith Packard 2003-04-25 11:54:05 UTC
It should use the 'most complicated' format of those presented in the list, but
the Render extension doesn't have the right semantics for doing addition from an
alpha-only picture to an RGBA picture in this case.  That means combining
monochrome or simple anti-aliased text with per component text must be done with
a  simple alpha-only format.
Comment 2 Bugzilla Administrator 2003-05-16 19:36:05 UTC
Actually, it needed to be A8 if mixing ARGB32 with other formats as the
precompositing step inside the server doesn't do the right thing when mixing
ARGB32 with A8.
Comment 3 Jeremy Huddleston Sequoia 2011-10-01 14:12:46 UTC
Mass update: Close all bugs resolved over one year ago.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.