From: Thomas Ward <slingshooter@valkyrie.net>
To: speakup@braille.uwo.ca
Subject: Re: word documents
Date: Mon, 17 Mar 2003 03:40:08 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0303170317060.6653-100000@localhost.localdomain> (raw)
In-Reply-To: <20030317062559.19403.13142.Mailman@speech.braille.uwo.ca>
Hi, Dannie. Well, in theory we can use Star Office 6.0 or Open Office
1.0 for Linux, but Star
Office accessability is still in it's infancy.
For you and everyone else who is interested in X-windows accessability and
Star Office 6 accessability I'll outline what I know, what current state
is, and and where this is going.
First, you'll need an updated distribution of Linux that will have the
Gnome 2.2 desktop, or update your Linux system, libraries, etc to gnome
2.2. I know for a fact that Red Hat 8.1 and Mandrake 9.1 will be shipping
sometime this spring with Gnome 2.2.
After obtaining Gnome 2.2 you will need to check out gnome common,
gnome-speech libraries, and gnopernicus from cvs, and build them. This
often the most frustrating step.
If you are using Star office 6 you will need the Java virtual machine in
jre 1.4 or better, install it, and then install the Java accessability
bridge for Linux.
At last you will need to install Star Office 6. Fortunately, I did not
have to buy it because it ships with Mandrake Linux Delux already.
After all this accessability wasn't all that fantastic, or anything I
could write home about. However, future versions may improve as
development continues. I assume since Sun is pushing the development of
gnopernicus, and are also the creators of Star office accessability will
improve over time, and when they have more time to deal on specific
applications and not have to worry about the core which is still under
development.
I will also inform everyone here that this information is a couple of
months old. I haven't been able to get the vary latest gnopernicus
compiled yet, and I have not updated the java access, etc.
I'm waiting for Mandrake 9.1 to be released before I attempt to upgrade
gnopernicus, the java access, etc.
next parent reply other threads:[~ UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030317062559.19403.13142.Mailman@speech.braille.uwo.ca>
` Thomas Ward [this message]
[not found] <20030316235502.7926.4073.Mailman@speech.braille.uwo.ca>
` Thomas Ward
Jude DaShiell
` Chuck Hallenbeck
-- strict thread matches above, loose matches on Subject: below --
Joseph C. Lininger
` Aaron Howell
` Dave Hunt
` Igor Gueths
` Dave Hunt
` Charles Crawford
` Jude DaShiell
` Janina Sajka
` Kenny Hitt
` ccrawford
` Kenny Hitt
` Erik Heil
` William F. Acker WB2FLW +1-303-722-7209
` ccrawford
` Joseph C. Lininger
` Danny Crone
` Ann Parsons
` Jude DaShiell
` Ann Parsons
` Charles Crawford
` Ann Parsons
[not found] ` <Pine.LNX.4.33.0303160909310.714-100000@athame.gmpexpress.n et>
` Charles Crawford
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.44.0303170317060.6653-100000@localhost.localdomain \
--to=slingshooter@valkyrie.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).