Console text encoding issues during mod installation

[Argent77]

I found a strange encoding issue for text displayed during installation in the text console. WeiDU appears to switch character encoding from OEM 850 to Windows-1252.

A test mod to demonstrate: TestEncoding.zip (Screenshot)

The test mod includes a single traified line that contains the special character 'Æ' in both OEM 850 and Windows-1252 encoding.

Text in component name is initially displayed in OEM 850 (expected), but subsequent copies of the same line are displayed in Windows-1252 encoding if you install the component (unexpected). Encoding stays in OEM 850 if you choose not to install the component.

(Tested on Windows 7 with western regional settings.)

[Wisp]

This is not WeiDU, it's Windows. Install the mod from the command line and redirect (>) the command output to some file. No strings are changed.

[AL|EN]

@Argent77
I face similar issue but testing using Windows 10 1507 show no issue: http://image.prntscr.com/image/5fabf504d9ff4162b18c72fee391520a.png


Adding UTF-8 into Windows Console (CMD) is not an easy task because:

As Chip said, UTF-16 is rather baked into the stuff we do. The console host does use UTF-16 somewhere in there. We just have the matter of dealing with code pages throughout the history of computing existence that causes us heartburn every time we think about how to fix this. It’s definitely something that we would like to look into on our backlog.