From: Willem van der Walt <wvdwalt@csir.co.za>
To: Henrik Nilsen Omma <henrik@ubuntu.com>
Cc: speakup@braille.uwo.ca
Subject: Re: Feisty SpeakUp
Date: Fri, 27 Oct 2006 17:09:26 +0200 (SAST) [thread overview]
Message-ID: <Pine.LNX.4.64.0610271706450.21289@localhost.localdomain> (raw)
In-Reply-To: <4542121A.4040006@ubuntu.com>
Adding speakup so that it talks out of the vertual box would be good.
For a live cd, I would suggest espeak as the synth because of its small
size.
See www.oralux.org
You might save some work may be.
On Fri, 27 Oct 2006, Henrik Nilsen Omma wrote:
> Hello,
>
> I'd like to ask for some input on a spec I'm doing for the next version
> of Ubuntu. We currently have speakup in the kernel but it's very far
> from Just Works. See:
> https://wiki.ubuntu.com/Accessibility/Specs/FeistySpeakup
>
> I guess I first have to ask what the common use cases are. Is speakup
> largely used by system admins and developers working from the CLI? Is it
> valuable to have a Live CD that boots to the CLI with speakup? We
> currently don't have CLI Live CD AFAIK.
>
> The possible areas I could imagine improving usability are:
>
> * Server edition -- Currently has the speakup module, but not simple
> way to install or run live
> * The debian installer -- currently used on the alternate and server CDs
> * spoken boot -- have all the boot messages read out as you boot
> * Standard CLI, simple launch -- For those who prefer gnome it may be
> difficult to recover when X fails. It should be trivial to launch
> speakup in such cases: 'start-speakup'. An introduction with basic
> operating instructions should be read out.
> * anything else?
>
>
> Another point I want to emphasise is that if we do this it would be in
> the main Ubuntu distribution, not a special derivative. It is not just
> intended for advanced computer users, but beginners as well. The
> features should then also get picked up by Kubuntu, Edubuntu, Mephis, etc.
>
>
> Henrik
>
> _______________________________________________
> 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 and
e-mail legal notice. Views expressed herein do not necessarily represent the
views of the CSIR.
CSIR E-mail Legal Notice
http://mail.csir.co.za/CSIR_eMail_Legal_Notice.html
CSIR Copyright, Terms and Conditions
http://mail.csir.co.za/CSIR_Copyright.html
For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR
Legal Notice send a blank message with REQUEST LEGAL in the subject line to
CallCentre@csir.co.za.
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.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Henrik Nilsen Omma
` Willem van der Walt [this message]
` Gene Collins
` Scott Ford
` John Heim
` Henrik Nilsen Omma
` Marcel Oats
feisty speakup Jude DaShiell
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.0610271706450.21289@localhost.localdomain \
--to=wvdwalt@csir.co.za \
--cc=henrik@ubuntu.com \
--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).