Nightinggale
Deity
- Joined
- Feb 2, 2009
- Messages
- 5,378
I haven't been overly active on the forum either because I haven't had much to say. I'm working on getting full support for Russian and it turned into adding support for all single byte codepages listed here: http://msdn.microsoft.com/en-us/goglobal/bb964654
Middle East and Far East languages needs a different font file, but apart from that it seems to be working. I'm going to write a new XML interface to set up IDs for GameFont as we will need one, which can tell which unicode IDs goes with which GameFont IDs.
There are also some bugs and exe limitations, which needs to be worked out. For starters windows sets which codepage to use, which might not be the one we want. This is actually a vanilla bug as GameFont is hardcoded to windows-1252. Functions to change which codepage to use was added in vs2005, but we have to use the 2003 edition
I'm thinking of adding a guide on how to change this setting in windows or tell people to use AppLocale. Also I think that most people will not suffer from this problem as usually windows is set to use the local language meaning if you depend on getting Cyrillic, your windows is likely set to Russian and you will get the right codepage. The problem is that relying on windows to set the right codepage is unreliable and what if it sets it to windows-1250? None of the translations will look right in that one, though basic A-Z looks right in all of them.
Middle East and Far East languages needs a different font file, but apart from that it seems to be working. I'm going to write a new XML interface to set up IDs for GameFont as we will need one, which can tell which unicode IDs goes with which GameFont IDs.
There are also some bugs and exe limitations, which needs to be worked out. For starters windows sets which codepage to use, which might not be the one we want. This is actually a vanilla bug as GameFont is hardcoded to windows-1252. Functions to change which codepage to use was added in vs2005, but we have to use the 2003 edition

I'm thinking of adding a guide on how to change this setting in windows or tell people to use AppLocale. Also I think that most people will not suffer from this problem as usually windows is set to use the local language meaning if you depend on getting Cyrillic, your windows is likely set to Russian and you will get the right codepage. The problem is that relying on windows to set the right codepage is unreliable and what if it sets it to windows-1250? None of the translations will look right in that one, though basic A-Z looks right in all of them.