[vox-tech] Re: Printouts cliped, how to fix?

[Kenneth Bloom]

I appologize if this hits the list too many times. I've never used geckomail to respond to vox-tech before, and I don't think it handled the reply-to in an 
expected way.

CUPS doesn't seem to use printcap to store anything other than just the names of the printers, so hearing that printcap doesn't have any useful 
information in it leads me to believe that he is using CUPS. Filter information may be found someone else, but I don't know where that is. Try going to 
http://localhost:631/ and verifying how well your printer settings in the computer match the physical situation of your printer.

> ---ORIGINAL MESSAGE---
> Date: Wed, 18 Sep 2002 00:28:35 -0700
> To: vox-tech@lists.lugod.org
> Subject: Re: [vox-tech] Printouts cliped, how to fix?
> From: Peter Jay Salzman <p@dirac.org>
> Reply-To: vox-tech@lists.lugod.org
> 
> begin Ryan <ryan@mother.com> 
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > On Tuesday 17 September 2002 11:56 pm, Ryan wrote:
> > > On Tuesday 17 September 2002 11:52 pm, Peter Jay Salzman wrote:
> > > > ryan,
> > > >
> > > > what happens when you send text to the raw device?
> > >
> > > loads a page, doesn't print anything.
> > 
> > for 10 minutes....
> 
> i can't imagine printing being any faster by accessing the raw device;
> you've bypassed the spooler.  something wierd is happening.
> 
> does messages say anything wierd about parport driver?
> 
> > then it printed without mucking up the edges.
>  
> ok, this is what i thought it would do.
> 
> grasping at straws...
> 
> maybe you can rig up an input filter to make a copy of the job once it's
> spooled.  queue the job with lpr and compare the post spooled version
> with the original job.  prolly a fruitless endeavour, but all i can come
> up with.
> 
> are you using cups or lprng?  i've never used either one.  maybe they do
> some filtering not explicitly mentioned in printcap?
> 
> pete
>