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

--===============0599617181==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-18yYS8GWS7PCjZpFP/UZ"


--=-18yYS8GWS7PCjZpFP/UZ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Tue, 2006-01-17 at 15:12 -0800, George Williams wrote:

> I was told so when I implemented them in fontforge. But I wasn't in the
> initial discussions so I'm not the best source.

I also recall discussions which discovered that the .otb extension was
otherwise unused in most of the world. It doesn't matter at all to me; I
ask FreeType to try and open the font, completely ignoring the extension
has proven a valuable property, although it does sometimes challenge the
FreeType font file handling code with 'unusual' file data.

--=20
[email protected]

--=-18yYS8GWS7PCjZpFP/UZ
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)

iD8DBQBDzX3UQp8BWwlsTdMRAv5cAKC60iUJs9h5RjdxkwB1tmaK4TKnhgCgkcfj
Mr2IQvX3bJ25iGUnaBBataA=
=LtwA
-----END PGP SIGNATURE-----

--=-18yYS8GWS7PCjZpFP/UZ--



--===============0599617181==
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

--===============0599617181==--