View Single Post
Old 05-15-2017, 08:07 PM   #341
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,906
Karma: 47303822
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by MGlitch View Post
Am I correct in recalling that kobo_extra.css only applies to kepubs sent over to the device -after- the file is placed in the root directory?
Quote:
Originally Posted by rashkae View Post
Yes, that is correct.

the purpose of this kobo_extra.css is to add the work arounds to the bugs with kepub and full screen display. This is what the patches do for you by default if you install those. If you do not intend to use full screen, or if you patch your firmware with the community patches, (including the full screen bug fixes), then you do not need this.
This is correct, but incomplete.

Firstly, the kobo_extra.css handling is part of the main KoboTouch driver. That will apply it to epubs* as they are sent to the device. If you use the extended driver, it will be applied to kepubs that the driver generates. The extended driver will also look in a location on the PC for the kobo_extra.css and copy it to the device before sending the books.

* It's possible it is applied to kepubs in the library, but I don't remember. If it doesn't, it should.
davidfor is offline   Reply With Quote