public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Michael Whapples <mikster4@msn.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Orca speech-dispatcher back-end, was Re: Espeak, gnome-speech and alsa
Date: Wed, 21 Feb 2007 13:03:57 +0000	[thread overview]
Message-ID: <BAY103-DAV323255DD50676DFF4C9A38E880@phx.gbl> (raw)
Message-ID: <1172063037.7187.34.camel@layla> (raw)
In-Reply-To: <1172062801.7187.32.camel@layla>

I am slightly unsure exactly myself what the problems were (as I said it
> was sometime ago so can't remember fully), I just remember that at the
> time the gnome-speech speech-dispatcher driver worked better (on my
> computers it didn't seem to have any noticable lag that way, compared
> with the orca speech-dispatcher back-end).
> 
> I will see sometime soon if I still get the problems I was having with
> the orca speech-dispatcher back-end, unless it is going to be added to
> orca within a couple of weeks (as that will help when updating orca as
> it won't need to be added everytime I update).
> 
> From
> Michael Whapples
> On Mon, 2007-02-19 at 19:13 +0100, Tomas Cerha wrote:
> > Michael Whapples wrote:
> > > Some time ago, I did try the speech-dispatcher back-end for orca, but didn't 
> > > continue to use it as I remember that there were some issues with it knowing 
> > > when the speech had finished and sometimes missing parts of speech.
> > 
> > Any more details on this would be greatly appreciated.  Part of it might
> > have already been solved, since the backend now supports speech progress
> > notifications.  Anyway, I'm not sure I understand what you mean.  Could
> > you please give an example for each problem?  Thank you very much for
> > your answer.
> > 
> > > Also whenever I do an update I would need to re-apply the back-end
> > 
> > This will change soon, since the Speech Dispatcher backend will be
> > included in Orca (in a few weeks).
> > 
> > Best regards, Tomas.
> > 
> > 




  parent reply	other threads:[~ UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Michael Whapples
 ` Jonathan Duddington
 ` O.T. ESpeak Windows version doesn't work David Harvey
   ` Jonathan Duddington
     ` David Harvey
       ` Jonathan Duddington
         ` David Harvey
           ` Jonathan Duddington
             ` David Harvey
               ` Jonathan Duddington
               ` Michael Whapples
 ` Espeak, gnome-speech and alsa Michael Whapples
 ` Tomas Cerha
   ` Michael Whapples
     ` Tomas Cerha
     [not found]       ` <1172062801.7187.32.camel@layla>
     [not found]         ` <1172063037.7187.34.camel@layla>
           ` Michael Whapples [this message]
 ` Michael Whapples

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=BAY103-DAV323255DD50676DFF4C9A38E880@phx.gbl \
    --to=mikster4@msn.com \
    --cc=speakup@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).