[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: how to get MOzilla to print to Cups printer through kprint



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 27 May 2003 08:06 pm, Donald Spoon wrote:
> Jeremy Petzold wrote:
> > On Tuesday 27 May 2003 08:08 pm, Donald Spoon wrote:
> >>Jeremy Petzold wrote:
> >>>how can you get mozilla to print to the cups printer I have? be it
> >>>through kprint or directly through cups? I could not find any info on
> >>> it in mozilla help so I am hoping that one of you may have had an
> >>> experience with this.
> >>>
> >>>thanks,
> >>>
> >>>Jeremy
> >>
> >>If you have the "cupsys-bsd" package installed, then the
> >>"Default/Postscript" selection in Mozilla works just fine.... for me.
> >>Recent changes in X (from testing) have introduced Xprint on my system,
> >>which I am just  starting to expore.  It is supposed to interface
> >> recent versions of Mozilla with CUPS too, but I don't know enuf about
> >> it to be able to advise you...sorry.
> >>
> >>Cheers,
> >>-Don Spoon
> >
> > doe sit just send the data directly to cups?
>
> I would guess so... I don't have anything else installed on my system
> that would accept it! (Like lprng, lpr, etc).
>
> I don't really know the physical routing the Mozilla stuff takes, but it
> eventually winds up in the CUPS printing system without any extra effort
> on my part.  Just hit "print" in Mozilla, accept the "default/postscript
> printer" and it does it's thing...
>
> -Don Spoon-

I don't use mozilla much but I know you can edit the properties on the 
default ps printer to 'kprinter', assuming you have kdebase & cups 
installed. AFAIk, the lpr command is present in cups without having 
cupsys-bsd, using 'lpr <filename>' with a properly configured cups printer 
here works also.
- -- 
Greg Madden
Debian GNU/Linux
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE+1FJfk7rtxKWZzGsRAujPAJ9QeJUSzytg0fKwHZeea0vHEYpU8wCdFBs7
sG3mAXgTMG7M6wdHu6lJ7Vc=
=L/XB
-----END PGP SIGNATURE-----



Reply to: