v1.10 contains a fix and has been tested by an affected user.

The only thing is, I can still not reproduce the issue myself.

But at least, it is fixed

I still cannot reproduce this error on my machine. It must be something related to special characters or locale settings. 🤔

An awesome user gave me his corrupted data for me to test with, because I could not reproduce this before.

So I will work on this with highest priority