From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 227F51EF826; Thu, 9 Oct 2014 12:08:20 -0400 (EDT) Received: from rgout0507.bt.lon5.cpcloud.co.uk (rgout0507.bt.lon5.cpcloud.co.uk [65.20.0.228]) by befuddled.reisers.ca (Postfix) with ESMTP id E91511EF7B7 for ; Thu, 9 Oct 2014 12:08:18 -0400 (EDT) X-CTCH-RefID: str=0001.0A090203.5436B2F0.020A, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-Junkmail-Premium-Raw: score=27/50, refid=2.7.2:2014.10.7.91518:17:27.888, ip=86.140.30.210, rules=__MOZILLA_MSGID, __HAS_MSGID, __SANE_MSGID, __HAS_FROM, __HAS_REPLYTO, __USER_AGENT, __MOZILLA_USER_AGENT, __MIME_VERSION, __TO_MALFORMED_2, __TO_NO_NAME, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __SUBJ_ALPHA_END, __IN_REP_TO, __CT, __CT_TEXT_PLAIN, CT_TEXT_PLAIN_UTF8_CAPS, __CTE, __REPLYTO_SAMEAS_FROM_ADDY, __REPLYTO_SAMEAS_FROM_ACC, __REPLYTO_SAMEAS_FROM_DOMAIN, __ANY_URI, __CP_MEDIA_BODY, __CP_URI_IN_BODY, __C230066_P2, __OEM_SOFTWARE_1, __SUBJ_ALPHA_NEGATE, __FORWARDED_MSG, BODY_SIZE_4000_4999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, __URI_NS, SXL_IP_DYNAMIC[210.30.140.86.fur], HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, RDNS_SUSP, OEM_SOFTWARE_X1, BODY_SIZE_7000_LESS X-CTCH-Spam: Unknown Received: from [192.168.0.77] (86.140.30.210) by rgout05.bt.lon5.cpcloud.co.uk (8.6.122.06) (authenticated as mike.ray@btinternet.com) id 543311C400695B18 for speakup@linux-speakup.org; Thu, 9 Oct 2014 17:08:16 +0100 Message-ID: <5436B2F3.1070401@raspberryvi.org> Date: Thu, 09 Oct 2014 17:08:19 +0100 From: Mike Ray Reply-To: mike@raspberryvi.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: speakup@linux-speakup.org Subject: Re: a little sysadmin story 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> <5436AF66.2020105@tysdomain.com> In-Reply-To: <5436AF66.2020105@tysdomain.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 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: Thu, 09 Oct 2014 16:08:22 -0000 The Windows screen-reader NVDA has OCR built in. It uses Tesseract to OCR the screen. On 09/10/2014 16:53, Littlefield, Tyler wrote: > Could probably be done with an arduino board. OCR is no easy deal > though. There's a reason why companies invest millions. You could hack > something together, however. This only really works on console screens > and console screens that don't use ncurses or something similar. > Otherwise there would have to be some kind of driver or something to > help parse out text that needs to be handled. e.g: do you just OCR an > entire screen taskbar and all on gnome? > > On 10/9/2014 11: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