Quote:
Originally Posted by KevinH
Just pushed that change to master.
|
A quick test on Windows 10 shows no problems (Windows 10). I did basically the same tests that you described earlier in the thread. Sigil actually converted my ini files to utf-8 whenever Sigil opened. There was no need to save or close.
The only issue I see that may trip a few people up, is that some of the default Saved Searches (convert entities to characters and vice-versa) can look like the Replace/Find field is empty after converting the file to utf-8. Anything with invisible space characters can look empty now. But that will also only affect the manual editing of those files. The Saved Search editor dialog has always looked like there's nothing in fields with invisible unicode characters (even when they were stored in the ini files as escape coded).
The good news is that they can still add those invisible characters as escaped hex codes when manually editing those files. And Sigil will convert them.
They've always had to enter unicode characters in the Saved Search Editor Dialog: escaped hex codes entered there have always ended up double-escaped in the ini files.
Long story short: those who only edit Saved Searches through Sigil's dialog should notice no difference in behavior whatsoever. And those who edit the files manually should have an easier time of it!
