Annotated edit history of
lispmtopgm(1) version 1, including all changes.
View license author blame.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
lispmtopgm |
|
|
2 |
!!!lispmtopgm |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
SEE ALSO |
|
|
7 |
BUGS |
|
|
8 |
AUTHOR |
|
|
9 |
---- |
|
|
10 |
!!NAME |
|
|
11 |
|
|
|
12 |
|
|
|
13 |
lispmtopgm - convert a Lisp Machine bitmap file into pgm format |
|
|
14 |
!!SYNOPSIS |
|
|
15 |
|
|
|
16 |
|
|
|
17 |
__lispmtopgm__ [[''lispmfile''] |
|
|
18 |
!!DESCRIPTION |
|
|
19 |
|
|
|
20 |
|
|
|
21 |
Reads a Lisp Machine bitmap as input. Produces a portable |
|
|
22 |
graymap as output. |
|
|
23 |
|
|
|
24 |
|
|
|
25 |
This is the file format written by the |
|
|
26 |
tv:write-bit-array-file function on TI Explorer and |
|
|
27 |
Symbolics lisp machines. |
|
|
28 |
|
|
|
29 |
|
|
|
30 |
Multi-plane bitmaps on lisp machines are color; but the |
|
|
31 |
lispm image file format does not include a color map, so we |
|
|
32 |
must treat it as a graymap instead. This is |
|
|
33 |
unfortunate. |
|
|
34 |
!!SEE ALSO |
|
|
35 |
|
|
|
36 |
|
|
|
37 |
pgmtolispm(1), pgm(5) |
|
|
38 |
!!BUGS |
|
|
39 |
|
|
|
40 |
|
|
|
41 |
The Lispm bitmap file format is a bit quirky; Usually the |
|
|
42 |
image in the file has its width rounded up to the next |
|
|
43 |
higher multiple of 32, but not always. If the width is not a |
|
|
44 |
multiple of 32, we don't deal with it properly, but because |
|
|
45 |
of the Lispm microcode, such arrays are probably not image |
|
|
46 |
data anyway. |
|
|
47 |
|
|
|
48 |
|
|
|
49 |
Also, the lispm code for saving bitmaps has a bug, in that |
|
|
50 |
if you are writing a bitmap which is not mod32 across, the |
|
|
51 |
file may be up to 7 bits too short! They round down instead |
|
|
52 |
of up, and we don't handle this bug gracefully. |
|
|
53 |
|
|
|
54 |
|
|
|
55 |
No color. |
|
|
56 |
!!AUTHOR |
|
|
57 |
|
|
|
58 |
|
|
|
59 |
Copyright (C) 1991 by Jamie Zawinski and Jef |
|
|
60 |
Poskanzer. |
|
|
61 |
---- |
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.