From: Luke Yelavich <themuso@themuso.com>
To: speakup@braille.uwo.ca
Subject: Re: An idea,
Date: Tue, 26 Jul 2005 17:14:49 +1000 [thread overview]
Message-ID: <20050726071449.GA18192@localhost.localdomain> (raw)
In-Reply-To: <584DE893B0E08F4B9748E295029F1E97022AEB19@maya.aztec.soft.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, Jul 26, 2005 at 05:03:26PM EST, Murthy T S N wrote:
> Hi all,
> I am following this list and all topics are very much required.
> Now my question is
> Can we make an effort to support either gnome or kde using speakup?
> Please share your ideas in this regard.
Not without a great deal of work. As it is, GNOME and KDE have their own
screen readers, of which GNOME's is more advanced at this point in time.
It is unable to use all the speech synthesizers that speakup supports,
but this could change in the future.
- --
Luke Yelavich
GPG key: 0xD06320CE
(http://www.themuso.com/themuso-gpg-key.txt)
Email & MSN: themuso@themuso.com
ICQ: 18444344
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC5eLpjVefwtBjIM4RAmfIAKDkePHUe3eBJkhNNgqF4tb5RMHaLgCg6r9V
9vSy17pdVemSxE3DbDY46aY=
=aoiY
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
Murthy T S N
` Luke Yelavich [this message]
` Willem van der Walt
` Re[2]: " Farhan
` Gregory Nowak
` Sean McMahon
` shuttle coverage Igor Gueths
` An idea, Lorenzo Taylor
` Kenny Hitt
` Kelly Prescott
` John covici
` Sergei V. Fleytin
` Janina Sajka
` Kelly Prescott
` hank smith
` John covici
` Janina Sajka
` Scott Berry
` Luke Yelavich
` remapping keys in Gnopernicus was " Kenny Hitt
` Farhan
` Kenny Hitt
` Janina Sajka
` Sean McMahon
` Sean McMahon
` Laura Eaves
` Sean McMahon
` Chris Norman
` Chris Norman
` Kenny Hitt
` Sean McMahon
Sina Bahram
Laura Eaves
` Sina Bahram
` Laura Eaves
` Sina Bahram
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=20050726071449.GA18192@localhost.localdomain \
--to=themuso@themuso.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).