Open markusstoll opened 3 years ago
Did some research - this handling was introduced for the Windows version. I will create a PR where my fix will only affect the macOS version and leave the Windows version untouched
I guess this issue can be closed
When compiling with a fresh VisualStudio installation on macOS BigSur it turns out, the default encoding is set to ASCII which is causing some problems with your current encoding handling. Especially the path conversions for the changes view do make things worse. Before trying to build a pull request - for which runtime is this actually needed?