Re: [ft] Creating an [OT]TF font from BDF font

--===============0291041490==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-MyHUosMQ9uNdVO2ZVzk6"


--=-MyHUosMQ9uNdVO2ZVzk6
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2005-12-14 at 22:16 +0100, David Turner wrote:

> I'd like to know the following:
>=20
> - is this feature useful for fontconfig / libXft ? Or should we yank
> it from
>   FreeType ?

It's not terribly useful for fontconfig or libXft, where it is useful is
in converting sfnt back into BDF files in case you want to take a font
and use it with old non-TTF supporting X servers.

> - I don't understand completely the difference between atoms and
> non-property
>   strings. Aren't these the same things ? Why distinguish them then ?

All I care about is regenerating a matching BDF file; I'd like to see
whatever it takes to preserve every aspect of the original font files.

-keith


--=-MyHUosMQ9uNdVO2ZVzk6
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBDoLnpQp8BWwlsTdMRAsSIAKCFh6PpOpNjuuKSRF0QxLnVgwQaeQCfQ45D
2WzjqfhAi37Isa/hdAJ01UE=
=z3vY
-----END PGP SIGNATURE-----

--=-MyHUosMQ9uNdVO2ZVzk6--



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

_______________________________________________
Freetype mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype

--===============0291041490==--