-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reading the full-stop at the ends of paragraphs #41
Comments
What is the application you are using to read the text? |
Scrivener. http://www.literatureandlatte.com PS: You can try this out directly from Edit>Speech>Settings: The test paragraph there ends in a full-stopDOT |
Update. I just remembered there was a loglevel... Using a hex editor: or: Sadly, I only see the SSML, not the input data. I'd say this is caused by the paragraph breaks being converted into, um, something. However, I cannot say if Scrivener does or if that's part of the SAPI-SSML conversion. However, as this character works with SAPI voices, I'd say it needs to be converted into something that doesn't trigger the preceding "." to be read, e.g. by adding a space character. (EDIT: When I said "works" above, I meant that SAPI sees the character as whitespace, not that it speaks it as a proper paragraph break. With the second example, SAPI still says "twelveThree", instead of "twelve. Three" as a human would.) As a luxury feature, replacing it with a short pause (e.g. |
PS: There's another small issue: It seems changing the loglevel disables logging completely until the host application is restarted. I haven't run further tests into that, though. |
Using local voice Sonia on Windows 10, I find that it reads the full-stop at the end of paragraphsDOT
This is mildly annoying and not something that happens with the standard Windows voicesDOT
It doesn't happen when a paragraph ends with a ?, ", or something like that. It also doesn't happen in the middle of a paragraph or with single-line inputs (like the preview in the system settings). I suspect this is an artefact of the way the text is transformed?
The text was updated successfully, but these errors were encountered: