English/Chinese messages and text encoding
Server text, log text, client interface text and SQL storage are different layers. Translate display content while retaining keys and placeholders.
The outcome to aim for
Server text, log text, client interface text and SQL storage are different layers. Translate display content while retaining keys and placeholders.
Before you start
Read the complete procedure and its version notes. Record the affected server role and keep an untouched backup outside scanned data folders.
Files you need
One step at a time
- STEP 1
ENG is English and CHS is Simplified Chinese. Keep catalog keys consistent across supported language folders. The server also ships SPN, POR and THA catalogs.
- STEP 2
Preserve %s, %d, formatting controls and tab delimiters in TSV catalogs. A changed placeholder can break a message even when the translation looks correct.
- STEP 3
Client labels require the matching client language resources. Changing a server Message.xml string does not translate an unrelated client button.
- STEP 4
For Chinese names, inspect MultilingualNameSwitch and ChineseGuildNameSwitch, then follow the supplied database migration instructions. Collation changes need a planned backup and application compatibility check.
- STEP 5
Test character names, guild names, chat, notices, command aliases and logs after relog; use more than one client language.
Progress is saved only in this browser. Completion is your learning record, not proof of a live server change.
Apply the real change
Use the load method stated in the steps for this system. Startup-only settings require a planned restart. The reload finder below shows recorded groups; confirm whether the particular field is startup-only.
Find the file’s reload instructions →Verify the result in game
If the expected result is missing, restore the backed-up files and repeat the same reload/restart before adding another change.