X BitMap
A sample XBM file
|
|
Filename extension |
|
---|---|
Internet media type | image/x‑xbitmap, image/x‑xbm[1] |
Type of format | Image file formats |
Extended from | C (programming language) |
Extended to | X PixMap (XPM) |
In computer graphics, the X Window System used X BitMap (XBM), a plain text binary image format, for storing cursor and icon bitmaps used in the X GUI.[2] The XBM format was replaced by XPM for X11 in 1989.[3]
Contents
Format
XBM files differed markedly from most image files in that they took the form of C source files. This meant that they could be compiled directly into an application without any preprocessing steps, but it also made them far larger than their raw pixel data. The image data was encoded as a comma-separated list of byte values, each written in the C hexadecimal notation, '0x13' for example, so that multiple bytes are used to express a single byte of image information.[4]
XBM data typically appeared in headers (.h files) and consisted of a series of static unsigned char arrays containing the monochrome pixel data. They featured one array per image stored in the header. The following piece of C code exemplifies an XBM file:
#define test_width 16
#define test_height 7
static char test_bits[] = {
0x13, 0x00, 0x15, 0x00, 0x93, 0xcd, 0x55, 0xa5, 0x93, 0xc5, 0x00, 0x80,
0x00, 0x60 };
In place of the usual image-file-format header, XBM files had two or four #define statements. The first two #defines specified the height and width of the bitmap in pixels. The second two, if they existed, specified the position of any hotspot within the bitmap. (Programmers used a hotspot within the image for bitmapped cursors to define where to position the "pointer" of the cursor, generally at 0,0.)
The image data consisted of a line of pixel values stored in a static array. Because a single bit represented each pixel (0 for white or 1 for black), each byte in the array contained the information for eight pixels, with the upper left pixel in the bitmap represented by the low bit of the first byte in the array. If the image width did not match a multiple of 8, the display mechanism ignored and discarded the extra bits in the last byte of each row.
Support
Some web browsers support displaying XBM images as a holdover from the early days of the world wide web, when XBM was the minimal non-proprietary image file format. The Arena web browser had full support since version 0.3.34 (25 July 1997).[5] XBM support was removed from Internet Explorer 6, Mozilla Firefox 3.6,[6] and WebKit-based browsers.[7] There is a strong indication that Chromium (and therefore, also, Google Chrome) does not support XBM.[8] Documentation for Opera 2.12 and 6.0 indicates that XBM was at least previously supported.[9][10]
Some image viewers/converters, e.g., XnView, FFmpeg and IrfanView, still support XBM.[11] A 48×48 XBM can be converted to Ikon and eventually X-Face with Netpbm tools.[12]
Despite having been superseded by the XPM format, XBM is still used by some modern but lightweight window managers like Openbox to define simple button images in a window's title bar, such as the iconify/minimize, restore, and maximize buttons.[13]
See also
References
- ↑ .xbm MIME type not registered at IANA
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.