Date: Sun, 27 Sep 1998 20:05:54 -0800 (AKDT) From: groggy@iname.com To: Dan Nelson <dnelson@emsphone.com> Cc: groggy@iname.com, freebsd-questions <questions@FreeBSD.ORG> Subject: Re: lynx & PRE Message-ID: <Pine.BSF.3.96.980927191941.1633A-100000@abc.xyz.net> In-Reply-To: <19980927201405.A21471@emsphone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
it's not EASY to explain these problems!!!
it's driving me crazy and makes me look like
a fool. lynx does not necessarily screw up
ON the bad html, LYNX WREAKS HAVOC DOWN FARTHER
in a document. does this make sense now?
for example,
------------------------------------------------------------
<TITLE> BAD HTML </TITLE>
GOOD HTML (lynx displays logically)
GOOD HTML (lynx displays logically)
GOOD HTML (lynx displays logically)
BAD HTML (lynx may display this seemingky ok too)
GOOD HTML (lynx displays logically)
GOOD HTML (lynx displays logically)
GOOD HTML (lynx displays logically)
GOOD HTML (lynx wreaks havoc here because of BAD HTML above)
------------------------------------------------------------
now, if you take the example below, which DOES seemingly
display OK, add run it thru a validator (w3c 4.0 strict
for example), you get:
Error at line X:
[...] <IMG SRC="g.gif" ALT="[G1]"> text1
^ document type does not
allow element <IMG> here
believe me - i'm not crazy. i wish lynx WOULD
screw up on the bad HTML, but it doesn't. it
screws up your document on GOOD HTML, farther
down in a document. this is creating hell for
me as i try to get my good ole lynx 2.7 and
netscape 3.04 web pages working with lynx 2.8
and netscape 3.04. i can't believe no one
else has mentioned this hassle. probably
not many web authours pay much attention
to detail, and/or care about lynx/netscape
viewability, and/or mix graphics/text
in neat and close arrangements ...
i'm not yet necessarily sure that the problems i'm
having are the result of the bad HTML. it could be
that lynx chokes on certain combinations of
elements and tags. this will take alot of work
to figure out since lynx appears indescriminate
on exactly where the crummy output will appear.
On Sun, 27 Sep 1998, Dan Nelson wrote:
> In the last episode (Sep 26), groggy@iname.com said:
> > since lynx cannot utilize FRAMES, this destroys all capabilities of
> > designing well formatted HTML pages of mixed graphics & text. lynx
> > relied on embedding things within PRE block for formatting without
> > frames.
>
> You can always put the lynx-friendly stuff in a <noframes> container.
>
> > for example, try this with lynx 2.8:
> >
> > [G1] text1 [G2] text2
> > [G1] text 1 [G2] text2
> > [G1] text 1 [G2] text2
> >
> > with lynx 2.7, this was no problem.
> > i could have 2 perfectly aligned columns.
> > now, this is impossible.
> >
> > you cannot say:
> >
> > <PRE>
> > <IMG SRC="g.gif" ALT="[G1]"> text1 <IMG SRC="g.gif" ALT="[G2]"> text2
> > <IMG SRC="g.gif" ALT="[G1]"> text 1 <IMG SRC="g.gif" ALT="[G2]"> text2
> > <IMG SRC="g.gif" ALT="[G1]"> text 1 <IMG SRC="g.gif" ALT="[G2]"> text2
> > </PRE>
> >
> > any longer.
>
> I just pasted this into a file and it looks just like your quoted text
> above; using lynx 2.8.1dev.29 (20 Sep 1998). What do you see on your
> console, and what version of lynx are you using?
>
> -Dan Nelson
> dnelson@emsphone.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980927191941.1633A-100000>