--===============0378693897==
Content-Type: multipart/signed;
boundary="nextPart6068459.Ik92gkVYGg";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart6068459.Ik92gkVYGg
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

I'm trying to give krdc a little care, especially on the RDP side. One of t=
he=20
new features of rdesktop is the ability to use local devices on the remote=
=20
system, such as having sound played locally (through /dev/dsp) and using th=
e=20
local print spools.

There are a couple of issues associated with printing though. The first is=
=20
knowing what printers are actually available on the system - it looks like=
=20
KMPrinterList is a candidate, but it comes with a beefy warning against usi=
ng=20
it in application code. It would also be nice to know what drivers are need=
ed=20
for each print queue, especially if the answer isn't "just use postscript".

Any suggestions?

Brad

--nextPart6068459.Ik92gkVYGg
Content-Type: application/pgp-signature

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

iD8DBQBDooOOGwwszQ/PZzgRAop5AKCF6XDe935QH7eoyYXB99L4ezbUvACePL4E
dPHNxPS3PO70sZ4lhjtOd+k=
=7q4i
-----END PGP SIGNATURE-----

--nextPart6068459.Ik92gkVYGg--

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


>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


--===============0378693897==--