Path: utzoo!mnetor!uunet!husc6!rutgers!iuvax!pur-ee!uiucdcs!uxc.cso.uiuc.edu!uxe.cso.uiuc.edu!swofford From: swofford@uxe.cso.uiuc.edu Newsgroups: comp.sys.mac Subject: Re: phonetic code wanted Message-ID: <46100037@uxe.cso.uiuc.edu> Date: 13 Dec 87 17:27:00 GMT References: <174400088@uxc.cso.uiuc.edu> Lines: 36 Nf-ID: #R:uxc.cso.uiuc.edu:174400088:uxe.cso.uiuc.edu:46100037:000:2273 Nf-From: uxe.cso.uiuc.edu!swofford Dec 13 11:27:00 1987 dorner@uxc.cso.uiuc.edu(Steve Dorner) writes in comp.sys.mac >Does anyone out there have code for turning text into phonetics? >Either code that takes a word and turns it into a string of specially >defined phonetics (ala Speechlab) or that makes a kind of hash code for >sound out of it (ala WriteNow's spelling checker) would be nice. > >I say ``code'' rather than ``algorithm'', because I suspect a lot of >the work would be in developing letter combination->sound tables. > >I'm looking for this because I'm developing an online phonebook, and >would like to be able to say ``sounds like'' when requesting a name. >(After that, I can add full charades support :-)) If memory serves me correctly, and I unfortunately don't have the docs with me now, there is a Macintalk routine which will automatically do that for you. All you do is pass a handle (or pointer) to some text and it returns a handle (or pointer) to the equivalent phonetic text. This is how SpeechLab does it, and I would assume any similiar program which uses MacinTalk since you can then pass the phonetic text to Macintalk and have it spoken. I will try to look up the exact routine specs later and get back to you. +--------------------------------------------------------------------------+ + | + + Leonard Rosenthol | USnail: 205 E. Healey #33 + + Halevai Software | Champaign, Il 61820 + + GEnie: MACgician | + + ARPA: swofford@uxe.cso.uiuc.edu | Bitnet: 3FLOSDQ@UIUCNOSA.BITNET + + | + +--------------------------------------------------------------------------+ + Disclaimer #1: Since I own the company, I can say whatever I want, and + + not be responsible for it! + + + + Disclaimer #2: Anything I say may be construed as being under the + + jurisdiction of Disclaimer #1 + +--------------------------------------------------------------------------+