From: jonathan chetwynd <j.chetwynd@btinternet.com>
To: blinux-list@redhat.com
Subject: Re: Emacspeak, flite and handhelds
Date: Mon, 13 May 2002 16:21:05 +0100 [thread overview]
Message-ID: <3CDFD9E1.5060407@btinternet.com> (raw)
In-Reply-To: <E1771TQ-0000iv-00@debian.linux>
in theory it should be possible, and I've been chasing this for about a
year.
One real problem is that emacspeak and emacs are fair sized programs.
I've not yet seen either ported to handhelds, I've heard on excellent
authority that this has been achieved with a 1Gb pcmcia card, I just
don't have one.
I'm currently using an ipaq 3850 with a foldable keyboard.
I've been told that support for mmc/sd cards is currently being written.
This will kind of double the available storage.
64Mb is just not enough.
I'm a teacher of adults with severe learning difficulties, and whilst
they can see, they mostly can't read well.
best wishes
jonathan
http://www.peepo.com
prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
'Georgina'
` Saqib Shaikh
` Mike Gorse
` Arent_Kits_van_Heijningen[106016.3614]
` 'Georgina'
` blinky
` 'Georgina'
` blinky
` Pawel Loba
` blinky
` 'Georgina'
` jonathan chetwynd [this message]
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=3CDFD9E1.5060407@btinternet.com \
--to=j.chetwynd@btinternet.com \
--cc=blinux-list@redhat.com \
/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).