<prompt>tags, but limits available functionality
<voice>tags in order to use different voices and languages.
xml:langproperty is slightly different in Polly, but it is also very strict.
en_us. In Polly, the same language property syntax is
en-US.In Polly, the language code is lower-case followed by a dash, which is followed by the dialect code in upper-case.
<acronym>tag. Polly doesn’t support this attribute and, if used, returns an error. In the IVR, this results in no audio.
<say as type="amount">gets replaced with
<say as interpret-as="unit">.
<voice>tags as follows within the prompt block:
<prompt>block, use multiple
<voice>blocks. For example:
<speak>tag should be used to specify the desired language through the attribute
lg-CNis the language-country pair specified in the Language column from that table of supported languages here: https://docs.aws.amazon.com/polly/latest/dg/voicelist.html.
<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 here: https://docs.aws.amazon.com/polly/latest/dg/voicelist.html.
<voice>tag the attribute variant="number" should be used to specify whether a standard voice (variant=1) or neural voice (variant=2) is desired. Note that only certain voices support the neural option. See: https://docs.aws.amazon.com/polly/latest/dg/voicelist.html for a list of voices that support neural, and https://docs.aws.amazon.com/polly/latest/dg/NTTS-main.html for the differences between standard and neural voices.
<voice>block can further be marked up with the following SSML tags that are supported by Plum Voice for Amazon Polly.