From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from dsl092-170-084.wdc2.dsl.speakeasy.net ([66.92.170.84] helo=concerto.rednote.net) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1CPJa0-000501-00 for ; Wed, 03 Nov 2004 06:45:32 -0500 Received: from concerto.rednote.net (localhost.localdomain [127.0.0.1]) by concerto.rednote.net (8.13.1/8.12.11) with ESMTP id iA3BifhY007521 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Nov 2004 06:44:41 -0500 Received: (from janina@localhost) by concerto.rednote.net (8.13.1/8.13.1/Submit) id iA3Biffi007520; Wed, 3 Nov 2004 06:44:41 -0500 Date: Wed, 3 Nov 2004 06:44:41 -0500 From: Janina Sajka To: Sean McMahon , "Speakup is a screen review system for Linux." Message-ID: <20041103114441.GK6259@rednote.net> References: <20041101213931.GA30821@bruzos> <20041102131826.GD6259@rednote.net> <002c01c4c104$92ca54e0$77ac7682@azwaterDOM.wr.usgs.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <002c01c4c104$92ca54e0$77ac7682@azwaterDOM.wr.usgs.gov> User-Agent: Mutt/1.4.1i X-Operating-System: Linux concerto.rednote.net 2.6.9-1.649spksmp Organization: Capital Accessibility LLC (http://www.CapitalAccessibility.com) X-PGP-Key: http://www.CapitalAccessibility.com/JaninaSajka_gpg_key.html Cc: Subject: Re: writing spk howto (?) X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Nov 2004 11:45:37 -0000 Precisely. And Kirk is the boss. Sean McMahon writes: > While we're on the subject of writing howtos, is there some process for getting > these things on the speakup site? Is there a general cvs project or aria for > documentation of speakup? > Sean > ----- Original Message ----- > From: "Janina Sajka" > To: ; "Speakup is a screen review system for Linux." > > Sent: Tuesday, November 02, 2004 6:18 AM > Subject: Re: writing spk howto (?) > > > > Absolutely, you should do a Speakup with Software Speech HOWTO. The > > community needs one desparately, and there aren't enough of us document > > writers to go around. > > > > In all honesty, I must tell you that writing a clear, concise, and > > complete HOWTO is hard work. I don't say this to discourage you, but to > > point out that there's a reason why more HOWTOs aren't just out there to > > be plucked off the net. My advice is to start simple, and Speakup With > > Software Speech sounds to me like about the right task. > > > > I will tell you that I attempted to write a HOWTO for Speakup on Linux > > together with a professional tech writer from IBM. When the tech writer > > left IBM this project stalled--after over 6 months of work between us. > > That's when I took the pieces that I actually knew something about and > > created the Installation HOWTO for the Speakup Modified Fedora Core. > > > > Which reminds me, writing a HOWTO is only part of the job. The rest of > > the job is maintaining the HOWTO which means making new versions when > > new facts change the advice people need to have. > > > > > > > > David Bruzos writes: > > > > > > Hello everyone: > > > This is my first time posting to this mailing list. I have come here many > times before to find info about Linux and > > > Speakup. I have a running system largely due to the existence of this list. > So, first, I like to thank the people that > > > organize it and everyone involved in Speakup for their work. Kirk is the > man! > > > > > > Last week I searched through the archives for hours to find out how to > configure my software synth. I saw, among other > > > things that there are no howtos for discribing this process and that most of > the documentation is somewhat outdated. > > > Anyway, it would have been much earier for me to setup software speech if > there would have been an organized guide or > > > howto, that explains how to do it... I am sure that this is no news to most > people in this list! > > > > > > So, I figured that now that I know how to do it, I can put together such a > document. In fact, I would like to > > > contribute by doing this. I can not program well enough to improve speakup, > but I could help out with the docs. I > > > would like to write a general Linux/Speakup howto, but I can not promise > that I can finish something like that any time > > > soon. So, the software synth thing is a better short term goal. I am a > full-time student at the University of North > > > Florida and soon to be a Dad, so time might be a problem in the > > > comming weeks... > > > > > > I would like to know what other mailing list members think about this. Are > there some reasons why I should not do this? > > > Are there other people working on a similar project? Anywthing is cool. > Oh, I am also a Linux newbey, so I might ask > > > simple questions sometimes... > > > > > > I am 23 years old and totally blind, so speakup is very important for me. I > have been using Linux for about one year > > > and used Windows/jfw before that. I started with Fedora Core 1 and now use > > > Fedora Core 2 and Mandrake 10 as well. The reason for Mandrake is so that I > can help my father when required... > > > > > > Thanx! > > > > > > David > > > > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > -- > > > > Janina Sajka, Chair > > Accessibility Workgroup > > Free Standards Group (FSG) > > > > janina@freestandards.org Phone: +1 202.494.7040 > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Janina Sajka, Chair Accessibility Workgroup Free Standards Group (FSG) janina@freestandards.org Phone: +1 202.494.7040