Hello UTF experts. I need a sanity check regarding UTF handling in UE13.20+2.
I have a script that writes to the output window. The stuff that gets written originates from a DOS-ASCII file. Things are displayed correctly in the output window
For instance:
addMapField("sk-nøgtxt-10", skNoegtxt_10);
If I select this line and copy it to the clipboard and paste in into a empty DOS-ASCII file, I get:
addMapField("sk-nøgtxt-10", skNoegtxt_10);
Ok, fair enough. The scripting engine and/or the UE outputWindow method write() writes a UTF file in the outputWindow. And when I paste it into a non-UTF document some characters are "corrupted".
In UE13.10+4 I would then just perform a File - Conversions - UTF-8 to ASCII even though the file format is already ASCII. The conversion was able to find and fix characters, so I would end up with the correct ASCII data:
addMapField("sk-nøgtxt-10", skNoegtxt_10);
And then I could get on with my "ASCII" work. (I no not work with UTF files in general).
But in UE13.20+2 the menu option File - Conversions - UTF-8 to ASCII is greyed out when I'm in a non-UTF file. So suddenly I can't convert the UTF characters pasted into a non-UTF document
In the hotfix UE13.20+2 a number of hints about UTF are listed:
* Read only UTF-8, UTF-16BE, and ASCII Escaped Unicode files
* Find/replace and UTF-8 to ASCII conversion
* Save As fails to convert line endings with Unicode files
Why is UTF-8 to ASCII greyed out suddenly ? Do you think it's an error in the UE13.20+2 hotfix - or an error that's finally fixed ? If someone supports me in that it is an error in UE13.20+2 I will report it to IDM Support.
Workaround for UE13.20+2: To get on I first have to paste the clipboard contents into a blank non-UTF file. Save it to the harddisk as DOS-ASCII. And reopen the file and rely on the UTF autodetection to flag the file as a UTF-file. Then I can convert to ASCII with File - Conversions - UTF-8 to ASCII and copy/paste the string into my target file.
I have a script that writes to the output window. The stuff that gets written originates from a DOS-ASCII file. Things are displayed correctly in the output window
For instance:
addMapField("sk-nøgtxt-10", skNoegtxt_10);
If I select this line and copy it to the clipboard and paste in into a empty DOS-ASCII file, I get:
addMapField("sk-nøgtxt-10", skNoegtxt_10);
Ok, fair enough. The scripting engine and/or the UE outputWindow method write() writes a UTF file in the outputWindow. And when I paste it into a non-UTF document some characters are "corrupted".
In UE13.10+4 I would then just perform a File - Conversions - UTF-8 to ASCII even though the file format is already ASCII. The conversion was able to find and fix characters, so I would end up with the correct ASCII data:
addMapField("sk-nøgtxt-10", skNoegtxt_10);
And then I could get on with my "ASCII" work. (I no not work with UTF files in general).
But in UE13.20+2 the menu option File - Conversions - UTF-8 to ASCII is greyed out when I'm in a non-UTF file. So suddenly I can't convert the UTF characters pasted into a non-UTF document
In the hotfix UE13.20+2 a number of hints about UTF are listed:
* Read only UTF-8, UTF-16BE, and ASCII Escaped Unicode files
* Find/replace and UTF-8 to ASCII conversion
* Save As fails to convert line endings with Unicode files
Why is UTF-8 to ASCII greyed out suddenly ? Do you think it's an error in the UE13.20+2 hotfix - or an error that's finally fixed ? If someone supports me in that it is an error in UE13.20+2 I will report it to IDM Support.
Workaround for UE13.20+2: To get on I first have to paste the clipboard contents into a blank non-UTF file. Save it to the harddisk as DOS-ASCII. And reopen the file and rely on the UTF autodetection to flag the file as a UTF-file. Then I can convert to ASCII with File - Conversions - UTF-8 to ASCII and copy/paste the string into my target file.