Then we'd better get eSpeak supporting Unicode pronunciation before I can confidently recommend anything besides Emacspeak to younger generations. Otherwise, they’ll turn back to iOS, and Voiceover, which can speak Emoji and such, pretty quickly. I know, I’m not a developer so it probably won’t happen until Reece gets to the bottom of the to do list and gets the strings translated to all 102 languages, but really, it needs doing. I have several ways to get the word out, but if we are to be successful, we can’t have this glaring emission to tell teens/Young adults about, and believe me, they’ll notice. Facebook, Twitter, even chatting programs like Skype, are full of Unicode characters, and its about time our synthesizers, or synthesizer managers, get with the times. -- Sent from Discordia using Gnus for Emacs. Email: r.d.t.prater@xxxxxxxxx Long days and pleasant nights! Linux for blind general discussion <blinux-list@xxxxxxxxxx> writes: > At this point, speech-dispatcher is not designed to be a text > processor, as correct me if I'm wrong, but I do believe it assumes > that supported synthesizers already have built in text processing > capabilities. Any pronunciation handling in either speech-dispatcher > or a screen reader should handle user-defined exceptions only, until > or unless speech-dispatcher becomes a text processing application that > sends raw phonemes to most if not all supported speech synthesizers. > Otherwise, we risk serious pronunciation errors similar to the Speakup > error I noted earlier. Of course, if full text processing is indeed on > the roadmap for speech-dispatcher, then this message may be > disregarded in its entirety. > ~kyle > > _______________________________________________ > Blinux-list mailing list > Blinux-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/blinux-list _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/blinux-list