Difference between revisions of "SCUMM/Technical Reference/Charset resources"

Character sets define the fonts used by SCUMM to draw text, such as dialogue, on the screen.

Character sets define the fonts used by SCUMM to draw text, such as dialogue, on the screen.

The V1 and V2 font format is identical to that found in V3 games; the big difference is that in V1 and V2, the font is not stored in the game data files, but rather is hardcoded into the executable.

The V1 and V2 font format is identical to that found in V3 games; the big difference is that in V1 and V2, the font is not stored in the game data files, but rather is hardcoded into the executable.

Another minor difference compared to the V3 format is that all characters are exactly 8x8 pixels big. Thus the font is always monospaced, unlike V3 fonts.

Another minor difference compared to the V3 format is that all characters are exactly 8x8 pixels big. Thus the font is always monospaced, unlike V3 fonts.

The header looks as follows:

The header looks as follows:

After this header the character data starts. Every character in the charset takes up exactly 8 bytes, representing 8x8 pixels in which the actual character is contained (the actual width and height of the char should be computed from the charset header).

After this header the character data starts. Every character in the charset takes up exactly 8 bytes, representing 8x8 pixels in which the actual character is contained (the actual width and height of the char should be computed from the charset header).

The header looks as follows:

The header looks as follows:

|2      ||                || unknown

|2      ||                || unknown

|-

|-

|-

|-

|1      || byte            || number of bits per pixel

|1      || byte            || number of bits per pixel

Character glyphs may be 1, 2, 4 or 8 bits per pixel, and can be masked.

Character glyphs may be 1, 2, 4 or 8 bits per pixel, and can be masked.

is drawn as. Pixel value 0 is used for transparency; the other values are

is drawn as. Pixel value 0 is used for transparency; the other values are

mapped using the color map in the header.

mapped using the color map in the header.

The character data pointers contain the offset, relative to the byte

The character data pointers contain the offset, relative to the byte

This can be 0 if that particular character is not encoded in the character

This can be 0 if that particular character is not encoded in the character

set. The character data itself is formatted as follows:

set. The character data itself is formatted as follows:

</pre>

</pre>

Like all other resources in V5 and later, the charset data is stored in a chunk, in this case a 'CHAR' chunk. The header looks as follows:

Like all other resources in V5 and later, the charset data is stored in a chunk, in this case a 'CHAR' chunk. The header looks as follows:

|2      || short          || version ? (always 0x6303 in dott)

|2      || short          || version ? (always 0x6303 in dott)

|-

|-

|-

|-

|1      || byte            || number of bits per pixel

|1      || byte            || number of bits per pixel

Observe that this header is identical to the V4 header with a few bytes added to the start of it. The charset format is otherwise identical to the V4 format described above.

Observe that this header is identical to the V4 header with a few bytes added to the start of it. The charset format is otherwise identical to the V4 format described above.

=== NUT (V7 & V8) charset format ===

=== NUT (V7 & V8) charset format ===