Join GitHub today
Pronounce button reading pitchless hiragana readings only #778
That is true - TTS is currently given the reading only; since the TTS engine ignores pitch markings it will read it quite flat. The advantage is that it will read all readings. If the TTS engine was given only the kanji, then it would read just the first reading.
Perhaps the best idea is to allow the user to choose what will be sent to the TTS engine - either kanji, or reading.
Selection dialog implemented in Aedict 3.41. It seems that the TTS still have some issues, at least the default Google one, since it reads 喰べる as something like 'kviberu' ;) Anyways, at least now you can choose what the TTS will read.
Don't trust the TTS too much - albeit the speech synthesis made huge progress, it is still just an automatized tool which may make mistakes.