Re: lynx word bleeding?

Hi Ian,


> As Mouse says, this site isn't sending a Content-Type header.  Lynx
> actually has an option for this, and so if Lynxes are treating
> it differently it probably means the option differs between
> environments.
>
> Extract from lynx.cfg:
>
> .h2 PREFERRED_CONTENT_TYPE
> # When doing a GET, lynx expects the server to provide a Content-Type, i.e.,
> # the MIME name which tells it how to present data.  When that is missing
> # lynx uses this value.
> #PREFERRED_CONTENT_TYPE: text/plain
>
> You can set this within Lynx on the (o)ptions screen, though by default
> it's not saved to disk.  You want to set it to text/html in order to
> properly view the above page.

and this seems to be the issue.
Shellworld lynx 2.9.0dev.5
Has this as text/plain, not html.
Older copies of lynx here, and  the other shell example I can check  read 
the page just fine.
Ian you indicate that this cannot be saved on the options menu, meaning it 
must  be corrected  where ever the compile or main lynx.cfg is stored?

Thanks,
Karen