public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Scott Ford" <w8sef@sbcglobal.net>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@braille.uwo.ca>
Subject: RE: Greetings from Ubuntu
Date: Tue, 3 Oct 2006 13:09:37 -0400	[thread overview]
Message-ID: <000001c6e70e$b554cdb0$6c01a8c0@toshibauser> (raw)
In-Reply-To: <452288B4.3020208@ubuntu.com>

Hello,
	I attempted to run the live cd on a toshiba a55 notbook.  I could
not get ubuntu to boot up.  Would you know how to get it to boot?
 Scott

-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Henrik Nilsen Omma
Sent: Tuesday, October 03, 2006 11:59 AM
To: speakup@braille.uwo.ca
Subject: Greetings from Ubuntu

Hello SpeakUp List!

I've just been make aware of this list, so I'm writing to introduce myself.
I'm Henrik Nilsen Omma, Accessibility Coordinator at Ubuntu.

I see from the archives that there have been some questions about Ubuntu
Edgy, Orca etc. and some misconceptions that I'll try to clear up.

The aim of the Live CD is to provide an environment for exploring the system
and later installing it. This should work independently for both visually
and mobility impaired users. We are just a few bugs away from making it work
smoothly ;) -- but we still have a couple of weeks.

The default Ubuntu installer is written in GTK (as it runs on a Gnome
system). The reason it does not speak to Orca at the moment is that it is
running as root, while Orca runs as a user. We are preparing a fix for this,
but for now you can work around it by running Orca from a root terminal and
then running 'ubiquity' from there as well (the installer).
 The Kubuntu version of the installer is written in QT, but most VI users
would not want to install KDE at this point. Things are looking better for
KDE4 though.

We have also included speakup with our default Edgy kernel, but have not
prepared the required command line scripts for it yet. Any help with testing
speakup in Edgy and preparing such scripts would be great!

About myself: I'm not visually impaired but I do have a mobility impairment.
Of the Linux access tools, I only use sticky keys myself though I do have a
working familiarity with the others. My main role is to encourage,
facilitate and coordinate accessibility development in Ubuntu. I work with
end-users in the forums and mailing lists and with the core developers to
implement features.

Henrik
 

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

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.407 / Virus Database: 268.12.9/457 - Release Date: 9/26/2006
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.407 / Virus Database: 268.12.9/457 - Release Date: 9/26/2006
 



  parent reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Henrik Nilsen Omma
 ` Gabriel Vega
   ` Henrik Nilsen Omma
     ` Gabriel Vega
       ` Henrik Nilsen Omma
 ` Scott Ford [this message]
   ` Henrik Nilsen Omma
 ` Marcel Oats
   ` Henrik Nilsen Omma
     ` Marcel Oats
     ` Marcel Oats

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='000001c6e70e$b554cdb0$6c01a8c0@toshibauser' \
    --to=w8sef@sbcglobal.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).