Support for SSML?

Which SSML tags are supported and how depends only on the TTS voice you use. I cannot do anything else, except passing text to TTS engine, and including the tags as needed. The <break> is the most common SSML tag supported by different voices, but not all of them.
Also, how do you enter the SSML tags. Through the "Edit text" function on the main menu? This may not work well, I would need test the issues here some more. The way I used them so far was with "Edit speech" feature on the Settings menu, e.g. if you want a 500 ms pause on each comma, do a replacement:
 
Replacement kind: Case sensitive     (this does not matter much here, except that this is the fastest)
Pattern: ,
Replace: ,<break time="500ms"/>
 
Greg

Yes, standard is one thing, the actual implementations - another. However the voices should still speak correctly with SSML tags embedded, even if they don't handle them. They would stop speaking only if the tag coding was incorrect. I maybe could point errors if you gave me concrete examples of what exactly you did and where.

The online voices, currently only in Google TTS set I believe, send text of each sentence (actually, what @Voice highlights in yellow) to the Google server, and receive back "wave" data used to emit sound. How exactly they work, and which SSML tags they handle or not, I cannot say. They are products of Google company, not mine.
 
I tested a sentence like:
 
Just a test: <prosody pitch="+20%">Hello there</prosody>! test end.
 
with Google local voice it said everything, but without any changes in pitch. However, entering tags like this through the "Edit text" function on @Voice menu does not work correctly, one must do such things through "Edit speech".
 
Greg

It would be possible with the "Edit speech" function on the Settings menu of @Voice, but first you would have to consider which double-quotes characters are used in the text you are listening to, as there are several different double-quote characters available in the Unicode standard. There is the most common " that you can type directly from the keyboard (on a big US English keyboard it is just to the left of Enter key), and it's the same for opening and closing quotation mark.
 
There are other, some have opening quotation at the lower letter line and closing and the upper, others just look differently, maybe the opening double-quote character is slanted from left to right, and closing the other way, etc. If the quotation marks for opening and closing are different, it's easier to replace them with correct "prosody" code. If they are the same, it's more problematic.
 
Another complication is that @Voice speech replacements work only within one sentence scope. So the "prosody" would work if the opening and closing quotation are within the same sentence, but not otherwise. I would have to redo this feature, maybe to work on whole paragraphs of text or something, to work correctly in more cases.
 
Here is a sample replacement for the regular double quote character " that can be typed directly from keyboard, same for opening and closing:
 
- Open @Voice Settings menu - press Edit speech
- press the [+] button on top to add new replacement
- enter the following:
 
Type: Regular Expression (RegEx)
Pattern: "(.+?)("|$)
Replace: <prosody pitch="+20%">$0</prosody>
 
- hide keyboard and press Save, go back to text and test. Note that this will work only for TTS voices that support SSML and its "prosody" command.
 
Greg3

Little bump to this. It was all working fine for me via edit speech, but suddenly Google's online voices are ignoring the SSML. However it seemed to happen with the last update to this software, not Google's voices last update (looking at the latest updates for both). The voices just don't pronounce the SSML at all at the moment, so lets say you had "hi there" and changed the pitch up for another "hi there", they'd just say it at the same pitch. Whereas the offline ones do pronounce prosody pitch= etc or they won't say the words at all between the tags.
 
Tried re-installing. clearing cache, getting Google voices again etc. Odd...