Re: LYNX-DEV Long lines in HTML source, images without ALT

[Foteos Macrides]

"Hiram Lester, Jr." <address@hidden> wrote:
>On Sat, 16 Nov 1996, Hynek Med wrote:
>
>> But I was thinking about horizontal scrolling or just wrapping the source
>> where it overlaps..
>
>As I mentioned in my previous missive (my short notes always turn into
>missives...maybe it's majordomo :) ), it's been suggested about wrapping,
>and I think that the answer had to do with the way that Lynx handles text
>by just copying it into the HTML structure (HTStream?) and if you made it
>wrap the source, it would also wrap PRE formatted text which is
>undesirable.  Perhaps Fote or someone more familiar with it could restate
>it or point to the archives of the previous discussion.

        This has been discussed at length numerous times under the
category "Lynx is NOT a file viewer".  Try queries along those lines
to find the messages.

        Is there any possibility of the Lynx User Community setting
up and maintaining a Lynx FAQ that's a real FAQ, and not just treating
the Al's Picks to lynx-dev messages as if it were a real FAQ?

        In brief, Lynx does wrap into the HText structure when it's
rendering HTML, but not when it's processing source, because once
wrapped, it can't be unwrapped, and in the case of HTML source, you
do want to know whether the newlines are really there, or just
introduced by Lynx.  Everyone should have a "REAL file viewer" which
supports horizontal scrolling, and much more, in the 'p'rint and
'd'ownload options menus, ideally, one like most, which will go
automatically into hexadecimal display mode if you pass it a binary
file to "view".

        REAL file viewers which do everything one would want a
REAL file viewer to do are available for both Unix and VMS, and
should be used as helper apps for Lynx, rather than pointlessly
increasing the Lynx image to do things that an HTML client, per
se, need not do (IMHO 8-).

        HTML source, practically speaking, is text/plain.  The
only reason for rendering text/plain at all in Lynx, rather
than using a sophistocated plain text file viewer as a helper
app in the first place, is to be able to invoke the 'p'rint
menu for printing, mailing, etc. the file based on the site's
configurations for Lynx.  So, at the very least, a REAL viewer
for plain text should be included in that menu (and, ideally,
in the 'd'ownload menu as well).  Note that the Unix more does
not qualify as a "sophistocated plain text file viewer".  Get
most! (or something comparably sophistocated 8-)

                                Fote

=========================================================================
 Foteos Macrides            Worcester Foundation for Biomedical Research
 address@hidden         222 Maple Avenue, Shrewsbury, MA 01545
=========================================================================
;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;