Closed rhdunn closed 11 years ago
We already have issues #5 and #25 having something to do with language and locale mapping between Android and eSpeak. Even while running on an Android 4+ device there are some eSpeak voices without a proper pair from the android locale however what is new for me bulgarian voice is listed twice.
The locale related issues are #3 (Manderin vs Cantonese), #5 (Add the new languages) and #26 (Country-Variant broken on API level 8). Those are specific issues I have noticed with the current implementation to keep track of them.
This issue is about adding a test framework to verify the locale handling is working as expected. This is separate from fixing the locale issues mentioned above. It is about having a way to verify that:
1/ the TTS engine can be installed and properly queried (see issue #27); 2/ the TTS functions as expected (specifically w.r.t. locales).
Once this is in place, the other issues can be fixed by adding test cases to the tests added here.
I prefer to keep each issue as focused as possible as they are then easy to reproduce, fix and verify.
A core set of locale tests has now been added. Future locale-related tests will be added as part of the corresponding defects.
There are various issues with the current locale mappings in the android port of espeak. Also, there are two codepaths -- one for 2.2 - 3.x and another for 4.x.
To ensure that the implementations behave consistently, work as expected and avoid future regressions, a set of tests is needed to verify the behaviour.