diff options
| author | Thomas E. Dickey <dickey@invisible-island.net> | 1999-12-01 03:38:43 -0500 |
|---|---|---|
| committer | Thomas E. Dickey <dickey@invisible-island.net> | 1999-12-01 03:38:43 -0500 |
| commit | 4525eb4b32fdf2124e246285af59a1e14ecbf551 (patch) | |
| tree | b4fa005bd9b3ff3f0973cb1ea9e5ac4243ec2a39 /docs | |
| parent | 45f1aadc261561566cd074da1d9b0fb21a6ad78c (diff) | |
| download | lynx-snapshots-4525eb4b32fdf2124e246285af59a1e14ecbf551.tar.gz | |
snapshot of project "lynx", label v2-8-3dev_16
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/README.TRST | 20 | ||||
| -rw-r--r-- | docs/README.defines | 13 |
2 files changed, 12 insertions, 21 deletions
diff --git a/docs/README.TRST b/docs/README.TRST index 5bfa9092..fcff125b 100644 --- a/docs/README.TRST +++ b/docs/README.TRST @@ -34,7 +34,7 @@ pleasant results anyway for pages that (ab-)use more complex table structures for display formatting purposes (especially in view of Lynx limitations such as fixed character cell size and lack of horizontal scrolling; see also emacs w3 mode). Full table support within Lynx -hasn't happend so far, and continues to seem unlikely to happen in the +hasn't happened so far, and continues to seem unlikely to happen in the near future. The other basic idea is the observation that for simple tables, as @@ -47,19 +47,19 @@ by two simple transformations applied line by line: And that's exactly what TRST does. An implementation based on the simple observation above is relatively straightforward, for simple tables. On encountering the start of a TABLE element, Lynx generates -output as ususal for LMTS. But it also keeps track of cell positions +output as unusual for LMTS. But it also keeps track of cell positions and lengths in parallel. If all goes well, that additional information is used to fix up the already formatted output lines when the TABLE ends. If not all goes well, the table was not 'simple' enough, the -additional processing is cancelled. One advantage is that we always -have a 'safe' fallback to well-understood traditional LTMS formatting: +additional processing is canceled. One advantage is that we always +have a 'safe' fallback to well-understood traditional LMTS formatting: TRST won't make more complex tables look worse than before. -So what are 'simple' tables? A table is simple enough if each of its TR -rows translates into at most one display line in LTMS formatting (excluding +What are 'simple' tables? A table is simple enough if each of its TR +rows translates into at most one display line in LMTS formatting (excluding leading and trailing line breaks), and the width required by each row -(before as well as after fixup) does not exceed the availabe screen size. -Note that his excludes all tables where some of the cells are marked up as +(before as well as after fixup) does not exceed the available screen size. +Note that this excludes all tables where some of the cells are marked up as block elements ('paragraphs'). Tables that include nested TABLE elements are always specifically excluded, but the inner tables may be subject to TRST handling. Also excluded are some constructs that indicate that markup @@ -127,7 +127,7 @@ for testing. Most of the typical tables in typical Web pages aren't used in a way that can benefit from the TRST approach. Parts of such tables may still end up getting shifted left or right by the TRST code when that doesn't improve anything, but I haven't seen it make things -relly worse so far (with the current code). +really worse so far (with the current code). TRST and Partial Display ------------------------ @@ -151,7 +151,7 @@ To summarize: - TRST is a solution that works in many cases where lack of tabular support was most annoying. - TRST doesn't implement a full table model, and it is extremely unlikely - that it will ever be the basis for that. So keep on exploring external + that it will ever be the basis for that. Keep on exploring external solutions, or perhaps waiting for (better: working on) a more fundamental redesign of Lynx's rendering engine. diff --git a/docs/README.defines b/docs/README.defines index ba80b0cc..7f728895 100644 --- a/docs/README.defines +++ b/docs/README.defines @@ -106,27 +106,19 @@ Both: Related to experimental (unsupported) character style code ------------------------------------------------------------ -# -DUSE_COLOR_STYLE (see INSTALLATION, Section II-1c) probably needs -DNCURSES +# -DUSE_COLOR_STYLE (see INSTALLATION, Section II-1c) needs SVr4 curses # -DUSE_HASH (see INSTALLATION, Section II-1c) probably needs the above # -DLINKEDSTYLES (see INSTALLATION, Section II-1c) probably needs the above Other general ------------- -# -DDONT_TRACK_INTERNAL_LINKS - Handle following links to same doc differently. -# -DEXP_CHARTRANS_AUTOSWITCH (see INSTALLATION, Section II-1c) # -DIGNORE_CTRL_C Define if Control-C shouldn't exit lynx. -# -DLY_FIND_LEAKS (see INSTALLATION, Section II-1c) # -DNO_CPU_LIMIT Disables Max CPU timeout (includes CLOCKS_PER_SECOND) # -DNO_DUMP_WITH_BACKSPACES Disables -with_backspaces code -# -DNSL_FORK For fork-based name server lookups that can be 'z'apped. -# -DSYSLOG_REQUESTED_URLS -# if you would like logging of client requests via syslog() # -DUSE_VASPRINT Use vasprintf() function -# -DUSE_ZLIB (see INSTALLATION) -# -DDECLARE_WAIS_LOGFILES see comments in makefile.in # -DNO_RULES Disables code for CERN-style rules files -# -DHAVE_SIGACTION Can use sigaction() and related functions # -DMISC_EXP Enable some truly experimental stuff +# -DINACTIVE_INPUT_STYLE_VH Different style for showing inactive text fields Untested -------- @@ -143,7 +135,6 @@ they are set. Normally installers shouldn't have to care about these symbols. COOKIE_FILE LYMain.c default cookie file in HOME dir -SAVE_TIME_NOT_SPACE HTString.c minimize number of some malloc calls SHOW_WHEREIS_TARGETS LYCurses.h whereis search highlighting USE_KEYMAPS LYCurses.h use of .lynx-keymaps files |