View Single Post
Old 06-30-2015, 01:28 AM   #13
darryl
Wizard
darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.
 
darryl's Avatar
 
Posts: 2,912
Karma: 58015962
Join Date: Nov 2011
Location: Australia
Device: Kobo Aura H2O, Kindle Oasis, Huwei Ascend Mate 7
I think davidfor did change the content server to cownload kepub files as kepub.epub to Kobo devices.

In the meantime, I have had a look at the relevant source and applied my very limited Python knowledge with surprising success. Two minor changes to add the kepub format in content.py fix the problem. This means, of course, that the content server now supports not only epub, mobi and azw3 but also kepub. Sounds much more impressive than it is! I will have a look at submitting a patch according to the instructions in the manual. However, one consequent change will be necessary to metadata plugboards. Trying to add a plugboard for the content server specifying kepub as the format in the preferences gui still results in an error message that kepub is not supported by the content server. If I get a chance I will see if I can fix this before trying to submit any changes.

EDIT: Please see my further post below.

Last edited by darryl; 06-30-2015 at 03:20 AM.
darryl is offline   Reply With Quote