cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
124
Views
0
Helpful
0
Comments
cdnadmin
Community Member
This document was generated from CDN thread

Created by: Janine Graves on 17-01-2007 02:53:38 AM
What is the best way of writing a large app (production grade) that will have to be maintained in more than one language and use ASR, TTS and pre-recorded audio.

I understand that one can change the Default Audio Directory for the prerecorded audio. And one can change the xml:lang in the java code to help point to the correct TTS or ASR engine.

But, the actual text for the TTS must be different for the different languages. Do most people use a variable for the prompt TTS text, and set the value based on the language selection? Or do they use dynamic configurations for this?

And for ASR, will changing the xml:lang value work with builtin grammars (digits, time, date, etc.) - ie, do the builtin grammars exist for each language?

It seems like a lot of work to do this for every single prompt. Is there any plan to make Studio make it easier to write and maintain multi-language apps?

Thanks, Janine

Subject: RE: multi language apps
Replied by: Vance Vagell on 19-01-2007 03:59:51 PM
Hi Janine,

Please refer to the following Audium Knowledge Base articles for a thorough overview of how to create multilingual voice apps using Audium Studio:

"Developing a multilingual application"
"Can I use different audio paths for each language my application supports?"

Note that since the writing of those articles we have introduced a new element in Studio called "Application Modifier" (in the "Context" folder of the Elements view). Among other abilities, this element allows you to set the xml:lang attribute for all pages after it is visited. By using this element in key points in your call flow, you can change the xml:lang attribute without using Java code.

In regards to TTS text, there are many ways to approach this. One possibility is to create a dynamic configuration class that all of your voice elements use, that retrieves the appropriate prompts from a back-end system (database, property files, etc.) and then configures the element to use them. Note that some languages may require special encodings that support a wider range of characters (such as Cantonese, Japanese, etc.), in that case please ensure that the Application Modifier element is used to change the encoding before incorporating that TTS text into your VoiceXML.

In regards to how your ASR engine will function in a multi-lingual implementation, please refer to your ASR documentation. This behavior may vary by vendor.

We are always interested in making Studio easier and more intuitive to use, and multi-lingual application development is no exception. Our development team has been working on innovative new approaches to this task for future releases.

Should you have any further questions about multi-lingual applications, please let us know and we would be glad to continue this discussion.

Regards,
Vance
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Quick Links