Re: More webbrowsers for the list at FAQ8

> > Some of the browsers available are not on the list at http://www.openbsd.org/faq/faq8.html#Browsers. I have added them in the diff below, and also tweaked the explanation on installing/ports vs packages to make it less repetitive.
> > Brett.

> 
> This rewording is putting too much emphasis on installing from ports,
> packages should be first and more prominent.
> 

OK, I reworded that part again. Though why is the policy to emphasize packages over ports these days?

Also since I sent in the last patch, I noticed that kazehakase is no longer in ports, so removed it from the list.



Index: www/faq/faq8.html
===================================================================
RCS file: /cvs/www/faq/faq8.html,v
retrieving revision 1.234
diff -u -r1.234 faq8.html
--- www/faq/faq8.html	28 Nov 2011 03:24:31 -0000	1.234
+++ www/faq/faq8.html	31 Jan 2012 22:57:09 -0000
@@ -1030,7 +1030,7 @@
 <p>
 <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=lynx&amp;sektion=1">Lynx</a>,
 a text-based browser, is in the base system, and has SSL support.
-Other browsers in the <a href="#Ports">ports tree</a>, include (in
+Other browsers available include (in
 no particular order):
 
 <p>
@@ -1048,8 +1048,6 @@
  <li><a href="http://www.opera.com/">Opera</a> Commercial browser, i386
    only (requires Linux emulation).
  <li><a href="http://www.w3.org/Amaya/">Amaya</a> The W3C's browser and editor.
- <li><a href="http://kazehakase.sourceforge.jp/">Kazehakase</a>, a lightweight
-  browser able to use either the WebKit or Gecko rendering engines.
  <li><a href="http://www.twotoasts.de/index.php?/pages/midori_summary.html">Midori</a>,
    a WebKit-based browser from the Xfce project.
  <li><a href="http://sites.google.com/a/chromium.org/dev/Home">Chromium</a>
@@ -1060,27 +1058,41 @@
  <li><a href="http://www.conkeror.org/">Conkeror</a>
   a keyboard-oriented, highly-customizable, highly-extensible web browser
   based on Mozilla.
+ <li><a href="http://surf.suckless.org/">Surf</a>
+  Extremely minimal webbrowser based on webkit/gtk+. 
+ <li><a href="http://www.dillo.org/">Dillo</a>
+  Fast and lightweight, based on Fast Light ToolKit and custom rendering engine (note: no javascript support).
+ <li><a href="http://www.netsurf-browser.org/">Netsurf</a>
+  Lightweight web browser based on custom rendering engine (note: no javascript support).
+ <li><a href="http://projects.gnome.org/epiphany/">Epiphany</a>
+  GNOME web browser based on webkit.
+ <li><a href="https://code.google.com/p/arora/">Arora</a>
+  Simple Qt4-based browser using WebKit.
 </ul>
 
 <p>
 <b>Console (Text mode) Browsers</b>
 <ul>
- <li><a href="http://elinks.cz/">elinks</a> Feature-rich, can render
+ <li><a href="http://elinks.cz/">Elinks</a> Feature-rich, can render
    both frames and tables, highly customizable.
- <li><a href="http://www.w3m.org/">w3m</a> Has table and frame
+ <li><a href="http://www.w3m.org/">W3M</a> Has table and frame
    support (also has a graphical mode). 
- <li><a href="http://artax.karlin.mff.cuni.cz/~mikulas/links/">links</a>
+ <li><a href="http://artax.karlin.mff.cuni.cz/~mikulas/links/">Links</a>
    Has table support.
+ <li><a href="http://freecode.com/projects/retawq">Retawk</a>
+  Interactive, multi-threaded text mode web browser.
 </ul>
 
 <p>
-You will find all these in the <a href="faq15.html">packages
-collection</a>.  All the above mentioned browsers are
-located in <tt>/usr/ports/www/</tt> after the installation of the ports
-tree.  Most are also available as pre-compiled 
+Most of the abovementioned browsers are available as pre-compiled
 <a href="faq15.html#PkgMgmt">packages</a>, available on the 
 <a href="../ftp.html">FTP servers</a> and on the 
-<a href="../orders.html">CD-ROM</a>.  As most of the graphical browsers
+<a href="../orders.html">CD-ROM</a>.  
+After the installation of the <a href="#Ports">ports tree</a>, all
+can also be found in the <tt>/usr/ports/www/</tt> directory.
+
+<p>
+As most of the graphical browsers
 are very large and require quite some time to download and compile, 
 one should <i>seriously</i> <a href="#PortsvsPkgs">consider</a> the
 use of packages where available.