Re: LYNX-DEV No links, etc, at www.plextor.com

[Al Gilman]

  From: Tom Zerucha <address@hidden>

  I didn't get a BAD HTML! message, but the following, from www.plextor.com
  showed no links nor images.  Note the extra </head>.  Or it might be the
  comments.  How do I set up the default comment style to be the one that
  shows the most possible information (and so it would be set on startup).
  
At the minimum, there is a comment issue with this page.  Putting Lynx
2.6 in the "historical comment parsing" mode at least get some stuff
to appear.

There is no single mode of comment parsing which "shows the most
possible information."  There are multiple forms of malformed
comments out there on the web and they do not all yield the most
information under one parsing style.  That is why there are two
degrees of freedom w.r.t.  comment parsing in Lynx's bag of
tricks.

You can make any comment parsing mode the startup default via
userdefs.h, lynx.cfg or aliasing in a command-line option.  Read
lynx.cfg for some documentation.

Al Gilman

PS: This case illustrated a problem with the class of text preference
settings files.  Here, for example, in lynx.cfg we find:

------------------------quote ----------------------------------
                                                                    (p39 of 59
# If HISTORICAL_COMMENTS is TRUE, Lynx will revert to the "Historical"
# behavior of treating any '>' as a terminator for comments, instead of
# seeking a valid '-->' terminator (note that white space can be present
# between the '--' and '>' in valid terminators).  The compilation default
# is FALSE.
#
# The compilation default, or default defined here, can be toggled via a
# "-historical" command line switch, and via the LYK_HISTORICAL command key.
#
#HISTORICAL_COMMENTS:TRUE

-----------------end quote --------------------------------------------------

In the example quoted above, the commented-out example is the
_opposite_ of the compilation default, whereas in other places in
lynx.cfg the commented examples are _equivalent_ to the
compilation defaults.

Having the commented examples be the compilation defaults is probably
safer, and makes changing the compilation defaults more work.

It will be less confusing for users if the usage were consistent
in this regard.

Al
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;