Localize Asset - Revision history

CraigChrist8239 at 07:06, 31 October 2015

2015-10-31T07:06:57Z

← Older revision		Revision as of 07:06, 31 October 2015
Line 9:		Line 9:
	[[Category:BO1]]		[[Category:BO1]]
	[[Category:BO2]]		[[Category:BO2]]
	Localize assets are by far the simplest asset to work with. These take the normal concept of localized strings, in that developers can use a simple ID string that will find the localize asset with the appropriately formatted string, so language experts and translators conflict with programmers as little as possible. This asset is so simple, that it hasn't changed from the leaked Call of Duty 4 Alpha all the way up to ~~Advanced Warfare~~.		[[Category:BO3]]
			Localize assets are by far the simplest asset to work with. These take the normal concept of localized strings, in that developers can use a simple ID string that will find the localize asset with the appropriately formatted string, so language experts and translators conflict with programmers as little as possible. This asset is so simple, that it hasn't changed from the leaked Call of Duty 4 Alpha all the way up to Black Ops 3.
	struct LocalizeEntry		struct LocalizeEntry
	{		{

CraigChrist8239: /* Source Format */

2014-12-28T09:18:24Z

Source Format

← Older revision		Revision as of 09:18, 28 December 2014
Line 28:		Line 28:
	For example take the following localized string in the "exe.str",		For example take the following localized string in the "exe.str",
	REFERENCE SERVERISFULL		REFERENCE SERVERISFULL
			LANG_ENGLISH "Server is full."
			Also notes and flags can be applied to individual localized strings, which are skipped by the compiler, like so
			REFERENCE SERVERISFULL
			NOTES "The string returned when a client tries to join a game that is filled"
			FLAGS "0"
	LANG_ENGLISH "Server is full."		LANG_ENGLISH "Server is full."
	If you compiled this for the english version of the game, it would produce the localized string EXE_SERVERISFULL with the value "Server is full."		If you compiled this for the english version of the game, it would produce the localized string EXE_SERVERISFULL with the value "Server is full."

CraigChrist8239 at 21:19, 28 October 2014

2014-10-28T21:19:21Z

← Older revision		Revision as of 21:19, 28 October 2014
Line 5:		Line 5:
	[[Category:MW3]]		[[Category:MW3]]
	[[Category:Ghosts]]		[[Category:Ghosts]]
			[[Category:AW]]
	[[Category:WaW]]		[[Category:WaW]]
	[[Category:BO1]]		[[Category:BO1]]
	[[Category:BO2]]		[[Category:BO2]]
	Localize assets are by far the simplest asset to work with. These take the normal concept of localized strings, in that developers can use a simple ID string that will find the localize asset with the appropriately formatted string, so language experts and translators conflict with programmers as little as possible. This asset is so simple, that it hasn't changed from the leaked Call of Duty 4 Alpha all the way up to ~~Ghosts~~.		Localize assets are by far the simplest asset to work with. These take the normal concept of localized strings, in that developers can use a simple ID string that will find the localize asset with the appropriately formatted string, so language experts and translators conflict with programmers as little as possible. This asset is so simple, that it hasn't changed from the leaked Call of Duty 4 Alpha all the way up to Advanced Warfare.
	struct LocalizeEntry		struct LocalizeEntry
	{		{

CraigChrist8239 at 20:48, 29 December 2013

2013-12-29T20:48:00Z

← Older revision		Revision as of 20:48, 29 December 2013
Line 1:		Line 1:
	__NOTOC__		__NOTOC__
	[[:Category:Assets]]		[[Category:Assets]]
	[[:Category:CoD4]]		[[Category:CoD4]]
	[[:Category:MW2]]		[[Category:MW2]]
	[[:Category:MW3]]		[[Category:MW3]]
	[[:Category:Ghosts]]		[[Category:Ghosts]]
	[[:Category:WaW]]		[[Category:WaW]]
	[[:Category:BO1]]		[[Category:BO1]]
	[[:Category:BO2]]		[[Category:BO2]]
	Localize assets are by far the simplest asset to work with. These take the normal concept of localized strings, in that developers can use a simple ID string that will find the localize asset with the appropriately formatted string, so language experts and translators conflict with programmers as little as possible. This asset is so simple, that it hasn't changed from the leaked Call of Duty 4 Alpha all the way up to Ghosts.		Localize assets are by far the simplest asset to work with. These take the normal concept of localized strings, in that developers can use a simple ID string that will find the localize asset with the appropriately formatted string, so language experts and translators conflict with programmers as little as possible. This asset is so simple, that it hasn't changed from the leaked Call of Duty 4 Alpha all the way up to Ghosts.
	struct LocalizeEntry		struct LocalizeEntry

CraigChrist8239: Created page with "NOTOC :Category:Assets :Category:CoD4 :Category:MW2 :Category:MW3 :Category:Ghosts :Category:WaW :Category:BO1 :Category:BO2 Localize asset..."

2013-12-29T20:47:31Z

Created page with "__NOTOC__ Category:Assets Category:CoD4 Category:MW2 Category:MW3 Category:Ghosts Category:WaW Category:BO1 Category:BO2 Localize asset..."

New page

__NOTOC__
[[:Category:Assets]]
[[:Category:CoD4]]
[[:Category:MW2]]
[[:Category:MW3]]
[[:Category:Ghosts]]
[[:Category:WaW]]
[[:Category:BO1]]
[[:Category:BO2]]
Localize assets are by far the simplest asset to work with. These take the normal concept of localized strings, in that developers can use a simple ID string that will find the localize asset with the appropriately formatted string, so language experts and translators conflict with programmers as little as possible. This asset is so simple, that it hasn't changed from the leaked Call of Duty 4 Alpha all the way up to Ghosts.
struct LocalizeEntry
{
const char *value;
const char *name;
};
Where name would be the ID the developer uses, and then value would be the translated string for this version of the game.
== Source Format ==
The localized strings are located in ".str" files at the path "raw/english/localizedstrings/". The ".str" file can have normal C++ notes, and is preceded with the following header.
VERSION "1"
CONFIG "C:\trees\cod3\cod3\bin\StringEd.cfg"
FILENOTES ""
Each string is then separated into ".str" files by category, with the file name being appended to the localized strings at compilation. Each individual string is stored in a ".str" file like so,
REFERENCE NAME
LANG_ENGLISH "Value"
Then each language is added like so. Be aware that the value "#same" will copy the text from the english version of the game.
LANG_GERMAN "Wert"
For example take the following localized string in the "exe.str",
REFERENCE SERVERISFULL
LANG_ENGLISH "Server is full."
If you compiled this for the english version of the game, it would produce the localized string EXE_SERVERISFULL with the value "Server is full."

Localize Asset - Revision history

CraigChrist8239 at 07:06, 31 October 2015

CraigChrist8239: /* Source Format */

CraigChrist8239 at 21:19, 28 October 2014

CraigChrist8239 at 20:48, 29 December 2013

CraigChrist8239: Created page with "__NOTOC__ :Category:Assets :Category:CoD4 :Category:MW2 :Category:MW3 :Category:Ghosts :Category:WaW :Category:BO1 :Category:BO2 Localize asset..."

CraigChrist8239: Created page with "NOTOC :Category:Assets :Category:CoD4 :Category:MW2 :Category:MW3 :Category:Ghosts :Category:WaW :Category:BO1 :Category:BO2 Localize asset..."