🚀 go-pugleaf

In article <974@ark.cs.vu.nl> kleef@cs.vu.nl (Patrick van Kleef) writes:
 >In article <1987Apr10.153033.9373@gpu.utcs.toronto.edu> lharris@gpu.utcs.toronto.edu (Leonard Harris) writes:
 >>
 >>Hi.
 >>Does anyone have the documentation for the image processor that was posted
 >>to the net a while back.  In particular, how does one read in non-.IM files?
 >>
 >>thanks
 >>/leonard
 >
 >The reason I didn't sent them is that they're 'rather Dutch' and I
 >didn't feel like translating them. The main documentation file,
 >including the IM-picture file format, is huge and it would take
 >me days to work it thru and translate it.
 >
 >Sorry about that, it's just one of those things.
 >
 >If there's any1 out there who's willing to translate them (a job
 >for a foreign student Dutch?) I'd be willing to upload it to this
 >Vax and then mail it on.
 >
 >Paul 'Red' Molenaar

  Try assuming that a .IM file (which is 65536 bytes long) is 256 x 256
pixel elements.  Far as I can tell, this is, in fact, the format used.
(No color, just one byte for each pixel at 256 gray scale levels.)

  A friend of mine whipped up a program which will read NEO, PI?, PC?
or TNY picture files and convert them to .IM form.  He had to drop some
of the width to get everything into IM format without having to do
pixel compression so he dropped an equal number of pixels from the start
and the end of each scanline.  It's a bit disapointing for a few pictures,
but it works well for an "average" picture and is fairly quick.

  If I get enough interest, I'll try to talk him into letting me put it
out on the net.

(Hows that for a quicky translation Paul?)

  (And I don't even know Dutch... :)

--- 
John Stanley (john@viper.UUCP)
Software Consultant - DynaSoft Systems
UUCP: ...{amdahl,ihnp4,rutgers}!{meccts,dayton}!viper!john