FONT (File Format) - Revision history

imported>Antidote at 20:10, 11 March 2016

2016-03-11T20:10:33Z

← Older revision		Revision as of 20:10, 11 March 2016
Line 185:		Line 185:
	\| u32		\| u32
	\| 4		\| 4
	\| '''Kerning index'''		\| '''Kerning start index'''
	\|-		\|-
	\| 0x2E		\| 0x2E
Line 262:		Line 262:
	\| u16		\| u16
	\| 2		\| 2
	\| '''Kerning index'''		\| '''Kerning start index'''
	\|-		\|-
	\| 0x1B		\| 0x1B

>Aruki: /* Glyphs */

2016-03-01T12:19:26Z

Glyphs

← Older revision		Revision as of 12:19, 1 March 2016
Line 117:		Line 117:
	The kerning index value is the index of the first kerning table entry for the given character. Since the table is sorted in alphabetical order, this can be used to speed up lookup time.		The kerning index value is the index of the first kerning table entry for the given character. Since the table is sorted in alphabetical order, this can be used to speed up lookup time.

	This section of the file changes somewhat from version 2 to 4. Starting in version 4, font textures are able to be split up into multiple layers, which allows multiple glyphs to be encoded in the same space on the texture. A "layer index" value was introduced to track which ~~Layer~~ the glyph is on. Additionally, a lot of 32-bit values were reduced to 8- or 16-bit. Aside from that, though, the actual layout is still the same, with the same values in the same places.		This section of the file changes somewhat from version 2 to 4. Starting in version 4, font textures are able to be split up into multiple layers, which allows multiple glyphs to be encoded in the same space on the texture. A "layer index" value was introduced to track which layer the glyph is on. Additionally, a lot of 32-bit values were reduced to 8- or 16-bit. Aside from that, though, the actual layout is still the same, with the same values in the same places.

	==== Version 2 (Metroid Prime NTSC) ====		==== Version 2 (Metroid Prime NTSC) ====

>Aruki: /* Glyphs */

2016-03-01T12:19:00Z

Glyphs

← Older revision		Revision as of 12:19, 1 March 2016
Line 117:		Line 117:
	The kerning index value is the index of the first kerning table entry for the given character. Since the table is sorted in alphabetical order, this can be used to speed up lookup time.		The kerning index value is the index of the first kerning table entry for the given character. Since the table is sorted in alphabetical order, this can be used to speed up lookup time.

	This section of the file changes somewhat from version 2 to 4. Starting in version 4, ~~glyphs~~ are able to be ~~encoded to only one particular RGBA channel~~, which allows multiple glyphs to be encoded in the same space on the texture. A "~~channel~~ index" value was introduced to track which ~~channel~~ the glyph is on. Additionally, a lot of 32-bit values were reduced to 8- or 16-bit. Aside from that, though, the actual layout is still the same, with the same values in the same places.		This section of the file changes somewhat from version 2 to 4. Starting in version 4, font textures are able to be split up into multiple layers, which allows multiple glyphs to be encoded in the same space on the texture. A "layer index" value was introduced to track which Layer the glyph is on. Additionally, a lot of 32-bit values were reduced to 8- or 16-bit. Aside from that, though, the actual layout is still the same, with the same values in the same places.

	==== Version 2 (Metroid Prime NTSC) ====		==== Version 2 (Metroid Prime NTSC) ====
Line 227:		Line 227:
	\| u8		\| u8
	\| 1		\| 1
	\| '''~~RGBA channel~~ index'''		\| '''Layer index'''
	\|-		\|-
	\| 0x13		\| 0x13

imported>Antidote at 05:08, 21 October 2015

2015-10-21T05:08:01Z

← Older revision		Revision as of 05:08, 21 October 2015
Line 42:		Line 42:
	\| u32		\| u32
	\| 4		\| 4
	\| '''Vertical offset'''		\| '''Vertical offset''' ''(note: not present in version 1)''
	\|-		\|-
	\| 0x14		\| 0x14
Line 50:		Line 50:
	\|-		\|-
	\| 0x18		\| 0x18
			\| bool
			\| 1
			\| {{unknown\|'''Unknown'''}}
			\|-
			\| 0x19
			\| bool
			\| 1
			\| {{unknown\|'''Unknown'''}}
			\|-
			\| 0x1A
	\| u32		\| u32
	\| 4		\| 4
	~~\| {{unknown\|'''Unknown'''}} ''(note: not present in version 1)''~~		\| {{unknown\|'''Unknown'''}}
	\|-
	~~\| 0x1C~~
	~~\| u16~~
	~~\| 2~~
	\| {{unknown\|'''Unknown'''}}
	\|-		\|-
	\| 0x1E		\| 0x1E

>Aruki: /* Version 4 (Metroid Prime PAL/Trilogy) */ consistency

2015-08-07T23:30:11Z

Version 4 (Metroid Prime PAL/Trilogy): consistency

← Older revision		Revision as of 23:30, 7 August 2015
Line 252:		Line 252:
	\| u8		\| u8
	\| 1		\| 1
	\| '''Vertical ~~Offset~~'''		\| '''Vertical offset'''
	\|-		\|-
	\| 0x19		\| 0x19

imported>Antidote: Missing value

2015-08-07T22:03:17Z

Missing value

