Bug with special characters when nativizing blueprints
The Unreal Build Tool fails when packaging a project (tested when packaging for Android (DXT)), with some nativized blueprints and those nativized blueprints reference a C++ class (cpp or header file) that contains Umlauts like "ö" even just in comments, even when compilation and packaging the same project without nativized blueprints works without failure.
The Build Tool fails with error message: " fatal error: UTF-16 (LE) byte detected in file, but encoding is not supported". The file is encoded in UTF-8.
Keep in mind that "ö" is a legal character in UTF-8 and is not supposed to be a problem, especially not when only used in comments.
asked Dec 11 '17 at 06:58 PM in Bug Reports
It's not a bug, it was intentional. I have no idea why. I just know I had to replace the © in all my file headers with (c) to get it to compile -- maybe around 4.16-4.17 or so.
If you only use the character(s) in comments then just remove them, no choice AFAIK.
If you have them in your strings then there is a localization system that Epic put in. You'll need to use that to use special characters in the actual game. You could look here: https://wiki.unrealengine.com/The_Easy_Way_Of_Translating_Your_Game but note it's pretty old so things may have changed a bit since then.
answered Dec 12 '17 at 02:22 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here