1
0
mirror of https://github.com/rkd77/elinks.git synced 2024-11-04 08:17:17 -05:00
elinks/doc
2006-01-10 22:18:03 +01:00
..
man Preprocess elinks.1.in and elinkskeys.5 to add title and date fields 2006-01-10 17:09:02 +01:00
tools Remove obsolete elinksmanual(1) link. 2006-01-10 22:10:37 +01:00
.gitignore Revive doc/.gitignore 2005-09-23 15:08:02 +02:00
.vimrc Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
bittorrent.txt Add a little documentation about the BitTorrent client 2005-10-03 21:56:27 +02:00
bookmarks.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
code2doc.conf More perl snacks; added macro:[] for #define'd values; api dom/scanner.h 2006-01-09 14:06:47 +01:00
color-model.txt Remove now useless $Id: lines. 2005-10-21 09:14:07 +02:00
dev-intro.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
ecmascript.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
events.txt Document that pre-format-html hooks are given a session pointer. 2005-12-17 16:01:15 +00:00
exmode.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
faq.txt Remove useless FAQ entry 2006-01-10 18:55:06 +01:00
feedback.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
hacking.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
index.txt Remove now useless $Id: lines. 2005-10-21 09:14:07 +02:00
installation.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
introduction.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
lua-scripting.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
mailcap.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
Makefile More dependencies. 2006-01-10 22:18:03 +01:00
manual.txt Add a little documentation about the BitTorrent client 2005-10-03 21:56:27 +02:00
marks.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
mime.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
perl.pod Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
README Remove now useless $Id: lines. 2005-10-21 09:14:07 +02:00
remote.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
small.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
tabs.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
terminals.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00
urlshortcuts.txt Drop useless comment block now that CVS Id tags are gone 2006-01-03 14:28:26 +01:00

			Overview of the ELinks documentation

There is only limited documentation available for ELinks so far, sorry. It
basically consists of the documents in this directory and the features.conf,
README and INSTALL files in the project's root directory.

The files you will find in this directory are manpages living in the man/
directory and a bunch of .html and especially .txt (wait, you expect HTML
browser to carry its documentation around in HTML?) documents. The index.txt
file contains the table of contents which should help you navigating between
the files.

Tools
-----

The manual is written in asciidoc, however you will also need xmlto to process
docbook XML generated by asciidoc into manpages and the html-chunked manual.
If you want to translate .pod files you need pod2html.

All these tools are checked by configure, thus to successfully build all the
possible documentation (with the tools available on the system), just run

	$ make all-docs

in the doc/ directory.

Contributing
------------

Contributions are very warmly welcomed, whether it is fixing typos or bad
grammar, rewritings or new material. Any information relevant to ELinks usage
can be included in the manual, including FAQ material, tips and cheats ;)

There is no strict codingstyle, but please don't limit your use of whitespaces
and take a look at the style used in the current documents to get ideas of what
is reasonable.

Contributions should be sent to Jonas Fonseca <fonseca@diku.dk> or to the
ELinks mailing list. If you are changing something in an existing document,
please read about how to make unified patches in the Patches section of the
doc/hacking.txt file.