From owner-freebsd-questions@FreeBSD.ORG Sun Aug 3 19:40:35 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 096E878A for ; Sun, 3 Aug 2014 19:40:35 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C1EA26CD for ; Sun, 3 Aug 2014 19:40:34 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s73JeU2X004038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 3 Aug 2014 13:40:30 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s73JeUxw004035; Sun, 3 Aug 2014 13:40:30 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 3 Aug 2014 13:40:30 -0600 (MDT) From: Warren Block To: Beeblebrox Subject: Re: printcap configuration problem In-Reply-To: <20140803083513.47e21f3b@rsbsd.rsb> Message-ID: References: <1405676044178-5929730.post@n5.nabble.com> <53C919E0.6070008@bananmonarki.se> <20140718183958.1864052a@rsbsd.rsb> <20140727221419.35efb9b0@morena.maps.net> <1406966714419-5934110.post@n5.nabble.com> <1406986762673-5934162.post@n5.nabble.com> <20140803083513.47e21f3b@rsbsd.rsb> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 03 Aug 2014 13:40:30 -0600 (MDT) Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Aug 2014 19:40:35 -0000 On Sun, 3 Aug 2014, Beeblebrox wrote: >> Both cases are for use with a printer that understands PostScript >> natively. A plain LaserJet 2100 does not, > Mine does, it's the 2100tn model, has native ps level-II > http://people.virginia.edu/~cavcomp2/printers/hp/2100/2100.htm > >> Sorry, I don't understand the question. > > Well, my first question was: Why under the current filter setting does > lpd scrape or cut 4 lines from the top? I'm able to get the hard copy > the way I want it to look by increasing the top margin by 4 lines, > save it as a ps file, then lpr the file from command line. lpd does not mess with the input file, although the filter might. I suspect that this just means you need to supply some margin settings for enscript in the psif filter. See enscript(1). > The ghostscript comment was referring to previous discussion - sorry > for the confusion: If I want to print in r: 300 x 300, the only way > that's going to happen is by sending it through ghostscript, if I > understand correctly? No, that's not necessary. PostScript can be told what resolution to use. A filter would have to append that to the start of the PS program, similar to the way duplex can be set. See this thread for an example: https://forums.freebsd.org/viewtopic.php?&t=40651 I have some additional filters on my list of things to add to the Handbook, but no idea when I can work on them. > How could I modify psif so that "lpr -Php2100 -r300 somefile.ps" would > result in 1. check if ps 2. adjust for one of available resolution > options (300 OR 600). -r is already used by lpr. Actually, I have not experimented with passing through options that way, and don't know if it can be done. I'd just define two printers, one for 300DPI and one for 600DPI. The header code is probably going to be <> setpagedevice or <> setpagedevice That might be different on a printer as old as the LJ2100. It can be tested in plain PS files sent directly to the printer.