pettarin / epub3reader

EPUB3Reader Android App

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Webpage not available.

pejic opened this issue · comments

I am getting a "webpage not available" error whenever i try to open an epub. FBReader opens them, so they should not be corrupt.

Device: Samsung Galaxy S3, SGH-T999V.
OS: Cyanogenmod-10.2.0 (Android 4.3.1)

I've installed EPUB3 Reader via F-droid: https://f-droid.org/repository/browse/?fdid=it.angrydroids.epub3reader

I have the Android SDK and Eclipse installed in case you need me to perform more advanced debugging.

device-2014-01-25-112858

Thank you for the accurate issue report. Can you tell us what kind of epub you are trying to open? Is it publicly available? Can you give us a link to it, so that we can download it and try to replicate the issue?

Thanks for the reply,

I downloaded the book from www.bean.com. The book I had issues with is not freely available; however, I have just tried one from their website that is. It has the same issue:

http://www.baenebooks.com/p-217-a-hymn-before-battle.aspx
(The "EPUB/Nook/Stanza Format" link under the "Download Unzipped Files" section)

Thank you for providing a sample.

I replicated the issue you described.

There is a bug in the current code that builds the path of the XHTML files to be loaded into the WebView, when the OPF file is in the root directory of the EPUB container, as in your sample.

We will fix this bug ASAP, thanks again for reporting.

Marco committed a quick fix for this issue in the devel branch. You can get the APK here:

https://github.com/pettarin/epub3reader/blob/devel/workspaceeclipse/EPUB3Reader/bin/EPUB3Reader.apk

Since that portion of the code needs to be polished, I am not pushing the fix to the master branch yet. We planned a deep refactoring round for late February/beginning of March.

I close the issue, thanks for letting us know about it.

I pushed the fix to this issue (and only this fix) to the master branch as well.

Please note that the above observation about the planned upcoming refactoring is still valid.