Path: utzoo!attcan!uunet!mcvax!unido!ecrcvax!johng
From: johng@ecrcvax.UUCP (John Gregor)
Newsgroups: comp.lang.postscript
Subject: Re: image problem
Summary: Me too
Message-ID: <535@ecrcvax.UUCP>
Date: 17 May 88 20:09:53 GMT
References: <11116@sunybcs.UUCP>
Reply-To: johng@ecrcvax.UUCP (John Gregor)
Organization: ECRC, Munich 81, West Germany
Lines: 20
Posted: Tue May 17 21:09:53 1988

In article <11116@sunybcs.UUCP> bowen@sunybcs.UUCP (Devon E Bowen) writes:
>I'm having a problem with printing a bitmap. 
>[ goes on to say that bitmap of one size works while another size doesn't]

Yes, I've had that problem also.  It seems rather arbitrary.  It isn't
the largest (in either or both dimensions) bitmaps or the smallest that
fail.  Padding with 00's or ff's always fix the problem.  If I could
predict which bitmaps caused the problems, I would pad them
automatically.  So far, the only trend I've seen is that one or both
dimensions had a relatively large prime as a factor (but not always).
Could it be some bug in partitioning the bitmap?  More likely it's just
another example of how humans impose patterns on random data.

At least I know I'm not the only one...

-- 
pqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpqpq
bdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbdbd

John Gregor                                     johng%ecrcvax.UUCP@germany.CSNET