RealSpeak Engine
Voice Tag Attributes
<gender>
The gender attribute should not be used if the name attribute is already being used for the <voice> tag.
<age>
This attribute is not supported.
<name>
If you have an onsite system, please contact your sales account manager for which of these voices you have installed on your server.
The following names are supported by their respective engines:
If no name is specified, Jill is the default voice for the US Realspeak Engine while Emily is the default voice for the UK Realspeak Engine.
Please contact your account manager if you want any of the following Realspeak voices:
The case-sensitive language code attribute MUST be used along with its corresponding xml:lang attribute if the language is not en-US (American English). For example, to hear the Mexican Spanish voice “Javier”, one must type the following:
NOTE: For US speech recognition, we currently only offer American English speech recognition, Spanish speech recognition, and French-Canadian speech recognition for Plum DEV. If you are interested in any other speech recognition languages, please contact your sales representative.
NOTE: For UK speech recognition, we currently only offer American English speech recognition and British English speech recognition for Plum DEV. If you are interested in any other speech recognition languages, please contact your sales representative.
<speak>
The <speak> tag should be used to specify the desired language through the attribute xml:lang=”lg-CN”, where lg-CN is the language-country pair specified in the Language column from the table of supported languages.
Please note that each voice has an associated language. Selecting a language that is not associated with the voice will result in unpredictable behavior; however, in many cases, you will hear the language the text was written in accented by that voice’s associated language.
<voice>
The <voice> tag should be used to specify the desired voice through the attribute name=”name”, where name is the voice specified in the Name/ID column for the table of supported voices.
If another voice is desired, it should specified using the <speak> and <voice> tags as follows within the prompt block:
To sequentially use multiple languages and voices within a <prompt> block, use multiple <speak> and <voice> blocks. For example:
<xml:lang>
If you have an onsite system, please contact your sales account manager for which of these languages you have installed on your server.
Please contact your account manager if you want any of the following Realspeak languages:
Note that different syntax is used for the xml:lang attribute for the RealSpeak Engine. For example, to hear a French speaker you need to use the case-sensitive county code, i.e.,<voice xml:lang=“fr-FR”>.
SSML Tags
An “x” marks that the Child Tag is supported by the speech engine. An asterisk (*) means that there are notes to explain the difference between the speech engines.
<break>
This works as expected.
<paragraph>
This works as expected.
<phoneme>
Phoneme Set for Nuance RealSpeak:
Key
<prosody>
When using a Realspeak TTS voice, the talking speed of the TTS voice does not revert back to the normal speed after the <prosody> tag closes.
To revert it back to normal, you must use the <prosody> tag again with the attribute of “volume” set to “100.0” and the attribute of “rate” set to “default”.
Note that this engine does not support the “pitch” attribute.
You cannot specify the “rate” value as an integer using this engine, but percentages and the presets rates (“fast”, “medium”, “slow”, or “default”) work as expected.
<say-as>
The table below shows the <say-as> tag types supported by this engine.
acronym: The acronym tag type works fine in the US, but does not work in the UK.
date:mdy: The preferred format of this tag is “month abbreviation day, year”. For example, to return “December 25, 2001”, you would type “Dec 25, 2001”. You can also use the “month/day/year” format such as “12/25/01” for the US, but this format will not work in the UK.
date:dmy: The preferred format of this tag is “day month abbreviation, year”. For example, to return “December 25, 2001”, you would type “25 Dec, 2001”.
date:ymd: The preferred format for this tag is “year month abbreviation day”. For example, to return “December 25, 2001”, you would type “2001, Dec 25”.
date:my: The format of this tag should be “month abbreviation, year”. For example, to return “December, 2001”, you would type “Dec, 2001”.
date:md: The preferred format for this tag is “month abbreviation day”. For example, to return “December 25”, you would type “Dec 25”. You can also use the “month/day” format such as “12/25” for the US, but this format will not work in the UK.
date:dm: The preferred format for this tag is “day month abbreviation”. For example, to return “December 25”, you would type “25 Dec”.
date:ym: The preferred format for this tag is “year/month”. For example, to return “December 2001”, you would type “2001/12”.
date:y: The date:y tag type works fine in the US, but does not work in the UK.
measure: For Realspeak, either format, 5'4“ or 5m, will work.
net:uri: The RealSpeak Engine does not read back URLs correctly and will play a web address as 'www point examplewebsite point com'.
time: The time tag type works fine in the US, but does not work in the UK.
telephone: The telephone tag type works fine in the US, but does not work in the UK.
The format for telephone numbers is: 123-456-7890
The format for telephone extensions is: 123-456-7890 ext1234
NOTE: For extensions, Realspeak will say the number back correctly. In the example above, Realspeak will say, “one two three four five six seven eight nine zero, extension one two three four.”
currency: When using the say-as type, currency, for AT&T Natural Voices with a Spanish TTS voice, please keep in mind that you will need to format the currency to $<dollar amount>,<cents amount>. The currency amount will not be pronounced correctly if you format it as $<dollar amount>.<cents amount>.
<sentence>
This functions as expected.
Last updated