[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] tagsoup?

From: Karen Lewellen
Subject: Re: [Lynx-dev] tagsoup?
Date: Wed, 27 Sep 2017 10:31:14 -0400 (EDT)

Thanks for this information. I found the item in the options menu, tested as Meetup asked, finding that the option does not improve the situation.
So they must think again.

"No one is born hating another person because of the color of his
skin or his background or his religion ... People must learn to
hate, and if they can learn to hate, they can be taught to
love... For love comes more naturally to the human heart than its
opposite." Nelson Mandela.

On Tue, 26 Sep 2017, Larry Hynes wrote:

Karen Lewellen <address@hidden> wrote:
Hi folks,
I am engaged in troubleshooting with meetup over their comment submission
button .
They have asked about a lynx feature called tagsoup, which they claim
manages html5 better.
This does not ring a bell, but I have not played with the html5 aspects of
Lynx  much.
The parser? their words.
Any wisdom on this?

From man lynx:

        initialize parser, using Tag Soup DTD rather than SortaSGML.

From Lynx_users_guide.html, which can be found online at

if it is not available to your local lynx installation

HTML error recovery

Lynx often has to deal with invalid HTML markup. It always tries
to recover from errors, but there is no universally correct way for
doing this. As a result, there are two parsing modes: "SortaSGML"
attempts to enforce valid nesting of most tags at an earlier stage
of processing, while "TagSoup" relies more on the HTML rendering
stage to mimic the behavior of some other browsers. You can also
switch between these modes with the CTRL-V key, and the default can
be changed in lynx.cfg or with the -tagsoup command line switch.

The "SortaSGML" mode will often appear to be more strict, and makes
some errors apparent that are otherwise unnoticeable. One particular
difference is the handling of block elements or <li>..</li> inside
<a HREF="some.url">..</a>. Invalid nesting like this may turn anchors
into hidden links which cannot be easily followed, this is avoided
in "TagSoup" mode. See the [62]help on following links by number
for more information on hidden links. Often pages may be more
readable in "TagSoup" mode, but sometimes the opposite is true.
Most documents with valid HTML, and documents with only minor errors,
should be rendered the same way in both modes.

If you are curious about what goes on behind the scenes, but find
that the information from the -trace switch is just too much, Lynx
can be started with the -preparsed switch; going into SOURCE mode
(“\” key) and toggling the parsing mode (with CTRL-V) should then
show some of the differences.

see also:

Lynx-dev mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]