Hello,
First post here, and I want to thank everyone involved for an awesome game.
However, I ran into some very strange behavior yesterday when I installed the latest dev release of UFO: AI, from muton's compilation. The filename was ufoai-2.3-dev-29004-Debug-pentium3-O1-sse-7z-small-win32.exe and it installed quite handily.
I use the English language version, but for some reason when going into the input options and looking at the keybindings, they appear in Finnish. I'm located in Finland, and that's what the Windows location info says, but I have an English language Windows XP Pro and I do not ever use any programs localized to Finnish if I can help it. I could change the language of the game interface to anything I chose from the list, but no matter what I picked, the keybinding explanations stayed in Finnish.
It seems like for some reason the game was using the selected interface language files for everything else, but it always mapped the keybindings to the Windows location info and picked that language for them. I found this HIGHLY annoying. It's also an issue for users who may be in other countries and have their PC location info set according to that and then get something that is only gibberish to them. It is also an issue if there are multiple users in the same household who speak different languages and only use one language in common.
There is a workaround:
Go to the [drive]:\[installdirectory]\UFOAI-2.3-dev\base\i18n directory, make a new directory (e.g. Archive) and dump all the language subdirectories except the one you want in there. This forces the game to use the only available language file to display the keybindings in the correct language regardless of any other settings. Obviously this workaround locks the game into that one language and you need to restore the appropriate archived directories to their normal location to have the option to change the interface language.
To me, this behavior seems to be a bug, but since I know next to nothing about the architecture and the mechanics of the interface, I'm not quite sure. It could be a feature as a result of certain coding issues, but it is certainly not expected behavior. It could also be a Windows issue, which is why this post is here. For this reason it should be looked at if anyone finds the time.
Thank you for your time.