There are some issues supporting 1.5 that are resolved in version 13 (0.10.1). Google seems to have totally broken a class used by the widget (among others) and have introduced some really interesting web browser bugs that have been worked-around (I hope).
Use the Widget menu option to change default font size, font color, and background color. This brings up an on-screen widget with scrolling bars for setting values.
Many pdf->html converters insert line breaks at the end of each visual line. This will flow all wrong on your phone, so you may want to turn off those line breaks. By default, html paragraphs insert a line of space when they end. This is optional and use depends on how well your books are formatted.
auduaReader uses a number of different algorithms to try to determine reasonable breaks in text and html files. The best results are when html chapters are clearly marked in some fashion (such as using <h tags). When chapters are not clearly marked, auduaReader will break the book up to maximize ram usage while still allowing useful finger-fling in the center for quick within-chapter placement.
Here's an example of an html document that's reasonable (not great) Tin Woodman from Project Gutenberg. The first section is hard-formatted and too wide but the chapters flow very well. Starting with version 6(0.6.0), text files are always split at 60 lines per chapter (a standard physical page).
Html documents are hard to paginate correctly and many html documents are poorly formed so it is possible that the reader may malfunction on some html books. The current version seems to be very reliable with moderately well-formed html.
Yes. auduaReader supports the three most common flavors of unicode but unfortunately the android phone browser does not display all unicode characters. I assume they are not in the fonts. Try it on a web page with unicode characters.
Starting with version 8, auduaReader supports a wide range of character encodings. To change the character encoding of your book (the way auduaReader interprets non-english characters) go to the book properties (long click the book and click Edit info) and change the Text format option.
It's really a lot of work to read a book using finger-drag. Let me think, brush your thumb on the top to flip a page or drag up the screen just right for a page. If you really want to do that set all three zones to finger-drag in the Clickzone Settings.
No. Many html books are not well-formed, especially public-domain books. Although the web browser is moderately forgiving of bad html, the version of it that uses supplied data is less so - it may just stop parsing and you lose a table of contents (for example). If the page displays as a browser error then it has hit bad characters. I'm happy to examine any such books to determine why the browser choked.
With version 10 (0.9.0) you can now click-through to a web address if the address is in a finger-drag zone. This brings up a secondary browser at that web page. For security reasons you can not click-through to pages in the phone memory. auduaReader is not a web browser.
In order to keep the phone awake during auto-scroll (otherwise it would sleep while you're reading) auduaReader uses the wakeLock function. This requires a WAKE_LOCK permission.
Any program has bugs. At the moment auduaReader has no dedicated beta testers so (gasp) it may ship with a bug. Please report these via the author email link at marketplace. I will resolve them asap.
Please feel free to send email to the author email link at Android Marketplace. All feedback will be pondered carefully, thanks.