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

Pronounce button reading pitchless hiragana readings only #778

Closed
tyress opened this Issue Jul 16, 2017 · 5 comments

Comments

Projects
None yet
2 participants
@tyress

tyress commented Jul 16, 2017

Would be great if it read the Kanji directly as I think (I think) pitch is automatically taken into account with TTS. Currently the popular Hashi (箸 and 橋) are pronounced the same.

@mvysny

This comment has been minimized.

Show comment
Hide comment
@mvysny

mvysny Jul 17, 2017

Owner

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 if I let the TTS to read the kanji first, then the readings, that would do the trick? Not sure here, perhaps it will confuse the user even more.

Perhaps the best idea is to allow the user to choose what will be sent to the TTS engine - either kanji, or reading.

Owner

mvysny commented Jul 17, 2017

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 if I let the TTS to read the kanji first, then the readings, that would do the trick? Not sure here, perhaps it will confuse the user even more.

Perhaps the best idea is to allow the user to choose what will be sent to the TTS engine - either kanji, or reading.

@tyress

This comment has been minimized.

Show comment
Hide comment
@tyress

tyress Jul 17, 2017

I think it's okay to get the kanji part read first, but personally I think it might sound good to get to choose? It's rare, but 執行 (しっこう, etc.)for example has four readings and the output seems like a good demonstration of why being to choose might be great :)

tyress commented Jul 17, 2017

I think it's okay to get the kanji part read first, but personally I think it might sound good to get to choose? It's rare, but 執行 (しっこう, etc.)for example has four readings and the output seems like a good demonstration of why being to choose might be great :)

@mvysny

This comment has been minimized.

Show comment
Hide comment
@mvysny

mvysny Jul 17, 2017

Owner

I think I remember now: when I introduced TTS, the engines back then were way simpler and couldn't handle reading kanjis. However it seems that the situation has been improved now. I'll thus add support for the picker on what to read.

Owner

mvysny commented Jul 17, 2017

I think I remember now: when I introduced TTS, the engines back then were way simpler and couldn't handle reading kanjis. However it seems that the situation has been improved now. I'll thus add support for the picker on what to read.

@mvysny

This comment has been minimized.

Show comment
Hide comment
@mvysny

mvysny Jul 17, 2017

Owner

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.

Owner

mvysny commented Jul 17, 2017

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.

@mvysny mvysny closed this Jul 17, 2017

@tyress

This comment has been minimized.

Show comment
Hide comment
@tyress

tyress Aug 8, 2017

It's awesome by the way, thanks

tyress commented Aug 8, 2017

It's awesome by the way, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment