Nuance Vocalizer Developer's Guide - Avaya Support

mode, Vocalizer can also interpret ISO-8859-1 input character if you provide anappropriate XML header: This message is in iso 8859 1 format For most English text, encoding is not an issue because of the directcorrespondence between UTF-8 and 7-bit ASCII; characters numbered 0 to 127in 7- or 8-bit ASCII are the same as the characters numbered 0 to 127 in UTF-8.However, if you enter non-English expressions in SSML mode, such as wordslike “coup d'état,” you must specify the encoding. Failure to enter the encodingcauses unpredictable behavior. For example, entering text in the Offline AudioGenerator with at least one accented character produces no output.Caution: When using non-English voice packs and entering text in SSML mode,you must specify the encoding type, ISO-8859-1, to avoid unpredictablebehavior. For example, entering text in the Offline Audio Generator with at leastone accented character produces no output. See “Text encoding” on page 88.The following encoding values are recognized by Vocalizer:■■■■utf-8utf-16iso-8859-1us-asciiWhen using the element in SSML, if you select IPA as the alphabet,the IPA characters can be represented by multi-byte values only, and the entiredocument passed to Vocalizer must therefore be encoded using either UTF-8 orUTF-16.URI formats for the SSML elementVocalizer handles a specific set of http: and file: URI formats (per RFC s 2616 and2396) for the VoiceXML element. For example, this table shows illegalformats:URIErrorC:/foo.wav Invalid format per RFC 2396file://C:/foo.wavUses only two forward slashes (/) instead of threebetween the colon (:) and the “C”.The correct form is: file:///C:/foo.wav40Nuance Vocalizer 3.0Developer’s Guide