Espeak pronounces sentences with fullstop as it is comma

[sevapopov2]

I don't know if it was already mentioned, but I noticed that eSpeak for iOS pronounces sentences with fullstop as if they have coma and not fullstop. You can find it if you type two sentences and eSpeak will pronounce them. Steps to reproduce:

1. Open notes app or any text editor on iOS
2. Write "Hello. How are you?"'
   Type the same sentence in eSpeak command line on Windows or Linux.

Expected result: the intonation should lower after fullstop as if the sentence is finished, as you here it on Windows and Linux.
Actual result: eSpeak's intonation gets higher after fullstop. As if there is comma or something else but not fullstop.
ESpeak-ng 1.11, iOS 16.3.

[sevapopov2]

Hello! @djphoenix Would it be possible to fix that? Thank you!

[thgcode]

I think this and issue #45 might be related... I think it maybe could be some incorrect SSML interpretation of the text sent by Voiceover, but I don't have a Mac to debug it... but I think if someone could debug it, see the differences between the SSML generated by NVDA for example and Voiceover could generate some insight on how to solve the problem.

[Arqeria]

I think this and issue #45 might be related... I think it maybe could be some incorrect SSML interpretation of the text sent by Voiceover, but I don't have a Mac to debug it... but I think if someone could debug it, see the differences between the SSML generated by NVDA for example and Voiceover could generate some insight on how to solve the problem.

I’ve been thinking the same, but I don’t know enough about either SSML or swift to understand exactly what’s happening here. It’s frustrating because the Mac version of ESpeak doesn’t have this problem, so this may well be specifically related to how IOS VoiceOver handles punctuation, a.k.a. not fixable by us. I’ve contacted Apple’s accessibility team regarding this issue, but to no avail.

What puzzles me is the fact that nobody else seems to be reporting this. I’ve brought it up elsewhere before, but nobody else has ever been able to see what we’re seeing here. It kind of makes me wonder if maybe something in VoiceOver settings might be responsible for it, but I’ve looked all over and I can’t seem to find anything.

Interestingly, paragraphs do appear to be read normally, so that may provide a clue as to how this can be fixed. I tried changing full stop to paragraph in the punctuation dictionary settings, but either it didn’t accept that or it just didn’t work. @djphoenix

[patricus3]

noticed it too.