"N" <n@[EMAIL PROTECTED]
> wrote in message
news:481033f0$0$1631$5a62ac22@[EMAIL PROTECTED]
> "Dudley Hanks" <hanks.dudley@[EMAIL PROTECTED]
> wrote in message
> news:MqVPj.1889$XI1.1092@[EMAIL PROTECTED]
>>
>> "Jürgen Exner" <jurgenex@[EMAIL PROTECTED]
> wrote in message
>> news:nv40141341tdan0va2du159aempg848i4j@[EMAIL PROTECTED]
>>> "Dudley Hanks" <hanks.dudley@[EMAIL PROTECTED]
> wrote:
>>>>I'm trying a new feature on my site, and I'm wondering if someone
might
>>>>take
>>>>the time to drop by and test it for me.
>>>>
>>>>http://www.geocities.com/hanks.dudley/index.html
>>>
>>> The layout of that page is quite poor. Because a picture says more
than
>>> a thousand words I added my comments into a screenshot:
>>> http://mysite.verizon.net/jurgenex/images/comment.GIF
>>>
>>> Sorry, but you asked for it :-(
>>>
>>> jue
>>
>> Yes, I did, and I'd love to know what you posted. But, reading text
from
>> a screen shot with a screen-reader is just about impossible. So, I
guess
>> I won't be able to learn from your expertise.
>>
>> But, hey, thanks for taking the time to visit my site.
>>
>> Take Care,
>> Dudley
>>
>>
>
>
> Dudley, can you read if the text is large?
If I blow the image up to where only two or three characters fit on the
screen (I have a 17" wide screen monitor), and, if I can get light
characters on a black background, I can "see" the text. However, at that
magnification, it's not practical to crawl around the screen looking for
words. It just takes too long.
Using Omnipage, I can process an image and extract the text, but screen
shots have too many elements interfereing with the text. Also, the
program
trys to make sense of fragments and peice them together into
semi-intelligent statements. It isn't always successful.
I've learned from experience not to bother with screen shots.
Take Care,
Dudley
|
