The reason I asked how many downloads and whether those experiencing the gross performance issues use the 32 or 64 bit versions was this:
if the number of users experiencing the problems is a fraction of the Sigil 0.9.12 installed base,
and
if everyone's .ini files would have been shifted to UTF-8 then,
why are so few people experiencing those problems.
Given the behaviour I had with video embedding was so similar, and it was due to a dodgy shell extension I was using at the time, that only affected Sigil***, then...
I also wonder if it might be worth having one of the unlucky few to try uninstalling whatever bit-wise they have and installing the other one (i.e. if they installed 64bit, uninstall that, and install the 32bit). That's been known to solve inexplicable calibre issues - Qt being the common denominator.
But then again who knew .ini file encoding could be so recalcitrant
*** that's not a reflection on Sigil, the same shell extension feature had an inconsequential side effect on a later version of my preferred file manager - which apart from being written in C++ has little in common with Sigil.
BR
Quote:
Originally Posted by KevinH
If not your ini files are fine and then we are back to what BetterRed suggested that something on your Windows machine is causing havoc for Sigil.
|