public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Glenn <glennervin@cableone.net>
To: <mike@raspberryvi.org>,
	"Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: a little sysadmin story
Date: Thu, 9 Oct 2014 11:15:27 -0500	[thread overview]
Message-ID: <9849F292329C4B2FB3AF33EB9986B793@your2c061f0461> (raw)
In-Reply-To: <5436B2F3.1070401@raspberryvi.org>

I have used TextDetective on my iPhone to OCR a computer monitor a number of 
times.
Not as good of results as it would be from paper, but often enough to know 
what screen is displayed.
Glenn
----- Original Message ----- 
From: "Mike Ray" <mike@raspberryvi.org>
To: <speakup@linux-speakup.org>
Sent: Thursday, October 09, 2014 11:08 AM
Subject: Re: a little sysadmin story



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" <mike@raspberryvi.org>
>> To: <speakup@linux-speakup.org>
>> 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" <albert.e.sten_clanton@verizon.net>
>>> To: <tyler@tysdomain.com>; "Speakup is a screen review system for
>>> Linux."
>>> <speakup@linux-speakup.org>
>>> 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


  reply	other threads:[~ UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Deedra Waters
 ` Brian Buhrow
   ` Deedra Waters
 ` Janina Sajka
   ` Deedra Waters
     ` Littlefield, Tyler
       ` Littlefield, Tyler
         ` Al Sten-Clanton
           ` Glenn
             ` Mike Ray
               ` Glenn
                 ` Littlefield, Tyler
                   ` Glenn
                   ` Mike Ray
                     ` Glenn [this message]
                 ` Tom Fowle
                   ` covici
                     ` Blake Hardin
                       ` Kyle
                     ` Kelly Prescott
                   ` Janina Sajka
                     ` Kelly Prescott
                       ` Janina Sajka
                   ` John G. Heim
             ` Janina Sajka
               ` Glenn
                 ` John G. Heim
       ` Janina Sajka
         ` Samuel Thibault
     ` John G. Heim
       ` covici
         ` John G. Heim
       ` Littlefield, Tyler
         ` John G. Heim
           ` covici
             ` speakup in the kernel John G. Heim
               ` covici
                 ` John G. Heim
               ` Samuel Thibault
                 ` covici
                   ` Samuel Thibault
                     ` covici
                 ` John G. Heim
                   ` Samuel Thibault
                     ` covici
       ` a little sysadmin story Janina Sajka
     ` Janina Sajka
 ` John G. Heim
   ` Deedra Waters
     ` John G. Heim

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=9849F292329C4B2FB3AF33EB9986B793@your2c061f0461 \
    --to=glennervin@cableone.net \
    --cc=glennervin@gmail.com \
    --cc=mike@raspberryvi.org \
    --cc=speakup@linux-speakup.org \
    /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).