Re: lynx-dev improving documentation

[Al Gilman]

Philip:

> > how should i make available material which might go in the distribution?
> > it won't be HTML, nor is it likely to be patches:

You have seriously diminished your chances of seeing your work
included at this point already.  If you are suggesting some
documentation that should be available for the lynx community but
not distributed in the distribution, it just needs to be linked
somewhere in the web of resources that lynx.browser.org leads
you to.  This includes options

        at l.b.o directly, as Rob reminded us
        at Lynx links, (Subir has always been cooperative)
        at the distribution site (ditto for Scott, Jim et al.)
        at a site you provide

If it is intended as changes to the content of a distribution, it
should be in a format that someone actively changing the file set
that patch-o-matic runs from finds convenient to work with.

Don't say "it won't be a patch."  Ask "what are acceptable patch
formats?"  The current developers may be a little more flexible
than at some times in the past.
        
Al