Sigil 0.8.0 Released

[blackest]

Originally Posted by JSWolf

There is a very well formatted ePub version (with images) of Three Men in a Boat that you can download for free (right here at MobileRead) and not actually have to do any editing to.

Yes there is, its very good, Thats why i'm using it to look at the css and styling images based on examples from the book. It was working well in 0.74, I thought i might have corrupted it, so downloaded a fresh copy and found the same problem, switching between code and book view.

The version of Sigil 0.8.0 I compiled for OSX 10.7.5 seems to work well, it is on linux mint i'm finding a problem.

[Toxaris]

Perhaps it would be a good idea to bring BookView to its final resting place... Preview should be enough I think...

[Doitsu]

Originally Posted by blackest

Hi is there any debugging that can be turned on for Sigil i'm finding problems with 3 men in a boat on linux mint with the unofficial deb package switching between code view and book view i'm getting a segmentation fault. It could be low ram related.

I've just tested Sigil 0.8.0 with Three Men in a Boat on an old 64-bit Linux 3.2 machine with only 2GB RAM and didn't encounter any segment faults when switching between code view and book view.
You may want to test your RAM with the memory test option of a live distro to exclude RAM issues.

[blackest]

Originally Posted by Doitsu

I've just tested Sigil 0.8.0 with Three Men in a Boat on an old 64-bit Linux 3.2 machine with only 2GB RAM and didn't encounter any segment faults when switching between code view and book view.
You may want to test your RAM with the memory test option of a live distro to exclude RAM issues.

It is odd but it is a 32bit system which I should have said. Thankyou for taking time to investigate this (it also has 2gb ram).

[DiapDealer]

Originally Posted by blackest

It is odd but it is a 32bit system which I should have said. Thankyou for taking time to investigate this (it also has 2gb ram).

I haven't extensively tested the 32-bit version of my Linux binary packages, but I use the 64-bit version every day on Linux Mint with no segfaults.

The only segfaults I've ever gotten with either of those packages have been when closing Sigil--and that was always limited to the first time it was run.

As far as debugging (without compiling your own debug version), about all you can is run it using gdb and see if the backtrace after the segfault yields anything useful. Also, the launch script (/usr/local/bin/sigil) has a line commented out that would allow one to do some debugging of the launching (or the availability) of the various Qt plugins.

Also keep in mind those packages are "unofficial"
But by all means, if you discover any details about the segfault, please consider sharing them in the stickied thread for those builds. I'd love to be able to fix it if at all possible.

[blackest]

Originally Posted by blackest

It is odd but it is a 32bit system which I should have said. Thankyou for taking time to investigate this (it also has 2gb ram).

Problem cured if not solved.

In my home folder is this folder

.local/share/sigil-ebook/sigil
I deleted all its contents and started Sigil again loading the book from the command prompt.
instead of opening in code view it opened in book view and switching between views was fine.

I can only assume that something was wrong within that folder, that sigil was choking on.
It may be that this folder held preferences from 0.7.4 and they have changed between versions but that is just a guess.

[DiapDealer]

Originally Posted by blackest

Ican only assume that something was wrong within that folder, that sigil was choking on.
It may be that this folder held preferences from 0.7.4 and they have changed between versions but that is just a guess.

It's a good guess.
Deleting the Sigil.ini file and letting it be recreated has often "fixed" some Sigil issues.

[sunab]

Hi Sigil users,

Just a post to inform I've setup an Ubuntu repository (ppa) to offer lastest stable release of Sigil.

ppa:sunab/sigil-release

https://launchpad.net/~sunab/+archiv.../sigil-release

[KevinH]

Hi JSWolf,

If you turn off all auto-cleaning, load your epub, and then save it (without any cleaning) all of your font issues go away. I checked and vritually nothing in the epub is changed except for the locations of the files. Somehow the css updated font urls were not being passed to the BookView and Preview modes. It appears to be a race.

So this is a bug. That should not happen. With some help from user_none we have a tentative patch for this. If it works out, the next release will include this patch.

KevinH

Originally Posted by JSWolf

I've PMed the problematical ePub so you can have a look and see what's what.

[Hitch]

Originally Posted by Toxaris

Perhaps it would be a good idea to bring BookView to its final resting place... Preview should be enough I think...

+1

Hitch

[signum]

You have a choice to use Book View or not. I don't understand your zeal to remove that choice from me. The main thing that drew me to Sigil in the first place was that it was the ONLY product to provide WYSIWYG editing. All the other products do code editing only, and some might be a better choice for you. I'm very happy with Sigil the way it is.

[JSWolf]

Originally Posted by KevinH

Hi JSWolf,

If you turn off all auto-cleaning, load your epub, and then save it (without any cleaning) all of your font issues go away. I checked and vritually nothing in the epub is changed except for the locations of the files. Somehow the css updated font urls were not being passed to the BookView and Preview modes. It appears to be a race.

So this is a bug. That should not happen. With some help from user_none we have a tentative patch for this. If it works out, the next release will include this patch.

KevinH

Thanks for hopefully fixing this bug. I don't have auto-cleaning turned on. Just the reformatting.

[varlog]

Originally Posted by signum

You have a choice to use Book View or not. I don't understand your zeal to remove that choice from me. The main thing that drew me to Sigil in the first place was that it was the ONLY product to provide WYSIWYG editing. All the other products do code editing only, and some might be a better choice for you. I'm very happy with Sigil the way it is.

+1 (sorry Hitch, but it is an user feature).

[theducks]

Originally Posted by varlog

+1 (sorry Hitch, but it is an user feature).

It is like a modern Medication (as advertised on TV), The list of side effects is simply horrific.

[Hitch]

Originally Posted by theducks

It is like a modern Medication (as advertised on TV), The list of side effects is simply horrific.

+1.

Varlog:

Hey, as long as you're happy to answer all the questions from all the users that have issues due to it, great. I don't mean to sound snippy, but the truth is, a huge percentage of the posts on the Sigil forum are about "bugs" (hmph) that happen because John Doe thinks it's a word-processor and TREATS it as such. Sigil isn't now, and never WAS, intended to run like that. Even when Valloric first introduced it, it was never supposed to be a replacement for Word or OO or whatever-your-flavor-is. I suspect it never will be. What are we at now, in terms of lines of code? AT 7, it was what, a million lines? Do we really think that the guys will add the other 5 million lines of code that are needed to make it actually work LIKE a Word processor?

I don't understand why "preview" isn't good enough. I don't care about taking the option away from you, as long as the rest of us (who don't use it) don't have to reply to all the questions caused thereby. And, to be clear, that we aren't expected to support further enhancements in that (the word-processing/WYSIWYG) area, over productivity enhancements.

Hitch