aaron said:
The problem is that the book itself is not readable.
actually, the problem is you got a dated version of the app. i'll send you one that contains the text-to-speech capability. even then, however, it seems to me that i could program an app that was tailored specifically for the sight-impaired, stripping out everything that was extraneous to them and adding features that were consciously geared to their needs. i'm willing to do the work of programming such an app. but aside from some basic ideas, i'm somewhat at a loss in terms of designing it. but if you would like to guide me -- backchannel, of course -- i would certainly take that on.
If you could put the text of the book in an edit type field, and cause the down arrow key to move down one line at a time, you might (and I stress might) solve it.
even in the version you have, you can summon up the text in an editfield that your screenreader might be able to handle. it's under the "notes" menu, if i remember correctly, since that editfield is what is displayed when a person clicks on a footnote-indicator in the paginated text. it's also useful to a person who wants to quickly scroll through the text. a paginated display is a better vehicle for reading the text, but a scrollable field also has its benefits for some purposes. plus, in the current version is a command to copy the text of the page(s) currently displayed to the _clipboard_, where -- it is my understanding -- some screenreaders will read it. that command is under the edit menu, where you'd expect it. thanks for your feedback, i appreciate it greatly... -bowerbird