public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: ameer armaly <ameer@charter.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Cc: Speakup Distribution List <speakup@speech.braille.uwo.ca>
Subject: Re: Missing something important
Date: Wed, 28 Apr 2004 20:39:12 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0404282035310.775@debian> (raw)
In-Reply-To: <Pine.LNX.4.58.0404281930080.24368@champion.sent.com>

Hey chuck
Speechd.conf should be in /etc/speech-dispatcher, if not,
/usr/local/etc/speech-dispatcher/speechd.conf.
As to putting things together, here's a script to do it all.
This simply requires that you have sftsyn installed; module or builtin
doesn't matter.

#!/bin/sh
#software speech script
#start speech dispatcher
speech-dispatcher
#load speakup softsynth module:
#this requires that we first change to no synth in some cases, so we may
as well to be safe.
echo none >/proc/speakup/synth_name
echo sftsyn >/proc/speakup/synth_name
#start speechd_up
speechd_up

this should at least give you an idea of how things are structured; it's a
bit complex at first (i was planning to leave it until the summer), but
once you get it working it works like a charm.


On Wed, 28 Apr 2004, Chuck Hallenbeck wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I think I am missing something concerning this soft speech stuff.
> What I am missing is something to read! I have everything
> installed and tested, but need to be pointed to a basic
> orientation to how to put the pieces together.
>
> For instance: I guess I need to recompile my kernel with
> everything connected with speakup set as modules, right? At the
> moment I have speakup_ltlk and speakup_sftsyn compiled into the
> kernel, but that evidently will never do for being able to switch
> from one to the other. Where is there something to read about
> that?
>
> For another thing, Jacob and Steven are talking about a
> configuration file called speechd.conf, the first I have heard of
> it! I can't find any such file on my system. Where should I look,
> and more importantly, what can I read? It is not mentioned in any
> of the docs I have read, and none of these software pieces seems
> to have any man pages.
>
> Is there a write-up on software speech with speakup? I am
> suffering from a "having come to the table after the meal has
> begun" syndrome.
>
> Chuck
>
>
> - --
> The Moon is Waxing Gibbous (62% of Full)
> My home page is now at http://www.mhcable.com/~chuckh
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iQCVAwUBQJBAGjVdG8M9x9tGAQI8CwQApnaz5aV667NSNMpUIHgKPbV10LmVgU21
> sUaUDxlr88YoAOiF74MFST3dFkmur/ms6wNduZW6zr8+KyjsuoRc4sWKtlBqXC7E
> ebiS6bAOAJM0h/nC3dutG34TDQ2B4/WTovVXUP5dXR3nAjKB/I3VoBLbehZAWiY9
> VGcBRByRq5g=
> =hvSG
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>


  parent reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Chuck Hallenbeck
 ` Stephen Clower
   ` Chuck Hallenbeck
   ` Jacob Schmude
 ` ameer armaly [this message]
   ` Chuck Hallenbeck
     ` Steve Holmes

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

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

  git send-email \
    --in-reply-to=Pine.LNX.4.58.0404282035310.775@debian \
    --to=ameer@charter.net \
    --cc=speakup@braille.uwo.ca \
    --cc=speakup@speech.braille.uwo.ca \
    /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).