View Single Post
Old 06-22-2016, 02:22 PM   #1432
jackie_w
Grand Sorcerer
jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.jackie_w ought to be getting tired of karma fortunes by now.
 
Posts: 6,252
Karma: 16544692
Join Date: Sep 2009
Location: UK
Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3
Quote:
Originally Posted by DiapDealer View Post
No. You can't read epub2 books with the epub3 engine. You can only choose to read epub3 books with the epub2 engine if you want (or you used to be able to anyway).

My books ARE epub3. If they're not already when I buy them, I convert them to epub3 myself before I read them.

The reason I prefer Bookari's epub3 engine is because I get a finer-grained control over font-size, and because it displays italics correctly (all the time) when using a custom reading font. And because of pop-up foot-notes.

It'll get straightened around--I'm not worried. Wouldn't be the first time I had to roll back to an earlier version to wait out an issue.
Ah, OK, thanks

FWIW I also think the chunky font-size jumps in Bookari are annoying. It's the only epub reader I have with this problem. I solved the Bookari errors quirks with custom fonts in EPUB2 by using an @import to a CSS file stored on my Android device. It seems more reliable.
jackie_w is offline   Reply With Quote