From: Charles Crawford <ccrawford@acb.org>
To: speakup@braille.uwo.ca
Subject: Re: text editing with speakup
Date: Thu, 19 Jun 2003 06:00:02 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0306190559170.1427-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0306172039360.978-100000@Champion.novocon.net>
Seems to me the problem is that the Linux text editors all use silly
commands while WordPerfect has a well thought out and easy system of
navigation and commands.
On Tue, 17 Jun 2003, Chuck Hallenbeck wrote:
> Seems to me that Word Perfect for Linux, if it existed, would
> have the same problem that all proprietary software has: i.e., it
> uses a proprietary format that assumes the availability of Word
> Perfect for anyone wishing to work with the document. I know you
> can make plain text files with WP, but why bother to use WP if
> you want to make plain text files? What are the advantages of
> Word Perfect for Linux that would be worth the limitations of a
> proprietary file format?
>
> Or am I missing something?
>
>
> On Tue, 17 Jun 2003, jude dashiell wrote:
>
> > Only version of that I've ever run into came on infomagic disks and would
> > need gnome or kde or some other form of x to run it. It's for that reason
> > I'd not use wp under Linux or even have it take up disk space here.
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
--
-- Charlie Crawford
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
Joseph C. Lininger
` Alex Snow
` Thomas Stivers
` Charles Crawford
` Alex Snow
` jude dashiell
` Chuck Hallenbeck
` White, Matt
` Charles Crawford
` Janina Sajka
` jude dashiell
` Charles Crawford [this message]
` Chuck Hallenbeck
` White, Matt
[not found] ` <Pine.LNX.4.44.0306190611290.678-100000@Champion.novocon.ne t>
` Charles Crawford
` Luke Davis
` Janina Sajka
` jude dashiell
` White, Matt
` Steve Holmes
` Alex Snow
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.0306190559170.1427-100000@localhost.localdomain \
--to=ccrawford@acb.org \
--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).