Dingoonity.org

Cool an epub reader! not that I enjoy text-to-speech, but I do like reading epubs, usually use an e-ink tablet, but this was a fun surprise.
Thanks!

Its interface is kind of buggy right now.

1. After pressing SELECT to enter the menu, I can go to following pages by pressing Down at the last item. When I am on the last page, pressing Down brings me to an empty page. Exiting and re-entering the menu with another press of SELECT continues to give me the empty page. I cannot use Up to get back to a real page, ever, preventing me from exiting Bard normally.

2. After pressing START to enter the options, I do not see which option is selected because the selection blue is not very different from the normal blue. However, after selecting new options for a while, the options that had been selected before seem to be bold.

3. After pressing START to enter the options, I have the same page bug as with SELECT (see 1.) but pressing START twice allows the menu to come back to the first page.

4. When auto-scrolling with A, words that were bold on the first line become non-bold if they are only partially in view due to scrolling. If enough text was bold in it, and the non-bold font allows one more word to fit in the first line, the viewport is reflowed and the position of the rest of the text changes.

5. When manually scrolling with Down and reaching the last line in the viewport, the viewport is scrolled one page and the selection marker moves to the first word on the new page (good). When scrolling with Up and reaching the first line in the viewport, the viewport is scrolled one line, and the selection marker moves to the last line, which is only one line up (bad).

6. When speaking text with X, any word that was bold and was successfully spoken completely disappears when the selection marker moves off it.

7. After speaking text with X and finishing the document or stopping speech, pressing Y to go one page up only moves individual words (sometimes) or lines into view until the top of the document is reached, at which point paging down and up with B and Y works fine.

raygan (#4): I've been using Glutexto to read (and edit) fixed-width text files, and it works pretty well. Although, of course, having good reflow in this application even when using a fixed-width font means one less application to worry about for reading text files (not for editing).

One bug though I've not see before is:

Quote from: Nebuleon on August 08, 2014, 09:54:33 pm

6. When speaking text with X, any word that was bold and was successfully spoken completely disappears when the selection marker moves off it.

a) When I speak the Bard Help file, it does appear to delete the highlighted words (e.g. the keys A B X Y), but that is because the system thinks there is a "sentence" break there (due to the markup) and it advances the display at each sentence boundary.  Is that the phenomena you are seeing or are you seeing something else?

b) I am working on a new version and will add these to the list of bugs.  I have been trying to support Hindi, Chinese and Japanese (for my other users), but I'll continue to improve user interface issues.  c) Also I'd prefer to have the screen blank while its talking (or at least be an option to this) so it can save battery when its reading long stories to me.

Alan

a: I believe that is it, yes. And then if you try to page up from the end of the document after it's finished speaking, the text breaks come back one by one. Those could be related.

b: Oh boy, Hindi. I hope that doesn't break your brain Chinese and Japanese are simpler unless you want to support vertical layout as well.

c: Having the screen blank itself while speaking would be good, yes, except in the case where it's speaking something that's misspelled or complicated, it's bugging up the word and you want to see what it is before it goes off-screen. I don't know how common that is in practice.