I saw this morning lots of mails from issues I have starred saying they have been marked as fixed in 0.2.0beta. Been hitting F5 constantly since..................

Off to test this....

Thanks for all your hard work.

Edit:
I haven't used it much yet, but this baby is FAST!

Edit2:
A few niggles:
Deleting a file takes me to the top in the book browser, which is a bit of a pain, if you have a long list of files.
Can't change file extensions from within the browser. Mostly I'm thinking of changing between xtml (which Sigil uses) htm and html.

The errors are telling you that the Qt libraries that are available on the PATH do not match the ones Sigil needs.

On Linux, you cannot run the "sigil" executable directly. You need to run "sigil.sh". That sets up the LD_LIBRARY_PATH environment variable and starts Sigil. All of this is done so the Qt libs the installer places in the /opt/sigil dir are picked up during load.

The desktop and the start menu shortcuts call this shell script for you, use those.

This all pertains to Sigil installed from the provided binary installers. If you compiled the source yourself, you can just call "sigil" since you need >Qt 4.6.0 on the PATH just to compile the sources.

This behavior is nothing new and has been present in several previous versions of Sigil.

Why do you want to do that? It doesn't matter what the extension is for HTML files, what determines the "type" of HTML/XHTML is the declaration in the file. And your Reading System doesn't care, since it loads content based on the MIME type specified in the OPF.

What Sigil is trying to prevent is a user renaming an XHTML file to, say, JPEG. That would screw things up internally.

But what I could do is implement a "whitelist", where you could go from "xhtml" <-> "html" <-> "htm" etc. Same thing for "jpeg" <-> "jpg".

Thanks. Will 0.2.0 install over the top of 0.1.9 or should you uninstall it first?

If you install a new version of Sigil to a different folder than the previously installed one, then the two can safely coexist.

If you install to the same path, the original installation is overwritten. InstallJammer takes care of that, and there are no problems in 99.9999% of such overwriting installations. But then there's that 0.0001%...

Personally, I overwrite it and I've never had a problem. And no one has ever reported a problem caused by such an installation.

The errors are telling you that the Qt libraries that are available on the PATH do not match the ones Sigil needs.

On Linux, you cannot run the "sigil" executable directly. You need to run "sigil.sh". That sets up the LD_LIBRARY_PATH environment variable and starts Sigil. All of this is done so the Qt libs the installer places in the /opt/sigil dir are picked up during load.

The desktop and the start menu shortcuts call this shell script for you, use those.

Using the menu and desktop links doesn't open Sigil at all, using /opt/sigil$ ./sigil.sh on the command line results in