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

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


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

On Wed, 2005-12-21 at 15:18 +0100, Juliusz Chroboczek wrote:
> > It's not terribly useful for fontconfig or libXft, where it is useful i=
s
> > 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.
>=20
> Well, that you already can do, using fstobdf (it's still in the tree,
> right?).  Now, if there are clients that still make use of ad hoc font
> properties, they should be shot.

Right, we can easily generate a BDF file, but without some place to
store the properties that only BDF exposes in the TTF file, we'll lose
some data. It's probably not terribly important data, but I think saving
all of it is a prerequisite for switching from BDF to SFNT files as the
canonical delivery and archival mechanism.

-keith


--=-LfhmzjeqTZLoLZRht90G
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)

iD8DBQBDqYrOQp8BWwlsTdMRAr8fAJ4jkEoXYroHUvbBdbQWvMMy5SgWzwCfWORG
c0TTmjfHGvVYn4SaPgK2FjQ=
=+szu
-----END PGP SIGNATURE-----

--=-LfhmzjeqTZLoLZRht90G--



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

--===============0762357484==--