public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Scott Ford <scotte.ford@gmail.com>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@braille.uwo.ca>
Subject: RE: slackware and accessibility packages
Date: Fri, 5 Oct 2007 07:53:07 -0400	[thread overview]
Message-ID: <000001c80746$4c5a4a70$e50edf50$@us> (raw)
In-Reply-To: <1191578005.28487.19.camel@localhost>

Michael,
	I for one think that the idea is a great one.  I do not have a
hardware synth, and I do not have the knowledge, or interest to do the
technical work required to figure out how to set up a distribution or the
packages up like you describe.  I was introduced to Linux by slackware when
it was on a fist full of floppies.  I would be interested.  
Scott
  -----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Michael Whapples
Sent: Friday, October 05, 2007 5:53 AM
To: speakup@braille.uwo.ca
Subject: slackware and accessibility packages

Hello,
I don't know how much interest this would be, but I am sure you will let
me know. I am thinking of creating slackware packages of some of the
accessibility related tools and any dependencies which are not already
in packaged formats. This would also cover any dependencies for these
packages which are not already available in slackware packages (either
from slackware or some of the alternative repositories). I have
currently made packages for espeak and speech-dispatcher (I have also
done dotconf as this is a dependency for speech-dispatcher).

I am considering starting a project/community for this topic. Aims would
be to create and maintain SlackBuild scripts and packages as described
above, encourage mainstream projects to include accessibility as default
(eg. gnome slacky www.slacky.eu installs orca, gnome-speech as default
when doing a full install, and they have festival in the repository, but
they don't install festival as part of a full install (so orca by
default cannot output speech), I would try and encourage them to alter
this to include festival as part of a full install). Also I would try
and encourage projects to take on packages not currently included at all
and possibly maintain the package for them (eg. neither slackware or
gnome slacky have espeak, speech-dispatcher or speechd-up so there is no
way to use speakup with software synths without compiling software). I
would not intend to try and create a custom distro of slackware, as I
think it is preferrable if the accessibility is there as default,
although I wouldn't rule it out should there be a significant call for
something and it being sufficiently different that a custom distro would
make sense (eg. a slackware install disk with speakup and software
speech support, so an install can be done without a hardware synth).

Any ideas on this? Is there call for this?

From
Michael Whapples


_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup



  parent reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Michael Whapples
 ` Willem van der Walt
 ` Luke Yelavich
 ` Scott Ford [this message]
 ` Steve Holmes
   ` Michael Whapples
 tony seth

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='000001c80746$4c5a4a70$e50edf50$@us' \
    --to=scotte.ford@gmail.com \
    --cc=scott@adaptiveit.us \
    --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).