From: Justin Ekis <jekis@ntelos.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: getting orca included in gnome 2.16
Date: Sat, 10 Jun 2006 15:11:39 -0400 [thread overview]
Message-ID: <20060610191139.GA12027@debian> (raw)
In-Reply-To: <20060610162154.GG2259@rednote.net>
On Sat, Jun 10, 2006 at 12:21:54PM -0400, Janina Sajka wrote:
> Are they also prepared to have only one web browser? ONly one media
> player? ONly one word processor? Only one email client application?
If I understand correctly, they are talking about inclusion in the
official gnome.org desktop release. and that is exactly the situation.
epiphany is the web browser, totem is the media player, gedit is the
word processor and evolution is the email application.
Look at ftp.gnome.org/pub/GNOME/desktop/2.14/2.14.2/sources
> The day may come when there is but one screen reader on the GUI desktop,
> but I rather doubt it given that both Gnome and KDE are likely to remain
> with us. However, to proactively restrict inclusion while all manner of
> other (sometimes only half-baked) applications are included rankles.
They said the GNOME desktop. The GNOME desktop release seems to have
exactly one of everything and I doubt any of it is half baked. If it's
not in that directory it's not included in the official desktop.
> Frankly, it's an insult. This kind of grudging support for accessibility needs to be stopped
> right now. In fact, it's a stretch to even call it "support."
>From my reading of the mailing lists, the new version of yelp was
held out of at least one and I think two desktop releases because it
had accessibility regressions. That sounds like support to me.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <447F2C89.8090507@sun.com>
` Janina Sajka
` Justin Ekis [this message]
` Janina Sajka
` Jim Grimsby JR.
[not found] ` <448B16EC.9040300@ubuntu.com>
` Janina Sajka
[not found] ` <20060610193754.GC21840@alchar.org>
` Janina Sajka
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=20060610191139.GA12027@debian \
--to=jekis@ntelos.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).