From: Okash Khawaja <okash.khawaja@gmail.com>
To: covici@ccs.covici.com,
"Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: speakup-r functionality
Date: Sun, 28 May 2017 21:48:56 +0100 [thread overview]
Message-ID: <20170528204856.GA883@sanghar> (raw)
In-Reply-To: <m31sr8ltbe.wl-covici@ccs.covici.com>
On Sun, May 28, 2017 at 02:39:17PM -0400, John Covici wrote:
> Well, find a document such as a text file -- I use emacs for this, but
> I suppose any editor will work -- of course it has to be in a text
> console. Now, make sure the synthesizer supports indexing -- I think
> indexing support was not implemented for all drivers. Now do
> speakup-r and the file should be spoken and when you hit the control
> key the cursor should be where the last word spoken. Currently its a
> number of lines down. Try this with the old speakup with the serial
> workaround patch to hear what it is supposed to b like.
>
> Hope this helps.
Thanks. I don't have a synth that supports indexing. But it looks like
this fix by Dan Carpenter likely addresses the issue:
http://linux-speakup.org/pipermail/speakup/2017-May/060802.html
handle_cursor_read_all() in main.c ultimately calls into
spk_ttyio_in_nowait. If value returned by spk_ttyio_in_nowait() is 0xff
when 0x00 is expectd then sentence count and index count will be
different (higher in this case) than expected.
I have update speakup.tgz to include this fix. If the above explanation
makes sense then please test it when possible.
Okash
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Okash Khawaja
` John Covici
` Okash Khawaja [this message]
` John Covici
` Okash Khawaja
` John Covici
` Okash Khawaja
` John Covici
` Okash Khawaja
` John Covici
` Okash Khawaja
` John Covici
` Okash Khawaja
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=20170528204856.GA883@sanghar \
--to=okash.khawaja@gmail.com \
--cc=covici@ccs.covici.com \
--cc=speakup@linux-speakup.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).