02-16-2013, 04:09 AM | #16 | ||||||
Member
Posts: 12
Karma: 10
Join Date: Jan 2009
Device: Handspring Palm
|
Quote:
My point has been that using the epub input code will work fine. I will do more investigation before I start programming in earnest. I understand that you want to help keep me technically accurate, but correcting me on things which are not going to be technical problems, and that aren't likely to actually be implemented in the broken way I stated does nothing except derail this discussion. I'm sorry I snapped at you, but I was only trying to state the worst case that I remembered might be true, as a way of "padding my estimates". Basically, if I say, "Even if X is true, we should still be fine," please don't correct me to tell me X is false, unless you think that's something I could somehow miss later. Quote:
Quote:
The file contains literally no formatting, tags or css, and no links to external css. Near the end of the book, turning the page takes 2-5 seconds near the beginning of the book (I didn't time this) but over 15 seconds near the end of the book. (I timed this) You might argue that this is a bug in the kobo, and/or this would be fixed if the book had proper chapter marks. I agree with both of those statements, but I consider them tangent to my point. I think this means that books of this size should have been automatically split by Calibre into smaller pieces before being sent to my Kobo. Since 700KB in size was way too long, I'm planning to try splitting at 25KB, 75KB, 100KB, 150KB, and 250KB. I'm hoping that a default of 100KB will be a "small enough" default piece to fix this problem, and large enough that users won't get annoyed at "too many" page breaks. Then I want to test what effect using Kepubs has on the speed with the diffierent sizes. (I'll be testing this as soon as I manage to get my Kobo working, since this file seems to have caused it to hang.) Quote:
Quote:
Firstly, I won't correct you because I think "kepub reader" is a perfectly good description. I do use "kepub renderer" in some places, but that is because it fits the discussion. Quote:
|
||||||
02-16-2013, 06:06 AM | #17 |
Generally Awesome Person
Posts: 1,080
Karma: 2178847
Join Date: Jan 2013
Location: /dev/kmem
Device: Kobo Clara HD, Kindle Oasis
|
If this means you're considering adding the Kobo JavaScript code to any kepubs you generate, be sure that your local copyright laws will permit you to distribute it. In general, the lack of copyright notice and license (which is the case for the official kepubs I've taken apart) means "copyright is applied by the owner, all rights reserved, no redistribution allowed". Same goes for the Kobo-specific CSS, but rhe only CSS change that seems to be important for a kepub is forcing 'margin:0'.
|
02-17-2013, 06:11 AM | #18 | |
Member
Posts: 12
Karma: 10
Join Date: Jan 2009
Device: Handspring Palm
|
Quote:
At this point, I'm trying to find any books Kobo might have put under free distribution or something similar. |
|
02-17-2013, 08:35 AM | #19 |
Generally Awesome Person
Posts: 1,080
Karma: 2178847
Join Date: Jan 2013
Location: /dev/kmem
Device: Kobo Clara HD, Kindle Oasis
|
The problem isn't finding free distribution books (although that's not exactly easy either) it's finding that specific file freely redistributable. Even if you find a book that you can redistribute that has the Kobo files, that probably only allows you to redistribute the whole package and not the component files.
If you do find a freely re-distributable version though, do let us all know. I'd like to be able to include it. |
02-17-2013, 09:46 PM | #20 | ||||||||
Grand Sorcerer
Posts: 24,905
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
|
Quote:
Quote:
My apologies for explaining something that I happened to have done some research on in the past. And also my apologies for correcting some terminology in the attempt to make sure we were all talking about the same thing. Quote:
Quote:
Quote:
To get a 653KB file in an epub after a conversion, you had to make a change to the conversion settings. The default split size on the 260KB. Try redoing the conversion but make sure the split size is the default or smaller. What do you mean by "header" and "footers"? They don't makes sense in an epub. Was this a conversion from a PDF that had headers and footers that weren't removed? Quote:
To explain this, I mentioned a epub I have earlier. This is one I constructed specifically to test some size related questions someone else had. The book has about 30 chapters. The original version had each chapter in a separate file between 10KB and 50KB in size. Plus there were three small files for cover and other non-story things. I combine the chapters into three files that were 342KB, 296KB and 739KB in size. They are in that order in the file. When I uses this before, I was testing battery life, and didn't pay attention to page turning speed. But, I put it back on and did some quick tests. At the beginning of the book the page turning is sub-second. At the end of the first file, it is slower, but still sub-second. At the beginning of both the other files, it is fast. The only real noticeable speed drop is at the end of the third file, the 739KB file. And then it is maybe three seconds. No were near as bad you are seeing with smaller file sizes. The difference is that the code in this book is clean. There are no extra tags for weird things. CSS is used to handle everything nicely. The epub you are describing is badly formatted. This will cause performance problems. Cleaning this up will help a lot more that splitting the files up. But, splitting on chapters (when calibre can detect them) and using the default split size (mainly for when the chapter detection fails) will usually result in reasonable performance. For curiosity, I also put the book on as a kepub. It didn't have the extra spans, but that shouldn't affect the performance much. Page turning on it was sub-second throughout the book. I would be interested to see this book you are having trouble with. It would be interesting to see exactly what sort of code in the book caused this as I have never seen performance as bad as you describe. If you are willing to send it to me, send a PM with a place I can get it, or I can send email address. As to determining an optimum split size, which device are you going to use? Touch, Glo or Mini? Or maybe the original Kobo or Kobo WiFi? And which firmware version? The performance is different on all these devices and the different firmware has had a lot of effect on performance as well. Quote:
Quote:
The performance of books on the Kobo device is a different matter. These books would behave like that if you put them on without using calibre. |
||||||||
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Touch .kepub.epub | davidfor | Kobo Reader | 233 | 01-12-2014 08:15 AM |
Kepub - how does it work? | Lynx-lynx | Kobo Reader | 5 | 01-31-2013 06:09 AM |
Plugin calibre epub to kepub | Tumeconnais | Kobo Developer's Corner | 0 | 01-16-2013 04:26 PM |
Plugin for making a summary list about your books | equilan1986 | Plugins | 2 | 01-08-2013 07:21 AM |
A little help and direction... | stevejay | Deals and Resources (No Self-Promotion or Affiliate Links) | 12 | 02-19-2009 05:24 PM |