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

Mispronunciation issues #41

Closed
GoogleCodeExporter opened this issue Apr 5, 2016 · 1 comment
Closed

Mispronunciation issues #41

GoogleCodeExporter opened this issue Apr 5, 2016 · 1 comment

Comments

@GoogleCodeExporter
Copy link

I wasn't 100% sure where this should go, so I'll put it here where it should 
get seen, and if it's the wrong place then someone can tell me to move it.

There are a few words that the TTS fails to pronounces correctly, which can be 
problematic if you're relying on it for directions when driving somewhere 
you're not familiar with. I was just wondering if it might help to list the 
words it has trouble with, so that exceptions can be identified - maybe it 
would help with working out amendments to the rules to improve the accuracy.

The one I've noticed it consistently having trouble with is Solihull (a town 
south of Birmingham that I've been driving through lately). It should be 
pronounced with the emphasis on the So, and the li pronounced as in lick. TTS 
pronounces it with the emphasis on the li, which is pronounced as in like.

I know it's a nitpick, but I just wanted to help improve an already very useful 
tool.

Original issue reported on code.google.com by nickb...@gmail.com on 4 Jul 2010 at 3:40

@GoogleCodeExporter
Copy link
Author

We are primarily responsible for the development of the Android platform TTS 
capabilities, not the voice engines.  I would recommend reporting 
mispronunciation issues to the engine developers directly.  Additionally, 
Android 2.2 (Froyo) adds support for substituting TTS engines in the platform 
and Loquendo has developed an impressive solution that is currently available 
for purchase on Market.  I suggest you give their application a try for higher 
fidelity TTS output.

Original comment by caseybur...@google.com on 20 Jul 2010 at 1:50

  • Changed state: Invalid

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

No branches or pull requests

1 participant