Re: LYNX-DEV lynx2.7.1ac-0.20 available

[Jude DaShiell]

There might be an easier solution for speech synthesizer users that would
save alot of coding.  If there's a hit, make the line of the hit line 2 on the 
screen;
display line 1 as it exists in the search material, then on line 2,
display a modified line with inequality symbols surrounding the
search string <hit>.  After that, display what will
fit on the screen.  This way, it doesn't matter if highlighting detection is on 
or not.  That kind of detection can slow performance down on some systems in
use on the net, so avoiding the need to use it might help level
the playing field for us.  If the <hit> stuff is all differently colored while 
being
displayed that may help some users with color vision.

On Mon, 5 May 1997, Al Gilman wrote:

>   From: Hynek Med <address@hidden>
>   Subject: Re: LYNX-DEV lynx2.7.1ac-0.20 available
> 
>   On Sun, 4 May 1997, Klaus Weide wrote:
>   
>   > Note that there have been some changes in the devel code regarding
>   > WHEREIS behavior, already since lynx2.7.1ac-0.12 or so, on which no-one
>   > has commented (maybe nobody has noticed).  They do not affect what is
>   > searched (form fields etc.) but only how the screen is positioned
>   > after a search, and whether the screen is refreshed (in some cases).
>   
>   I have noticed that what you searched for is highlited, and positioned in
>   the middle of the screen - and I like it!
>   
> Laura Eaves uses a screen magnifier and starts with the
> upper-left portion of the eighty by twenty four characters.  She
> definitely prefers that the match which has been found be on the
> top line of the displayed page.
> 
> She pointed out that speech users, at least many of them, have no
> indication of text highlighting in their speech output.  This
> still leaves me unclear as to what speech users would prefer.  If
> one does a "read line" after the page loads, one might want the
> hit to be on that line.  If one lets the page load and then does
> a "read screen" it might actually be preferred to have a line or
> more of context read off before the line with the hit in it is
> spoken.  This is the notion that I was focused on when I first
> suggested the change.
> 
> Of course, the eyeball behavior that I was not thinking about is
> the ability to rapidly acquire the first highlight on the page,
> and by shape recognition move to the top of the paragraph or list
> that the hit is in.
> 
> It sounds as though a lynx.cfg configuration setting is the most
> desirable out.  I think we can be reasonably confident that
> people using one-line Braille displays, will also prefer that the
> hit appear on the top line.
> 
> Feedback from speech users would be nice to have, but if
> configurability is not a big deal, it may be possible to figure
> out how to proceed without that feedback.
> 
> --
> Al Gilman
> 
> 
> ---------- End of message ----------
> 
> lynx-learners welcome message, 'subscribe' and 'unsubscribe'
> info are available by sending an E-Mail message to
> address@hidden with the line
> info lynx-learners
> in the body of the message.
> 
> lynx-learners archives are at
> Linkname: lynx-learners mailing list archives index
> URL:
> http://WWW.Sasquatch.Com/~jddjeff/Internet/World_Wide_Web/lynx/lynx-learners/
> 
> Accuracy and clarity are in the mind of the experimenter.
> CCCW = Comments, Corrections, & Cwestions Welcome.
> 


jude <address@hidden>

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;