1
0
Fork 0
Go to file
Petr Baudis c94471fde8 Throw in install-sh, missing, and mkinstalldirs, and detect BSD install
presence in the configure script.
2005-09-17 20:00:58 +02:00
Unicode Convert part of the build to the new build system 2005-09-15 21:03:56 +02:00
config Throw in install-sh, missing, and mkinstalldirs, and detect BSD install 2005-09-17 20:00:58 +02:00
contrib Merge with git+ssh://pasky.or.cz/srv/git/elinks.git 2005-09-17 08:45:23 +02:00
debian Convert part of the build to the new build system 2005-09-15 21:03:56 +02:00
doc Merge with git+ssh://pasky.or.cz/srv/git/elinks.git 2005-09-17 08:45:23 +02:00
intl Convert part of the build to the new build system 2005-09-15 21:03:56 +02:00
po Fix building of .gmo files 2005-09-16 02:54:38 +02:00
src Fix building when commit-id is not found 2005-09-17 16:21:35 +02:00
test Convert part of the build to the new build system 2005-09-15 21:03:56 +02:00
.gitignore Remove traces of nuts and automake. 2005-09-16 13:44:33 +02:00
.vimrc Add root .vimrc which didn't make it in the CVS->GIT convertion. 2005-09-15 17:38:20 +02:00
ABOUT-NLS Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
AUTHORS Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
BUGS Reformat BUGS a bit. Test commit. :-) 2005-09-15 17:41:42 +02:00
COPYING Clarify the GPL upgrades policy a bit, and propose an addition 2005-09-17 03:33:36 +02:00
ChangeLog Talk about gitweb as well. 2005-09-15 17:19:10 +02:00
INSTALL Significantly retouch the OpenSSL vs. GNUTLS tractate. 2005-09-17 04:01:08 +02:00
Makefile Fix starting a build from a subdirectory ELBuild-wise 2005-09-16 02:07:36 +02:00
Makefile.base Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
Makefile.config.in Put the commit ID in the version string 2005-09-17 14:45:59 +02:00
Makefile.lib Indent the output of CC and LINK 2005-09-17 14:41:51 +02:00
NEWS Move notice of GNUTLS >= 1.2 requirement to NEWS file 2005-09-17 11:54:14 +02:00
README Retouch the history section (does it really belong here?). Also various 2005-09-17 03:40:37 +02:00
SITES Merge with git+ssh://pasky.or.cz/srv/git/elinks.git 2005-09-17 08:45:23 +02:00
THANKS Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00
TODO Remove the ref. to now non-existing doc/book/TODO. 2005-09-17 03:16:50 +02:00
autogen.sh Remove traces of nuts and automake. 2005-09-16 13:44:33 +02:00
configure.in Throw in install-sh, missing, and mkinstalldirs, and detect BSD install 2005-09-17 20:00:58 +02:00
features.conf Initial commit of the HEAD branch of the ELinks CVS repository, as of 2005-09-15 15:58:31 +02:00

README

ELinks - an advanced web browser
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

ELinks is an advanced and well-established feature-rich text mode web
(HTTP/FTP/..) browser. ELinks can render both frames and tables, is highly
customizable and can be extended via scripts. It is very portable and runs
on a variety of platforms.

The ELinks official website is available at

	http://elinks.or.cz/

Please see the SITES file for mirrors or other recommended sites.  If you
want to install ELinks on your computer, see the INSTALL file for further
instructions.

A good start point is documentation files available in doc/, especially the
file named index.txt.

If you want to request features or report bugs, see community information at
http://elinks.or.cz/community.html and feedback information available at
http://elinks.or.cz/feedback.html.

If you want to write some patches, please first read the doc/hacking.txt
document.

If you want to add a new language or update the translation for an existing
one, please read po/README document.

If you want to write some documentation, well, you're welcome! ;)



Historical notes
~~~~~~~~~~~~~~~~

Initially, ELinks was a development version of Links (Lynx-like text WWW
browser), with more liberal features policy and development style.  Its purpose
was to provide an alternative to Links, and to test and tune various new
features, but still provide good rock-solid releases inside stable branches.

Why not contribute to Links instead?  Well, first I made a bunch of patches for
the original Links, but Mikulas wasn't around to integrate them, so I started
releasing my fork. When he came back, a significant number of them got refused
because Mikulas did not like them, as he just wouldn't have any use for them
himself.  He wants to keep Links with a relatively closed feature set and merge
only new features which he himself needs.  It has advantages that the tree is
very narrow and the code is small and contains very little bloat.

ELinks, on the contrary, aims to provide a full-featured web browser, superior
to both lynx and w3m and with the power (but not slowness and memory usage) of
Mozilla, Konqueror and similar browsers. However, to prevent drastic bloating
of the code, the development is driven in the course of modularization and
separation of add-on modules (like cookies, bookmarks, ssl, scripting etc).

For more details about ELinks history, please see

	http://elinks.or.cz/history.html

If you are more interested in the history and various Links clones and versions,
you can examine the website at

	http://links.sf.net/



$Id: README,v 1.24 2005/01/11 15:51:02 jonas Exp $

vim: textwidth=80