[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Sun, 3 Jan 1999 08:56:28 -0500 (EST)
> > no - the examples I know of are delimited with <server> and <script>
> > is line-oriented, and all of that is lost in rendering).
> <script> is HTML, lynx parses it right and ignores the content.
> <server> isn't HTML, lynx doesn't know anything about this tag so
> it ignores it, and shows the content (according to whatever mode
> is in effect).
which pays attention to newlines: someone decided to make ';' optional
syntax for most occurrences. So running the text together is misleading.
> I assume the content of <server> is meant to be interpreted by a server,
> so a file with that tag in it isn't meant to be viewed by a HTML browser
> without preprocessing. So no wonder you don't like how lynx shows it. :)
> I guess other browsers would have the same "problem".
I didn't look with IE - this may be NS-specific stuff.
> Do you want to add recognition of <server> to lynx, to be able to view
> the code verbatim? It might make sence for some people, but isn't really
I agree - but there's cases like that where Lynx accommodates things that
A similar (unrelated) issue: I've seen NS interpret text with backspaces
as underlined/overstruck. Likewise html doesn't do anything useful with
backspace, but it would make Lynx more useful (perhaps).
Thomas E. Dickey