From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (qmail 22622 invoked from network); 6 Dec 1998 15:09:40 -0000 Received: from mail.redhat.com (199.183.24.239) by lists.redhat.com with SMTP; 6 Dec 1998 15:09:40 -0000 Received: from mail.spin.ch (mail.spin.ch [194.209.46.6]) by mail.redhat.com (8.8.7/8.8.7) with ESMTP id KAA21298 for ; Sun, 6 Dec 1998 10:04:47 -0500 Received: from localhost (tpo2@localhost) by mail.spin.ch (8.9.1a/8.9.1/Debian/GNU) with SMTP id QAA14644; Sun, 6 Dec 1998 16:04:35 +0100 Date: Sun, 6 Dec 1998 16:04:35 +0100 (CET) From: "T.Pospisek's MailLists" Reply-To: "T.Pospisek's MailLists" To: blinux-list@redhat.com cc: ac1164@messiah.edu Subject: Re: Concerning BLinux project In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Id: On Sun, 6 Dec 1998, Hans Zoebelein wrote: > Wha about these CX interface libs? I don't really get the importance of those. > ---------- Forwarded message ---------- > Date: Sat, 5 Dec 1998 08:28:34 -0500 (EST) > From: Corbin > To: zocki@goldfish.cube.net > Cc: aaron corbin > Subject: Concerning BLinux project > > Hi, I'm a senior computer science major at Messiah College. I'm in the > stages of trying to find a senior project. If I could write something > that would contribute to the BLinux project, that would be great. But I > don't really know what to write (I just found the website two days ago), > and not being blind, I don't even know what would be really > useful. Is there anything you could think of that *needs* to be written, > and (sadly) is novel enough that I could use it as a senior project? Are > you the right person to be asking this? Should I ask someone else? Hi Aaron, your email has been forwarded to the blinux mailing list by Hans. Here's my opinion on the topic: The goal of the blinux project is the availability of a linux system that can be perfectly used >without< the need to see. In the process of trying to set up such a system I have come accross the problem, that there are far too many different parts around that >don't fit together<. You've got a speech output system for emacs called emacspeak. For this you have drivers for braille terminals, for speech cards and for software synthesisers. There are screen-reader packages which themselves need yet other drivers. There are kernel patches which enable feedback through speech and/or braille which use still other drivers. In short: it's a mess. Peoples efforts are lost becase they go on reinventing the wheel (interfaces/drivers/interpreters) again and again. What I feel is >>badly<< needed is an effort to see through the available work, get a picture of what's around, have a look at research and existing development (Java's speech interface, Microsoft's, the Freespeech interface, etc.) and propose: - a simple and generic text to speech/braille interface I have hints on this list, that there might be something like that in on the way (at least the seeds of it). See for example Roger Buthenut's recent postings on this list. The interface >>really<< needs to be generic enough to be able to adapt to a broad range of applications and to be to easily accomodate ports of existing drivers, so it should be done with thought and consideration of the research and work that's around. I think this could be a very rewarding work. My 2c. * t ------------------------------------------------------------------------------ Tomas Pospisek - Freelance: Linuxing, Networking http://spin.ch/~tpo/freelance www.SPIN.ch - Internet Services in Graubuenden/Switzerland ------------------------------------------------------------------------------