View Single Post
Old 02-01-2012, 04:21 PM   #675
Xennex1170
Addict
Xennex1170 ought to be getting tired of karma fortunes by now.Xennex1170 ought to be getting tired of karma fortunes by now.Xennex1170 ought to be getting tired of karma fortunes by now.Xennex1170 ought to be getting tired of karma fortunes by now.Xennex1170 ought to be getting tired of karma fortunes by now.Xennex1170 ought to be getting tired of karma fortunes by now.Xennex1170 ought to be getting tired of karma fortunes by now.Xennex1170 ought to be getting tired of karma fortunes by now.Xennex1170 ought to be getting tired of karma fortunes by now.Xennex1170 ought to be getting tired of karma fortunes by now.Xennex1170 ought to be getting tired of karma fortunes by now.
 
Posts: 355
Karma: 289856
Join Date: Oct 2011
Location: Honolulu, Hawaii
Device: Kobo Touch
Quote:
Originally Posted by symon79 View Post
No no, the book descriptions are still in the sqlite database (in the content table) for most books (I would say 90%).

Are the Kobo devs actually reading this thread?

I think it's really a must to be able to read book descriptions (otherwise you'll have to judge a book by it's cover instead of the content [preview] before start reading it;-)).
Actually I meant that it would take up onboard storage space regardless if the book description was part of the book or inserted in a field in the sqlite DB. How much space would you feel is adequate to allocate to the descriptions? Note for double byte character sets each character takes up 2 bytes. (e.g. 512 characters is 1K of storage space.) Which brings up the question how much storage space is currently used for each book record in the sqlitedb?

One feature I would find useful is to be able to move sideloaded books between the KT and the inserted microSD card.

Last edited by Xennex1170; 02-01-2012 at 04:38 PM.
Xennex1170 is offline   Reply With Quote