VoiceGuide IVR Software Main Page
Jump to content

Search the Community

Showing results for tags 'arabic'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 3 results

  1. After downloading full Arabic package including ‘Display’ ‘Text to speech’ and ‘Keyboard’ subcomponents we would like to make VoiceGuide read ‘arabic’ sentences. However, it seems that ‘Arabic’ characters written and retrieved from any Microsoft software (Word, Wordpad, Notepad) or other third parties text editor (Notepad++) cannot be interpreted and displayed on any ‘VoiceGuide’ UI text editor interface (Text Box input field). The Unicode format (seems to be ‘UTF8’) related gets displayed in unreadable characters that cannot be processed by the Arabic TTS_Engine. (Please refer to the attached image for full details) We did confirm though, that numerical characters (1, 2 …) are well spelled and pronounced in arabic. Can you please let us know whether there any specific setting that need to be enabled in the Voiceguide or any additional plugins to be added in order to make the Voiceguide VB text editor to display correctly Arabic characters, words and full sentences. Please find in the attachment a snapshot of the Voice guide VB Script editor window along with the logs captured Arabic sentence interpretation testing. Thanks for your support. Attach: log file + screenshot log.zip
  2. After downloading a new Arabic ‘text to speach’ engine using the download procedure mentioned by Micorsoft : Settings > Time & Language > Region & Language > Language options > Speech, select Download We tried to toggle between the existing text to speech engine and the new downloaded one by changing the value pointed by the ‘TTS_SAPI_Engine’ as shown in the VB code below : vg.RvSet $RV_LINEID, "TTS_SAPI_Engine", "Microsoft David Desktop - English (United States)" From the ‘VoiceGuide’ logs ‘0527_ktTts.txt’ it seems that ‘TTS_SAPI_Engine’ is addressing the Windows Registry Key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\’ giving access to only the following TTS values: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\TTS_MS_EN-US_DAVID_11.0 Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech\Voices\Tokens\TTS_MS_EN-US_ZIRA_11.0 However, looking further in the Windows register database (via regedit) the new installed TTS engine there seems to be another Windows Registry key ‘Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices’ addressing the actual TTS packages including the new ‘Arabic’ that we are targeting (and not considered by VoicGuide TTS APis’ Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_arEG_Hoda Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enUS_DavidM Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enUS_MarkM Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enUS_ZiraM Is there a way or another TTS API (expect TTS_SAPI_engine ) that would allow us to point to ‘Speech_OneCore’ registery’ values instead of ‘Speech’ ones. Best Regards,
  3. Dear VoiceGuide, I am using VoiceGuide Enterprises+Dialer. I am going to install acapela tts on server.I want to SAPI TTS to read the text of English and Arabic based on selection from user(Example:Press 1 for Arabic,press 2 for English) once user press 1 script will go on as Arabic scenario. Let me know how can i set up the above scenario as well as if i placing Arabic text its showing as "????" please check the image below