1
0
mirror of https://github.com/rkd77/elinks.git synced 2024-12-04 14:46:47 -05:00
Go to file
2005-09-17 08:14:20 +02:00
config
contrib No more $ld$s. 2005-09-15 20:03:22 -04:00
debian
doc Converted doc/ to ELBuild 2005-09-16 04:38:48 +02:00
intl
po Fix building of .gmo files 2005-09-16 02:54:38 +02:00
src block_itrm(): drop useless intermediate variable. 2005-09-16 17:20:12 +02:00
test
Unicode
.gitignore Remove traces of nuts and automake. 2005-09-16 13:44:33 +02:00
.vimrc
ABOUT-NLS
AUTHORS
autogen.sh Remove traces of nuts and automake. 2005-09-16 13:44:33 +02:00
BUGS
ChangeLog
configure.in Define PACKAGE and VERSION macros in config.h. 2005-09-16 13:54:26 +02:00
COPYING
features.conf
INSTALL
Makefile Fix starting a build from a subdirectory ELBuild-wise 2005-09-16 02:07:36 +02:00
Makefile.base
Makefile.config.in Add missed CONFIG_NLS to Makefile.config 2005-09-17 08:14:20 +02:00
Makefile.lib Fix dependencies tracking and default clean rule. 2005-09-16 13:48:22 +02:00
NEWS
README
SITES
THANKS
TODO

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 welcomed ;)



History
~~~~~~~

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.
If you are more interested, you can examine the Links website at
http://links.sf.net/.

Why not contribute to Links instead?  Well, first I made a bunch of patches for
the original Links, but 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 possibilities of 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,
lua etc).

For more about ELinks history, see http://elinks.or.cz/history.html




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

vim: textwidth=80