- Have the client react properly to the default .etx (and
.ETX) suffix used to distinguish setext-formatted matter from
mere plaintext (the suffix stands for Enhanced
TeXt).
- In Lynx-2.3 Beta, the current distribution
version, this is already done in source code, so documents with such
suffixes automatically are treated as MIME type
text/x-setext. By default the Lynx does not know about the
sv, however... after all there could be more than one setext
client in existence. So we have to alias the two somehow.
Add those two lines to your ($HOME/) lynx.cfg (or equivalent)
configuration file:
VIEWER:text/x-setext:sv %s
PRINTER:setext viewer:sv %s %s:TRUE
- Older Lynxes and possibly other clients may require to have the
binding suffix--MIME-type defined explicitly. In $HOME/.lynx.cfg this
would look like this:
SUFFIX:.etx:text/x-setext
- Now, quit, do 'rehash' and launch the client by pointing it at any
setext file ('sv.man' in the package will do nicely). The browser
should launch the sv automatically, and have it display the
setext doc in a structured manner. Upon quitting/ leaving the
sv you should be returned back to the WWW-client.
- Observe that once a browser has been configured to recognize setext
and process it automatically the only way to extract/save such documents
locally will be by using the
-source or equivalent
fetch-raw-document option of your browser. In the Lynx this would
be:
% lynx -source scheme://site/path/file.etx
That's it, folks.