<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
> I agree that this seems to duplicate LANGUAGE, but in fact it<BR>> only complements it. The LANGUAGE field is still used and the<BR>> VOCAB_RELATIVE_PATH only appends to it. If the functions in "SAY" had<BR>> relative paths just like the playback and background functions do, this<BR>> would not be an issue, but they are hard coded. I would like<BR>> to implement this but I would need to change the syntax and I do not<BR>> wish to do so for compatibility reasons.<BR><BR>So let's try for a real example then; are you saying that you'd have<BR>French prompts installed under 'fr', but want some specific variants for<BR>digits that would be used only by code that wanted to speak digits?<BR><BR>If so, you could install the specific digits *only* under fr_special,<BR>and set LANGUAGE to fr_special; this will cause Asterisk to find the<BR>digits under fr_special, but the non-digit prompts under plain fr.<BR>
<BR>
Response: <BR>
<BR>
I agree, but there would be lot's of flip flopping around on the LANGUAGE flag. This would also render "say" functions<BR>
to not play the correct language syntax for numbers, dates and times as the functions are not aware on how to play fr_special1, fr_special2, ...<BR>
<BR>
NicChap<BR></body>
</html>