← Older revision		Revision as of 22:03, 7 August 2015
Line 186:		Line 186:
	\|}		\|}

	==== Version 4 (Metroid Prime PAL) ====		==== Version 4 (Metroid Prime PAL/Trilogy) ====

	{\| class="wikitable"		{\| class="wikitable"
Line 250:		Line 250:
	\|-		\|-
	\| 0x18		\| 0x18
			\| u8
			\| 1
			\| '''Vertical Offset'''
			\|-
			\| 0x19
	\| u16		\| u16
	\| 2		\| 2
	\| '''Kerning index'''		\| '''Kerning index'''
	\|-		\|-
	\| ~~0x1A~~		\| 0x1B
	\| colspan=3 {{unknown\|End of glyph definition}}		\| colspan=3 {{unknown\|End of glyph definition}}
	\|}		\|}

>Aruki: /* Textures */

2015-03-28T05:30:08Z

Textures

← Older revision		Revision as of 05:30, 28 March 2015
Line 287:		Line 287:
	{{research\|minor\|Someone should look at the code to make sure the info in this section is accurate.}}		{{research\|minor\|Someone should look at the code to make sure the info in this section is accurate.}}

	Textures used by FONT files are encoded in a bit of an unorthodox manner. The font format allows for multiple glyphs to be encoded in the same spot on the texture by splitting up the texture into multiple layers. The way this is handled on the textures is by encoding the textures with palettes (as C4), but modifying the palette indices at runtime and loading each layer one at a time as a separate ~~layer~~. Each bit of the palette index corresponds to a layer, so up to four layers per font are supported. The MSB refers to layer 0, while the LSB refers to layer 3. In DKCR, font textures are encoded as C8, so theoretically the game could use up to eight layers per font; however, it still never actually uses more than four.		Textures used by FONT files are encoded in a bit of an unorthodox manner. The font format allows for multiple glyphs to be encoded in the same spot on the texture by splitting up the texture into multiple layers. The way this is handled on the textures is by encoding the textures with palettes (as C4), but modifying the palette indices at runtime and loading each layer one at a time as a separate texture. Each bit of the palette index corresponds to a layer, so up to four layers per font are supported. The MSB refers to layer 0, while the LSB refers to layer 3. In DKCR, font textures are encoded as C8, so theoretically the game could use up to eight layers per font; however, it still never actually uses more than four.

	The texture format is determined by a value in the header. These are the possible settings:		The texture format is determined by a value in the header. These are the possible settings:

>Aruki: /* Textures */

2015-03-28T05:29:19Z

Textures

← Older revision		Revision as of 05:29, 28 March 2015
Line 287:		Line 287:
	{{research\|minor\|Someone should look at the code to make sure the info in this section is accurate.}}		{{research\|minor\|Someone should look at the code to make sure the info in this section is accurate.}}

	Textures used by FONT files are encoded in a bit of an unorthodox manner. The font format allows for multiple glyphs to be encoded in the same spot on the texture by splitting up the texture into multiple layers. The way this is handled on the textures is by encoding the textures with palettes (as C4), but modifying the palette indices at runtime and loading each layer one at a time as a separate layer. Each bit of the palette index corresponds to a layer, so up to four layers per font are supported. The MSB refers to layer 0, while the LSB refers to layer 3. In DKCR, font ~~texture~~ are encoded as C8, so theoretically the game could use up to eight layers per font; however, it still never actually uses more than four.		Textures used by FONT files are encoded in a bit of an unorthodox manner. The font format allows for multiple glyphs to be encoded in the same spot on the texture by splitting up the texture into multiple layers. The way this is handled on the textures is by encoding the textures with palettes (as C4), but modifying the palette indices at runtime and loading each layer one at a time as a separate layer. Each bit of the palette index corresponds to a layer, so up to four layers per font are supported. The MSB refers to layer 0, while the LSB refers to layer 3. In DKCR, font textures are encoded as C8, so theoretically the game could use up to eight layers per font; however, it still never actually uses more than four.

	The texture format is determined by a value in the header. These are the possible settings:		The texture format is determined by a value in the header. These are the possible settings:

>Aruki: /* Textures */

2015-03-28T05:28:45Z

Textures

← Older revision		Revision as of 05:28, 28 March 2015
Line 287:		Line 287:
	{{research\|minor\|Someone should look at the code to make sure the info in this section is accurate.}}		{{research\|minor\|Someone should look at the code to make sure the info in this section is accurate.}}

	Textures used by FONT files are encoded in a bit of an unorthodox manner. The font format allows for multiple glyphs to be encoded in the same spot on the texture by splitting up the texture into multiple layers. The way this is handled on the textures is by encoding the textures with palettes (as C4), but modifying the palette indices at runtime and loading each layer one at a time as a separate layer. Each bit of the palette index corresponds to a layer, so up to four layers per font are supported. In DKCR, font texture are encoded as C8, so theoretically the game could use up to eight layers per font; however, it still never actually uses more than four.		Textures used by FONT files are encoded in a bit of an unorthodox manner. The font format allows for multiple glyphs to be encoded in the same spot on the texture by splitting up the texture into multiple layers. The way this is handled on the textures is by encoding the textures with palettes (as C4), but modifying the palette indices at runtime and loading each layer one at a time as a separate layer. Each bit of the palette index corresponds to a layer, so up to four layers per font are supported. The MSB refers to layer 0, while the LSB refers to layer 3. In DKCR, font texture are encoded as C8, so theoretically the game could use up to eight layers per font; however, it still never actually uses more than four.

	The texture format is determined by a value in the header. These are the possible settings:		The texture format is determined by a value in the header. These are the possible settings:

>Aruki: /* Header */

2015-03-28T05:25:46Z

Header

← Older revision		Revision as of 05:25, 28 March 2015
Line 77:		Line 77:
	\| u32		\| u32
	\| 4		\| 4
	~~\| {{unknown~~\|'''~~Unknown~~'''}}		\| '''Texture format''' (see [[#Textures\|Textures]])
	\|-		\|-
	\| -		\| -