Difference between revisions of "Localization"

From wowdev
Jump to navigation Jump to search
(Localization offset is cancaled in Cataclysm.)
Line 1: Line 1:
 +
A column marked as Loc is actually 16 columns with one column per language and a bitmask in the end.
 +
 +
There can be multiple languages filled in -- i.e. multi-language DBCs are possible.
 +
 +
Blizzard no longer uses multiple columns for Localization since Cataclysm. From there on, there just is one column with a string in the language given by the locale directory. This conserves space and prevents errors with missing locale data as present on a lot of modded servers, where a locale_i DBC is taken and edited, packed and distributed, therefore resulting in empty strings for all clients not using locale_i. In Cataclysm and up, there just will be wrong language strings.
 +
 
{| style="background:#FCFCFC; color:black"
 
{| style="background:#FCFCFC; color:black"
 
|-  
 
|-  
Line 25: Line 31:
 
| +16 || || BitMask that always follows output string data.
 
| +16 || || BitMask that always follows output string data.
 
|}
 
|}
 
Localization offset is cancaled in Cataclysm.
 

Revision as of 21:52, 6 October 2012

A column marked as Loc is actually 16 columns with one column per language and a bitmask in the end.

There can be multiple languages filled in -- i.e. multi-language DBCs are possible.

Blizzard no longer uses multiple columns for Localization since Cataclysm. From there on, there just is one column with a string in the language given by the locale directory. This conserves space and prevents errors with missing locale data as present on a lot of modded servers, where a locale_i DBC is taken and edited, packed and distributed, therefore resulting in empty strings for all clients not using locale_i. In Cataclysm and up, there just will be wrong language strings.

Column Field
0 enUS / enGB English / Great British
1 koKR Korean
2 frFR French
3 deDE German
4 zhCN Chinese
5 zhTW Taiwan
6 esES / esMX Spanish / Mexican
7 ? ?
8 ruRU Russian
+16 BitMask that always follows output string data.