Shaun Jurrens on Sun, 10 Feb 2002 23:17:29 +0100 (CET)(envelope-from owner-apsfilter-help@apsfilter.org)


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

Re: scaling problems with 7.2.1


On 06-Feb-02 Michael Loßin wrote:
#>On 06-Feb-02 Shaun Jurrens wrote:
#>> I upgraded recently from apsfilter 5.2.1 (iirc) to 7.2.1 and since then I
#>> seem to have some wierd scaling problems.  I'm using the fbsd port and 
#>> AFPL Ghostscript 7.03 (2001-10-20) on a HP 4L printer.
#>
#>Did you really change just from 5.2.1 to 7.2.1, or did you also
#>update ghostscript or some other important package?

	I updated ghostcript from a 6 version to 7.03
	(ghostscript-afpl-nox11-7.03_1) as well.
#>
#>> The basic problem appears as huge scaling of printed documents, i.e. a
#>> printjob from a remote (also 4.5 fbsd) machine from netscape, is printed
#>> side-by-side on numerous A4 pages.
#>
#>I have a hard time picturing what you mean here...

	Ok, the printouts are 4x's larger than normal, i.e. i get only half of
	the left side of a page and that is printed on 2 A4 pages, really
	huge.

#>
#>Does that apply only to print jobs from Netscape? What happens
#>if you print to a file (from within netscape) and view that file
#>in ghostview?

	It's the same with star office as well.  The print server has no X so
	I can't really view it there.  I could install ghostview on the
	workstation making the requests and check it out.
#>
#>Do the same problems occur when you print directly on the server
#>machine? Does "aps2file -D ..." give any hints there?
#>
	I played around with aps2file a little, but haven't taken the time to
	set it up in printcap yet.
#>
#>> PRINTER='ljet4d'
#>> PAPERSIZE='a4'
#>> METHOD='auto'
#>> QUALITY='high'
#>> COLOR='mono'
#>> RESOLUTION='600x600'
#>
#>I don't know if the "ljet4d" driver is the correct one for the
#>LaserJet 4L -- the "L" editions are known to be very picky.
#>Maybe the "gimp-print/stp" driver (or "omni" if you are very
#>adventurous) can help.
#>
#>(The fact that gimp-print has separate drivers for the LJ4 and
#>LJ4L is an indication that you might be using the wrong driver.)

	Strangely enough, apfilter's test print works perfectly with that
	driver.  It also worked with previous versions of apsfilter. If it's
	of any consequence, using just "ljet4" gives the same results.  I don't
	know enough about the gimp drivers to have used them yet, but I'll
	give that a go too, if my other experiments don't work.
#>
#>> I've try adjusting resolutions, gray/mono settings, auto/raw setting (raw
#>> just spits out garbage) and even hacking a little in apsfilter itself,
#>but
#>> I haven't taken the time to do a lot of debugging "echos" yet, to see why
#>> it's having problems with the remote printing headers.  I'm using the
#>stock
#>> fbsd lpd's on both machines.  I've tried running lpd -d on the printer
#>> "server" and see no errors there.  The outdated info on debugging
#>apsfilter
#>> (uncomment "#set -x") no longer applies.  I haven't run out of things to
#>> try yet, but I've done quite a bit, including reading the handbook and
#>FAQ
#>> and searching the ML archives.  Perhaps someone has an idea here.
#>
#>You can still add "set -x" in a single at the top of the script,
#>but I assume that it's rather a ghostscript/driver issue here.

	I can see the ports have been updated recently for ghostscript, so
I'll probably take the easiest solution first and update that, then go from
there.  I wish this was in perl, perhaps I'll get irritated enough to
re-write it (apsfilter, that is).  In any case thanks for the help.  It
took me a while to answer, because I forgot to say CC: me, because I'm not
on the list.
#>
#>
#>Michael

-- 
Yours truly,

Shaun D. Jurrens
shaun@shamz.net
shamz@freenix.no

IRCNET nick: shamz #chillout #unix #FreeBSD