[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
lynx-dev suggestion: usual handling of tags inside <PRE> block
|
From: |
Vlad Harchev |
|
Subject: |
lynx-dev suggestion: usual handling of tags inside <PRE> block |
|
Date: |
Fri, 5 Mar 1999 10:28:33 +0400 (SAMT) |
It seems that it will be useful to allow lynx to interpret tags
inside <PRE> block preserving the layout of the source in <pre>.
This is supported by at least Netscape (even <HTML>,<HEAD>,<BODY>
are not required for NS) and kfm ( <HTML>,<HEAD>,<BODY> tags are required
for document to be parsed as HTML even for file with .html extension).
Both of them allow tags like <b>,<i> and even <a>.
This feature allows quick pseudo-html-formatting of the pure-text documents
for which no hypertext source in any form isn't availble by inserting tags
like <b>,<i> around chapter titles, etc using 'sed'. Currently default
HTML-parser in lynx, when encounters any tag in <pre> block, discards <pre>
semanics and treats everything like no <pre> was specified. It seems to me
that lynx won't have problems or logical inconsistences displaying such html
files since it's character based. It's also a good solution for documents that
contain tables - the tables can be rendered with some other tools (may be even
on http server based on the name of the user-agen header) to the html and
placed within <pre> with normal html formatting. If there will be such http
servers, it will be nice to pass the width of the screen in characters in
user-agen header like 'Lynx/2.8.2dev.12-80 libwww-FM/2.14`, where 80 is the
width of the screen. It's likely that GNU-oriented sites will support it -
such formatting can be achived with Perl scripts on server side probably with
the use of nroff.
Best regards,
-Vlad
- lynx-dev suggestion: usual handling of tags inside <PRE> block,
Vlad Harchev <=