[kc7zzv]

Originally Posted by davidfor

That isn't correct. When a kepub is synced from the Kobo servers, the cover image is supplied separately. And the database entries aren't added in the same way as when a book is sideload. But, I assume you are talking about about the "cover-image" property. From looking at non-DRM kepubs, this is not used in them. My understanding is this is a property is from the epub3 spec. Adding it to a kepub, which is really a epub2, is a cheat I discovered a few weeks ago. I assume it works because Kobo is using the same code to handle epub3 and their kepubs.

Could you PLEASE stop belaboring this point. I don't CARE. Either it doesn't follow the spec, in which case I don't care, because it's "close enough" for import to treat as an epub or it does follow the spec, in which case it's (by definition) close enough to treat as an epub for import purposes.

> I don't know why you are seeing that performance. I recently took a 30 chapter epub that was built with one chapter per file and combined them down to three files. The sizes where about 350KB, 250KB and 700KB each. This worked perfectly on the device with no noticeable performance from the split version.

Well, I don't either. I assume it has something to do with the size, and I expect to find out during my initial exploration.

> But if the sizes are the problem, you have your conversion options set wrong. You should use the "Structure Detection" page of the conversion options to split the files into chapter based files in the epub. This is what you are saying is needed to be done to create a kepubs, so you will be relying on those options anyway.

> to be clear, a kepub does not have to be split up into a file per chapter. They follow the exact same rules for this as an epub. The designer of the book decides how to do it and Kobo just adds the extra spans and ids. I haven't seen many kepubs that don't split the chapters, but I do have some. And an important thing is that every kepub I have looked at, has exactly the same file structure as the epub I also got from the Kobo shop.

As I see it, this is entirely beside the point. Split size (in my very limited testing) can heavily impact performance, in which case, the split size on kepubs should be optimized for the kobo. It is possible that it doesn't have an impact on performance, in which case I expect to find that out too.

Just give up on convincing me that this won't speed things up. I've read enough information supporting this to believe it. Either it will, and I'll find that out in my exploration, before I write much code, or it won't, and I'll find that out during my exploration, before I write much code.


> What changes are you talking about? I tweak my epubs, but that is because I prefer them to look like paper books. In fact, if I have a paper version, I use that as the guide. But, I would be stunned if I am doing anything that would make it look worse on other readers. About the only thing I do that I think is specific to the Kobo reader is to push chapter headings low enough on the screen that they aren't hidden by the top menu when it is displayed. If you have have some examples, I would love to hear what they are.

a) Chopping the epub into tiny pieces puts in page-breaks in ugly places. It it doesn't help performance, then this isn't something I want on other readers.
b) Adding the kobo ids, spans, and javascript make the file bigger, and so does splitting the file into more pieces.



Finally, something you didn't mention is that some people don't want their Kobo reading their epubs in the "kepub reader". (Yes, calling it the kepub reader is a slight oversimplification. Please don't waste our time correcting me) By treating both formats as first class formats, users can easily choose which they want in the same way they choose between other formats, like epub vs lit.

Originally Posted by DoctorOhh

You can change the split size in the epub output preference, but...



...it doesn't split smart.

Yes. I want to try to split on chapters.

Originally Posted by DoctorOhh

I don't own a Kobo but can't you configure the filename as needed via the metadata plugboard?

I once had a computer case... It didn't have enough circulation when I put a beefy video card in it. It worked really well after drilling several holes in it, but it didn't work out of the box for me.

Basically, I want to make Calibre work really well with the Kobo, out of the box, not just for me after configuring settings, templates, the plugboard, etc...