Multilingual support for playback of BMLT meeting info in Yap.

[webfacilitator]

Is your feature request related to a problem? Please describe.
The new Spanish translation of prompts in Yap 3.xx, combined with the playback of meeting info stored in English, produces Spanglish, which is not desirable to English or Spanish speakers.

Describe the solution you'd like
The solution that would be best is to have the same language voice support existing in Yap now for prompts be extended to meeting information. This may require some type of field in BMLT indicating which language the info is saved in.

Describe alternatives you've considered
The alternative is to separate English and Spanish Yap instances and manually translate the few Spanish meetings that exist in our region/zone. Then keep all English speaking meetings info to be played back with the default English voice, thereby matching English prompts with English meeting info.

Mention any other of the Github handles that are also interested in this enhancement

Additional context
This issue of intermixing languages is a byproduct of Yap having advanced in multilingual support beyond what is currently implemented with BMLT typically.

[dgershman]

This is a shortfall of the BMLT in which meeting information language is not stored. You get to choose one.

[dgershman]

The one option is to use "Format" to determine the language. Based off that designation, it would direct the voice to use.

[webfacilitator]

Using the format field sounds like a good solution.

[dgershman]

You'd have to map Format to Language as a configuration setting in Yap, because format codes can vary from root server to root server.

[dgershman]

So are you expecting that regardless of the language selected it would play back the meeting in the format code selected (with say the default being a pre-selected language)?

Or are you expecting that if you select a specific language that it would only return meetings that are tagged with that specific format mat (with say the default being a pre-selected language)?

[webfacilitator]

The 1st option — matching languages for meeting info playback. Separating them we are going to manually right now.

…

On Thu, May 2, 2019 at 5:40 PM Danny Gershman ***@***.***> wrote: So are you expecting that regardless of the language selected it would play back the meeting in the format code selected (with say the default being a pre-selected language)? Or are you expect that if you select a specific language that it would *only* return meetings that are tagged with that specific format mat (with say the default being a pre-selected language)? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#281 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AF6DMBZC2B52KZ4Z36X5UBLPTNNTLANCNFSM4HJQ4AFQ> .

[dgershman]

Seems feasible. On Fri, May 3, 2019 at 4:12 PM webfacilitator <notifications@github.com> wrote:

…

The 1st option — matching languages for meeting info playback. Separating them we are going to manually right now. On Thu, May 2, 2019 at 5:40 PM Danny Gershman ***@***.***> wrote: > So are you expecting that regardless of the language selected it would > play back the meeting in the format code selected (with say the default > being a pre-selected language)? > > Or are you expect that if you select a specific language that it would > *only* return meetings that are tagged with that specific format mat > (with say the default being a pre-selected language)? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#281 (comment)>, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AF6DMBZC2B52KZ4Z36X5UBLPTNNTLANCNFSM4HJQ4AFQ > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#281 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAOD3O4E673P7AYM3J45KGLPTSMBTANCNFSM4HJQ4AFQ> .

[dgershman]

Looked at this again, and it's too complicated to implement for such a small number of use cases. The root server doesn't haven't a native capability currently to facilitate this.