Quote:
Originally Posted by Jane Eyre
Ok. So, let's imagine you or me or anyone else having stored in their kobo, hundreds of kepub files (the 16 gb of storage may easily convince users to do so), and for each of them one sets fonts, margins, etc in differents ways. So the device should memorize huge different configuration data...I think this type of situation would slow the device down a lot..
|
Actually, no. The information on the configuration set for an ebook is stored in the database entry for the ebook and takes very little space. When a change is made, the default for the next book is set to match.
Edit: if you are interested, you can find this information stored in the content_settings table in the KoboReader.sqlite database.
As for setting fonts, margins, etc. in different ways, I know of no one who sets those separately for every ebook. Most people tend to set those once and stick with those settings for 90+ percent of their ebooks. My preference is to set the margins, line spacing, font size, etc. in the CSS so no changes are necessary.
BTW, my Clara HD has 128GB of storage and at the moment over 14,000 ebooks stored on it. So far the only issue I see is that search is slower than when I have only 100 books on it but I am talking about 3 seconds for the search results to start popping up compared to less than 1 second. Most of this is due to the database being bigger than available RAM so a search needs to start swapping.
I'm not sure why you specified kepub files. As far as I am aware, the difference in space use between epub and kepub are pretty negligible.