Font rendering problem in 1.6 branch (fine in 1.5 and master)
Paulo César Pereira de Andrade
pcpa at mandriva.com.br
Sat Jan 17 22:50:34 PST 2009
Keith Packard wrote:
> On Fri, 2009-01-16 at 14:58 -0800, Dan Nicholson wrote:
>> On Fri, Jan 16, 2009 at 2:51 PM, Jeremy Huddleston
>> <jeremyhu at freedesktop.org> wrote:
>> > Ah... I figured it out... It has to do with --enable-builtin-fonts
>> > going from "no" by default in 1.5 to "yes" by default in 1.6 to being
>> > removed in master.
>> > If this is being punted in master, and has been off in previous
>> > releases, should we turn it back off in 1.6 by reverting
>> > 385943e0e97463ce4681a9b6a4a40d7e3c91e51e ?
>> > http://cgit.freedesktop.org/xorg/xserver/commit/?id=385943e0e97463ce4681a9b6a4a40d7e3c91e51e
>> What about backporting 49b93df8a3002db7196aa3fc1fd8dca1c12a55d6 to 1.6?
> I'm good with either pulling the master stuff to 1.6 or reverting the
> 1.6-specific change. But, I'd need to see a patch from the 1.6 branch
> and the promise that someone (or ones) tested it.
> I had to hack googleearth to remove the custom libQt so that I could get
> fonts displayed in that application...
Attached is the patch just "backported" to 1.6 branch (careful,
it is still hot :-)), including the extra change I made in master
Tests I did were:
1. start with a valid font path specified in xorg.conf
2. start without a font path specified in xorg.conf, and non existant
default font path
3. start without a font path specified in xorg.conf, and correct
default font path
4. start with "startx -- -fp incorrect-font-path"
5. start with "startx -- -fp properly-specified-font-path"
6. start with font path specified in xorg.conf, but without fonts in
the directory (i.e.; cd /tmp; mkfontdir; startx -- -fp /tmp)
It worked as expected in all cases (falling back to builtin fonts
if the "real" fixed font could not be found)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7465 bytes
Desc: not available
More information about the xorg