nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Read Aloud -- A Request to Logos

Now that Read Aloud is officially a feature of Logos, may I request that as part of the book rebuilding process, that you add a step to check for major issues that may be causing problems with Read Aloud throughout the resource file? For example, if you read aloud in the NLT, I've noticed at least these two problems everywhere:

- The first letter after a left open quote (") gets 'eaten' up and not pronounced. e.g. "Yet... is pronounced like et, "But... is pronounced like ut, "For... is like or.

- The long dash (--) does not insert a pause.

Back in Logos 3 with the read aloud feature, I've noticed many other strange behavior with other books, such as no pause in between verses or between section headings and paragraph breaks, etc. I believe a good number of folks use this very valuable feature (some folks may rely on it due to eyesight and other issues). I would like to ask Logos to add this to your checklist while rebuilding the books (at least I believe that's where the problems could be fixed, but I could be wrong -- it might require software coding changes too).

Thanks for your consideration!

Peter

Find more posts tagged with

Comments

TCBlack

Since read aloud is really a gateway into the operating systems text to voice features; these may be issues with the Microsoft Sapi 5.3 engine.

Nevertheless, I agree with your findings and hope that Logos can do something about it.

LimJK

Peter,

It depends on what voice you use, it actually makes a difference. Fundamentally, what is needed is a kind of pronunciation editor similar to those from textaloud to over come such side effects.

I have just tested Readaloud on NLT with Microsoft Anna shipped with Windows 7. It sounded alright, without the side effects you mentioned. I also found AT&T voices such as Crystal, to be alright through out the beta testing period.

If you use Neospeech voices, there is another problem that I have reported. when you start reading the second and subsequent resource, it does not read.