On Thu, 16 Mar 2000, Henry Nelson wrote:
> > Try two of the documents I use to test it:
> >
> > http://earthspace.net/The_sky/sky_top.html
> > http://weather.ec.gc.ca/forecast/yul.html
> >
> > Try with lynx/slang and lynx/ncurses and you'll see the difference.
>
> Well, I must confess it will be impossible for me to test with ncurses,
> but I did the next best thing and tested with MSIE (Oh! Hurts!).
Well, that's like comparing appels and oranges. I'm comparing the behaviour
of lynx/slang and lynx/ncurses. Try compiling lynx without the two lines in
LYCurses.c and you'll see the difference.
> _To me_, anyway, there is no "problem." In fact, having the underlining is
> really the kind of emphasis the people who designed those pages are hoping
> for, AFAIKT.
I don't think that "underlining is really the kind of emphasis the people who
designed those pages are hoping for" and even if it is, it is made to be seen
with Netscape and/or MSIE. 99,99999% of those people has never seen lynx and
they don't care about how their pages are rendered by lynx.
> > > Without knowing how you access Lynx it's hard to say much,
> >
> > I access it through a shell acces in my ISP. I use a VT100/VT102 terminal
> > emulator with color support. I dial to my ISP and access the shell.
>
> Well, you've been warned about that :). Hope your description's name is
> not "vt100", but some unique name. I often use the model number of the
> monitor, PC or modem, whatever is appropriate for the situation.
It doesn't matter which "description name" I use if I have control over it
and I'm the only person using my account.
> > > two routes depending on where you want to redefine them. Easiest might
> > > be to change your terminfo description, i.e., change smul and rmul (I
> > > *think* those are the ones.) to nullify them or change them to bold or
> > > something rather than have underlining.
> >
> > I dont want to follow that path. By doing that I would be just masking
> > the problem. I want it to be corrected. It was by doing that that the
> > problem was
>
> I agree there.
>
> > > The other way would be to patch Lynx to remove the underline attribute
> > > associated with those colors. To be thorough you probably would have to
> > > grep through the /src source files for things like "USE_SLANG,"
> > > "UNDERLINE_," "start_underline," etc.
> >
> > That's what I wanted to do. I did a grep on underline and tried to find
> > out where the problem could be but my knowledge of C and of the lynx code
> > didn't take me anywhere.
>
> That's why no one else has done it. It's not worth anyone's time unless
> it's important or *fun* enough for him/her.
I think I can understand that. What I can understand is the kind of excuses I
get when I ask.
> > > since as Klaus has pointed out, some (a lot?) of those if clauses with
> > > USE_SLANG are probably no longer needed.
> >
> > Do you remember when he mentioned that?
>
> Around the time John Davis did major changes, 0.38??? Maybe 1997.
>
> > > Klaus also questioned these lines in LYCurses.c:
> > > 728 SLtt_add_color_attribute(4, SLTT_ULINE_MASK);
> > > 729 SLtt_add_color_attribute(5, SLTT_ULINE_MASK);
> > > Maybe you can just delete them; worth a try if underlining is so undesirable.
> >
> > Et voil�!!! Thank you very much, Henry. Removing those two lines
> > corrected the problem. I knew it would take a lot less time to correct
> > the problem than to discuss if the problem is really a problem, if it's
> > "hardcoded" or
>
> Is it a "problem" still remains questionable.
For me there is doubt that it was a problem. For the others it's, at least,
an incoherence between the behaviour of lynx/slang and lynx/ncurses.
> > I don't know whether that change will have side effects but it's working
> > fine. Here's the patch, which I hope will be incorporated into the next
> > release:
>
> I can't agree with blind incorporation. See below.
I agree. Maybe now people will find it "fun" or important to do a cleanup in
that part of the code. However, I'll incopoorate it into my compilations.
> > #if (defined(VMS) || defined(UNIX)) && !defined(__CYGWIN__)
> > - SLtt_add_color_attribute(4, SLTT_ULINE_MASK);
> > - SLtt_add_color_attribute(5, SLTT_ULINE_MASK);
>
> Why is that "!defined(__CYGWIN__" there? Indicates to me that the whole
> if statement is wrong and shouldn't be there. What does color_attribute
> have to do with OS? Isn't CYGWIN practically UNIX?
That's for people who really understands that to answer.
> Good ol' cut-n-paste has orphaned some lines. We need someone who can use
> an eraser as well as a pencil.
I agree but for the moment the eraser wroks fine.
> > Thank you very much again and take care.
>
> Thank Klaus. (I should say more in the way of praise, but will refrain.)
Well, maybe Klaus is the source of the information but I thank _you_ for
having given it to me.
Ismael
--
________________________________________________________________
| |
| ISMAEL CORDEIRO | mailto:[EMAIL PROTECTED] |
| Production sound mixer | http://ismael.cordeiro.com/ |
| Montr�al - Qu�bec - Canada | ftp://ftp.pubnix.net/users/ismael |
|________________________________________________________________|
