[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Two suggestions for speechd-el

From: Jan Buchal
Subject: Two suggestions for speechd-el
Date: Tue, 31 Aug 2010 07:38:09 +0200

>>>>> "CB" == Christopher Brannon <cmbrannon79 at gmail.com> writes:

    CB> Cleverson Casarin Uliana <clever92000 at yahoo.com.br> writes:
    >> My second suggestion is about porting speechd-el to MS Windows.
    >> Because it's completely written in Elisp, I think the only
    >> requirement for it to work under Windows is to write a driver for
    >> outputting speech to a Windows-based technology, such as Sapi

    CB> There's a thread about this topic in the archives. Look here,
    CB> for instance:
    CB> http://lists.freebsoft.org/pipermail/speechd/2008q3/001461.html
    CB> I'm not sure whether this guy got Speechd-el up and running on
    CB> Windows, but I think he may have. I knew him from usenet; he was
    CB> brilliant. Unfortunately, he passed away at age 23. He tried
    CB> several different approaches. 1. Run an SSIP server on Windows.
    CB> An implementation does exist for that platform. 2. Run Speech
    CB> Dispatcher on a Linux laptop, and tell the local Speechd-el to
    CB> communicate with the remote instance of Speech Dispatcher. 3.
    CB> Run Speech Dispatcher under Linux, inside of a virtual machine.
    CB> Again, Speechd-el needs to communicate with a server on a
    CB> different host. Options 2 and 3 are going to be more difficult
    CB> to experiment with nowadays, because by default, Speech
    CB> Dispatcher and Speechd-el use Unix-domain sockets for
    CB> communication, rather than TCP sockets. I'm not certain whether
    CB> it is possible to make the current version of Speechd-el use
    CB> TCP; I haven't tried.
If I know the TCP communication in speechd-el still works. The best
sollution will be make done the new implementation of Speech Dispatcher
based on python but it is of course much bigger task.

Jan Buchal
Tel: +420242486008
Mob: +420608023021

reply via email to

[Prev in Thread] Current Thread [Next in Thread]