***************
*** 11,28 ****
  Unix/Linux.  When I was a newbie of Linux, I felt I always could not find
  the man pages that I need.  I believed the man pages must be somewhere in the
  system, but I just could not find the name of it.
- 
  So I thought, maybe we need new graphical man page system.  I don't like
  xman because it looks ugly and it is difficult to use (I felt).  I think
  gnome-help-browser is too slow and it eats too much memory (about 12M on my
  system).  It does not have index search function, and it can not be operated
  with keyboard shortcuts.
- 
  I think an ideal help system must have the index search function (just like
  the help system on windoze).  This will help a newbie to find the
  information that s/he needs, and sometimes help him/her go around to see
  what other man pages are there in the system, in his leisure time.
- 
  Gman is nothing else but a simple front-end for the usual man page system.
  The most basic job of gman is to build a database for all the man pages
  and display them (or part of them) on the screen.  When user decides to read
--- 11,28 ----
  Unix/Linux.  When I was a newbie of Linux, I felt I always could not find
  the man pages that I need.  I believed the man pages must be somewhere in the
  system, but I just could not find the name of it.
+ 
  So I thought, maybe we need new graphical man page system.  I don't like
  xman because it looks ugly and it is difficult to use (I felt).  I think
  gnome-help-browser is too slow and it eats too much memory (about 12M on my
  system).  It does not have index search function, and it can not be operated
  with keyboard shortcuts.
+ 
  I think an ideal help system must have the index search function (just like
  the help system on windoze).  This will help a newbie to find the
  information that s/he needs, and sometimes help him/her go around to see
  what other man pages are there in the system, in his leisure time.
+ 
  Gman is nothing else but a simple front-end for the usual man page system.
  The most basic job of gman is to build a database for all the man pages
  and display them (or part of them) on the screen.  When user decides to read
***************
*** 38,44 ****
  $ make
  (change to super user if needed)
  # make install
- 
  This will put gman binary in /usr/local/bin, and its manual page
  in /usr/local/man/man1.
  
--- 38,44 ----
  $ make
  (change to super user if needed)
  # make install
+ 
  This will put gman binary in /usr/local/bin, and its manual page
  in /usr/local/man/man1.
  
***************
*** 48,60 ****
  It's easy to write a simple software that can work, but the problem is
  in making it work better.  It took me a lot of time to improve it's UI
  and some other little things, such as:
- 
  1. Multi-threading.
     When you have many manual pages on your system, some of the work (such
     as update window) will take a lot of time.  So I used multi-thread
     programming, which means that the user can input new commands at any
     time, without waiting for the previous operation to end.
- 
  2. ~/.gman file.
     Every time gman starts up, it will read some configuration information
     from $HOME/.gman file.  And every time gman exits, it will also write the
--- 48,60 ----
  It's easy to write a simple software that can work, but the problem is
  in making it work better.  It took me a lot of time to improve it's UI
  and some other little things, such as:
+ 
  1. Multi-threading.
     When you have many manual pages on your system, some of the work (such
     as update window) will take a lot of time.  So I used multi-thread
     programming, which means that the user can input new commands at any
     time, without waiting for the previous operation to end.
+ 
  2. ~/.gman file.
     Every time gman starts up, it will read some configuration information
     from $HOME/.gman file.  And every time gman exits, it will also write the
***************
*** 64,74 ****
  To do
  =====
  
-  * autoconf support, especially if GNOME support is included.
   * use of gettext for easier translation to other languages.
-  * improvment for the parser when reading the ~/.gman file (context.c).
   * internal method of displaying manual pages, not with xterm.
- 
  Your comments and suggestions will be the most important for gman
  development.  Patches (bug fixes or code additions) are welcome.
  
--- 64,74 ----
  To do
  =====
  
   * use of gettext for easier translation to other languages.
+  * autoconf support, especially if GNOME support is included.
+  * improvement for the parser which reads the ~/.gman file (context.c).
   * internal method of displaying manual pages, not with xterm.
+ 
  Your comments and suggestions will be the most important for gman
  development.  Patches (bug fixes or code additions) are welcome.
  
