Re: Problems with libXft-2.1.5 and bitmap fonts

--===============0335681213==
Content-Type: multipart/signed; boundary="==_Exmh_921478451P";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit

--==_Exmh_921478451P
Content-Type: text/plain; charset=us-ascii


Around 14 o'clock on Mar 18, Joe Marcus Clarke wrote:

> Sure enough, bitmap fonts no longer load correctly in GNOME.  This seems
> to be directly related to xftfreetype.c rev 1.40.  This always fails for
> the affected fonts:
> 
>  if (FT_Set_Char_Size (face, face->available_sizes[best].x_ppem,  
> face->available_sizes[best].y_ppem, 0, 0) != 0)

Yes, there is a bug in the BDF and PCF loaders which continue to use the 
old 'width/height' elements of the bitmap size structure while the TTF 
loader now uses the new x_ppem/y_ppem elements which are documented as 
describing the nominal size of the strike.

I've sent in a fix which is in FreeType CVS (I believe), so at least the 
problem will eventually go away.

It's all a horrible mess; I'm not sure why FreeType added these new 
elements and changed the semantics of the existing elements.

Clearly what we need to do is have both fontconfig and Xft check the 
FreeType version number and apply suitable kludges to work with known 
versions of the libraries.

-keith



--==_Exmh_921478451P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh version 2.3.1 11/28/2001

iD8DBQFAWhWDQp8BWwlsTdMRAprlAKDVHrpehA9mtdHghUH063RN0aoIuQCePzgy
km5ck6L3Bp6FPIAtiff5krk=
=62QH
-----END PGP SIGNATURE-----

--==_Exmh_921478451P--


--===============0335681213==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
xlibs mailing list
[email protected]
http://freedesktop.org/mailman/listinfo/xlibs

--===============0335681213==--