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

--===============0645928970==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-i6NhyEC2diBwQ+uP7SsZ"


--=-i6NhyEC2diBwQ+uP7SsZ
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Fri, 2005-12-09 at 01:07 +0100, Werner LEMBERG wrote:

> Hmm, why not simply adding a special `BDF ' table which holds all
> properties?  This should be straightforward, and you get lossless
> conversion.

Yes, this was my plan. I got side-tracked before I managed to implement
it though.

I need this + a utility to regenerate BDF files from the TTF so I can
validate a lossless round-trip for the existing BDF files.=20

If anyone wants to pick up this little project, I can assure them that
once working, I'll delete all of the BDF files from the X.org CVS
repository and never ship them again, and we'll also deprecate all of
the horrid BDF-based font tools. Note that the X server already happily
loads these .TTF fonts, and will even automatically transcode them to
generate any of the supported encodings, so we actually gain
functionality, reduce disk space usage, reduce code size and eliminate
build-time font compilation. There aren't many projects offering this
kind of win-win-win-win proposition...

-keith


--=-i6NhyEC2diBwQ+uP7SsZ
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)

iD8DBQBDmNPmQp8BWwlsTdMRAorYAJ9yRqY/fR5lU5h7K9Fmh4YC0/4Q3QCgwSzL
OULZ1jFtzbmYS+/sXBLyy5k=
=s4j9
-----END PGP SIGNATURE-----

--=-i6NhyEC2diBwQ+uP7SsZ--



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

--===============0645928970==--