public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Willem van der Walt <wvdwalt@csir.co.za>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: slackware and accessibility packages
Date: Fri, 5 Oct 2007 12:12:19 +0200 (SAST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0710051210290.1583@localhost.localdomain> (raw)
In-Reply-To: <1191578005.28487.19.camel@localhost>

I am not a Slacware user anymore, but I think having packages available 
always makes life
easier even if you know how to roll your own.
I think the one you are missing there is speechd-up.
REgards, Willem

On Fri, 5 Oct 2007, Michael Whapples wrote:

> 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
> 

-- 
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.  MailScanner thanks Transtec Computers for their support.



  reply	other threads:[~ UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Michael Whapples
 ` Willem van der Walt [this message]
 ` Luke Yelavich
 ` Scott Ford
 ` 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=Pine.LNX.4.64.0710051210290.1583@localhost.localdomain \
    --to=wvdwalt@csir.co.za \
    --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).