[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190316102202.py3qczl3g4fw3myn@function>
Date: Sat, 16 Mar 2019 11:22:02 +0100
From: Samuel Thibault <samuel.thibault@...-lyon.org>
To: Chris Brannon <chris@...-brannons.com>, deedra@...-brannons.com,
Okash Khawaja <okash.khawaja@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
speakup@...ux-speakup.org, devel@...verdev.osuosl.org,
William Hubbs <w.d.hubbs@...il.com>,
Kirk Reiser <kirk@...sers.ca>, linux-kernel@...r.kernel.org
Subject: Re: Staging status of speakup
Hello,
Please keep the lists in Cc, so that not only I have the information
(in particular since I will probably *not* have the time to investigate
myself).
Samuel Thibault, le sam. 16 mars 2019 10:35:43 +0100, a ecrit:
> The problem is that neither Okash nor I are even casual users of
> speakup, so we need a walk-through of the kind of operation that
> produces the issue.
deedra Waters <deedra@...-brannons.com> wrote:
> it's dead simple
For a user, perhaps, but again, neither Okash or I are actual users of
speakup, so we have just no idea what casual use is.
> just lead the screenreader read large blocks of text i guarantee it's
> reproduceable.
Which shortcut do you use to make the screen reader read it? What is
"large"? Is that only one 80x25 complete output screen? Is that cat-ing
a long text? How is it garbled: is that right from the beginning of the
text? or at some point during it? or is that just a piece of it and then
it's Ok again?
Samuel
Powered by blists - more mailing lists