From: Mario Lang <mlang@teleweb.at>
To: blinux-list@redhat.com
Subject: Status report
Date: Wed, 03 Jul 2002 16:33:58 +0200 [thread overview]
Message-ID: <87fzz06fu1.fsf@lexx.delysid.org> (raw)
Hey listers.
I just felt like sending a mail to the community again.
Here are some random infos I want to get across to you:
1. #blinux is alive!
On irc.openprojects.net, the #blinux has some visitors from
time to time. Right now I'm talking with sebfrance there about their
brlspeak distribution. vortex (author of eflite) also
used to hang out there. If you feel like
asking questions, or talking about linux for the blind,
visit us there.
2. eflite in debian unstable.
I'm not sure if I announced this here before, but
eflite is now available as binary package in debian unstable
(codename sid). Only missing part is to patch up the
emacspeak configuration script to offer eflite as an
configuration option, but this is stalled due
to some reasons right now. Mainly because eflite
doesn't implement the lisp-level of functions a speech server
would need to provide, and emacspeak configuration depends on
those files being present (iirc).
3. brltty is in debian:
This is very very old news,
but in case you didn't notice, debian unstable/testing both
have some version of brltty (2.98.5). A debconf
interface is provided, so you can in theory easily select
your device name, driver type and translation table. This should
be quite easy to do, in case you are using a sighted person
to get things going.
Feedback, tips, patches always welcome!
P.S.: What is all this debian fuss about? This year I decided it
would be worth the effort to participate in this project. see
<url:http://nm.debian.org/nmstatus.php?email=mlang%40delysid.org> for
details.
--
CYa,
Mario
reply other threads:[~ UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87fzz06fu1.fsf@lexx.delysid.org \
--to=mlang@teleweb.at \
--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).