From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 2EAEE1EF7BC; Fri, 10 Oct 2014 04:11:31 -0400 (EDT) Received: from mail0200.smtp25.com (mail0200.smtp25.com [174.37.170.200]) by befuddled.reisers.ca (Postfix) with ESMTPS id 7E78A1EF7AF for ; Fri, 10 Oct 2014 04:11:27 -0400 (EDT) Received: from ccs.covici.com (s-out-001.smtp25.com [67.228.91.90]) by s-out-001.smtp25.com (8.14.2/8.14.2) with ESMTP id s9A8BJol013385 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 10 Oct 2014 04:11:19 -0400 Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.9/8.14.8) with ESMTP id s9A8BItV027924; Fri, 10 Oct 2014 04:11:18 -0400 To: "Speakup is a screen review system for Linux." Subject: Re: a little sysadmin story In-reply-to: <1412911271.3408239.177306073.210519F2@webmail.messagingengine.com> References: <86a956i23h.fsf@vibrator.pk5001z> <20141009125200.GI1044@opera.rednote.net> <86ppe1gyed.fsf@vibrator.pk5001z> <543691D1.9050000@tysdomain.com> <543693B5.9060601@tysdomain.com> <5436A145.30001@verizon.net> <478C3EC865774707826A4B0E156AE72B@your2c061f0461> <5436AA7E.7030808@raspberryvi.org> <9BB45DB8ACB5452BB988DBFEE96594BB@your2c061f0461> <1412911271.3408239.177306073.210519F2@webmail.messagingengine.com> Comments: In-reply-to Tom Fowle message dated "Thu, 09 Oct 2014 20:21:11 -0700." X-Mailer: MH-E 8.2; nmh 1.3; GNU Emacs 23.4.1 Date: Fri, 10 Oct 2014 04:11:18 -0400 Message-ID: <27921.1412928678@ccs.covici.com> From: covici@ccs.covici.com X-SpamH-OriginatingIP: 70.109.53.110 X-SpamH-Filter: s-out-001.smtp25.com-s9A8BJol013385 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Cc: Glenn X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Oct 2014 08:11:31 -0000 I have heard (never tried this myself) that the knfb reader on the iphone was actually able to read the monitor text on a screen, if so this would be great, no substitute for a real screen reader, but interesting nonetheless. Tom Fowle wrote: > The idea of a stand alone screen reader hardware box with video input is > intreaguing and has > been tried by several folks including Dean Blazie. but that was years > ago. > I suspect actual screen text would be no problem, if perhaps a bit slow, > but > finding focus and defining/dealing with actual graphics could be a real > headache. > > I think you'd need at least two processors, one to do the OCR and the > second > to run the screen reader and speech. Don't guess the Raspbery pi would > have > the "MIPS" for the ocr task. > > BTW, the optacon actually connected to a mac's serial port and you could > read the screen directly with some kind of reader that Berkeley systems > had > as a prototype. the company died before it could be brought to full > operation > > For many years I kept seeing brags about optacon being restarted, but so > far as i know none ever came to reality. > > Tom Fowle > wa6ivgtf@fastmail.fm > > > On Thu, Oct 9, 2014, at 08:49 AM, Glenn wrote: > > I do a little of that. > > I do know a little, enough to know what is possible. > > I studied and got a HAM license a long time ago. > > Glenn > > ----- Original Message ----- > > From: "Mike Ray" > > To: > > Sent: Thursday, October 09, 2014 10:32 AM > > Subject: Re: a little sysadmin story > > > > > > > > Get your soldering iron out then Glenn :-p > > > > > > > > On 09/10/2014 16:28, Glenn wrote: > > > What we need is a piece of hardware that does OCR directly from the video > > > port. > > > It seems like that would be a relatively easy device to produce, given > > > what > > > we have these days. > > > Glenn > > > ----- Original Message ----- > > > From: "Al Sten-Clanton" > > > To: ; "Speakup is a screen review system for Linux." > > > > > > Sent: Thursday, October 09, 2014 9:52 AM > > > Subject: Re: a little sysadmin story > > > > > > > > > First, I thank Janina for raising certain issues better than I could. > > > (I also thank others who've made valuable points from different angles.) > > > > > > Second, where is the equivalent code for kicking in the monitor when we > > > boot up? Shouldn't the aim be to treat our access technology in the > > > same or an equivalent way, to the degree possible? > > > > > > Al > > > > > > On 10/09/2014 09:55 AM, Littlefield, Tyler wrote: > > >> I also wanted to point out that most companies and organizations are a > > >> bit weird about installing anything. The fact that Speakup is in the > > >> kernel, but the entire idea of installing a special program which > > >> they're not sure of, be it screen reader or magnification bothers most > > >> people, so this isn't just an issue of Speakup possibly being better. > > >> There are reasons and there obviously is a need for speakup to get > > >> better, perhaps that means coming out of kernel space. But a sad story > > >> from once upon a time with a moral unrelated is not quite the point. > > >> On 10/9/2014 9:46 AM, Littlefield, Tyler wrote: > > >>> This whole story sounds like it needs another couple of bears to make > > >>> it all interesting. So speakup crashed the kernel. I've had issues, > > >>> but apart from known bugs I've never seen speakup panic the kernel all > > >>> the time. Speakup caused a system to crash? Perhaps. People should > > >>> also backup their work. > > >>> On 10/9/2014 9:34 AM, Deedra Waters wrote: > > >>>> Janina, > > >>>> > > >>>> speakup was the cause because when bossman came down to hook up a > > >>>> monitor and look, the panick messages had something to do with speakup. > > >>>> > > >>>> As for backing up their work, they were trying to fix their fuck-up to > > >>>> begin with. The initial problem wasn't with speakup. However when i was > > >>>> helping them debug it, speakup made the kernel panick and crash. > > >>>> > > >>>> Debian i dont think likes people with root access on their box to begin > > >>>> with, but i think they kind of didn't like speakup in their kernel to > > >>>> begin with. > > >>>> > > >>>> I suspect on the other hand that if speakup was a user-space app, it > > >>>> wouldn't have mattered to them so much. If a userspace program crashes > > >>>> it doesn't take down the whole box. When speakup does though, it takes > > >>>> down the whole box. > > >>>> > > >>>> > > >>> > > >>> > > >> > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@linux-speakup.org > > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup@linux-speakup.org > > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > > > > > > > > > -- > > Michael A. Ray > > Analyst/Programmer > > Witley, Surrey, South-east UK > > > > The box said: 'install Windows XP, 7 or better'. So I installed Linux > > > > Interested in accessibility on the Raspberry Pi? > > Visit: http://www.raspberryvi.org/ > > From where you can join our mailing list for visually-impaired Pi hackers > > _______________________________________________ > > Speakup mailing list > > Speakup@linux-speakup.org > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > > > > _______________________________________________ > > Speakup mailing list > > Speakup@linux-speakup.org > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup > _______________________________________________ > Speakup mailing list > Speakup@linux-speakup.org > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com