Blob Blame History Raw
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML><HEAD><TITLE>Lispmtopgm User Manual</TITLE></HEAD>
<BODY>
<H1>lispmtopgm</H1>
Updated: 06 March 1990
<BR>
<A HREF="#index">Table Of Contents</A>

<A NAME="lbAB">&nbsp;</A>
<H2>NAME</H2>
lispmtopgm - convert a Lisp Machine bitmap file to PGM

<A NAME="lbAC">&nbsp;</A>
<H2>SYNOPSIS</H2>

<B>lispmtopgm</B>
[<I>lispmfile</I>]

<A NAME="lbAD">&nbsp;</A>
<H2>DESCRIPTION</H2>

<p>This program is part of <a href="index.html">Netpbm</a>.

<p><b>listpmfile</b> reads a Lisp Machine bitmap as input and
produces a PGM image as output.

<P>This is the file format written by the tv:write-bit-array-file
function on TI Explorer and Symbolics lisp machines.

<P>Multi-plane bitmaps on lisp machines are color; but the Lispm image
file format does not include a color map, so we must treat it as a
monochrome instead and produce PGM.  This is unfortunate.

<A NAME="lbAE">&nbsp;</A>
<H2>SEE ALSO</H2>

<A HREF="pgmtolispm.html">pgmtolispm</A>,
<A HREF="pgm.html">pgm</A>

<A NAME="lbAF">&nbsp;</A>
<H2>LIMITATIONS</H2>

The Lispm bitmap file format is a bit quirky;  Usually the image in the file
has its width rounded up to the next higher multiple of 32, but not always.
If the width is not a multiple of 32, we don't deal with it properly, but 
because of the Lispm microcode, such arrays are probably not image data 
anyway.

<P>Also, the Lispm code for saving bitmaps has a bug, in that if you
are writing a bitmap which is not mod32 across, the file may be up to
7 bits too short!  They round down instead of up, and we don't handle
this bug gracefully.

<A NAME="lbAG">&nbsp;</A>
<H2>AUTHOR</H2>

<P>Copyright (C) 1991 by Jamie Zawinski and Jef Poskanzer.


<HR>
<A NAME="index">&nbsp;</A><H2>Table Of Contents</H2>
<UL>
<LI><A HREF="#lbAB">NAME</A>
<LI><A HREF="#lbAC">SYNOPSIS</A>
<LI><A HREF="#lbAD">DESCRIPTION</A>
<LI><A HREF="#lbAE">SEE ALSO</A>
<LI><A HREF="#lbAF">BUGS</A>
<LI><A HREF="#lbAG">AUTHOR</A>
</UL>
</BODY>
</HTML>