fontconfig commands

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


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

Hi,

the fontconfig (as opposed to libfontconfig) package is shipped with
three commands viz
fc-cache
fc-list
fc-match

These commands are currently used by the fontconfig-test suite and the
API used by these commands are on the way to being standardised.

Also, these commands are not required by applications at runtime (the
application developer will use the fontconfig api provided to achieve
similar functionality as provided by libfontconfig), and are more user
commands.
Do these commands really need to be in the spec merely because they are
used in the test-suite ?=20

-- pradosh


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

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

iQEVAwUAQ6EVl3/NtiPREx7AAQInIggAmLNr0D0dkPvedc8gB8LiGzWJs5RC6lwb
9lutEogfmENgaiH71k+ou9IvqBk0lxAq40wOa1M4UduljIH33B/Jje2Se+86kgx9
MO0uigqJ/leHkh4xH9X3fciwMPPoM3QFnNXpdgPAfvcuev+nWKKYXpFbsVoFZKUV
3k9u6ExMjmXiTYUrKjuf3l8mFxmSCQWla4eTWAZFHTj0YRXKl2KWcyHJcuapHLmJ
OgHxauV5hjee4BTt0RFlWkQX2nKea8q5v+kUSM9YkvcvioQg0IdUH7x+qhNB6WRu
uyZgICD3oWbaMQHEa7WS2MAtU7xhdY8/3Y14bxzJ0w939IH7UKC+oQ==
=Ul4M
-----END PGP SIGNATURE-----

--=-HDQuoa2JF97es3GCYrhy--


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

_______________________________________________
lsb-spec mailing list
[email protected]
http://mail.freestandards.org/mailman/listinfo/lsb-spec

--===============1983118429==--