[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] won't render as it thinks it is not text/html

From: Thomas Dickey
Subject: Re: [Lynx-dev] won't render as it thinks it is not text/html
Date: Sun, 24 Oct 2004 09:12:13 -0400 (EDT)

On Sun, 24 Oct 2004, Atsuhito KOHDA wrote:

> From: Thomas Dickey <address@hidden>
> Subject: Re: [Lynx-dev] won't render as it thinks it is not text/html
> Date: Sat, 23 Oct 2004 16:12:39 -0400 (EDT)
> > On Sun, 24 Oct 2004, Dan Jacobson wrote:
> >
> > > $ wwwoffle -O 
> > >
> > > Content-Type: text/html; charset=EUC-JP
> > > But lynx says it is not text/html and won't render it.
> > > It warns about the charset, but then just calls $PAGER on the source.
> >
> > This is a repeat of an earlier report (which I addressed in 2.8.6dev.6):
> (snip)
> > I'm able to view the page with 2.8.6dev.6 (though the alert message
> > regarding EUC-JP can be annoying).
> Hi Dan, sorry but the lynx-cur package (of Debian) is of dev.5
> yet because there seems a minor problem with dev.6 (and dev.7)
> so I didn't upload the package of dev.6 nor dev.7  But I already
> packaged lynx-cur of dev.7
> I put lynx-cur of dev.7 in

> so you can test it in normal Debian's way.

hmm - "normal" for me is to mainly use dselect, and occasionally some
special apt-get command.  I'll see how to install this.

> > btw - the page appears to be ASCII -
> yes, it looks so.

And an alignment problem there is surprising.  The changes that I made for
adjusting link-position were to allow for multicolumn characters earlier
on the same line.  (Of course, in changing things, I could have also added
a bug - but for an ASCII page such as this, I'd expect our results to be
the same).

> >    [INLINE]   Free/Libre and Open Source Software for Geoinformatics:
> >    GIS-GRASS Users Conference
> >    Presented by FOSS/GRASS 2004 International Organizing Committee
> The problem I mentioned above is that these lines looked
>     Presented by FOFOSS/GRASS 2004 International Organizing Committee
>                  ^^
> on kterm with normal settings.

odd - it looks normal to me (checking with kterm, and setting display
charset to EUC-JP).  I put two screenshots (of the options menu, because I
can see the effect of the display charset there)  in

to show the effect of the display charset:


If the display charset doesn't match, then lynx and ncurses will not agree
on the width of strings written to the display.  And as I noted, there
may be places in the code which I have not yet discovered that must be
modified to work properly.

Thomas E. Dickey

reply via email to

[Prev in Thread] Current Thread [Next in Thread]