edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Tyler Spivey <tspivey@pcdesk.net>
To: Patrick Smyth <patricksmyth@fastmail.com>, edbrowse-dev@edbrowse.org
Subject: Re: Cli-focused screen reader
Date: Fri, 9 Sep 2022 12:18:09 -0700	[thread overview]
Message-ID: <789a4e25-e4e0-64e1-b9e1-ace1ca79e522@pcdesk.net> (raw)
In-Reply-To: <87czc4wgl6.fsf@gmail.com>

Try installing the python3-speechd package.

On 9/9/2022 11:25 AM, Patrick Smyth wrote:
> Hi all,
> Apologies if this is a basic or trivial question, but I wanted to ask 
> about setting up screen readers for the command line on Linux. I am 
> using Linux Mint (functionally Ubuntu LTS), and while I can use Orca to 
> read X11 terminals, it's quite slow and annoying to use, and I'd prefer 
> something specific to the terminal. I'm also pretty happy with speakup 
> when I drop out of the graphical interface, so not looking for anything 
> there.
> I've tried a couple command-line specific screen readers, and I've had a 
> lot of trouble getting them to work. The two I've tried recently are 
> tdsr (https://github.com/tspivey/tdsr) and fenrir 
> (https://github.com/chrys87/fenrir). Setting aside Fenrir, since the 
> setup is a lot more involved, when I run tdsr I get the following error
> ModuleNotFoundError: No module named 'speechd'
> I have speech dispatcher installed with aptitude (apt-get install 
> speech-dispatcher). I downloaded the speech dispatcher project from 
> GitHub and tried importing the Python API, but it gives me a circular 
> import issue. Here's the speech dispatcher repo on GitHub, there's a 
> clients folder with a Python library: https://github.com/brailcom/speechd
> If people have gotten speech dispatcher for Python or the tdsr screen 
> reader working, I'd appreciate any guidance. If people are more familiar 
> with fenrir, I can try to articulate where I'm stuck with that, but it's 
> significantly more involved as a setup process. And apologies if 
> edbrowse isn't the place for this kind of question, though it seems 
> fairly likely some of us are using CLI screen readers in this community.
> Thanks, and hope you have a good end of the week!
> Best,
> Patrick

  parent reply	other threads:[~2022-09-09 19:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 18:25 Patrick Smyth
2022-09-09 18:36 ` Serge E. Hallyn
2022-09-09 19:28   ` Adam Thompson
2022-09-09 19:38     ` Serge E. Hallyn
2022-09-09 19:18 ` Tyler Spivey [this message]
2022-09-09 22:22   ` Patrick Smyth
2022-09-14 19:31     ` Patrick Smyth

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:

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

  git send-email \
    --in-reply-to=789a4e25-e4e0-64e1-b9e1-ace1ca79e522@pcdesk.net \
    --to=tspivey@pcdesk.net \
    --cc=edbrowse-dev@edbrowse.org \
    --cc=patricksmyth@fastmail.com \


* 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 NNTP newsgroup(s).