Originally Posted by eureka
As I see, chrox
in Github issues is trying various methods for invoking KPV for supported file types. I think, it will be worth to him to know that system Reader booklet supports plugins. Enabled plugins are listed in reader_plugins.xml
. In Kindle Touch this file is located in /opt/amazon/ebook/config/
, but it looks like in PW it's embedded into /opt/amazon/ebook/lib/ReaderSDK-impl.jar
(but still in a form of easily accessible text file).
I believe, that filetype-dependent part of system reader code is located in plugins that are defined in reader_plugins.xml
tried to reverse engineer plugin interface for 5.0.0 and implement it's own, invoked for EPUB files: https://github.com/yifanlu/KindleEPU...lu/kindle/epub
. It could help, but code is in unfinished state.
(I can't post to Github right now, sorry.)
Yes. You are right. The native ReaderBooklet supports PDF, Mobi and Azw document types via a plugin mechanism just like Yifanlu's EPUBBook implementation. But as there are already standalone epub readers like CoolReader and Kindlepdfviewer for Kindle why bother re-implementing another one. What we want is just launching an external reader from native home screen and returning to home screen after we close the document. It's much easier to implement a booklet as a launcher than a real book viewer. And it's already done for Kindle Paperwhite. See the project KPVBooklet at https://github.com/chrox/KPVBooklet
And there is a screenshot of the home screen after installing KPVBooklet.
Note that PDF, DJVU and EPUB documents can be directly opened with KPV while Mobi and AZW formats are handled by native amazon reader. The file types are registered not in the booklet plugin but in a sqlite database located at /var/local/appreg.db. More information can be found at https://github.com/hwhw/kindlepdfviewer/issues/653