Offsets change from client to client... If you have English and Korean my guess is that you have client translated with a new translation section in the PE.
The default code page is determined by the OS, and currently XP and Vista do it differently... 98 and NT4 will ONLY use the code page of the global system.
PT Game.exe is not Unicode, therefore you can only use ONE code page character set in ONE exe. This means, if you use Korean client exe non ASCII characters will be Korean, if you use Chinese client non ASCII characters will be Chinese. etc.
The code page in XP is usually the default user code page, OR the code page of the exe depending on MUI installation and XP East Asian Font Fix installation on the machine.
The code page use in Vista is largely determined by the default language of the client executable. It's default code page is looked up by the default language in the Version string of the resource section, which is removed from many modified executables because XP ignores it, and that wasn't the reason default language is included in a version string, but it's a good indicator to ease internationalisation. ^_^
My greatest problem with translating to languages that don't use Latin script is the way different operating systems interpret non Latin characters on different language versions.
If the PT game exe was Unicode and / or used Windows WChar strings instead of C ZStrings there would be no issue. But it doesn't, and I don't know of a
good way to make it do so.
Many intermediate solutions have been tried... Usually involving installation of one or other Microsoft internationalisation patches on to the client computer... which then present other problems, but provide reasonable coverage to the majority of your users.
The ultimate, correct solution is to use Korean client for Korean version, Japanese client for Japanese version and Vietnamese client for Vietnamese version... you can put English in any client (because ASCII characters are included in all code pages) and if you drop accents in French, Portuguese, German, Dutch etc. you can do the same... If you want to translate to Russian, Greek, Arabic or Hebrew or such, you are pretty much up a certain creek without a paddle.
Then, your only option is to force a code page via compatibility options on the client PC, and the process of doing that varies according to Windows OS version. 95-ME (Version 4) is different to 2K/XP (Version 5) is different again in Vista (Version 6) though the process is still the same in Windows 7 Betas, the XP/2K method still worked in Longhorn Betas, but don't in Vista. They just make a mess of your machine which is really difficult to uninstall and easier to re-install Vista, or use System Restore.
There must be a way to set the code page of the exe the way it has been done in the various official builds... if anyone knows it, please share. Even so, this doesn't correct the garbage in the window title on non-native language OS.
