I managed to trigger a very interesting bug... :)

[JSWolf]

Originally Posted by Terisa de morgan

Some related to jacket position (it works), tocs (so so) and covers (still pending).

ToC as in the NCX ToC? What are you going to eventually be doing with covers?

[Terisa de morgan]

Originally Posted by JSWolf

ToC as in the NCX ToC? What are you going to eventually be doing with covers?

To remove automatically the cover from the ToC when they appear. And yes, NCX ToC.

[compurandom]

It would be nice to fix a lot of things in TOCs...

Like removing stub TOCs, fixing TOCs that are out of order, maybe trim TOCs that are too deep with too many entries... I've seen a lot of TOCs with bad links that point to files missing from the epub, although adding the missing files would be better.

[JSWolf]

Originally Posted by Terisa de morgan

To remove automatically the cover from the ToC when they appear. And yes, NCX ToC.

I would like it if Modify ePub could add the cover to the NCX ToC if it doesn't exist. I like seeing the cover for my ePub. I always replace the generic cover with a real cover.

[DNSB]

Originally Posted by compurandom

You are completely missing the point. The point is that the books are not functioning the way the user desires. It doeasn't matter where the bug is, if it doesn't function the way the user wants, IT IS A BUG.

Your attempted logic is giving me a sprong ache. A bug is not something that does not function the way a user wants. Otherwise, following your logic, since my TV will not display a 4x3 broadcast without pillarboxing, that would be a bug.

IMNSHO, a bug is something that does not work the way the programmer intended. Since you seem to want the kepub renderer to function contrary to the epub 3 specification it was written to comply with, I would have to say it is not a bug. Is this a bug in the program you are using to convert epub to kepub? As I said before, GIGO. Giving it good input is yours to do.

You might try asking Kobo for a feature enhancement but since, AFAIK, Kobo does not officially or unofficially support third-party conversions to kepub, you may have tough sledding.

[DNSB]

Originally Posted by JSWolf

I would like it if Modify ePub could add the cover to the NCX ToC if it doesn't exist. I like seeing the cover for my ePub. I always replace the generic cover with a real cover.

Personally, I modify the NCX TOC to remove any references prior to the text I consider the start of the book so the first time I read the book, it will start where I want to start reading. The cover page, title page, blurb for the book, table of contents, list of other books by the author, copyright, etc. do not qualify. This does not prevent my ereader from displaying the cover on the sleep/power off screens, or in the home page, library, etc. views.

[JSWolf]

Originally Posted by DNSB

Personally, I modify the NCX TOC to remove any references prior to the text I consider the start of the book so the first time I read the book, it will start where I want to start reading. The cover page, title page, blurb for the book, table of contents, list of other books by the author, copyright, etc. do not qualify. This does not prevent my ereader from displaying the cover on the sleep/power off screens, or in the home page, library, etc. views.

I remove all of the rubbish like a review page, page full of links that some call a ToC, other books by the author, etc. I do have the cover shown when the book is first opened and from there it goes to the title page. I don't have any rubbish so I get right to the book in two page turns.

[jackie_w]

Originally Posted by JSWolf

I remove all of the rubbish like a review page, page full of links that some call a ToC, other books by the author, etc.

Me too. This is the second time this year I find myself in full agreement with you. Are you getting more reasonable or am I going off the rails?

[DNSB]

Originally Posted by JSWolf

I remove all of the rubbish like a review page, page full of links that some call a ToC, other books by the author, etc. I do have the cover shown when the book is first opened and from there it goes to the title page. I don't have any rubbish so I get right to the book in two page turns.

Whereas I leave the junk in place and use the oddity in the epub renderer that it starts on the first item listed in the toc.ncx the first time you open an ebook. Same effect other than I am really not interested in seeing the cover or title page.

Given the last book I modified would have required 28 page turns to get to the epigraph, it's worthwhile for me to do this while doing my usual cleanup on any new books such as removing references to fonts that are not found on ereaders without embedding them?

[Terisa de morgan]

Originally Posted by JSWolf

I would like it if Modify ePub could add the cover to the NCX ToC if it doesn't exist. I like seeing the cover for my ePub. I always replace the generic cover with a real cover.

I'm just the opposite, and some day I will be motivated enough to debug my modifications (emphasis in my, as some other plugins).

[JSWolf]

Originally Posted by jackie_w

Me too. This is the second time this year I find myself in full agreement with you. Are you getting more reasonable or am I going off the rails?

I think it's a bit of both.

I'm glad you are mellowing. It looks good.

[JSWolf]

Originally Posted by DNSB

Whereas I leave the junk in place and use the oddity in the epub renderer that it starts on the first item listed in the toc.ncx the first time you open an ebook. Same effect other than I am really not interested in seeing the cover or title page.

Given the last book I modified would have required 28 page turns to get to the epigraph, it's worthwhile for me to do this while doing my usual cleanup on any new books such as removing references to fonts that are not found on ereaders without embedding them?

The difference is that I get rid of extra crud meaning any embedded fonts I don't need/want as in Next Reads and the fonts that go with it from Penguin Random House eBooks and any excess graphics. I also modify a few other things like getting rid of excess CSS and making the margins to 0 and normalizing the font sizes where needed. I also losslessly compress all the graphics. I also make sure cover is the first NCX entry. I then validate. I don't have strange issues with validated eBooks.

[Terisa de morgan]

Originally Posted by JSWolf

The difference is that I get rid of extra crud meaning any embedded fonts I don't need/want as in Next Reads and the fonts that go with it from Penguin Random House eBooks and any excess graphics. I also modify a few other things like getting rid of excess CSS and making the margins to 0 and normalizing the font sizes where needed. I also losslessly compress all the graphics. I also make sure cover is the first NCX entry. I then validate. I don't have strange issues with validated eBooks.

I do almost the same than you... But removing cover from NCX.

[DNSB]

Originally Posted by JSWolf

The difference is that I get rid of extra crud meaning any embedded fonts I don't need/want as in Next Reads and the fonts that go with it from Penguin Random House eBooks and any excess graphics. I also modify a few other things like getting rid of excess CSS and making the margins to 0 and normalizing the font sizes where needed. I also losslessly compress all the graphics. I also make sure cover is the first NCX entry. I then validate. I don't have strange issues with validated eBooks.

I have to almost agree with you there though I tend to validate on opening before I even start editing. A surprising number of commercial ebooks fail to validate. Once I have modified and validated, the number of issues with reading the ebooks is pretty minimal. I don't bother with trying to losslessly compress the graphics since very few graphics source supply lossless originals.

One fun item were the sheer number of ebooks where the cover image was repeated. Attributor protected ebooks were a fine example where the first cover image had their logo and the second did not but there were enough others that bulked up the ebook with two cover images. Then there were those ebooks where the scene and/or chapter break was a graphic and every break had it's own copy of the image.

[compurandom]

Originally Posted by DNSB

A bug is not something that does not function the way a user wants.

Most of the professional computer industry might not agree with you.

I believe the old hacker's description of that is "broken as designed".

Now, if you document how broken it is, it becomes a misfeature.