Font rendering problem in 1.6 branch (fine in 1.5 and master)

[Jeremy Huddleston]

On Jan 17, 2009, at 18:49, 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?
>>
>> http://cgit.freedesktop.org/xorg/xserver/commit/?id=49b93df8a3002db7196aa3fc1fd8dca1c12a55d6
>
> 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.

Well, I don't do anything with the xfree86 ddx, so I can't really test  
that end... unless someone (most likely named Dan Nicholson) is  
willing to backport the changes, I'm gonna vote for the simple  
revert-49b93df8a3002db7196aa3fc1fd8dca1c12a55d6

> I had to hack googleearth to remove the custom libQt so that I could  
> get
> fonts displayed in that application...