Ubooquity is not supposed to write a BOM at the beginning of the preferences file.

Are you positive there is one in yours ?

No, Ubooquity is focused on collection browsing.

Updating said collection is out of its scope.

About documentation and a full client (something that have been on my mind too but that I won't start before several years, if ever): the best way to programmatically get data from Ubooquity is through the OPDS feed (explained in this post).

Ubooquity implements the OPDS specification, and you'll find everything you need (metadata, covers, files, links to extract individual pages) in the feed.

The individual links for page extraction is an extension of the OPDS format described in this document.

Unfortunately if the problem lies with the CSS support of the DPT-S1 browser, there is nothing I can do. :/

Sure !

Done.

By "proportionately" you mean distort the image so that it fits the whole screen ?

The documentation is probably not explicit enough, but the reverse proxy prefix in the advanced settings is not supposed to contain slashes. Just "ubooquity" should be enough.

Yep, memory consumption is already on my todo list. I'll investigate.

Covers are already available in the OPDS feed through an explicit link.

So any application using the feed can already use the cover without having to download the whole file.

I'm not a fan of cover extraction (it kind of "pollute" your collection with external files), especially since the cover are already for download through the server itself.

65k file handles is more than enough.

I still have to look for a file handle leak in Ubooquity. It's quite high on my todo list, I just lack the time right now...