Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tts voice to simply read the word #830

Closed
dezorianguy opened this issue Apr 10, 2018 · 2 comments
Closed

tts voice to simply read the word #830

dezorianguy opened this issue Apr 10, 2018 · 2 comments
Assignees
Labels

Comments

@dezorianguy
Copy link

@dezorianguy dezorianguy commented Apr 10, 2018

good day sir,

when I decide to let aedict read a word aloud, by pressing the speaker button next to the Kanji, it always opens up a box where I am presenting with 2 or more choices of what exactly I want it to read aloud. mostly I can choose the kanji and hiragana reading. which in speech doesn't make any difference...

so, for example choosing 車 to be read aloud. instead of just saying the word it let's me choose between 車 and くるま 。

if that could be fixed that would be awesome. :)

best wishes,
chris

@mvysny mvysny self-assigned this Apr 12, 2018
@mvysny mvysny added the bug label Apr 12, 2018
@mvysny
Copy link
Owner

@mvysny mvysny commented Apr 12, 2018

The old TTS engines were pretty weak and would say nothing if I passed in just "車". Hence I had to make the user to choose to pass either 車 or くるま, based on the level of the TTS he had installed.
However, Google's TTS got pretty awesome and now is able to read both 車 and くるま. So in this specific case where the word entry consists of just one kanji and just one reading, I should not display the choice popup but should simply always pass in "車"

@mvysny
Copy link
Owner

@mvysny mvysny commented Apr 12, 2018

Fixed in 3.49

@mvysny mvysny closed this Apr 12, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants