diff options
Diffstat (limited to 'lynx_help/keystrokes/option_help.html')
| -rw-r--r-- | lynx_help/keystrokes/option_help.html | 188 |
1 files changed, 93 insertions, 95 deletions
diff --git a/lynx_help/keystrokes/option_help.html b/lynx_help/keystrokes/option_help.html index 594010d9..6d9ae0f6 100644 --- a/lynx_help/keystrokes/option_help.html +++ b/lynx_help/keystrokes/option_help.html @@ -17,7 +17,6 @@ compiled in or chosen in `lynx.cfg':<P> <LI><A HREF="#CK">Cookies</A> <LI><A HREF="#ED">Editor</A> <LI><A HREF="#EM">Emacs keys</A> -<LI><A HREF="#LL">Execution links</A> <LI><A HREF="#KM">Keypad mode</A> <LI><A HREF="#LE">Line edit style</A> <LI><A HREF="#PM">Personal Mail Address</A> @@ -26,10 +25,13 @@ compiled in or chosen in `lynx.cfg':<P> <LI><A HREF="#CL">Show cursor for current link or option</A> <LI><A HREF="#UM">User Mode</A> <LI><A HREF="#VI">VI keys</A> +<LI><A HREF="#DC">Display Character set</A> <LI><A HREF="#DV">X DISPLAY variable</A></UL> <LI>Document Layout <UL> -<LI><A HREF="#tagsoup">HTML error tolerance</A> +<LI><A HREF="#AD">Assumed document character set</A> +<LI><A HREF="#JK">Raw 8-bit or CJK mode</A> +<LI><A HREF="#tagsoup">HTML error recovery</A> <LI><A HREF="#PU">Pop-ups for select fields</A> <LI><A HREF="#SI">Show Images</A> <LI><A HREF="#VB">Verbose Images</A></UL> @@ -37,16 +39,12 @@ compiled in or chosen in `lynx.cfg':<P> <UL> <LI><A HREF="#MB">Multi-bookmarks</A> <LI><A HREF="#BF">Bookmark file</A></UL> -<LI>Character Set Options -<UL> -<LI><A HREF="#AD">Assumed document character set</A> -<LI><A HREF="#DC">Display Character set</A> -<LI><A HREF="#JK">Raw 8-bit or CJK mode</A></UL> <LI>File Management Options <UL> <LI><A HREF="#FT">FTP sort criteria</A> <LI><A HREF="#LD">Local directory sort criteria</A> -<LI><A HREF="#DF">Show dot files</A></UL> +<LI><A HREF="#DF">Show dot files</A> +<LI><A HREF="#LL">Execution links</A></UL> <LI>Headers transferred to remote server <UL> <LI><A HREF="#PC">Preferred Document Charset</A> @@ -70,7 +68,7 @@ If set to 'ON' then the CTRL-P, CTRL-N, CTRL-F and CTRL-B keys will be mapped to up-arrow, down-arrow, right-arrow and left-arrow respectively. Otherwise, they remain mapped to their configured bindings (normally UP_TWO lines, DOWN_TWO lines, NEXT_PAGE and PREV_PAGE respectively). -<p>Note: setting emacs keys does not affect the line-editor bindings. +<p>Note: setting emacs keys does not affect the line-editor bindings. <H1><A NAME="LL">Execution links</A></H1> @@ -85,13 +83,13 @@ see Lynx Navigation) and having every link numbered (numbered links) so that the links may be selected by numbers instead of moving to them with the arrow keys. You can also number form fields. -<H1><A NAME="LE">Line edit style</A></H1> - -This allows you to set alternate key bindings for the built-in line editor, -if your system administrator has installed -<A HREF="alt_edit_help.html">Alternate Bindings</A>. -Otherwise, Lynx uses the <A HREF="edit_help.html">Default Binding</A>. - +<H1><A NAME="LE">Line edit style</A></H1> + +This allows you to set alternate key bindings for the built-in line editor, +if your system administrator has installed +<A HREF="alt_edit_help.html">Alternate Bindings</A>. +Otherwise, Lynx uses the <A HREF="edit_help.html">Default Binding</A>. + <H1><A NAME="PM">Personal Mail Address</A></H1> You may set your mail address here so that when mailing messages @@ -167,38 +165,67 @@ for beginners. <dt><EM>Advanced</EM>: The URL is shown on the status line. </dl> -<H1><A NAME="tagsoup">HTML error tolerance</A></H1> - -Lynx often has to deal with invalid HTML markup. It always tries to -recover from errors, but there is no universally correct way for doing -this. As a result, there are two parsing modes: -"<DFN>SortaSGML</DFN>" attempts to enforce valid nesting of most tags -at an earlier stage of processing, while "<DFN>TagSoup</DFN>" relies -more on the HTML rendering stage to mimic the behavior of some other -browsers. -You can also switch between these modes with the CTRL-V key, and the -default can be changed in lynx.cfg or with the -tagsoup command line -switch. - -<P> -The "SortaSGML" mode will often appear to be more strict, and makes -some errors apparent that are otherwise unnoticeable. One particular -difference is the handling of block elements or -<li>..</li> inside <a HREF="some.url">..</a>. -Invalid nesting like this may turn anchors into hidden links which -cannot be easily followed, this is avoided in "TagSoup" mode. See the -<a href="follow_help.html">help on following links by -number</a> for more information on hidden links. Often pages may be -more readable in "TagSoup" mode, but sometimes the opposite is true. -Most documents with valid HTML, and documents with only minor errors, -should be rendered the same way in both modes. - -<P> -If you are curious about what goes on behind the scenes, but find that -the information from the -trace switch is just too much, Lynx can be -started with the -preparsed switch; going into SOURCE mode ('\' key) -and toggling the parsing mode (with CTRL-V) should then show some of -the differences. +<H1><A NAME="AD">Assumed document character set</A></H1> + +This changes the handling of documents which do not explicitly specify +a charset. Normally Lynx assumes that 8-bit characters in those documents +are encoded according to iso-8859-1 (the official default for HTTP protocol). +Unfortunately, many non-English web pages forget to include proper charset +info; this option helps you browse those broken pages if you know somehow +what the charset is. When the value given here or by an -assume_charset +command-line flag is in effect, Lynx will treat documents as if they were +encoded accordingly. Option is active when 'Raw 8-bit or CJK Mode' is OFF. + +<H1><A NAME="JK">Raw 8-bit or CJK mode</A></H1> + +This is set automatically, but can be toggled manually in certain cases: +it toggles whether 8-bit characters are assumed to correspond with the display +character set and therefore are processed without translation +via the chartrans conversion tables. ON by default when the display +character set is one of the Asian (CJK) sets and the 8-bit characters +are Kanji multibytes. OFF for the other display character sets, +but can be turned ON when the document's charset is unknown +(e.g., is not ISO-8859-1 and no charset parameter was specified +in a reply header from an HTTP server to indicate what it is), +but you have no better idea than viewing it as from display character set +(see 'assumed document character set' for best choice). Should be OFF +when an Asian (CJK) set is selected but the document is ISO-8859-1 +or another 'assumed document character set'. The setting can also be toggled +via the RAW_TOGGLE command, normally mapped to '@', and at startup +via the -raw switch. + +<H1><A NAME="tagsoup">HTML error recovery</A></H1> + +Lynx often has to deal with invalid HTML markup. It always tries to +recover from errors, but there is no universally correct way for doing +this. As a result, there are two parsing modes: +"<DFN>SortaSGML</DFN>" attempts to enforce valid nesting of most tags +at an earlier stage of processing, while "<DFN>TagSoup</DFN>" relies +more on the HTML rendering stage to mimic the behavior of some other +browsers. +You can also switch between these modes with the CTRL-V key, and the +default can be changed in lynx.cfg or with the -tagsoup command line +switch. + +<P> +The "SortaSGML" mode will often appear to be more strict, and makes +some errors apparent that are otherwise unnoticeable. One particular +difference is the handling of block elements or +<li>..</li> inside <a HREF="some.url">..</a>. +Invalid nesting like this may turn anchors into hidden links which +cannot be easily followed, this is avoided in "TagSoup" mode. See the +<a href="follow_help.html">help on following links by +number</a> for more information on hidden links. Often pages may be +more readable in "TagSoup" mode, but sometimes the opposite is true. +Most documents with valid HTML, and documents with only minor errors, +should be rendered the same way in both modes. + +<P> +If you are curious about what goes on behind the scenes, but find that +the information from the -trace switch is just too much, Lynx can be +started with the -preparsed switch; going into SOURCE mode ('\' key) +and toggling the parsing mode (with CTRL-V) should then show some of +the differences. <!-- LP's version - for reference - TD @@ -221,10 +248,10 @@ from lynx.cfg or command line switch. <H1><A NAME="SI">Show Images</A></H1> Text-based browser cannot show images directly, so we have a choice: -ignore all images without ALT= text string (this is also switched by -<A HREF="../Lynx_users_guide.html#[-key">'[' key</A>), -show labels (see also "verbose images" for choice between [IMAGE] and filename), -use links for every image to make it possible to download them +<em>ignore all</em> images without ALT= text string +(this is also switched by <A HREF="../Lynx_users_guide.html#[-key">'[' key</A>), +<em>show labels</em> (see also "verbose images" for choice between [IMAGE] and filename), +<em>use links</em> for every image to make it possible to download them (also switched by <A HREF="../Lynx_users_guide.html#*-key">'*' key</A>). Changing these settings will not be saved but could be made permanent by changing the respective settings in lynx.cfg. @@ -242,7 +269,20 @@ If set to 'ON' then the lowercase h, j, k and l keys will be mapped to left-arrow, down-arrow, up-arrow and right-arrow respectively. <p>The uppercase H, J, K, and L keys remain mapped to their configured bindings (normally HELP, JUMP, KEYMAP and LIST, respectively). -<p>Note: setting vi keys does not affect the line-editor bindings. +<p>Note: setting vi keys does not affect the line-editor bindings. + +<H1><A NAME="DC">Display Character set</A></H1> + +This allows you to set up the default character set for your specific terminal. +The display character set provides a mapping from the character encodings +of viewed documents and from HTML entities into viewable characters. +It should be set according to your terminal's character set +so that characters other than 7-bit ASCII can be displayed correctly, +using approximations if necessary, +<A HREF="test_display.html">try the test here</A>. +Since Lynx now supports a wide range of platforms +it may be useful to note that cpXXX codepages are used within IBM PC computers, +and windows-xxxx within native MS-Windows applications. <H1><A NAME="DV">X DISPLAY variable</A></H1> @@ -280,48 +320,6 @@ if subdirectories are included (e.g., './BM/lynx_bookmarks.html'). Lynx will create bookmark files when you first 'a'dd a link, but any subdirectories in the filepath must already exist. -<H1><A NAME="AD">Assumed document character set</A></H1> - -This changes the handling of documents which do not explicitly specify -a charset. Normally Lynx assumes that 8-bit characters in those documents -are encoded according to iso-8859-1 (the official default for HTTP protocol). -Unfortunately, many non-English web pages forget to include proper charset -info; this option helps you browse those broken pages if you know somehow -what the charset is. When the value given here or by an -assume_charset -command-line flag is in effect, Lynx will treat documents as if they were -encoded accordingly. Option is active when 'Raw 8-bit or CJK Mode' is OFF. - -<H1><A NAME="DC">Display Character set</A></H1> - -This allows you to set up the default character set for your specific terminal. -The display character set provides a mapping from the character encodings -of viewed documents and from HTML entities into viewable characters. -It should be set according to your terminal's character set -so that characters other than 7-bit ASCII can be displayed correctly, -using approximations if necessary, -<A HREF="test_display.html">try the test here</A>. -Since Lynx now supports a wide range of platforms -it may be useful to note that cpXXX codepages are used within IBM PC computers, -and windows-xxxx within native MS-Windows applications. - -<H1><A NAME="JK">Raw 8-bit or CJK mode</A></H1> - -This is set automatically, but can be toggled manually in certain cases: -it toggles whether 8-bit characters are assumed to correspond with the display -character set and therefore are processed without translation -via the chartrans conversion tables. ON by default when the display -character set is one of the Asian (CJK) sets and the 8-bit characters -are Kanji multibytes. OFF for the other display character sets, -but can be turned ON when the document's charset is unknown -(e.g., is not ISO-8859-1 and no charset parameter was specified -in a reply header from an HTTP server to indicate what it is), -but you have no better idea than viewing it as from display character set -(see 'assumed document character set' for best choice). Should be OFF -when an Asian (CJK) set is selected but the document is ISO-8859-1 -or another 'assumed document character set'. The setting can also be toggled -via the RAW_TOGGLE command, normally mapped to '@', and at startup -via the -raw switch. - <H1><A NAME="FT">FTP sort criteria</A></H1> This allows you to specify how files will be sorted within FTP listings. |