Thanks for the feedback.

I have updated the ubooquity.sh file on the webiste (line separators were CRLF instead of LF), no point in having a bash script with Windows line separators.

I tested the files you sent me and reproduced your problem.

They trigger an infinite loop (hence the scan hang) in the library used by Ubooquity to unrar the files. This loop is a consequences of a few fixes I had applied to this library.

After reverting to the "official" Junrar version, the scan doesn't hang anymore (although the files can't be read either, there is definitely something wrong with them).

So I'll go back to the "official" Junrar in the next release as I can't control the consequences of the modifications I applied (I did not write them myself so I won't maintain them).

If the solution provided by TierParkToni doesn't work, upload them somewhere and send me the link, I'll take a look.

tom at vaemendis dot net

Still many months away.

Hello Peter,

do you have any error in the logs when that happens ?

Hello Praveen,

Ubooquity tracks the last page you read for a given book.

By default the page number is stored on the server.

But there is an option in the "Advanced" tab of the administration settings that allows you to have the page number stored in a cookie (so in the browser instead of on the server).

Both should work (although the cookie option doesn't work if you use different browser or devices, obviously).

If you have any idea as how to describe you issue with a bit more details, it might give me a lead as to why the feature doesn't work in your case.

Hello Jbugman,

What kind of theme do you have in mind ?

You can already theme Ubooquity with custom CSS and image.

If you mean full HTML structure theming, that is still in development but will definitely be part of one of the next releases as I will rely on it to modify the UI myself to add read/unread support on books.

Hi Frédéric,

1) I still plan to add a way to "plug" external PDF renderers to Ubooquity since I still haven't found a free Java library that is as efficient as tools like MuPDF or Poppler. But this feature is not at the top of my list yet (although it's not that far from the top), so it won't be implement very soon.

2) I don't have a complete understanding of the encoding issue you have encountered (as you can gather from the different threads about encoding on this forum), but what I'm sure of is that the encoding setting impacts the entire Java process (meaning all parts of Ubooquity), so there is no way to use it only for PDF related tasks.

The problem with encoding issues is that they are hard to reproduce on my side as they depend on your OS, your OS settings, the way you launch your JVM (the Java runtime) and the way your book files were written.

Thanks for the nice words everyone. :)

For reference, the Junrar version used in Ubooquity 2.1.2 is now this one:

https://github.com/vaemendis/junrar/commit/d9cb2e9699beda28e7209170e7d1635361d78484

(latest junrar/junrar version with my fix on top)