-
Notifications
You must be signed in to change notification settings - Fork 102
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
Restore page position #392
Comments
Thanks for taking time to post this issue. I thought I had fixed thus issue as part of #86 Could you please attach the epub to this issue so that I can test it. Currently I am revamping bookworm to bring it up to date with software libraries over the past couple of years and release it on Elementary OS 7. So I will get back to your issue once the upgrade is done. |
Sure, I zipped it so Github won't complain about the extension: |
Hi babluboy. I came to the github to also make a thread about this same issue. A book I'm reading is being parsed as 1 page per chapter (which may very well be a problem with the epub itself, not your software). I don't feel super comfortable sharing an epub on a public board, but just wanted to state that I share the issue that OP has. I think a good solution here may be adding a way to save the progress of a page when the user leaves the book so they can resume the chapter, rather than forcing the program to add more pages. The problem leading to these super sized pages is likely to be poor epub quality or a lack of metadata. |
Hi! I've just installed bookworm 1.1.2-3 on Arch Linux and I'm trying to read a book with it. It looks really cool, congrats! But when I close and open it again it starts at the top of the current page, and not at the position where I left. For small pages this can be irrelevant, but for the .epub I'm trying to read, at least how bookworm parsed it (didn't try other softwares), each page is a chapter (some very long). So restoring at the top of a page is equivalent to restore at the beginning of a long chapter, which isn't enough.
Is this expected behavior? Is there a way to fix it?
Thanks for the attention and for developing this software!
The text was updated successfully, but these errors were encountered: