unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: EMacspeak Windows
Date: Fri, 30 Mar 2007 13:03:50 +1000	[thread overview]
Message-ID: <87k5wz3015.fsf@lion.rapttech.com.au> (raw)
In-Reply-To: mailman.1561.1175131675.7795.help-gnu-emacs@gnu.org

"Wilfred Zegwaard (privé)" <wilfred.zegwaard@home.nl> writes:

> Hi,
>
> Is there anyone who can help me to let EMacspeak run on a Windows machine?
>
> Thanks,
>

It is non-trivial to get emacspeak to run on a windows platform. The first
problem you will have is the TTS driver code. This is written in Tcl. So, you
will either have to install Tcl for Windows (and I don't know anything about
Tcl for windows) or re-write the Tcl code using another scripting language. How
difficult this would be depends on the TTS engine you plan to use. If its a
hardware synthesiser connected to a serial port etc, it probably wouldn't be
that hard. However, if its a software synthesiser, it cold be more difficult if
you want to embed the synthesiser into the driver code (which is how the
current Tcl drivers work for some of the software synths, like IBM's ViaVoice). 

If you are able to get Tcl working for windows, you will probably have to
modify the code to cater for platform differences in things like directory path
seperators, device names etc. One nice thing about Tcl is that it is possibly
the easiest language to link with a C/C++ library (i.e. for the software speech
synth). I briefly had a look at doing the same with Perl, but ran into quite a
few problems because the automated header generation didn't like the C code in
the library I was trying to link with. 

There was an emacspeak driver written in C as an experiment some years back, so
you could write one in C, C# or even Java, but you will need good (fast)
regular expression library. The driver code (i.e. Tcl library and scripts) is
pretty straight forward and it wouldn't e too difficult to translate that to
another language. Emacs communicates with the driver via stdout/stdin, so there
are no real complications there. 

In summary, theoretically, it can be done, but you need to come up with new TTS
drivers and whatever language you choose, it will need regular expression
support and possibly the ability to link with C and C++ TTS libraries or use
their APIs. 

There is an emacspeak mailing list at emacspeak@cs.vassar.edu 

HTH

Tim

 
-- 
tcross (at) rapttech dot com dot au

  parent reply	other threads:[~2007-03-30  3:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1487.1174994711.7795.help-gnu-emacs@gnu.org>
2007-03-28 13:18 ` Compile mode in emacs!! Ken Goldman
2007-03-29  0:30 ` "Wilfred Zegwaard (privé)"
2007-03-29  1:25 ` EMacspeak Windows "Wilfred Zegwaard (privé)"
     [not found] ` <mailman.1561.1175131675.7795.help-gnu-emacs@gnu.org>
2007-03-30  3:03   ` Tim X [this message]
2007-03-30 20:19   ` "Wilfred Zegwaard (privé)"
2013-11-02 15:54 Emacspeak Windows Jarek Czekalski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k5wz3015.fsf@lion.rapttech.com.au \
    --to=timx@nospam.dev.null \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).