That's something I had planned from the start. So it'll be definitely done someday. I just don't know when yet.

I understand, but it will have to wait for a hypothetical complete "templatization" of Ubooquity (allow users to fully customize pages structure in addition to the CSS).

Server side bookmarks (allowing you to resume reading on a different device) are still planned and are quite high on my todo list.

Read/unread flag will be a side effect of this development.

You can expect it this year.

Thanks for the feedback !

I found a bug related to fonts which happens only in Firefox, not in Chrome.

I don't know yet if it explains your problem, but there is definitely something to fix.

Probably before summer.

Just in case: your font files are actually woff files, not ttf files ?

Also, could you open your javascript console (F12 in yout browser) and check if there is any error when you change fonts to Open Sans ?

Yep.

You followed the right steps.

You can post the custom CSS you wrote if you want me to check it.

Some epub files define the font in their own embedded CSS. In that case, fonts are not customizable.

Are you able to change the font of your book using the defaults fonts provided by Ubooquity ?

If not, this means the font is defined in the book CSS and cannot be changed.

I plan to try to replace the current HTTP server I use (NanoHTTPD) with Jetty. This would solve the header problem, among others.