req: wrong reading position / configurable prev / next jump units

[pvagner]

I am using latest FB Reader and TTS plus plugin on an LG G3 with Android 5.0 Lollipop.
Most likelly I've got a broken simple text file causing this behaviour. When this file is open in FB Reader running on my device it takes approx 830 FB Reader pages. I have used TTS plus to read first 220 pages. Of course I haven't read it all within a single reading session. The last reading session was so I have been reading from approx page 157 to page 220. I have rebooted my phone, started FB reader, it opened on page 220, then I went to the menu to start TTS plus. TTS plus has started reading from page 166. I can use prev / next buttons to move forward but If I close TTS plus and use FB Reader controls to adjust position after page 166 (e.g. navigation slider or when I swipe to the next page multiple times) TTS plus will always start reading from page 166. It will also update the book position accordingly.
I guess that it attempts to detect a previous section or something similar when starting reading aloud. Since I may have got a broken file here it might have issues finding section boundary on pages 167 to 220 thus it moves back to page 166 when I instruct it to read from page 220.
I do have the following feature requests in mind:

• Would it be possible to never skip back more than a single page when starting reading aloud eventhough it may not start with a proper section boundary?
• Would it be possible to configure how much prev / next buttons move within the document by? E.G. I would be happy if there was a switch so we can configure it to jump by sentences like it does currently and also jump by pages usefull in such an emergency situations like my current one.

Greetings

Peter

[gregko]

Hi Peter,

Sorry for the late answer, it’s hectic here. I would really need the file that causes the problem to see what happens and if this is something I can correct in TTS+ Plugin code, or if it would have to be fixed in the main FBReader code. Or you could also use my @voice Aloud Reader app, which can open simple text, html, PDF, doc/docx and ePub files for reading aloud and uses different code base, not FBReader, so it may be able to handle that file correctly.

Greg

From: pvagner [mailto:notifications@github.com]
Sent: Wednesday, June 03, 2015 6:41 PM
To: gregko/TtsPlus-FBReader
Subject: [TtsPlus-FBReader] req: wrong reading position / configurable prev / next jump units (#10)

I am using latest FB Reader and TTS plus plugin on an LG G3 with Android 5.0 Lollipop.
Most likelly I've got a broken simple text file causing this behaviour. When this file is open in FB Reader running on my device it takes approx 830 FB Reader pages. I have used TTS plus to read first 220 pages. Of course I haven't read it all within a single reading session. The last reading session was so I have been reading from approx page 157 to page 220. I have rebooted my phone, started FB reader, it opened on page 220, then I went to the menu to start TTS plus. TTS plus has started reading from page 166. I can use prev / next buttons to move forward but If I close TTS plus and use FB Reader controls to adjust position after page 166 (e.g. navigation slider or when I swipe to the next page multiple times) TTS plus will always start reading from page 166. It will also update the book position accordingly.
I guess that it attempts to detect a previous section or something similar when starting reading aloud. Since I may have got a broken file here it might have issues finding section boundary on pages 167 to 220 thus it moves back to page 166 when I instruct it to read from page 220.
I do have the following feature requests in mind:

• Would it be possible to never skip back more than a single page when starting reading aloud eventhough it may not start with a proper section boundary?
• Would it be possible to configure how much prev / next buttons move within the document by? E.G. I would be happy if there was a switch so we can configure it to jump by sentences like it does currently and also jump by pages usefull in such an emergency situations like my current one.

Greetings

Peter

—
Reply to this email directly or view it on GitHub #10 . https://github.com/notifications/beacon/ABqnfFfzSlg9QRNgnYyUKHRoPDL7WQqfks5oP3nkgaJpZM4E3N0-.gif