This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 30%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF%3C/text%3E%3C/svg%3E)
The word "Persien" is not pronounced correctly with the German Voice "de-DE-ConradNeural"
Even when I added the IPA to the lexicon it still wasn't quite right.
IPA: ˈpɛʁzi̯ən
Lexicon entry: <lexeme><grapheme>Persien</grapheme><phoneme>ˈpɛʁzi̯ən</phoneme></lexeme>
(lexicon lang is de-DE)
Azure TTS pronounciation: iə is read as a diphtong, which is not correct
Correct pronounciation: https://upload.wikimedia.org/wikipedia/commons/9/95/De-Persien.ogg
This can be reproduced by using the following SSML on the demo site (or by setting the language to Germany, selecting the voice Conrad and entering "Persien" in the text field):
https://azure.microsoft.com/en-us/services/cognitive-services/text-to-speech/?cdn=disable#features
SSML:
<speak xmlns="http://www.w3.org/2001/10/synthesis" xmlns:mstts="http://www.w3.org/2001/mstts" xmlns:emo="http://www.w3.org/2009/10/emotionml" version="1.0" xml:lang="de-DE"><voice name="de-DE-ConradNeural"><prosody rate="0%" pitch="0%">Persien</prosody></voice></speak>
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(278.4, 1%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYM%3C/text%3E%3C/svg%3E)
Hello @fnx
Thanks for reporting this issue, I have forwarded this issue to product team and will let you knonw once I get confirmation from them.
Regards,
Yutong
Hello @fnx
Just follow up with you, this issue has been forwarded to product team and I will let you know once I get any ETA for this feature, thanks.
Regards,
Yutong
Hello @fnx
Thanks for reporting this issue again.
This is an update - this issue has been forwarded to product engineering team and they are working on this issue. I hope it will be fixed soon.
Regards,
Yutong