Umlauts in config files cause encoding issues when synced through Perforce

When an Umlaut character is in an .ini file in the Engine that is in Perforce as a Text file type, the encoding for the text file becomes messed up once it is synced. This does not occur when testing the same behavior with normal text files.

1. Create a new project, add it to a perforce repository, and set up source control settings in the project
2. Inside of Project Settings > Input, create a new Action Mapping and call it ö (alt+0246)
3. Save the project
4. If the DefaultInput.ini in the Config folder isn't added to perforce, add it to perforce and set its Base Filetype to Text, to match all other .ini files.
5. Navigate to the "Workspace" tab in Perforce and remove the DefaultInput.ini from your workspace
6. Return to the "Depot" tab and then run "Get Latest Revision" on the DefaultInput.ini
7. Open DefaultInput.ini
   Result: Most of the text has been changed to Chinese
   Expected: All of the text should be the same.