06-15-2020, 03:39 PM
Hi, and thank you for your suggestions.
Concerning FB2 'v' elements within a poem, indeed, there was a bug that meant those tags weren't parsed right. I've fixed the code, and it should work better after the next update (within a week, I hope). More generally, FB2 support in Freda is a problem (ever since they made a bunch of breaking changes to the FB2 spec). The old FB2 spec was backward-compatible, in the sense that even if they added new tags that Freda did not understand, the words would still show up on the page (though maybe missing some formatting). The new spec doesn't work like that, and I have a nasty suspicion that the owners of the FB2 standard did this deliberately, to make it harder for competing ebook reader apps to stay compatible :-) ! Anyhow, the FB2 format does seem to be dying out - for best results, I'd recommend you to use Calibre to convert your FB2 books to EPUB.
Regarding your other suggestions, I'll add them to the list. To address them in turn:
2: is complicated for two reasons: firstly, actually coming up with the right setting name and description for this feature is not trivial. It's not really 'disable animations' because you're also wanting to disable the behaviour "drag the page half way down and leave it there" - which allows the user to see the bottom of this page and the top of the next, on the same screen. It's more "disable manual scrolling" and that's a bit hard to explain. Secondly, the way that Freda detects a 'page flick' motion is the same as the way it detects 'manual scrolling', so adding code to detect 'page flick' would not be simple. It's doable, but not simple ... and that's why I have not done it yet.
3: it's going to be very hard to provide all the customisation options that anyone could ever want, unless I actually implement a completely general 'language' for defining what content someone wants to see in (1) the page info ribbon (2) the page number area on the page. It is on my 'to do' list, but getting it right won't be simple.
4: The setting 'swipe to' on the controls screen should do what you need, when set to 'change page'. Is it not working?
5: It's on the to-do list.
6: You can increase the font size of the speed read text by increasing Freda's font size. Allowing the user to separately customise the size of the speed-read text is on my to-do list.
Concerning FB2 'v' elements within a poem, indeed, there was a bug that meant those tags weren't parsed right. I've fixed the code, and it should work better after the next update (within a week, I hope). More generally, FB2 support in Freda is a problem (ever since they made a bunch of breaking changes to the FB2 spec). The old FB2 spec was backward-compatible, in the sense that even if they added new tags that Freda did not understand, the words would still show up on the page (though maybe missing some formatting). The new spec doesn't work like that, and I have a nasty suspicion that the owners of the FB2 standard did this deliberately, to make it harder for competing ebook reader apps to stay compatible :-) ! Anyhow, the FB2 format does seem to be dying out - for best results, I'd recommend you to use Calibre to convert your FB2 books to EPUB.
Regarding your other suggestions, I'll add them to the list. To address them in turn:
2: is complicated for two reasons: firstly, actually coming up with the right setting name and description for this feature is not trivial. It's not really 'disable animations' because you're also wanting to disable the behaviour "drag the page half way down and leave it there" - which allows the user to see the bottom of this page and the top of the next, on the same screen. It's more "disable manual scrolling" and that's a bit hard to explain. Secondly, the way that Freda detects a 'page flick' motion is the same as the way it detects 'manual scrolling', so adding code to detect 'page flick' would not be simple. It's doable, but not simple ... and that's why I have not done it yet.
3: it's going to be very hard to provide all the customisation options that anyone could ever want, unless I actually implement a completely general 'language' for defining what content someone wants to see in (1) the page info ribbon (2) the page number area on the page. It is on my 'to do' list, but getting it right won't be simple.
4: The setting 'swipe to' on the controls screen should do what you need, when set to 'change page'. Is it not working?
5: It's on the to-do list.
6: You can increase the font size of the speed read text by increasing Freda's font size. Allowing the user to separately customise the size of the speed-read text is on my to-do list.