Firmware 4.32.19501

[mzel]

Originally Posted by davidfor

But, when are the freezes happening? Does the device recover? Or do you need to restart it?

It happens to me when my Forma is sleeping in koreader. It does not happen too often. I'd say once in two weeks. I see no difference between the current FW, or the previous versions.
To bring it back I have to restart it by the long press on the power button. Sometimes that does not work from the first time too.

[JSWolf]

Originally Posted by davidfor

Individual books can be checked with the calibre editor or Sigil. Both have ways to check for errors. Someone will tell you to use EPUBCheck, but that is overkill for this. If the book passes the check in the calibre editor without errors, I don't believe it will cause errors on the device.

Epubcheck is not overkill. I use both Calibre's error checker and epubcheck and if both pass, I'm good to go.

[MGlitch]

Originally Posted by mzel

It happens to me when my Forma is sleeping in koreader. It does not happen too often. I'd say once in two weeks. I see no difference between the current FW, or the previous versions.
To bring it back I have to restart it by the long press on the power button. Sometimes that does not work from the first time too.

KOReader isn’t stock so you’d have to chase down any potential issues there. Unless it also happens when you’re not using KOReader at all.

[Sirtel]

Originally Posted by JSWolf

Epubcheck is not overkill. I use both Calibre's error checker and epubcheck and if both pass, I'm good to go.

I don't check for errors at all. No freezes.

[JSWolf]

Originally Posted by Sirtel

I don't check for errors at all. No freezes.

In the past (pre-Kobo) most problems with Readers were due to errors in eBooks. So as long as i'm editing the code, I may as well check that I didn't make any structural mistakes. Also, I have checked some eBooks before making any changes and yes, there were errors.

[Sirtel]

Originally Posted by JSWolf

In the past (pre-Kobo) most problems with Readers were due to errors in eBooks. So as long as i'm editing the code, I may as well check that I didn't make any structural mistakes. Also, I have checked some eBooks before making any changes and yes, there were errors.

Of course there are, but as long as I can read them just fine, I'm not going to bother with them. Editing all my purchases takes enough time as it is, I don't want to spend any more on things that may never interfere with my reading.

Of course I buy by the hundreds. I don't read library books and KU isn't available in my country. So I have my hands full without adding error checking/fixing to my workload.

[DNSB]

Originally Posted by JSWolf

In the past (pre-Kobo) most problems with Readers were due to errors in eBooks. So as long as i'm editing the code, I may as well check that I didn't make any structural mistakes. Also, I have checked some eBooks before making any changes and yes, there were errors.

I have to agree with Jon here. I do check my ebooks for errors and correct any that are found. And yes, many of those errors are found in books from both indie and traditionally published books.

One recent horrible example was a freebie which had a single text document which was a web page—the code for different browsers was a dead giveaway —which did not display happily on my epub ereaders though the mobi version was not all that bad. A bit of splitting the various text segments, removal of unneeded javascript, etc., using Sigil's tool to convert inline styles to a stylesheet and then coalescing similar stylesheet entries wasted 30 minutes of my time but did give my wife a readable ebook.

The WebKit based renderer used by Kobo for .kepub.epub was not overly unhappy with the original epub though the attempted prettification of the chapter and part headers was a bit hard to take. Basically each letter had a random size making the chapter titles and headers look like a ransom note)

[Deobulakenyo]

Originally Posted by JSWolf

Epubcheck is not overkill. I use both Calibre's error checker and epubcheck and if both pass, I'm good to go.

I installed epubcheck plugin and i can't make it work. It says i do not have ACE whatever that is.

[compurandom]

I've had a number of epubs crash my kobo.

Most of the time, if I strip out all javascript and then do an epub->epub conversion with calibre, it fixes it. Sometimes the errors in the epub are too clever for that, and I have to bring it into the calibre epub editor and run it through the bug fixes a few times.

Usually the result is a book that leaves the kobo more responsive and is easier to read, and it rarely takes me more time to do than it would to read the table of contents of the book.

[davidfor]

Originally Posted by JSWolf

Epubcheck is not overkill. I use both Calibre's error checker and epubcheck and if both pass, I'm good to go.

Please actually read what I said. I was very explicit in what I said. I am only trying to get these books working. Epubcheck is unnecessary.

But, if you are being insistent, then I think that Epubcheck is extreme overkill for anyone preparing books for their own use. There are to things it highlights that just aren't a worry. Running it on top of either the calibre editor or Sigil check is just not needed.

And, unlike you, if someone can demonstrate a real problem on a Kobo ereader for a book that passes either the calibre editor or Sigil checks but not EPUBCheck, then I will take my words back.

[DNSB]

Originally Posted by Deobulakenyo

I installed epubcheck plugin and i can't make it work. It says i do not have ACE whatever that is.

Two options here, you have installed thiago.eec's Check Book plugin which seems to have rather severe issues. When I tried installing it a couple of months back, I couldn't even run the customization. I got bored watching the rotating ring after 10 minutes or so. It sounded nice since it could run Daisy's ACE accessibility checker and epub check from calibre's GUI but since I use both of those under Sigil, it wasn't worth the time to troubleshoot the issue.

Edit: had some time today and as part of the troubleshooting, installed node.js and ace before re-installing Check book. This allowed me to customize the plugin and then it would work. See the Daisy consortium page for Installation instructions.

Alternatively, you installed the epubcheck plugin for calibre's editor. If so, try installing Java. Epubcheck is a Java program (being stored as a .jar file is a bit of a dead giveaway). Check in the calibre plugins' epubcheck forum for more help.

[JSWolf]

Originally Posted by DNSB

Alternatively, you installed the epubcheck plugin for calibre's editor. If so, try installing Java. Epubcheck is a Java program (being stored as a .jar file is a bit of a dead giveaway). Check in the calibre plugins' epubcheck forum for more help.

Make sure you have the 64-bit version of Java installed. epubcheck may not work with the 32-bit version.

[Karellen]

Originally Posted by davidfor

Reading estimate Lower: program:mod($$#words, 12)
Reading estimate Higher: program:mod($$#words, 10)

I am not really sure what the 12 and 10 represent in the code above.
I get some weird estimates, like...
a 10,545 word book takes between 9 - 5 hours
a 109,767 word book takes between 3 - 5 hours
a 237,305 word book takes between 5 - 5 hours
a 372,000 word book has no estimates.

If I want to adjust the reading speed to between 200 and 250 words per minute, what values should I use?

[Skydog]

Sadly, our friend davidfor passed away last year.

[Karellen]

Originally Posted by Skydog

Sadly, our friend davidfor passed away last year.

Yes I am aware. Very, very sad.

I quoted his post for reference and I was hoping others might know the answer.