TTS

61 views
Skip to first unread message

madst...@gmail.com

unread,
Jul 5, 2012, 10:55:03 PM7/5/12
to mnemosyne-...@googlegroups.com
Before I was using the google text to speech link as an audio source for English to test out how practical that would be for students learning English, but now I am trying to use it as an audio source to learn Korean.

http://translate.google.com/translate_tts?tl=ko&q=%EA%B8%B0
is what I get if I try to copy and paste it.

http://translate.google.com/translate_tts?tl=ko&q=기
is what gives me a TON of errors.

Whats strange is that I believe I did this on an earlier version of the 2.0 beta, and it worked fine.

I asked in the past if there was ever going to be support for tts (there is actually a java thing here: http://code.google.com/p/jgoogletexttospeech/ ) and I believe the reply was "maybe." Are there any plans so add this type of tts for language learners? And is there any way I can use Korean now in mnemosyne? English still works fine.

madst...@gmail.com

unread,
Jul 5, 2012, 11:02:28 PM7/5/12
to mnemosyne-...@googlegroups.com
The problem seems to be specifically with the use of the Korean characters.

George Wade

unread,
Jul 5, 2012, 11:45:06 PM7/5/12
to mnemosyne-...@googlegroups.com
Were the question TTS in Japanese or Chinese I could give you half an answer: the Japanese / Chinese TTS should, or could be: pretty good in a preliminary learning sense of getting pronunciation nearly right. However — nuances of many kinds will be absent or misleading. Nuances like saying 'No Thanks' when the literal meaning is 'Yes of Course !' Well ! That takes a few years to learn anyway, unless you are 2 or 3 years old.

Translations are hit and miss. Need checking by a native. Wear armour and carry bottles of sake as presents.

George

madst...@gmail.com

unread,
Jul 6, 2012, 12:10:43 AM7/6/12
to mnemosyne-...@googlegroups.com
On Friday, July 6, 2012 12:45:06 PM UTC+9, George Wade wrote:
> Were the question TTS in Japanese or Chinese I could give you half an answer: the Japanese / Chinese TTS should, or could be: pretty good in a preliminary learning sense of getting pronunciation nearly right. However — nuances of many kinds will be absent or misleading. Nuances like saying 'No Thanks' when the literal meaning is 'Yes of Course !' Well ! That takes a few years to learn anyway, unless you are 2 or 3 years old.
>
> Translations are hit and miss. Need checking by a native. Wear armour and carry bottles of sake as presents.
>
> George

Korean is just a phonetic as English and matches intonation for question etc.

I have accurate translations.

The issue is with mnemosyne's ability to process Korean characters as part of the link.

George Wade

unread,
Jul 6, 2012, 2:15:17 AM7/6/12
to mnemosyne-...@googlegroups.com
Sorry, that is the part I don't know about.

Peter Bienstman

unread,
Jul 9, 2012, 5:39:21 AM7/9/12
to mnemosyne-...@googlegroups.com
(Sorry for the late reply, I was on holiday)

For the 2.0 release, I had to change the sound system, because that version had quite some serious bugs.

The current 2.0 sound system does noh have good support for unicode, which is why you see this.

However, since 2.0 has been released, there also has been a new release of the 2.0-betas sound system, so hopefully, I can reinstate it.

As for TTS, vote for it on our feature request site.

Cheers,

Peter
Reply all
Reply to author
Forward
0 new messages