Quote:
Originally Posted by Sarmat89
Why can't you detect the encoding of the existing INI file? Is that due to QT limitations?
|
It wouldn't matter. There's no way to guarantee error-free conversion back to ascii with ascii-escaped representations of utf-8 characters (and ONLY utf-8 characters that can't be represented with ascii) without causing worse damage to the INIs.
We messed up. All we can do now is rip the band-aid off and move forward with the correction. If you have preference backups from Sigil 0.9.10, you're golden. If you don't, you'll have some work to do to upgrade to the next version. For that we profusely apologize, but it is what it is. If we had a way to make this painless for everybody, we surely would. But this is why we made the recommendation to back up your preferences for 0.9.10 before we ever released 0.9.11.