Codepage/encoding issue with objectives and information strings in level scripts

[AdamPlenty]

Some characters, such as â, display just fine when read from the dat files, but are corrupted when read from a level script. An easy way to test this is to look at the French string 51 in Flowerhat; put the same string into a QUICK_OBJECTIVE or QUICK_INFORMATION script command, and the â will be corrupted. This happens with both UTF-8 and ANSI encodings, albeit with different corruptions.

[Loobinex]

Yes, this came up on discord a while back, and long story short, it's hear to stay.

[AdamPlenty]

Is there something that causes the game to treat level script strings as having a different codepage?

[AdamPlenty]

It seems this is a Notepad issue; even in ANSI, it saves â as 0xE2, but it should be 0x83. If I hex edit it to 0x83, it displays fine.

[AdamPlenty]

It seems this is a Notepad issue; even in ANSI, it saves â as 0xE2, but it should be 0x83. If I hex edit it to 0x83, it displays fine.

Notepad uses codepage 1252 for ANSI, not 850, which is what the game uses. We need something that uses codepage 850.

[AdamPlenty]

This is how to fix it:

[PieterVdc]

I'll look into it after the toml is in, already added conversion logic there