2,051
edits
Difference between revisions of "SCUMM/Technical Reference/Charset resources"
Jump to navigation
Jump to search
m
SCUMM/Technical Reference/Charset resources (view source)
Revision as of 02:55, 23 January 2011
, 02:55, 23 January 2011colour -> color
m |
m (colour -> color) |
||
| (4 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
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. | ||
== V1/V2 charset format == | |||
== The old charset format: V1-V3 == | |||
=== V1/V2 charset format === | |||
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. | ||
| Line 10: | Line 13: | ||
Currently, ScummVM includes fonts for english, french, german, italian and spanish game variants. It is not known whether there were other localizations, but if you encounter any make sure to tell the team about it! | Currently, ScummVM includes fonts for english, french, german, italian and spanish game variants. It is not known whether there were other localizations, but if you encounter any make sure to tell the team about it! | ||
== V3 charset format == | 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. | ||
=== V3 charset format === | |||
The header looks as follows: | The header looks as follows: | ||
| Line 28: | Line 33: | ||
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). | ||
== V4 charset format == | == The new charset format: V4-V6 == | ||
=== V4 charset format === | |||
The header looks as follows: | The header looks as follows: | ||
| Line 37: | Line 44: | ||
|2 || || unknown | |2 || || unknown | ||
|- | |- | ||
|15 || bytes || | |15 || bytes || color map | ||
|- | |- | ||
|1 || byte || number of bits per pixel | |1 || byte || number of bits per pixel | ||
| Line 50: | Line 57: | ||
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. | ||
The | The color map contains the colors each pixel of the character glyph | ||
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 | ||
after the end of the | after the end of the color map (byte 29), of the character data. | ||
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: | ||
| Line 103: | Line 110: | ||
</pre> | </pre> | ||
== V5/V6 charset format == | === V5/V6 charset format === | ||
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: | ||
| Line 116: | Line 123: | ||
|2 || short || version ? (always 0x6303 in dott) | |2 || short || version ? (always 0x6303 in dott) | ||
|- | |- | ||
|15 || bytes || | |15 || bytes || color map | ||
|- | |- | ||
|1 || byte || number of bits per pixel | |1 || byte || number of bits per pixel | ||
| Line 129: | Line 136: | ||
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 == | == The modern charset format: V7-V8 == | ||
=== NUT (V7 & V8) charset format === | |||
In V7 and V8 (Dig, FT, Comi), the fonts where stored in separate files with the extension "nut". We thus call the format used in these games the "NUT format". | In V7 and V8 (Dig, FT, Comi), the fonts where stored in separate files with the extension "nut". We thus call the format used in these games the "NUT format". | ||