Toby Blake wrote:
I agree to a certain extent, but I have my doubts about the
overall readyness of xprint for serious usage.
I say this because I've posted to this list in recent months
about
- Augment_Printer_List not working
[..]
At least you seem to know /something/ about the inner workings of
xprint. This knowledge may be invaluable for constructing the
user-level doc that we need.
This user-level doc should begin (as any good user-level doc
should) with some existential questions: why does this program
exist, what does this program do, and why you should use it.
Do you (or does anyone) happen to know why xprint exists at all?
This is a serious question. xprint is only needed for multilingual
prints from Mozilla & Co.; but why is a server needed for this?
Why is it a bright idea to involve the X server in printing? This
is not at all meant sarcastically, I just do not know why a
program running in X (like Mozilla) shouldn't be able to produce
its own Postscript without involving the X server; as I understand
it, the X server's job is to produce pixels on the screen, not to
generate Postscript code.
There is an alternative, called freetype printing. It does not
work as well as xprint does (when you have negotiated xprint's
quirks) but it could (I suppose) be improved. Does anyone know why
the freetype development path has been abandoned (by whom? the
Mozilla folks? Debian? I don't know) and the xprint path chosen
instead?
Regards, Jan
_______________________________________________
Xprint mailing list
[email protected]
http://mozdev.org/mailman/listinfo/xprint
