Quote:
Originally Posted by Frenzie
If you had forced MuPDF instead of crengine or vice versa it could explain different behavior. Other files do open? There is no reason the program itself should behave any differently.
|
Do you mean within Koreader itself? If so, I have no idea how to do that and haven't done it manually. Is it possible to check which engine is in use?
I would say that about a third of the files show these errors in the file browser within Koreader. All of those files are zipped fb2, which at first I thought was the problem; but the files that
do open are in the same format... And there doesn't seem to be anything wrong with the files since unzipping them manually and then reading the resulting fb2 works in Koreader. They work without unzipping on Alreader X on the same device, and also open just fine on Koreader on my Nova 3.
Could there have been a problem when indexing the files or something? Is there a way to tell Koreader to refresh the database or is this something that is done automatically?