From: Cheryl Homiak <chomiak@charter.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Integrating Speakup/ESpeakup into Debian boot process
Date: Tue, 7 Apr 2009 21:20:04 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0904072114360.26930@maranatha> (raw)
In-Reply-To: <20090408014939.GA16100@clearwire.net>
Well, I can see how you might have debian accessibility issues for other
reasons, but as far as using espeakup, as has been mentioned in other
posts, it's really quite straightforward. Espeakup came up automatically
as soon as I put the line for the soft module into /etc/modules. Orca is
also working well for me and it worked "out of the box" without a lot of
troubleshooting. The only thing i have to watch with debian
unstable is that I don't let an upgrade remove something important, so
sometimes I have to delay an upgrade. Other than that, I plan to continue
with debian at least for now. But distribution choices are a really
individual thing so I certainly can understand your point of view.
--
Cheryl
"Where your treasure is, there will your heart be also."
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
Jason White
` Daniel Dalton
` Cheryl Homiak
` Daniel Dalton
` Samuel Thibault
` Samuel Thibault
` Gaijin
` Cheryl Homiak [this message]
` Jason White
` Daniel Dalton
` Samuel Thibault
` Daniel Dalton
` Chuck Hallenbeck
` Gaijin
` Samuel Thibault
` Gregory Nowak
` Integrating Speakup/ESpeakup into Debian boot process, part 2 Gregory Nowak
` Gaijin
` William Hubbs
` Gaijin
` Integrating Speakup/ESpeakup into Debian boot process Daniel Dalton
` debian gripes, accessibility, and labels, was: " Gregory Nowak
` Daniel Dalton
` debian gripes, accessibility, and labels, was: Re: IntegratingSpeakup/ESpeakup " Juan Hernandez
` Georgina Joyce
` Integrating Speakup/ESpeakup " Kerry Hoath
` Michael Whapples
` Samuel Thibault
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=alpine.DEB.2.00.0904072114360.26930@maranatha \
--to=chomiak@charter.net \
--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).