It's a bit outside of the core functionnalities list I want to restrict Ubooquity to (the idea being to avoid feature creep).

But it might be quite simple to implement, I'll put it in my todo list.

The problem is that Ubooquity is not capable of making the difference between a moved file and a new file (to do that would require keeping hashes of files and comparing them each time a change occurs, a bit complex for the expected benefit).

For Ubooquity, the "primary id" of a file is its path. Change it and you have a new file.

And I'm afraid you will have the same problem when I add the read/unread flag feature. It will be reset each time you move a file.

I'm afraid that level of customization will not be available soon in Ubooquity. I try to use the time I have for bug fixes and core functionalities. In a very distant future maybe...

Your "preferences.xml" is corrupted. Stop Ubooquity, delete it, then restart Ubooquity. You'll loose your preferences, but they are probably already lost anyway.

There is: 2016 ! ;)

I am currently working on it. Though the principle is easy (epub files

are just zipped HTML files after all), there are a lot of tricky details

to take care of to have a usable reader. So I don't know exactly when

it will be done.

Screenshots are impressive !

I'll give it a try and update the theme list on Ubooquity site.

Thanks !

Indeed.

"Directory does not exist or is not readable: //DNS-345/Volume_1/Comics"

: either the path is wrong or the folder has not the appropriate user

permissions (on OS level).

The upgrade process is quite simple: stop Ubooquity, download the new jar file and replace the old one. Restart Ubooquity.