aniani/elinks
1
0
Fork 0
mirror of https://github.com/rkd77/elinks.git synced 2024-11-04 08:17:17 -05:00
Code
f513eefab9
elinks/doc
History
Petr Baudis 13ce7f6f81 Converted doc/ to ELBuild
2005-09-16 04:38:48 +02:00
..
man Fix starting a build from a subdirectory ELBuild-wise 2005-09-16 02:07:36 +02:00
tools Remove now obsolete .cvsignore files. 2005-09-15 18:33:20 +02:00
.vimrc Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
bookmarks.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
color-model.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +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 Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
events.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
exmode.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
faq.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
feedback.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
get-cvs-docs Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
hacking.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
index.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
installation.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
introduction.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
lua-scripting.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
mailcap.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
Makefile Converted doc/ to ELBuild 2005-09-16 04:38:48 +02:00
manual.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
marks.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
mime.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02: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 Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
remote.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
small.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
tabs.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
terminals.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
urlshortcuts.txt Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00

README 

			Overview of the ELinks documentation

There is only limited documentation available for ELinks, 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 the man pages 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?). The index.txt file
contains the table of contents listing all these 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 so that to successfully build all
possible documentation (with the tools available on the system) run

	$ make all-docs

in the doc/ directory.

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

Contributions are very warmly welcomed. Wether it be fixing of typos or bad
grammar, rewritings or new material. All info 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 whitespace
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>. If your changing
something in an existing document please read about how to make unified patches
in the Patches section of the doc/hacking.txt file.

$Id: README,v 1.14 2005/05/24 19:05:14 jonas Exp $