Re: lynx-dev <p>...</p><pre>...</pre>

[Laura Eaves]

I'm back after a long absence -- don't know how long I'll stay.

As for this thread:
I haven't looked at parser code lately, but as I remember
tagsoup treats </p> as if it were <p> (see comment in SGML.c)
whereas the "sorta-SGML" parser treats </p> as a junk tag.
I don't know which is right.
Klaus would know how to fix the parser if it indeed is a bug.

The workaround (which works for both parsers) is
to put a <p> before the first <pre>.
Putting the extra blank line at the start of the first <pre>
fixes the problem with Klaus' parser but
causes the tagsoup parser to spit out an extra blank line.
Ciao.
--le

> From: Karl Eichwalder <address@hidden>
> Date: 01 May 1999 22:12:12 +0200
>...
> Please view the following code with lynx:
>
> <p>
> text 1
> </p>
> <pre>
> preformatted text
> </pre>
> <p>
> text 2
> </p>
>
> =>
>
>    text 1
> preformatted text
>
>    text 2
>
> A blank line is missing after "text 1".  Only if I force lynx to use
> "tagsoup", the example is displayed okay.  But it should be the default
> to display:
>
>    text 1
>
> preformatted text
>
>    text 2
>
> If you don't close the first paragraph, it's even impossible to force
> lynx to display the needed blank line.  Please note, that every PRE
> element closes the previous block element (have a look at the HTML DTD).
>...
> Thanks for the time!