{"id":1339,"date":"2015-12-01T07:15:48","date_gmt":"2015-12-01T15:15:48","guid":{"rendered":"https:\/\/abilitytools.org\/blog\/?p=1339"},"modified":"2015-11-30T15:14:34","modified_gmt":"2015-11-30T23:14:34","slug":"making-your-android-device-aac-multi-lingual","status":"publish","type":"post","link":"https:\/\/abilitytools.org\/blog\/making-your-android-device-aac-multi-lingual\/","title":{"rendered":"Making your Android Device AAC Multi-Lingual"},"content":{"rendered":"<pre>by Chi Hung Luke Hsieh, Assistive Technology Advocate at Community Access Center<\/pre>\n<p>&nbsp;<\/p>\n<p><a href=\"https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/Screenshot_2015-10-07-10-36-40.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft wp-image-1344 \" src=\"https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/Screenshot_2015-10-07-10-36-40.png\" alt=\"Screenshot of phone showing apps google text to speech, and IVONA text to speech, also says speech rate and listen to an example and default language status is English\" width=\"373\" height=\"663\" srcset=\"https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/Screenshot_2015-10-07-10-36-40.png 720w, https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/Screenshot_2015-10-07-10-36-40-168x300.png 168w, https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/Screenshot_2015-10-07-10-36-40-576x1024.png 576w\" sizes=\"auto, (max-width: 373px) 100vw, 373px\" \/><\/a><\/p>\n<p>Due to my moderately severe speech disability, I have been paying close attention to the development of Augmented Assistive Communication (AAC) devices\/apps and Text to Speech Technology or Voice Engines.<\/p>\n<p style=\"text-align: justify;\">Those who have paying attention to my previous articles over the years may note that, as far as Text To Speech Voice Engines go, I swear by<a href=\"https:\/\/www.ivona.com\/\"> IVONA<\/a>, a Polish software company that was acquired by Amazon in 2012. And, as far as reproducing human-like quality speech goes, IVONA Voice Engine is still second to none in my opinion.\u00a0 However, while it does offer 23 high-quality European languages, the conspicuous absence of Asian Languages -even the major ones like Chinese Mandarin, Hindi, Japanese, Vietnamese and Korean- has left something to be desired. This is why, if one wants one\u2019s AAC app to speak Asian languages, one has to turn to <a href=\"https:\/\/play.google.com\/store\/apps\/details?id=com.google.android.tts&amp;hl=en\">Google TTS<\/a>.<\/p>\n<p>Most of you linguistic enthusiasts have probably already encountered Google Text to Speech Engine from Google Translation app and web services.\u00a0 And, most likely the first thing you may have noticed is the copious number of languages on the offer.\u00a0 Many of them come with a Speech Engine, and once Google (Alphabet) made Google TTS downloadable to individual Android Devices, Multi-Lingual AAC becomes simply a matter of matching keyboards with corresponding voice engines.<\/p>\n<p>My favorite third party keyboard for this particular purpose is <a href=\"https:\/\/play.google.com\/store\/apps\/details?id=com.nuance.swype.trial&amp;hl=en\">Swype by Nuance<\/a> because, like Google, it offers a copious selection of languages.<\/p>\n<p>Here are some more screenshots from my phone: The device is an LG G Flex (first generation), the AAC App is <a href=\"https:\/\/play.google.com\/store\/apps\/details?id=nl.asoft.speechassistant&amp;hl=en\">Speech Assistant<\/a> by ASoft.nl, and the third party keyboard is Swype.<\/p>\n<p><a href=\"https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/chinese.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft  wp-image-1341\" src=\"https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/chinese.png\" alt=\"chinese\" width=\"267\" height=\"475\" srcset=\"https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/chinese.png 720w, https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/chinese-168x300.png 168w, https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/chinese-576x1024.png 576w\" sizes=\"auto, (max-width: 267px) 100vw, 267px\" \/><\/a> <a href=\"https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/chinese2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft  wp-image-1342\" src=\"https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/chinese2.png\" alt=\"chinese2\" width=\"271\" height=\"482\" srcset=\"https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/chinese2.png 720w, https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/chinese2-168x300.png 168w, https:\/\/abilitytools.org\/blog\/wp-content\/uploads\/2015\/11\/chinese2-576x1024.png 576w\" sizes=\"auto, (max-width: 271px) 100vw, 271px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>by Chi Hung Luke Hsieh, Assistive Technology Advocate at Community Access Center &nbsp; Due to my moderately severe speech disability, I have been paying close attention to the development of Augmented Assistive Communication (AAC) devices\/apps and Text to Speech Technology or Voice Engines. Those who have paying attention to my previous articles over the years&hellip;<\/p>\n","protected":false},"author":2,"featured_media":1344,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[50],"tags":[8,2,7,19,17,5,31,77,15,45,30,76],"class_list":["post-1339","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aac","tag-apps-and-software","tag-at-network","tag-at-professional","tag-communication","tag-computer","tag-independence","tag-keyboard","tag-recreation","tag-social-media","tag-success-story","tag-swype","tag-technology"],"_links":{"self":[{"href":"https:\/\/abilitytools.org\/blog\/wp-json\/wp\/v2\/posts\/1339","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/abilitytools.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/abilitytools.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/abilitytools.org\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/abilitytools.org\/blog\/wp-json\/wp\/v2\/comments?post=1339"}],"version-history":[{"count":6,"href":"https:\/\/abilitytools.org\/blog\/wp-json\/wp\/v2\/posts\/1339\/revisions"}],"predecessor-version":[{"id":1349,"href":"https:\/\/abilitytools.org\/blog\/wp-json\/wp\/v2\/posts\/1339\/revisions\/1349"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/abilitytools.org\/blog\/wp-json\/wp\/v2\/media\/1344"}],"wp:attachment":[{"href":"https:\/\/abilitytools.org\/blog\/wp-json\/wp\/v2\/media?parent=1339"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/abilitytools.org\/blog\/wp-json\/wp\/v2\/categories?post=1339"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/abilitytools.org\/blog\/wp-json\/wp\/v2\/tags?post=1339"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}