Action13 - Revision history

Jgr: Fix incorrectly appearing in the format summary line

2022-01-27T23:25:01Z

Fix <feature> incorrectly appearing in the format summary line

← Older revision		Revision as of 23:25, 27 January 2022
Line 9:		Line 9:
	The data looks as follows:		The data looks as follows:

	<sprite-number> * <length> 13 ~~<feature>~~ <GRFID> (<language-id>)? <num-ent> <offset> <text...>		<sprite-number> * <length> 13 <GRFID> (<language-id>)? <num-ent> <offset> <text...>

	{\|		{\|

Frosch: use new grf templates

2012-04-01T13:08:56Z

use new grf templates

← Older revision		Revision as of 13:08, 1 April 2012
Line 3:		Line 3:
	Translating regular strings is easy by just overwriting them with an [[Action4\|action 4]], however this is not possible for translating GRF-specific strings in the D000 or DC00 range of IDs. Instead, these must be translated with this action 13.		Translating regular strings is easy by just overwriting them with an [[Action4\|action 4]], however this is not possible for translating GRF-specific strings in the D000 or DC00 range of IDs. Instead, these must be translated with this action 13.

	{{ottd\|}}Usage of this action with OpenTTD is troublesome in multiplayer. The action does not specify a language code for the translation, but forces the translation on every player. However, GRFs with only action 13 can be loaded as [[OpenTTD static NewGRF]]. {{~~grf~~\|8}} GRF version 8 alleviates this problem by providing the language that is overridden.		{{ottd\|}}Usage of this action with OpenTTD is troublesome in multiplayer. The action does not specify a language code for the translation, but forces the translation on every player. However, GRFs with only action 13 can be loaded as [[OpenTTD static NewGRF]]. {{grfFrom\|8}} GRF version 8 alleviates this problem by providing the language that is overridden.

	== Format ==		== Format ==
Line 35:		Line 35:
	\|<language-id>		\|<language-id>
	\|B		\|B
	\|{{~~grf~~\|8}} Which of TTD's languages these strings are for (only for GRF version 8 an higher)		\|{{grfFrom\|8}} Which of TTD's languages these strings are for (only for GRF version 8 an higher)
	\|-		\|-
	\|<num-ent>		\|<num-ent>

Frosch: update syntax

2011-12-01T21:17:15Z

update syntax

← Older revision		Revision as of 21:17, 1 December 2011
Line 9:		Line 9:
	The data looks as follows:		The data looks as follows:

	<sprite-number> * <length> 13 <feature> <GRFID> <num-ent> <offset> <text...>		<sprite-number> * <length> 13 <feature> <GRFID> (<language-id>)? <num-ent> <offset> <text...>

	{\|		{\|

Rubidium: Translation of multiple languages

2011-12-01T19:43:04Z

Translation of multiple languages

← Older revision		Revision as of 19:43, 1 December 2011
Line 3:		Line 3:
	Translating regular strings is easy by just overwriting them with an [[Action4\|action 4]], however this is not possible for translating GRF-specific strings in the D000 or DC00 range of IDs. Instead, these must be translated with this action 13.		Translating regular strings is easy by just overwriting them with an [[Action4\|action 4]], however this is not possible for translating GRF-specific strings in the D000 or DC00 range of IDs. Instead, these must be translated with this action 13.

	{{ottd\|}}Usage of this action with OpenTTD is troublesome in multiplayer. The action does not specify a language code for the translation, but forces the translation on every player. However, GRFs with only action 13 can be loaded as [[OpenTTD static NewGRF]].		{{ottd\|}}Usage of this action with OpenTTD is troublesome in multiplayer. The action does not specify a language code for the translation, but forces the translation on every player. However, GRFs with only action 13 can be loaded as [[OpenTTD static NewGRF]]. {{grf\|8}} GRF version 8 alleviates this problem by providing the language that is overridden.

	== Format ==		== Format ==
Line 32:		Line 32:
	\|4*B		\|4*B
	\|The GRFID of the file whose texts are to be translated		\|The GRFID of the file whose texts are to be translated
			\|-
			\|<language-id>
			\|B
			\|{{grf\|8}} Which of TTD's languages these strings are for (only for GRF version 8 an higher)
	\|-		\|-
	\|<num-ent>		\|<num-ent>

Frosch: version tags

2011-08-06T15:09:24Z

version tags

← Older revision		Revision as of 15:09, 6 August 2011
Line 1:		Line 1:
	==Description==		==Description==
			{{ottdp\|0.6\|2.6\|ttdprev=r857}}

	Translating regular strings is easy by just overwriting them with an [[Action4\|action 4]], however this is not possible for translating GRF-specific strings in the D000 or DC00 range of IDs. Instead, these must be translated with this action 13.		Translating regular strings is easy by just overwriting them with an [[Action4\|action 4]], however this is not possible for translating GRF-specific strings in the D000 or DC00 range of IDs. Instead, these must be translated with this action 13.

		⚫	{{ottd\|}}Usage of this action with OpenTTD is troublesome in multiplayer. The action does not specify a language code for the translation, but forces the translation on every player. However, GRFs with only action 13 can be loaded as [[OpenTTD static NewGRF]].
	Available since TTDPatch 2.6 alpha 1 (r857).

⚫	Usage of this action with OpenTTD is troublesome in multiplayer. The action does not specify a language code for the translation, but forces the translation on every player. However, GRFs with only action 13 can be loaded as [[OpenTTD static NewGRF]].

	== Format ==		== Format ==

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

2011-06-16T11:50:22Z

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

← Older revision		Revision as of 11:50, 16 June 2011
Line 3:		Line 3:
	Translating regular strings is easy by just overwriting them with an [[Action4\|action 4]], however this is not possible for translating GRF-specific strings in the D000 or DC00 range of IDs. Instead, these must be translated with this action 13.		Translating regular strings is easy by just overwriting them with an [[Action4\|action 4]], however this is not possible for translating GRF-specific strings in the D000 or DC00 range of IDs. Instead, these must be translated with this action 13.

	Available since 2.6 alpha 1 (r857).		Available since TTDPatch 2.6 alpha 1 (r857).

	Usage of this action with OpenTTD is troublesome in multiplayer. The action does not specify a language code for the translation, but forces the translation on every player. However, GRFs with only action 13 can be loaded as [[OpenTTD static NewGRF]].		Usage of this action with OpenTTD is troublesome in multiplayer. The action does not specify a language code for the translation, but forces the translation on every player. However, GRFs with only action 13 can be loaded as [[OpenTTD static NewGRF]].

Frosch: note about usage in OpenTTD

2011-06-15T19:00:54Z

note about usage in OpenTTD

← Older revision		Revision as of 19:00, 15 June 2011
Line 4:		Line 4:

	Available since 2.6 alpha 1 (r857).		Available since 2.6 alpha 1 (r857).

			Usage of this action with OpenTTD is troublesome in multiplayer. The action does not specify a language code for the translation, but forces the translation on every player. However, GRFs with only action 13 can be loaded as [[OpenTTD static NewGRF]].

	== Format ==		== Format ==

Pm-bot: use GRFID consistently

2011-06-15T16:05:19Z

use GRFID consistently

← Older revision		Revision as of 16:05, 15 June 2011
Line 9:		Line 9:
	The data looks as follows:		The data looks as follows:

	<sprite-number> * <length> 13 <feature> <~~grfID~~> <num-ent> <offset> <text...>		<sprite-number> * <length> 13 <feature> <GRFID> <num-ent> <offset> <text...>

	{\|		{\|
Line 29:		Line 29:
	\|Action 13		\|Action 13
	\|-		\|-
	\|<~~grfID~~>		\|<GRFID>
	\|4*B		\|4*B
	\|The ~~grfID~~ of the file whose texts are to be translated		\|The GRFID of the file whose texts are to be translated
	\|-		\|-
	\|<num-ent>		\|<num-ent>
Line 49:		Line 49:
	For action 13, <num-ent>, <offset> and <text...> work exactly as for [[Action4\|action 4]], but the offset may only refer to a text ID in the D000 or DC00 range of IDs.		For action 13, <num-ent>, <offset> and <text...> work exactly as for [[Action4\|action 4]], but the offset may only refer to a text ID in the D000 or DC00 range of IDs.

	Action 13 is skipped if the given ~~grfID~~ cannot be found or if the file is inactive; action 13 generates an error message and disables the current file if it appears before the GRF that it is translating.		Action 13 is skipped if the given GRFID cannot be found or if the file is inactive; action 13 generates an error message and disables the current file if it appears before the GRF that it is translating.

Pm-bot: use grfID consistently

2011-06-15T16:03:52Z

use grfID consistently

← Older revision		Revision as of 16:03, 15 June 2011
Line 9:		Line 9:
	The data looks as follows:		The data looks as follows:

	<sprite-number> * <length> 13 <feature> <~~grfid~~> <num-ent> <offset> <text...>		<sprite-number> * <length> 13 <feature> <grfID> <num-ent> <offset> <text...>

	{\|		{\|
Line 29:		Line 29:
	\|Action 13		\|Action 13
	\|-		\|-
	\|<~~grfid~~>		\|<grfID>
	\|4*B		\|4*B
	\|The ~~GRFID~~ of the file whose texts are to be translated		\|The grfID of the file whose texts are to be translated
	\|-		\|-
	\|<num-ent>		\|<num-ent>
Line 49:		Line 49:
	For action 13, <num-ent>, <offset> and <text...> work exactly as for [[Action4\|action 4]], but the offset may only refer to a text ID in the D000 or DC00 range of IDs.		For action 13, <num-ent>, <offset> and <text...> work exactly as for [[Action4\|action 4]], but the offset may only refer to a text ID in the D000 or DC00 range of IDs.

	Action 13 is skipped if the given ~~GRFID~~ cannot be found or if the file is inactive; action 13 generates an error message and disables the current file if it appears before the GRF that it is translating.		Action 13 is skipped if the given grfID cannot be found or if the file is inactive; action 13 generates an error message and disables the current file if it appears before the GRF that it is translating.

Pm-bot: Beautify wiki markup

2011-06-15T14:48:48Z

Beautify wiki markup

← Older revision		Revision as of 14:48, 15 June 2011
Line 5:		Line 5:
	Available since 2.6 alpha 1 (r857).		Available since 2.6 alpha 1 (r857).

	==Format==		== Format ==

	The data looks as follows:		The data looks as follows: