FBReaderJ released in new version for Android phones: ePub support improved
April 7, 2009 | 6:18 am
By David Rothman
FBReaderJ 0.3.1’s new wrinkles:
- “Library information has been moved from the config database into a separate database. Library speed is increased. The first library loading may take some time (about 3 seconds for 30 books in my library) however all the further loadings should be much faster.
- Library view has been changed. Tree view is used instead of simple list. (New screenshots are available.)
- Table of Contents has been implemented.
- Epub format support has been improved. NCX table of contents support has been added, OPF namespace has been supported, etc.”
Downloading link and other info: Here. Right now FBReaderJ is free. For reading nonDRMed e-book files in ePub, FB2 and OEB, this is the way to go for Android owners. FBReaderJ will be adding more formats. Meanwhile, later on this year, expect an e-reading app for Android phones from Lexcycle, developers of Stanza, one of the big players on the iPhone and iPod Touch. In the current version, Stanza can handle ePub as well as DRMed eReader among others, and DRMed ePub should be coming shortly.
The CSS issue: I’d love to know when FBReader will recognize CSS-related goodies in ePub, even though it’s nice to know of better support of tables of contents. Meanwhile see Mike Cane’s complaints about Adobe Digital Editions.
About the screenshot to the right, above: Yep, that’s only the icon showing, and the real story is an Android desktop. Still, I couldn’t resist. Warp the clock a bit, and Salvador Dali’s ghost might enjoy this one.
The library screenshot: Here’s the screen displaying goodies from Feedbooks.
Related: Google-linked news items on an Android tablets and netbooks.



Previous

SUBSCRIBE TO RSS
Comments:
I downloaded FBReader intending to use screensnaps for my ePub article.
It crashed on the pro version of the ePub.
When I coaxed it to work on my alpha version, the results were — to be charitable — hideous.
In addition, why can’t it see an eBook on the *desktop*?! Navigation is still bizarre and as unintuitive as it was back during my traumatic testing on the Nokia 770. And that was *years* ago, OK?