Summary:	ASTERISK-00298: [patch + redesign request] Non-english support in app_voicemail
Reporter:	app (app)	Labels:
Date Opened:	2003-09-23 12:20:59	Date Closed:	2004-09-25 02:49:37
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) app_voicemail2.diff
Description:	Patch to support the portuguese language in comedian mail. Assumes the change on the "I" option that has been included in bug 300 for say.c because "digits/at" needs several voice files on other languages. ****** ADDITIONAL INFORMATION ****** Testing voice files are available for /var/lib/asterisk/sounds/pt. A better set will be recorded later.
Comments:	By: John Todd (jtodd) 2003-09-29 03:12:04 This is a custom patch for Portugese; is there any reason that this could not either be more generalized for other languages, or that it would not be required if the existing multi-language structure is used with Asterisk? By: app (app) 2003-09-29 06:12:02 Same as bug 300. English rules could maybe be seen as a subset of the latin rules but other languages (Chinese? Japonese? Korean?) may have a completely different set of rules. We will probably need a completely new approach to these i18n issues. By: Paul Cadach (pcadach) 2003-10-13 05:40:30 May be to provide "lang_" interface for say*/voicemail* functions? Just provide functions like 'register_language(char *lang, struct lang_t *functions);' and 'unregister_language(char *lang);'. Functions in lang_t (if assigned) will handle say* / voicemail* requirements for internationalization. As for me I tries to provide russian and kazakh languages support for * and needs this API too. By: Olle Johansson (oej) 2004-04-13 13:41:12 Pcadash: Have you gone further with your register_language idea? It's an interesting approach. Would like to see some more of that architecture. Could you spend some time expanding it a bit and documenting it for review? By: Paul Cadach (pcadach) 2004-04-13 14:10:32 Now I'm working on russifying voicemail and say* stuff. After this work I'll be ready to produce some real information on hooks required for at least Russian language. After that I'll pass working scheme to translators which could provide me with Kazakh translations. As I could see for now most of the problems is to generate correct word's order for each language at voicemail stuff, and this will be most of ast_lang_t structure with language-specific procedures (for example, invent_message(), some other procedures needs to be re-organized to be more language independed). By: flavour (flavour) 2004-04-15 11:22:40 app: Any chance of making the pt soundfiles available for download? Even an imperfect set would make a nice addition to: http://voip-info.org/wiki-Asterisk+sound+files+international I would use them for starters... By: Olle Johansson (oej) 2004-04-15 14:40:22 For changes to say.c - see bug 1429. Let's start with fixing say.c and after that we'll look into what needs to be done to voicemail... Keep adding patches and bug reports to voicemail here so we document what problems we do have. By: Olle Johansson (oej) 2004-04-15 14:41:15 Changed subject to be more general. By: twisted (twisted) 2004-04-29 10:08:34 Can we get this patch updated to the current app_voicemail.c?  There have been quite a few changes to that app as of late, and I want to make sure that internationalization will reflect those changes. Thanks. By: flavour (flavour) 2004-04-29 11:51:48 Isn't activity in this area now happening in ASTERISK-1469? I've created a patch there that adds basic Internationalisation support & then some French variations. If this is approved, I can easily extend to Portuguese & Dutch as I have syntax examples for those... By: twisted (twisted) 2004-04-29 12:12:49 this is indeed the case... if you will move your patch over there and report back here when that's done, we'll close this out as a dupe. By: Olle Johansson (oej) 2004-04-29 13:43:09 Moving all patches and discussions to bug ASTERISK-1469. Follow me there :-)