Re: [Lynx-dev] lynx word bleeding?

2022-02-02 Thread Karen Lewellen
I was wondering  because it is marked as one of those that cannot be saved 
to  disc.




On Wed, 2 Feb 2022, Chime Hart wrote:

Hi Karen-and-All: As always the LYNX options menu acts like it will save, 
even when checking that box on link4 "save options to disk" but in this case 
it did not save.

Chime






Re: [Lynx-dev] lynx word bleeding?

2022-02-02 Thread Chime Hart
Hi Karen-and-All: As always the LYNX options menu acts like it will save, even 
when checking that box on link4 "save options to disk" but in this case it did 
not save.

Chime




Re: [Lynx-dev] lynx word bleeding?

2022-02-02 Thread Karen Lewellen

Yes chime, it is not there.
I am told by dreamhost that  it tends to be in a lynx.cfg that is 
stored elsewhere.

although it was I believe in their 2.8.9dev.16.

So I changed it in   shellworld 2.9.0dev.5, and it worked.
you were able to save the option?



On Wed, 2 Feb 2022, Chime Hart wrote:

Well, I took a look in an options menu in an older LYNX on Shellworld, where 
that particular setting is not there at all. On my Debian system with a 
current LYNX, I can switch over to html-and-yes I can enjoy that page.

Chime






Re: [Lynx-dev] lynx word bleeding?

2022-02-02 Thread Chime Hart
Well, I took a look in an options menu in an older LYNX on Shellworld, where 
that particular setting is not there at all. On my Debian system with a current 
LYNX, I can switch over to html-and-yes I can enjoy that page.

Chime




Re: [Lynx-dev] lynx word bleeding?

2022-02-02 Thread Karen Lewellen

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




Re: [Lynx-dev] lynx word bleeding?

2022-02-02 Thread Karen Lewellen

Hi Chime,
I just visited your link using what is 2.9.0dev.5
and indeed it is all code.
Makes me wonder if there is a setting misconfigured between  prior lynx on 
shellworld and this new build.

Karen
..who wants to visit that site  for its content now too.



On Tue, 1 Feb 2022, Chime Hart wrote:

Hi All: I still use Shellworld, as well as my own Debian setup. Funny thing 
is I visit

www.radiotapes.com
On my machine I only see raw html. Meanwhile
with  an older LYNX on Shellworld, I see the site fine, I have no idea why 
these 2 versions are seeing this site so differently? Thanks so much in 
advance

Chime






Re: [Lynx-dev] lynx word bleeding?

2022-02-02 Thread Ian Collier
Chime Hart writes:
> Hi All: I still use Shellworld, as well as my own Debian setup.  Funny
> thing is I visit
> www.radiotapes.com
> On my machine I only see raw html.

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.

Note: I believe there shouldn't be a space between the colon and 'text'
in the lynx.cfg setting - at least it didn't work for me with a space
but did work without.  This means there is a bug either in the parser
or in the sample lynx.cfg which comes with Lynx.

imc



Re: [Lynx-dev] lynx word bleeding?

2022-02-02 Thread Chime Hart
Thank you Mouse for examining. I did write my contact at that site. At the time 
I figured it had changed recently, but actually it were the LYNX changes on 
Shellworld. I remember there was a site back maybe 2008 or so which I had to 
switch to the source-code-and-back to regular view-and-it would correct. Just 
located the site of that program which went off in 2010, looks fine now, so I 
guess there's no point in my posting an url.

Chime