MobileRead Forums - View Single Post

davidfor · 08-20-2014, 06:44 AM

I have no idea whether Koreader handles epubs better than nickel, but it's handling of kepubs will be worse than for the equivalent epub. But only by a tiny bit.

As WS64 said, a kepub is really just an epub with some extras. Most of those extras a spans wrapping each sentence with an id. These are use by the ACCESS reader for bookmarking. Some purchased kepubs have javascript and some extra CSS that is used by ACCESS.

Because of this, any kepub converted from an epub will be bigger. Any renderer will take more time with the size and all the extra spans and use more memory. Hence, it will be a little slower. But, you probably won't notice the difference.

Also, the extended driver does not break the files down in size. Each file within an epub is processed to add the spans and are otherwise unchanged. If you use convert to kepub using a calibre conversion, you can break the files down, but converting to epub will do exactly the same thing. If ACCESS is handling sideloaded kepubs better than the RMSDK handles epubs, it probably means that ACCESS is better written. It is likely that it is adapted to the hardware better than RMSDK.

My opinion is:

If you are swapping between nickel and Koreader and prefer kepubs in nickel, then sideload as kepubs.

If you have decided only to use Koreader, don't bother with kepubs. But, don't worry about removing them and replacing them with the original epubs.

And if you are not using nickel, you probably should stop using the KoboTouch drivers in calibre. These read the database created by nickel. If you don't use nickel, it won't be populated and calibre won't show any books on the device. You would be better to use the "Folder device". This will scan the folder for books and find everything under that folder.

08-20-2014, 06:44 AM	#4
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	I have no idea whether Koreader handles epubs better than nickel, but it's handling of kepubs will be worse than for the equivalent epub. But only by a tiny bit. As WS64 said, a kepub is really just an epub with some extras. Most of those extras a spans wrapping each sentence with an id. These are use by the ACCESS reader for bookmarking. Some purchased kepubs have javascript and some extra CSS that is used by ACCESS. Because of this, any kepub converted from an epub will be bigger. Any renderer will take more time with the size and all the extra spans and use more memory. Hence, it will be a little slower. But, you probably won't notice the difference. Also, the extended driver does not break the files down in size. Each file within an epub is processed to add the spans and are otherwise unchanged. If you use convert to kepub using a calibre conversion, you can break the files down, but converting to epub will do exactly the same thing. If ACCESS is handling sideloaded kepubs better than the RMSDK handles epubs, it probably means that ACCESS is better written. It is likely that it is adapted to the hardware better than RMSDK. My opinion is: If you are swapping between nickel and Koreader and prefer kepubs in nickel, then sideload as kepubs. If you have decided only to use Koreader, don't bother with kepubs. But, don't worry about removing them and replacing them with the original epubs. And if you are not using nickel, you probably should stop using the KoboTouch drivers in calibre. These read the database created by nickel. If you don't use nickel, it won't be populated and calibre won't show any books on the device. You would be better to use the "Folder device". This will scan the folder for books and find everything under that folder.