Re: lynx-dev dev17 - lynxcfg.html problems

[T.E.Dickey]

> Hope you will extend comment section on top of cfg2html.pl 

will do (it helps to have reminders like this, since some of the assumptions
aren't as obvious as others).

> I found several assumption made on lynx.cfg layout: 
  
yes - I used the conventions that existed in the lynx.cfg to provide
hints (reduces the amount of markup required to make cfg2html.pl work).

> 1) uncommented options are assumed "default" 
> 2) commented out but flashed left options are assumed "default" 
> 3) a single letter in parenthesis will be emphasized 
>  
>  
> Problems: 
>  
> .h1 
> .h2 
> give bad side effect on cattoc.html 
> (blank line is required after .h1 at the moment) 

I can fix that (I didn't think it was critical, but on the next pass, I
can refine things like that).
>  
>  
> Many options in body.html have several "default" values 
> which was not intended, should be "examples" instead. 

right (they should be marked with ".ex" lines).

> That should be proof-readed, IMO. 
> Few paragraphs in lynx.cfg should be rewritten for better 
> html output, say INCLUDE section. 
>  
>  
> Following lines are assuned in different context 
>  
> STARTFILE (default) 
> #STRATFILE (default, or example if we have uncomented default) 
> # STRARTFILE (normal text) 
>  
> So I propose to extent this even more: let the following lines 
> will be assumed verbatim (no justification): 
>  
> #  some text (more than 1 space from comment symbol) 

that's what I intended (with a few hints to preserve the left-margin in
special cases)


-- 
Thomas E. Dickey
address@hidden
http://www.clark.net/pub/dickey