[asterisk-dev] [feature] Support for relative paths for all "say" functions

[Nicolas Chapleau]

> Date: Mon, 24 Aug 2009 21:06:01 -0500
> From: Tilghman Lesher tilghman at mail.jeffandtilghman.com



> They are in code only. Basically, the idea is that if you have es_ES, es_MX,
> or es_CO, or any one of many other regional codes for language "es", they
> will all follow the same grammatical rules. Previously, your language code
> had to match EXACTLY. Now, if you have "es_MX_company1" as your language,
> it will follow the grammatical rules for "es", if more specific rules for
> "es_MX" or "es_MX_company1" are not found.

 

Thanks, makes sense if it falls back.

 
> The point is that you shouldn't need to. You can create derivatives of the
> language that contains ALL of your prompts, including any dates, numbers, or
> others that you want pronounced differently, and they will all follow the
> language. When a prompt isn't found in your special collection, the language
> setting will be used to find more generic prompts to substitute. It's a
> pretty good schema meant to ensure that fallbacks exist, so you won't need to
> create entire voice libraries, merely to substitute one or two prompts.


I will setup an environment as per your suggestions and see it's implications. Thanks all for your input.

 

NicCHap. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20090825/3f6234bb/attachment.htm