Thread: Elipsa: Not accepting converted Kepubs
View Single Post
Old 06-26-2021, 10:31 PM   #5
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 Skydog View Post
Update: Started over with a factory reset. With the problem below cleared up, I was able to send a kepub to device, but it does not appear. The file is indeed on the Elipsa (checked folder) but apparently converted/sideloaded kepubs are not recognized. Any ideas?


After converting several epubs => kepubs, either on-the-fly or before, the same error message appears when attempting to send to device. Any chance this can be resolved in the future?

calibre, version 5.22.1
ERROR: Error: Error communicating with device

'utf-8' codec can't decode bytes in position 14-15: invalid continuation byte

Traceback (most recent call last):
File "calibre\gui2\device.py", line 89, in run
File "calibre\gui2\device.py", line 595, in _upload_books
File "calibre_plugins.kobotouch_extended.device.driver" , line 388, in upload_books
File "configparser.py", line 697, in read
File "configparser.py", line 1017, in _read
File "codecs.py", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode bytes in position 14-15: invalid continuation byte
That error is from the driver reading the config file on the device. There was string somewhere in the file that the library being used to read the file does not like. The reset of the device cleared this, but, it could appear again.

There is no error handling for that section of the code. I will look at adding that. Also, it is setting the hidden option for full-book page numbering. That hasn't been valid for a while, so I might add some handling of that. Or just remove it completely. Anyone remember what firmware that was added in and then removed?
davidfor is offline   Reply With Quote