<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
> Date: Mon, 24 Aug 2009 21:06:01 -0500<BR>> From: Tilghman Lesher <A href="mailto:tilghman@mail.jeffandtilghman.com">tilghman@mail.jeffandtilghman.com</A><BR><BR>
<BR>> They are in code only. Basically, the idea is that if you have es_ES, es_MX,<BR>> or es_CO, or any one of many other regional codes for language "es", they<BR>> will all follow the same grammatical rules. Previously, your language code<BR>> had to match EXACTLY. Now, if you have "es_MX_company1" as your language,<BR>> it will follow the grammatical rules for "es", if more specific rules for<BR>> "es_MX" or "es_MX_company1" are not found.<BR>
<BR>
Thanks, makes sense if it falls back.<BR>
<BR>> The point is that you shouldn't need to. You can create derivatives of the<BR>> language that contains ALL of your prompts, including any dates, numbers, or<BR>> others that you want pronounced differently, and they will all follow the<BR>> language. When a prompt isn't found in your special collection, the language<BR>> setting will be used to find more generic prompts to substitute. It's a<BR>> pretty good schema meant to ensure that fallbacks exist, so you won't need to<BR>> create entire voice libraries, merely to substitute one or two prompts.<BR><BR>
I will setup an environment as per your suggestions and see it's implications. Thanks all for your input.<BR>
<BR>
NicCHap. <BR><BR></body>
</html>