On Sun, Oct 07, 2018 at 11:39:48PM -0400, Zachary Lee Andrews wrote: > Hello all, > > I have noticed a potential bug and would like a few folks to verify... > When using lynx to convert a gopher menu into HTML, by using -source, > lynx fails to encode <, >, and & characters into <, >, and & > respectively. > > As a result when using lynx (or most other browsers) to open a saved > gopher listing, there will be terrible manging. > > > Here is an example command and URL: > > lynx -source gopher://gopher.zcrayfish.soy/1/irc/lynxtest > lynxtest.html > > lynx lynxtest.html > > > In my example, there are 11 lines... Lynx will only display 9 after > loading the saved HTML, and they're awful.
yes... there's a chunk in HTGopher.c like this:
if ((char) ich != LF) {
*p = (char) ich; /* Put character in line */
if (p < &line[BIG - 1])
p++;
} else {
which could encode the document.
--
Thomas E. Dickey <dic...@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net
signature.asc
Description: Digital signature
_______________________________________________ Lynx-dev mailing list Lynx-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/lynx-dev
