Action12 - Revision history

Rubidium: non-proportional font

2011-11-20T11:57:04Z

non-proportional font

← Older revision		Revision as of 11:57, 20 November 2011
Line 49:		Line 49:
	=== font ===		=== font ===

	The font to define glyphs for. The value can be 0 for the normal size, 1 for the small size, or 2 for the ~~large~~ size font.		The font to define glyphs for. The value can be 0 for the normal size proportional font, 1 for the small size proportional font, 2 for the large size proportional font, or {{ottdp\|1.2\|no\|ottdrev=23274}} 3 for the normal size non-proportional font.

	=== num-char ===		=== num-char ===

Frosch: version tags

2011-08-06T15:17:17Z

version tags

← Older revision		Revision as of 15:17, 6 August 2011
Line 1:		Line 1:
	==Introduction==		==Introduction==
			{{ottdp\|0.6\|2.5\|ttdprev=2.0.1 alpha 73}}

	This action allows loading and defining glyphs for any [http://www.unicode.org/ Unicode] character in the BMP (Basic Multilingual Plane), i.e. up to U+FFFF.		This action allows loading and defining glyphs for any [http://www.unicode.org/ Unicode] character in the BMP (Basic Multilingual Plane), i.e. up to U+FFFF.

	''Note'': If any .grf file containing an action 12 is loaded (even if it is inactive), TTDPatch is put into UTF-8 mode. This changes how character input is processed and how custom strings are stored in the savegame (they are converted to UTF-8 encoding). It is not possible to prevent this, and because of possible bugs in UTF-8 mode it is therefore preferable to put all font glyphs in separate .grf files to allow them to not be loaded in the case of problems.		''Note'': If any .grf file containing an action 12 is loaded (even if it is inactive), TTDPatch is put into UTF-8 mode. This changes how character input is processed and how custom strings are stored in the savegame (they are converted to UTF-8 encoding). It is not possible to prevent this, and because of possible bugs in UTF-8 mode it is therefore preferable to put all font glyphs in separate .grf files to allow them to not be loaded in the case of problems.

	Available since TTDPatch 2.0.1 alpha 73.

	== Format ==		== Format ==

Frosch: unify the order of nunchar and base-char

2011-06-18T12:15:58Z

unify the order of nunchar and base-char

← Older revision		Revision as of 12:15, 18 June 2011
Line 47:		Line 47:
	=== num-def ===		=== num-def ===

	This specifies how many definitions follow, each having <nowiki><font></nowiki>, <~~basechar~~> and <~~numchar~~>.		This specifies how many definitions follow, each having <nowiki><font></nowiki>, <num-char> and <base-char>.

	=== font ===		=== font ===
Line 61:		Line 61:
	The first Unicode character in a range to provide glyphs for.  This can be any Unicode character in the BMP.		The first Unicode character in a range to provide glyphs for.  This can be any Unicode character in the BMP.

	Note that all characters of a definition (i.e., <nowiki><font></nowiki> <~~basechar~~> <~~numchar~~> triplet) must fit within a "block" of 128 characters, i.e. you cannot define characters U+00E0..U+011F with one definition; instead you must split it into U+00E0..U+00FF and U+0100..U+011F because those are two different blocks.		Note that all characters of a definition (i.e., <nowiki><font></nowiki> <num-char> <base-char> triplet) must fit within a "block" of 128 characters, i.e. you cannot define characters U+00E0..U+011F with one definition; instead you must split it into U+00E0..U+00FF and U+0100..U+011F because those are two different blocks.

	== Example ==		== Example ==

Frosch: fix conversion

2011-06-18T12:13:42Z

fix conversion

← Older revision		Revision as of 12:13, 18 June 2011
Line 47:		Line 47:
	=== num-def ===		=== num-def ===

	This specifies how many definitions follow, each having <font>, <basechar> and <numchar>.		This specifies how many definitions follow, each having <nowiki><font></nowiki>, <basechar> and <numchar>.

	=== font ===		=== font ===
Line 61:		Line 61:
	The first Unicode character in a range to provide glyphs for.  This can be any Unicode character in the BMP.		The first Unicode character in a range to provide glyphs for.  This can be any Unicode character in the BMP.

	Note that all characters of a definition (i.e., <font> <basechar> <numchar> triplet) must fit within a "block" of 128 characters, i.e. you cannot define characters U+00E0..U+011F with one definition; instead you must split it into U+00E0..U+00FF and U+0100..U+011F because those are two different blocks.		Note that all characters of a definition (i.e., <nowiki><font></nowiki> <basechar> <numchar> triplet) must fit within a "block" of 128 characters, i.e. you cannot define characters U+00E0..U+011F with one definition; instead you must split it into U+00E0..U+00FF and U+0100..U+011F because those are two different blocks.

	== Example ==		== Example ==

Pm-bot: Bot: Automated text replacement (- 2.0 + TTDPatch 2.0)

2011-06-15T17:28:39Z

Bot: Automated text replacement (- 2.0 + TTDPatch 2.0)

← Older revision		Revision as of 17:28, 15 June 2011
Line 5:		Line 5:
	''Note'': If any .grf file containing an action 12 is loaded (even if it is inactive), TTDPatch is put into UTF-8 mode. This changes how character input is processed and how custom strings are stored in the savegame (they are converted to UTF-8 encoding). It is not possible to prevent this, and because of possible bugs in UTF-8 mode it is therefore preferable to put all font glyphs in separate .grf files to allow them to not be loaded in the case of problems.		''Note'': If any .grf file containing an action 12 is loaded (even if it is inactive), TTDPatch is put into UTF-8 mode. This changes how character input is processed and how custom strings are stored in the savegame (they are converted to UTF-8 encoding). It is not possible to prevent this, and because of possible bugs in UTF-8 mode it is therefore preferable to put all font glyphs in separate .grf files to allow them to not be loaded in the case of problems.

	Available since 2.0.1 alpha 73.		Available since TTDPatch 2.0.1 alpha 73.

	== Format ==		== Format ==

Pm-bot: Beautify wiki markup

2011-06-15T14:48:47Z

Beautify wiki markup

← Older revision		Revision as of 14:48, 15 June 2011
Line 7:		Line 7:
	Available since 2.0.1 alpha 73.		Available since 2.0.1 alpha 73.

	==Format==		== Format ==

	The data looks as follows:		The data looks as follows:
Line 35:		Line 35:
	Glyphs sprites may only use colors 00 (transparent), 01 (foreground) and 02 (shadow). A sprite that uses the shadow color MUST NOT use the [[RealSprites#compression\|chunked data format]].		Glyphs sprites may only use colors 00 (transparent), 01 (foreground) and 02 (shadow). A sprite that uses the shadow color MUST NOT use the [[RealSprites#compression\|chunked data format]].

	==Description==		== Description ==

	===sprite-number===		=== sprite-number ===

	The current sprite number.		The current sprite number.

	===length===		=== length ===

	The total number of bytes in this action 12.		The total number of bytes in this action 12.

	===num-def===		=== num-def ===

	This specifies how many definitions follow, each having <font>, <basechar> and <numchar>.		This specifies how many definitions follow, each having <font>, <basechar> and <numchar>.

	===font===		=== font ===

	The font to define glyphs for. The value can be 0 for the normal size, 1 for the small size, or 2 for the large size font.		The font to define glyphs for. The value can be 0 for the normal size, 1 for the small size, or 2 for the large size font.

	===num-char===		=== num-char ===

	The number of characters in the range.		The number of characters in the range.

	===base-char===		=== base-char ===

	The first Unicode character in a range to provide glyphs for.  This can be any Unicode character in the BMP.		The first Unicode character in a range to provide glyphs for.  This can be any Unicode character in the BMP.

	Note that all characters of a definition (i.e., <font> <basechar> <numchar> triplet) must fit within a ~~"~~block~~"~~ of 128 characters, i.e. you cannot define characters U+00E0..U+011F with one definition; instead you must split it into U+00E0..U+00FF and U+0100..U+011F because those are two different blocks.		Note that all characters of a definition (i.e., <font> <basechar> <numchar> triplet) must fit within a "block" of 128 characters, i.e. you cannot define characters U+00E0..U+011F with one definition; instead you must split it into U+00E0..U+00FF and U+0100..U+011F because those are two different blocks.

	==Example==		== Example ==

	583 * 10 12 02 00 08 F8 00 00 0C 00 01		583 * 10 12 02 00 08 F8 00 00 0C 00 01

Terkhen at 22:12, 14 June 2011

2011-06-14T22:12:00Z

← Older revision		Revision as of 22:12, 14 June 2011
Line 78:		Line 78:
	\|02\|\|<num-def>: we're defining two ranges of characters		\|02\|\|<num-def>: we're defining two ranges of characters
	\|-		\|-
	\|00\|\|<font>: first range, defining font 0 (normal size)		\|00\|\|<nowiki><font></nowiki>: first range, defining font 0 (normal size)
	\|-		\|-
	\|08\|\|<num-char>: defining 8 characters in a row		\|08\|\|<num-char>: defining 8 characters in a row
Line 84:		Line 84:
	\|F8 00\|\|<base-char>: character U+00F8 is the first character		\|F8 00\|\|<base-char>: character U+00F8 is the first character
	\|-		\|-
	\|00\|\|<font>: second range, also defining font 0 (normal size)		\|00\|\|<nowiki><font></nowiki>: second range, also defining font 0 (normal size)
	\|-		\|-
	\|0C\|\|<num-char>: defining another 12 characters		\|0C\|\|<num-char>: defining another 12 characters

Terkhen: Fix style and format

2011-06-14T22:11:18Z

Fix style and format

Show changes

Orudge: 9 revisions

2011-06-12T19:20:20Z

9 revisions

← Older revision	Revision as of 19:20, 12 June 2011
(No difference)

Orudge: 8 revisions

2011-06-12T19:01:21Z

8 revisions

← Older revision	Revision as of 19:01, 12 June 2011
(No difference)