Thread: Glo Calibre/Kobo Glo "error communicating with device."
View Single Post
Old 12-04-2017, 05:42 PM   #82
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 Owl_ View Post
Ok I've used the calibre's editor checked the bugs and selected the automatic fixing. There were few errors and was corrected exept for

AVVISO: CSS: Property: Unknown Property name. [3506:3: -webkit-border-radius]****[OEBPS/Styles/stylesheet.css]
AVVISO: Il collegamento punta a una posizione non presente nel file di destinazione****[OEBPS/toc.ncx]

the second warnig say: the link point to a position not present in the destination file
The first error is that a property is used in the stylesheet that isn't part of the epub2 standards. It won't harm as any ereader app should ignore unknown properties. But, some will handle it correctly. I think the kepup renderer will.

The second is that there is an entry in the ToC that point somewhere that doesn't exist. You can have the editor rebuild the ToC or edit it and remove the entry. The invalid entry will be marked. But again, this won't cause any problems on the device.
Quote:
Anyway I've tried to load the file on the ereader and works well


Another thing: I'd like to have a total full screen reading on my KA1. Cuold you suggest me the easier way? (a thread o something else)
The firmware has an unsupported full screen reading mode. It's not perfect and some of the problems need to be fixed with a patch. It is well discussed here. A search for "FullScreenReading" will find how to enable it.
davidfor is offline   Reply With Quote