New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZIP file support #9986
Comments
This piece of code is not executed by default, zip files are handled by muPDF due to bigger weight. koreader/frontend/document/credocument.lua Line 1490 in cbe7775
koreader/frontend/document/pdfdocument.lua Line 382 in cbe7775
You can enforce cre handling for a zip file via long-pressing it and choosing Open with... |
Thanks @hius07 , that is really neat! I had no idea about the open with. I'll think on this a little before I do anything, I'm thinking about making a wiki page (and maybe guide) update. |
@hius07 sorry for the delay (been sick :-() I went ahead and:
I've not yet made a README change yet for https://github.com/koreader/koreader/blob/master/README.md - seeking feedback on the wiki page(s) first. However I'm about to open a small PR to update the supported format list in the readme to match what is now in the wiki |
#10004 posted for the non-ZIP note |
Thank you, your wiki updates look good. |
Thanks, made a quick note to that effect in the wiki. |
Issue
Documentation mentions ZIP file support but does not explain this in detail
It looks like any supported format can be supported in a ZIP file IF the filename of the zip file is
*.FORMAT.zip
, e.g.:myfile.txt.zip
myfile.rtf.zip
However https://github.com/koreader/koreader/blob/master/frontend/document/credocument.lua#L155 indicates the file type can be inferred by the first filename in the archive (a feature supported by many softwre ebook readers like FBReader, AlReader, etc). This does not appear to work.
I think there are two issues at play here:
As always thanks to everyone working to support KoReader!
Steps to reproduce
See attached test/demo documents (from https://github.com/clach04/sample_reading_media):
Both books contain a single file called
test_book.txt
, no other files inside the ZIP archive.crash.log
(if applicable)No
crash.log
Let me know if logging is needed
If your issue doesn't directly concern a Lua crash, we'll quite likely need you to reproduce the issue with verbose debug logging enabled before providing the logs to us.
To do so, from the file manager, go to [Tools] → More tools → Developer options, and tick both
Enable debug logging
andEnable verbose debug logging
.You'll need to restart KOReader after toggling these on.
If you instead opt to inline it, please do so behind a spoiler tag:
crash.log
The text was updated successfully, but these errors were encountered: