Replies: 1 comment 2 replies
-
Would you consider ditching custom parsing in favor of a different engine, Readium? It's written in pure Kotlin, and should be able to handle most things you could find in epub3 ebooks. It already supports most improvements that were suggested in the milestone (images, pagination, text-to-speech, bookmarks), and additionally you can easily use it to support pdf files as well. You can also store books in a safe zone as you mentioned on #57, which you can test out with the test app they pre-build on their release page. The entire toolkit also has a ton of support, so development should continue to the foreseeable future. What do you think? |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Thread for Reader Improvement milestone.
Feel free to share your ideas here.
Beta Was this translation helpful? Give feedback.
All reactions