Thread: [Metadata Writer Plugin] KePub Metadata Writer
View Single Post
Old 06-30-2015, 09:08 AM   #20
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: 47303826
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by darryl View Post
Here are the very simple changes I made. I do not plan to submit them myself. Obviously the changes to the file in srv are not necessary given this is Kovid's re-write.
Are you sure of that? I can see equivalent code in the new server code that is limited to updating just epub, mobi and azw3.
Quote:
With the changes to the file in library/server there is no problem now with creating a content server metadata plugboard for the kepub format. When downloading kepub books from the content server they do download as kepub epub and the metadata plugboard is applied, at least so far as my setup to modify the title is concerned. It does not, however, actually create a collection or add the book to the collection. Am I correct in assuming that this is a function purely of the driver? It does work over USB using the Kobo Touch driver, but not with the content server.
Yes, the collections are created by the driver. It is doing this by directly updating the database on the device. The content server can't do this as the browser on the device is requesting a file, saving it and then triggering the book processing for it. There is no way for the content server to tell the device anything about collections.
Quote:
Given that adding support for new formats seems to be relatively trivial, is it actually worthwhile to support all formats with metadata writers? Support can easily be added on request of users or developers who use the particular format. Support for epub, mobi, azw3 and now kepub seems to cover all of the most common formats, with the exception, I suppose, of pdf, which is not really a great format for ereaders anyway.
Yes, but it means that someone has to make the request. And if someone adds a new format and creates the metadata writer plugin, they have to get the server code updated to handle it. If it is a brand new format that sweeps the world in a couple of days, then updating the server is OK. But, if it is a specialized format that very few people use, it wouldn't make sense.
davidfor is offline   Reply With Quote