View Single Post
Old 09-22-2012, 06:37 AM   #7
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Well, to tease everyone...

The database on the Touch has the following table:

Code:
CREATE TABLE content_settings (
ContentID TEXT NOT NULL,
ContentType INTEGER NOT NULL,
DateModified TEXT NOT NULL,
ReadingFontFamily TEXT,
ReadingFontSize INTEGER, 
ReadingAlignment TEXT, 
ReadingLineHeight INTEGER, 
ReadingLeftMargin INTEGER, 
ReadingRightMargin INTEGER, 
ReadingPublisherMode INTEGER, 
ActivityFacebookShare BIT default TRUE, 
PRIMARY KEY (ContentID, ContentType))
ContentId is used in several places in the database. It is the key used in the database to point to the actual book. The rest of the column namess match the settings in "Kobo eReader.conf" for the reading setup. I think this table was added in firmware 1.9.17. Unfortunately, it is always empty.

So, Kobo have considered implementing it, but haven't finished it.
davidfor is offline   Reply With Quote