You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chad-Vine-Doll edited this page Oct 3, 2023
·
11 revisions
Key
The keys of every entry in each localization file follows a rule:
Separator
The Key should be seperated by .:
Examples:
"Game.Item.Coin.name"// seperated to Game->Item->Coin->name"Game-Item-Coin-name"// valid, but consider the entire string (`Game-Item-Coin-name`)// as the name of the first and only class
First class name (top domain name)
All First class should have the same name
The name of the top domain can be set up in Localization Manager
Examples:
Consider the First class of all keys are defined as "Game":
"Game.Item.Coin.name"// seperated to Game->Item->Coin->name"Other.Item.Coin.name"// Will not be recognized when building Trie for the translation keys
Value
Escapes
Raw Content of a translated message can use some escape sequence to change the value in some way
Color Pattern
The color pattern allows you to customize the color of the text.
In order to show the color of the text, the text must be displayed in text component (UGUI or TMP) and enable Rich Text
§C §
The text between two § will be display in color of C