Full Text Books Support

[GoogleCodeExporter]

Please provide full Text book support. Ive been waiting on a ebook reader for 
android for a while now. I would like to see full text book support. This is 
something that I would be willing to pay for.

Original issue reported on code.google.com by HadToHa...@gmail.com on 12 Jan 2011 at 3:59

[GoogleCodeExporter]

I'd like to add support for full-text DAISY books too. There are some technical 
challenges which I have yet to solve. However, with your encouragement and 
encouragement from others, I'm motivated to invest more time in finding a 
solution.

Note: if you are looking for an ebook reader you might find 
http://www.fbreader.org/FBReaderJ/ useful as an alternative to this project.

PS: Can you tell me more about the DAISY books you would like to read. This 
would help with my plans and the testing.

Original comment by julianharty on 16 Jan 2011 at 10:04

• Changed state: Accepted

[GoogleCodeExporter]

Appreciate the hard work! I'm new to the daisy format and this is my first time 
hearing about it.  Ill do a search for some books that come in the format.  
What I was doing was using the Daisy Pipleline to convert various formats to 
daisy so I could test out the functionality of the android daisy reader. I've 
really wanted a ereader that would read books to me on my android phone and 
this is the only project that i've found that is trying to implement it.  
Thanks for the quick reply!  Ill try my best to support this project anyway i 
can.

Original comment by HadToHa...@gmail.com on 18 Jan 2011 at 4:34

[GoogleCodeExporter]

2011-Sep-02 I am working to implement this capability and I aim to make a 
release available in September with this capability.

Original comment by julianharty on 2 Sep 2011 at 8:11

[GoogleCodeExporter]

Original comment by julianharty on 2 Sep 2011 at 8:27

• Added labels: Priority-High, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Original comment by julianharty on 2 Sep 2011 at 9:14

• Added labels: Milestone-2011-September-Release

[GoogleCodeExporter]

For the implementation that uses jsoup, I have already noticed the difference 
in performance between low and higer-specification Android devices is 
significant.

For the current 2 simple tests in TestFullText, the tests claim to run in 1.6 
seconds on my Nexus One, and around 16 seconds on my older HTC Tattoo - roughly 
a 10 to 1 difference in performance. Each test parses the full contents of the 
WIPO html file (around 46KB). My guess is that the performance will be poor on 
lower-end devices so we may need to improve the user experience e.g. with a 
'loading...' screen. 

Original comment by julianharty on 4 Sep 2011 at 12:45

[GoogleCodeExporter]

Revision 353 
http://code.google.com/p/android-daisy-epub-reader/source/detail?r=353 has the 
first very rough cut that displays the full text for DAISY 2.02 full-text 
books. I need to improve the formatting of the contents e.g. to stop the text 
being treated as links (which causes the text to appear as underlined and in 
dark blue). However we're one step closer to supporting full-text books :)

Original comment by julianharty on 4 Sep 2011 at 4:32

[GoogleCodeExporter]

Revision 354 has some improvements for newer, larger screen devices, as the 
links are converted to plain text (so they don't appear in dark-blue 
underline). However the contents of full-text books is broken / incomplete on 
older, small screen devices. I think the problem may be triggered by the HTML 
tags in the content read from the book which seems to cause indigestion for 
older versions of Android (I'm guessing). Next steps include:
1. Create some test code to identify and isolate the causes of the 'missing' 
text on the older devices.
2. Devise ways to improve the formatting and layout of the text, especially for 
small-screen devices. This may require rethinking the gesture interface to 
enable users to scroll through the text.
3. Start considering how to use the TTS to read the contents of the full-text. 
This is likely to require 'chunking' the text into relatively consistent sizes. 
Perhaps we will be able to highlight the text being read on screen? Again, this 
may require separate test code to prove the concepts.

Original comment by julianharty on 4 Sep 2011 at 7:56

[GoogleCodeExporter]

We have added the ability parse and display the contents of full-text DAISY 
books to the new app. We're currently experimenting with using TTS to read 
aloud the contents of text books.

Original comment by julianharty on 16 Dec 2013 at 7:43

• Changed state: Started
• Removed labels: Milestone-2011-September-Release