CMU Window Manager bitmap

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Created page with "{{FormatInfo |formattype=electronic |subcat=Graphics }} '''CMU Window Manager bitmap''' (possibly also known as '''ITC''' bitmap) is an uncompressed bi-level raster image file...")
 
 
(4 intermediate revisions by one user not shown)
Line 2: Line 2:
 
|formattype=electronic
 
|formattype=electronic
 
|subcat=Graphics
 
|subcat=Graphics
 +
|extensions={{ext|cmu}}
 
}}
 
}}
 
'''CMU Window Manager bitmap''' (possibly also known as '''ITC''' bitmap) is an uncompressed bi-level raster image file format. It was apparently used by old versions of the Andrew Toolkit.
 
'''CMU Window Manager bitmap''' (possibly also known as '''ITC''' bitmap) is an uncompressed bi-level raster image file format. It was apparently used by old versions of the Andrew Toolkit.
Line 10: Line 11:
 
According to Netpbm, files have a 14-byte header containing a signature, width, height, and depth (which is always 1). The signature begins with the <code>F1</code> byte, and the header fields use big-endian byte order.
 
According to Netpbm, files have a 14-byte header containing a signature, width, height, and depth (which is always 1). The signature begins with the <code>F1</code> byte, and the header fields use big-endian byte order.
  
The [[file command]] thinks that the header is 16 bytes (''depth'' being 4 bytes instead of 2), the byte order is little-endian, and the signature still begins with <code>F1</code>.
+
The [[file command]] thinks that the header is at least 16 bytes (''depth'' being 4 bytes instead of 2), the byte order is little-endian, and the signature still begins with <code>F1</code>.
  
The ATK 6.3 source code implies that header can be 14 or 16 bytes, and that the byte order is indicated by the signature.
+
The ATK 6.3 source code implies that the header can be 14 or 16 bytes, and that the byte order is indicated by the signature.
  
 
(Yes, we know that all of these things cannot be true at the same time.)
 
(Yes, we know that all of these things cannot be true at the same time.)
 +
 +
== Identifiers ==
 +
The standard filename extension is unknown, but '''.cmu''' is sometimes used.
  
 
== Identification ==
 
== Identification ==
Line 23: Line 27:
  
 
== Software ==
 
== Software ==
* [http://netpbm.sourceforge.net/ Netpbm]: cmuwmtopbm, pbmtocmuwm
+
* [[Konvertor]]
 +
* [[Netpbm]]: cmuwmtopbm, pbmtocmuwm
 +
* [[XnView]]
 
* ftp://ftp.andrew.cmu.edu/pub/AUIS/auis-6.3/atk/raster/lib/ → oldrf.c
 
* ftp://ftp.andrew.cmu.edu/pub/AUIS/auis-6.3/atk/raster/lib/ → oldrf.c
 +
 +
[[Category:CMU]]

Latest revision as of 15:03, 22 February 2016

File Format
Name CMU Window Manager bitmap
Ontology
Extension(s) .cmu

CMU Window Manager bitmap (possibly also known as ITC bitmap) is an uncompressed bi-level raster image file format. It was apparently used by old versions of the Andrew Toolkit.

Contents

[edit] Format

There are evidently several varieties of the format, which differ in the size of the header, and the byte order of the header fields.

According to Netpbm, files have a 14-byte header containing a signature, width, height, and depth (which is always 1). The signature begins with the F1 byte, and the header fields use big-endian byte order.

The file command thinks that the header is at least 16 bytes (depth being 4 bytes instead of 2), the byte order is little-endian, and the signature still begins with F1.

The ATK 6.3 source code implies that the header can be 14 or 16 bytes, and that the byte order is indicated by the signature.

(Yes, we know that all of these things cannot be true at the same time.)

[edit] Identifiers

The standard filename extension is unknown, but .cmu is sometimes used.

[edit] Identification

Files begin with signature bytes F1 00 40 BB, or BB 40 00 F1.

[edit] See also

[edit] Software

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox