Dear Matthew,
please check this link. This is the official documentation. We also added the Config folder as proposed to the perforce stream. Also we created the TypeMap as it says. And as you can see, ini-Files should be text files, so you can diff/merge them etc. Thus, using binary does not make sense and it would also mean that I would have to change the typemap and changing ALL .ini files from text to binary file types. Would be possible but is a bit ugly.
Also please keep in mind that we now found out what the cause is and avoid Umlauts now, but this does not help other users. Also see below for why I am still thinking this is also a problem from the engine.
Additionally, as I said, just creating an empty text file with Umlauts works so from my point of view, the Engine is chainging something to the encoding part when adding Umlauts to the Input.ini. So PLEASE test this cast. Just create an empty text file (.ini) and add Umlauts (or lorem ipsum lorem etc). and add those to perforce. The file should not be messed up in any way. Thus, leading to my conclusion that the engine is changing encoding parameters when a user adds Umlauts to the Input Mapping etc.
At least you were able to reproduce the error and that the files get messed up using Umlauts as Input Action Mappings.
Also I do not understand why you can’t set an Input Ö as you mentioned, cant you add the german keyboard to windows?
Anyway, thanks for confirming that your server isn’t in Unicode-Mode. Then we at least have the same basis. If you do have a test server (because I guess you have more than 1) which is uncode-enabled, could you try the tests on this server instead? Unfortunately I cant really imagine what happens when changing the servers whole encoding to Unicode. Also because there are other non Unreal-related projects on it.