" printing for perl applications.
> >
> >
>
> I am not so sure Net::* is the correct place for an CUPS api (even if
> that is a nice thing) bridge, if it was a Net::IPP makes sense but CUPS
> is not only Net related.
>
> Arthur
>
--
//\\
|| D. Hageman<[EMAIL PROTECTED]> ||
\\//
super popular format,
but I always try to keep an eye on the future (while attempting to keep
one eye on the ground so I don't stuble over my own two feet).
Thanks for your input guys, I am starting to understand how the process works!
--
//\\
|| D. Hageman<[EMAIL PROTECTED]> ||
\\//
. I guess one can't really predict
the future and if later this prediction becomes true and people do such a
thing and more 'group'ing namespace can be considered then. I am okay
with the namespace XML::TEILite.
--
//\\
|| D. Hageman<[EMAIL PROTECTED]> ||
\\//
ILite
Any response is greatly appreciated.
--
//\\
|| D. Hageman<[EMAIL PROTECTED]> ||
\\//
packages to be clustered.
--
//========\\
|| D. Hageman<[EMAIL PROTECTED]> ||
\\//
Name: David Hageman
Email : [EMAIL PROTECTED]
Homepage:
User-ID : DHAGEMAN
Perl Modules: Potential MathML module, SAX filter for embeding perl
vars/code(?) into XML docs [web applications], Panda PDF wrapper?
--
//\\
|| D