View Single Post
Old 09-07-2013, 05:31 AM   #54
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
Quote:
Originally Posted by ibu View Post
@davidfor
Just some minutes ago I solved the problem - see the "edit section" in my post.
But thanks for your offer
I should have refreshed the thread before posting.
Quote:
Something else:
What do you think about an option to declare a path to a local "kobo_extra.css" instead of using a "kobo_extra.css" on the device?

I think, it's more comfortable for a user, when he could refer to his local "kobo_extra.css" in the configuration of KoboTouchExtended.
The root of the device was deliberately chosen to allow a different CSS for each device. Some of the changes would be constant across all devices, but, some would be different for the different models. Plus, for people that share a calibre library, they can easily set different CSS for their devices. When I did this, I also considered looking for a file on the SD card if it was installed and the book was sent there.
davidfor is offline   Reply With Quote