Fixed and available in Ubooquity 2.0.0.

The expression has to match the whole file path.

By whole file path I mean that Ubooquity tests each file with a path like that:

/myData/myBooks/Calibre-Upload/myBook.epub

So the expression has match what's around your folder name.
This one should work:

.*(LazyLibrarian|Calibre-Upload).*

I'll probably try to simplify this mechanism in the future (e.g. so that a simple "LazyLibrarian|Calibre-Upload" pattern works, without having to match the whole path).

Yes.

Pattern are described using regular expressions. You'll have to use a logical OR (described by a pipe: "|").

Here is a detailed tutorial to understand regexps:

https://regexone.com/

And here is a tool to easily test your expressions:

http://java-regex-tester.appspot.com/

Keep in mind that the expression you write will be matched against the entire path of the file, not only the filename.

Good idea, here you go:

http://vaemendis.net/ubooquity/downloads/Ubooquity-1.10.1.1.zip

Might be a bug, I'll investigate.

Consequences of not being able to extract these fonts are quite small anyway, even if you use the online epub reader.

If you don't see any table, the path must be wrong.

When entering a connection string to a file that does not exist, H2 will simply create it, without any table.

(so you must have a new, empty, ubooquity-4.h2.db file created somewhere)

By "data base", you mean the one created by Ubooquity or the total size of your files ?

Because for 45k books, the database will take around 200 MB, not more.

I didn't look into it yet, although I know exactly how to reproduce it, thanks to your tests.

It's on the list, perhaps not for 2.0 but definitely for 2.1 (see here).

I stopped providing estimations: software development is already hard to plan when doing it as your primary activity, respecting deadline on a side project is just impossible.

That being said, I can tell you what I still have to do before releasing the next version.

Two big tasks took me months in 2016: replacing the internal web server (using Jetty instead of NanoHTTPD) and rewriting Ubooquity UI.

They are done.

Now I'm working on bookmark synchronization. Once this feature is done, I'll realease Ubooquity 2.0 as a beta and work on minor features and bug fixes for a time, then release a stable 2.1.

I'd like to think that I'll be able to release 2.0 before spring, But I already said I wanted to release it by Christmas, so I'll just say "when it's done".