lynx-dev TRST: the next step

[Philip Webb]

looking forward to better table support, i compiled 2-8-3dev.14 .
unfortunately, the first set of tables i wanted to make use of
did not meet TRST's extremely limited capabilities.

in README.TRST, Klaus states:

  A table is simple enough if each of its TR rows translates
  into at most one display line in LTMS formatting (excluding leading
  and trailing line breaks), and the width required by each row
  (before as well as after fixup) does not exceed the availabe screen size.
  Note that <t>his excludes all tables where some of the cells are marked up
  as block elements ('paragraphs').

Lynx should ignore <P> ... </P> blocks when they occur inside tables:
they can never improve Lynx rendering & can make it very bad.
to see what happens goto  www.chass.utoronto.ca/~purslow/trst.html ,
where there is an example of a table from a recent transit report
with the <P> tags deleted (by hand) & then with them left in place.
Lynx makes an excellent job of the first; the second is grotesque.

surely, it's an easy matter to have Lynx ignore <P> tags within tables,
at least as an option in  lynx.cfg .  if Klaus doesn't care to do it
-- certainly, he's under no obligation to -- could he or someone else
tell me where to start in the source to do it myself.

-- 
========================,,============================================
SUPPORT     ___________//___,  Philip Webb : address@hidden
ELECTRIC   /] [] [] [] [] []|  Centre for Urban & Community Studies
TRANSIT    `-O----------O---'  University of Toronto