15 files changed, 179 insertions, 123 deletions
diff --git a/README b/README
index 82bf5466..16c4cadb 100644
--- a/README
+++ b/README
@@ -80,9 +80,11 @@ separate gems are made/installed for sisu v5 & sisu v6 contained in source:
 for individual steps (create, build, install) see rake options, rake -T to
 specify sisu version for sisu installed via gem
 
-  sisu _5.3.0_ --version
+  gem search sisu
 
-  sisu _6.0.0_ --version
+  sisu _5.3.3_ --version
+
+  sisu _6.0.3_ --version
 
 to uninstall sisu installed via gem
 
@@ -111,7 +113,6 @@ ruby setup.rb setup
 #[as root:]
 ruby setup.rb install
 
-
 further information:
 <http://i.loveruby.net/en/projects/setup/>
 <http://i.loveruby.net/en/projects/setup/doc/usage.html>
@@ -2229,7 +2230,7 @@ at:
 
 
 
-* Generated by: SiSU 6.0.1 of 2014w05/2 (2014-02-04)
+* Generated by: SiSU 6.0.3 of 2014w05/4 (2014-02-06)
 * Ruby version: ruby 2.0.0p353 (2013-11-22) [i386-linux-gnu]
-* Last Generated on: 2014-02-04 23:45:43 -0500
+* Last Generated on: 2014-02-08 20:38:31 -0500
 * SiSU http://www.sisudoc.org/
diff --git a/data/doc/sisu/CHANGELOG_v5 b/data/doc/sisu/CHANGELOG_v5
index 5ce22013..639d9d90 100644
--- a/data/doc/sisu/CHANGELOG_v5
+++ b/data/doc/sisu/CHANGELOG_v5
@@ -44,6 +44,8 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_5.3.3.orig.tar.xz
   * nginx conf
   * cgi search forms pgsql & sqlite
 
+* documentation, minor update
+
 %% 5.3.2.orig.tar.xz (2014-02-05:05/3)
 http://sources.sisudoc.org/gitweb/?p=code/sisu.git;a=shortlog;h=refs/tags/sisu_5.3.2
 http://sources.sisudoc.org/gitweb/?p=code/sisu.git;a=shortlog;h=refs/tags/debian/sisu_5.3.2-1
diff --git a/data/doc/sisu/CHANGELOG_v6 b/data/doc/sisu/CHANGELOG_v6
index c1b1c58e..5cc8918e 100644
--- a/data/doc/sisu/CHANGELOG_v6
+++ b/data/doc/sisu/CHANGELOG_v6
@@ -34,6 +34,8 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_6.0.3.orig.tar.xz
   * nginx conf
   * cgi search forms pgsql & sqlite
 
+* documentation, minor update
+
 %% 6.0.2.orig.tar.xz (2014-02-05:05/3)
 http://sources.sisudoc.org/gitweb/?p=code/sisu.git;a=shortlog;h=refs/tags/sisu_6.0.2
 http://sources.sisudoc.org/gitweb/?p=code/sisu.git;a=shortlog;h=refs/tags/debian/sisu_6.0.2-1
diff --git a/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_lng.yml b/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_lng.yml
index 4ab568ca..9b60f8c9 100644
--- a/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_lng.yml
+++ b/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_lng.yml
@@ -15,8 +15,9 @@
 #  #all:           'image'
 #% presentation/web directory, main path and subdirectories (most subdirectories are created automatically based on markup directory name)
 webserv:
-  url_root:     'http://www.sisudoc.org' #url to document root, without dir stub
-#  path:         '/var/www' #either (i) / [full path from root] or (ii) ~/ [home] or (iii) ./ [pwd] or (iv) will be made from home
+# url_root:     'http://www.sisudoc.org' #url to document root, without dir stub
+  url_root:     'http://192.168.1.108' #url to document root, without dir stub
+  path:         '/srv/www' #either (i) / [full path from root] or (ii) ~/ [home] or (iii) ./ [pwd] or (iv) will be made from home
 #  images:       '_sisu/image'
 #  man:          'man'
 #  cgi:          '/usr/local/lib/sisu-cgi'
@@ -130,6 +131,15 @@ program_set:
 #    flag:            true
 ##    action:          http://localhost:8081/cgi-bin/sisu_pgsql.cgi
 #    action:          http://search.sisudoc.org
-#    db:              sisu
+#    db:              manual
 #    title:           sample search form
 #promo:               sisu_search_libre, sisu_icon, sisu, open_society, fsf, ruby
+
+search:
+  sisu:
+    flag:            true
+    action:          http://192.168.1.108/cgi/sisu_search.cgi
+#   action:          http://192.168.1.108/cgi-bin/sisu_pgsql.cgi
+#    action:          http://search.sisudoc.org
+    db:              manual
+    title:           sample search form
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_howto.sst b/data/doc/sisu/markup-samples/manual/en/sisu_howto.sst
index 4a23bdfe..afba3e48 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_howto.sst
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_howto.sst
@@ -41,7 +41,7 @@ If SiSU is installed on your system usual man commands should be available, try:
 
 man sisu
 
-The SiSU man pages can be viewed online at:~{ generated from source using rman<br> http://polyglotman.sourceforge.net/rman.html <br>With regard to SiSU man pages the formatting generated for markup syntax is not quite right, for that you might prefer the links under:<br> http://www.jus.uio.no/sample }~
+The SiSU man pages can be viewed online at:~{ generated from source using rman \\ http://polyglotman.sourceforge.net/rman.html \\With regard to SiSU man pages the formatting generated for markup syntax is not quite right, for that you might prefer the links under: \\ http://www.jus.uio.no/sample }~
 
 An online version of the sisu man page is available here:
 
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_install_run.sst b/data/doc/sisu/markup-samples/manual/en/sisu_install_run.sst
index dfd56ec8..cadcde61 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_install_run.sst
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_install_run.sst
@@ -50,9 +50,11 @@ _1 rake gem_create_build_install_unstable # (to build and install sisu v6, alias
 for individual steps (create, build, install) see rake options, rake -T
 to specify sisu version for sisu installed via gem
 
-_1 sisu _5.3.0_ --version
+gem search sisu
 
-_1 sisu _6.0.0_ --version
+_1 sisu _5.3.3_ --version
+
+_1 sisu _6.0.3_ --version
 
 to uninstall sisu installed via gem
 
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_installation.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_installation.ssi
index f908bb6e..0c48c229 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_installation.ssi
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_installation.ssi
@@ -98,9 +98,9 @@ Once installed see man 8 sisu for information on additional programs that sisu m
 
 Further notes on install script.
 
-The install script is prepared using Rant, and a Rantfile *~rant is provided,~{ a Rantfile has been configured to do post installation setup }~ with more comprehensive install options, and post install and setup configuration and generation of first test file, if you have installed Stefan Lang's {~^ Rant }http://make.rubyforge.org/ ~{ http://make.rubyforge.org/ <br> http://rubyforge.org/frs/?group_id=615 }~ installed. While in the package directory, type: rant help, or rant -T, or to install SiSU _{as root}_, type:
+The install script is prepared using Rant, and a Rantfile *~rant is provided,~{ a Rantfile has been configured to do post installation setup }~ with more comprehensive install options, and post install and setup configuration and generation of first test file, if you have installed Stefan Lang's {~^ Rant }http://make.rubyforge.org/ ~{ http://make.rubyforge.org/ \\ http://rubyforge.org/frs/?group_id=615 }~ installed. While in the package directory, type: rant help, or rant -T, or to install SiSU _{as root}_, type:
 
-*install* is an install script prepared using Stefan Lang's {~^ Rant }http://make.rubyforge.org/ ~{ http://make.rubyforge.org/ <br> http://rubyforge.org/frs/?group_id=615 }~ It should work whether you have previously installed Rant or not. It has fairly comprehensive install options, and can do some post install and setup configuration and generation of first test file. For options type:
+*install* is an install script prepared using Stefan Lang's {~^ Rant }http://make.rubyforge.org/ ~{ http://make.rubyforge.org/ \\ http://rubyforge.org/frs/?group_id=615 }~ It should work whether you have previously installed Rant or not. It has fairly comprehensive install options, and can do some post install and setup configuration and generation of first test file. For options type:
 
 _1 ruby install -T
 
@@ -114,7 +114,7 @@ _1 ruby install base
 
 !_ installation with setup.rb
 
-{~^ setup.rb }http://i.loveruby.net/en/projects/setup/ is provided the package and will install SiSU~{ Minero Aoki<br> http://i.loveruby.net/en/projects/setup/doc/ }~ installation is a 3 step process~{ Installation instructions<br> http://i.loveruby.net/en/projects/setup/doc/usage.html }~ the following string assumes you are in the package directory and that you have root as sudo:
+{~^ setup.rb }http://i.loveruby.net/en/projects/setup/ is provided the package and will install SiSU~{ Minero Aoki \\ http://i.loveruby.net/en/projects/setup/doc/ }~ installation is a 3 step process~{ Installation instructions \\ http://i.loveruby.net/en/projects/setup/doc/usage.html }~ the following string assumes you are in the package directory and that you have root as sudo:
 
 _1 ruby setup.rb config && ruby setup.rb setup && sudo ruby setup.rb install
 
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_markup.sst b/data/doc/sisu/markup-samples/manual/en/sisu_markup.sst
index 69293637..fbd6d1f4 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_markup.sst
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_markup.sst
@@ -744,7 +744,7 @@ column three of row two, and so on
 
 a second form may be easier to work with in cases where there is not much information in each column
 
-*{markup example:}*~{ Table from the Wealth of Networks by Yochai Benkler<br> http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler }~
+*{markup example:}*~{ Table from the Wealth of Networks by Yochai Benkler \\ http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler }~
 
 code{
 
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_postgresql.sst b/data/doc/sisu/markup-samples/manual/en/sisu_postgresql.sst
index 574e307c..e5b0c4cb 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_postgresql.sst
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_postgresql.sst
@@ -54,29 +54,29 @@ may be used interchangeably.
 
 3~ create and destroy database
 
-!_ --pgsql --createall<br>
+!_ --pgsql --createall \\
 initial step, creates required relations (tables, indexes) in existing (postgresql) database (a database should be created manually and given the same name as working directory, as requested) (rb.dbi)
 
-!_ sisu -D --createdb<br>
+!_ sisu -D --createdb \\
 creates database where no database existed before
 
-!_ sisu -D --create<br>
+!_ sisu -D --create \\
 creates database tables where no database tables existed before
 
-!_ sisu -D --Dropall<br>
+!_ sisu -D --Dropall \\
 destroys database (including all its content)! kills data and drops tables, indexes and database associated with a given directory (and directories of the same name).
 
-!_ sisu -D --recreate<br>
+!_ sisu -D --recreate \\
 destroys existing database and builds a new empty database structure
 
 3~ import and remove documents
 
-!_ sisu -D --import -v [filename/wildcard]<br>
+!_ sisu -D --import -v [filename/wildcard] \\
 populates database with the contents of the file. Imports documents(s) specified to a postgresql database (at an object level).
 
-!_ sisu -D --update -v [filename/wildcard]<br>
+!_ sisu -D --update -v [filename/wildcard] \\
 updates file contents in database
 
-!_ sisu -D --remove -v [filename/wildcard]<br>
+!_ sisu -D --remove -v [filename/wildcard] \\
 removes specified document from postgresql database.
 
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_remote.sst b/data/doc/sisu/markup-samples/manual/en/sisu_remote.sst
index 959fbcf6..54ea9a7b 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_remote.sst
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_remote.sst
@@ -73,10 +73,10 @@ sisu -3R sisu_remote.sst
 
 2~ commands
 
-!_ -R [filename/wildcard] <br>
+!_ -R [filename/wildcard] \\
 copies sisu output files to remote host using rsync. This requires that sisurc.yml has been provided with information on hostname and username, and that you have your "keys" and ssh agent in place. Note the behavior of rsync different if -R is used with other flags from if used alone. Alone the rsync --delete parameter is sent, useful for cleaning the remote directory (when -R is used together with other flags, it is not). Also see -r
 
-!_ -r [filename/wildcard] <br>
+!_ -r [filename/wildcard] \\
 copies sisu output files to remote host using scp. This requires that sisurc.yml has been provided with information on hostname and username, and that you have your "keys" and ssh agent in place. Also see -R
 
 2~ configuration
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_search_cgi.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_search_cgi.ssi
index 03eef9ff..4e833b9b 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_search_cgi.ssi
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_search_cgi.ssi
@@ -25,6 +25,44 @@
 
 1~search_cgi Introduction
 
+2~ Setup search form
+
+You will need a web server, httpd with cgi enabled, and a postgresql database to which you are able to create databases.
+
+Setup postgresql, make sure you are able to create and write to the database, e.g.:
+
+``` code
+sudo su postgres
+  createuser -d -a ralph
+```
+
+You then need to create the database that sisu will use, for sisu manual in the directory manual/en for example, (when you try to populate a database that does not exist sisu prompts as to whether it exists):
+
+``` code
+createdb SiSUv6a_manual
+```
+
+SiSU is then able to create the required tables that allow you to populate the database with documents in the directory for which it has been created:
+
+``` code
+sisu --pg --createall -v
+```
+
+You can then start to populate the database, in this example with a single document:
+
+``` code
+sisu --pg --update -v en/sisu_manual.ssm
+```
+
+To create a sample search form, from within the same directory run:
+
+``` code
+sisu --sample-search-form --db-pg
+```
+and copy the resulting cgi form to your cgi-bin directory
+
+A sample setup for nginx is provided that assumes data will be stored under /srv/www and cgi scripts under /srv/cgi
+
 2~ Search - database frontend sample, utilising database and SiSU features, including object citation numbering (backend currently PostgreSQL) *~search
 
 {~^ Sample search frontend }http://search.sisudoc.org
@@ -36,7 +74,7 @@ Note you may set results either for documents matched and object number location
 
 % Several options for output - select database to search, show results in index view (links to locations within text), show results with text, echo search in form, show what was searched, create and show a "canned url" for search, show available search fields. Also shows counters number of documents in which found and number of locations within documents where found. [could consider sorting by document with most occurrences of the search result].
 
-!_ sisu -F --webserv-webrick<br>
+!_ sisu -F --webserv-webrick \\
 builds a cgi web search frontend for the database created
 
 The following is feedback on the setup on a machine provided by the help command:
@@ -63,13 +101,13 @@ By default, [unless otherwise specified] databases are built on a directory basi
 
 2~ Search Form
 
-!_ sisu -F<br>
+!_ sisu -F \\
 generates a sample search form, which must be copied to the web-server cgi directory
 
-!_ sisu -F --webserv-webrick<br>
+!_ sisu -F --webserv-webrick \\
 generates a sample search form for use with the webrick server, which must be copied to the web-server cgi directory
 
-!_ sisu -W<br>
+!_ sisu -W \\
 starts the webrick server which should be available wherever sisu is properly installed
 
 The generated search form must be copied manually to the webserver directory as instructed
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_search_intro.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_search_intro.ssi
index d5da379f..386b8175 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_search_intro.ssi
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_search_intro.ssi
@@ -25,7 +25,7 @@
 
 SiSU output can easily and conveniently be indexed by a number of standalone indexing tools, such as Lucene, Hyperestraier.
 
-Because the document structure of sites created is clearly defined, and the text object citation system is available hypothetically at least, for all forms of output, it is possible to search the sql database, and either read results from that database, or just as simply map the results to the html output, which has richer text markup.
+Because the document structure of sites created is clearly defined, and the text object citation system is available hypothetically at least, for all forms of output, it is possible to search the sql database, and either read results from that database, or map the results to the html or other output, which has richer text markup.
 
-In addition to this SiSU has the ability to populate a relational sql type database with documents at an object level, with objects numbers that are shared across different output types, which make them searchable with that degree of granularity. Basically, your match criteria is met by these documents and at these locations within each document, which can be viewed within the database directly or in various output formats.
+SiSU can populate a relational sql type database with documents at an object level, including objects numbers that are shared across different output types. Making a document corpus searchable with that degree of granularity. Basically, your match criteria is met by these documents and at these locations within each document, which can be viewed within the database directly or in various output formats.
 
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_sql.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_sql.ssi
index 6e54275b..f24fe2a9 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_sql.ssi
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_sql.ssi
@@ -30,7 +30,7 @@
 
 2~ populating SQL type databases
 
-SiSU feeds sisu markupd documents into sql type databases PostgreSQL~{ http://www.postgresql.org/ <br> http://advocacy.postgresql.org/ <br> http://en.wikipedia.org/wiki/Postgresql }~ and/or SQLite~{ http://www.hwaci.com/sw/sqlite/ <br> http://en.wikipedia.org/wiki/Sqlite }~ database together with information related to document structure.
+SiSU feeds sisu markupd documents into sql type databases PostgreSQL~{ http://www.postgresql.org/ \\ http://advocacy.postgresql.org/ \\ http://en.wikipedia.org/wiki/Postgresql }~ and/or SQLite~{ http://www.hwaci.com/sw/sqlite/ \\ http://en.wikipedia.org/wiki/Sqlite }~ database together with information related to document structure.
 
 This is one of the more interesting output forms, as all the structural data of the documents are retained (though can be ignored by the user of the database should they so choose). All site texts/documents are (currently) streamed to four tables:
 
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_sqlite.sst b/data/doc/sisu/markup-samples/manual/en/sisu_sqlite.sst
index a73ae16c..2c43aa92 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_sqlite.sst
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_sqlite.sst
@@ -55,28 +55,28 @@ may be used interchangeably.
 
 3~ create and destroy database
 
-!_ --sqlite --createall<br>
+!_ --sqlite --createall \\
 initial step, creates required relations (tables, indexes) in existing (sqlite) database (a database should be created manually and given the same name as working directory, as requested) (rb.dbi)
 
-!_ sisu -d --createdb<br>
+!_ sisu -d --createdb \\
 creates database where no database existed before
 
-!_ sisu -d --create<br>
+!_ sisu -d --create \\
 creates database tables where no database tables existed before
 
-!_ sisu -d --dropall<br>
+!_ sisu -d --dropall \\
 destroys database (including all its content)! kills data and drops tables, indexes and database associated with a given directory (and directories of the same name).
 
-!_ sisu -d --recreate<br>
+!_ sisu -d --recreate \\
 destroys existing database and builds a new empty database structure
 
 3~ import and remove documents
 
-!_ sisu -d --import -v [filename/wildcard]<br>
+!_ sisu -d --import -v [filename/wildcard] \\
 populates database with the contents of the file. Imports documents(s) specified to an sqlite database (at an object level).
 
-!_ sisu -d --update -v [filename/wildcard]<br>
+!_ sisu -d --update -v [filename/wildcard] \\
 updates file contents in database
 
-!_ sisu -d --remove -v [filename/wildcard]<br>
+!_ sisu -d --remove -v [filename/wildcard] \\
 removes specified document from sqlite database.
diff --git a/man/man1/sisu.1 b/man/man1/sisu.1
index f6bb6b5b..478f1f6f 100644
--- a/man/man1/sisu.1
+++ b/man/man1/sisu.1
@@ -1,4 +1,4 @@
-.TH "sisu" "1" "2014-02-05" "6.0.1" "SiSU"
+.TH "sisu" "1" "2014-02-05" "6.0.3" "SiSU"
 .br
 .SH NAME
 .br
@@ -913,16 +913,15 @@ Available man pages are converted back to html using man2html:
 An online version of the sisu man page is available here:
 
 .BR
-* various sisu man pages <http://www.jus.uio.no/sisu/man/> [^9]
+* various sisu man pages <http://www.jus.uio.no/sisu/man/> [^1]
 
 .BR
-* sisu.1 <http://www.jus.uio.no/sisu/man/sisu.1.html> [^10]
-
+* sisu.1 <http://www.jus.uio.no/sisu/man/sisu.1.html> [^2]
 .SH SISU BUILT-IN INTERACTIVE HELP, [DISCONTINUED]
 
 .BR
 This fell out of date and has been discontinued.
-.SH INTRODUCTION TO SISU MARKUP[^11]
+.SH INTRODUCTION TO SISU MARKUP[^3]
 
 .SH SUMMARY
 
@@ -932,7 +931,7 @@ source documents are
 .I plaintext
 (
 .I UTF-8
-)[^12] files
+)[^4] files
 
 .BR
 All paragraphs are separated by an empty line.
@@ -1473,7 +1472,7 @@ determines whether footnotes or endnotes will be produced
 .B resulting output:
 
 .BR
-[^13]
+[^5]
 
 .BR
 .B markup example:
@@ -1485,7 +1484,7 @@ normal text~{ self contained endnote marker & endnote in one }~ continues
 .B resulting output:
 
 .BR
-normal text[^14] continues
+normal text[^6] continues
 
 .BR
 .B markup example:
@@ -1620,7 +1619,7 @@ about {~^ SiSU }http://url.org markup
 .B resulting output:
 
 .BR
-aboutSiSU <http://www.sisudoc.org/> [^15] markup
+aboutSiSU <http://www.sisudoc.org/> [^7] markup
 
 .BR
 Internal document links to a tagged location, including an ocn
@@ -1684,7 +1683,7 @@ GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian
 and Ruby" <http://www.sisudoc.org/>
 
 .BR
-ruby_logo.png 70x90 "Ruby" <http://www.ruby-lang.org/en/> [^16]
+ruby_logo.png 70x90 "Ruby" <http://www.ruby-lang.org/en/> [^8]
 
 .BR
 .B linked url footnote shortcut
@@ -1769,7 +1768,7 @@ information in each column
 
 .BR
 .B markup example:
-[^18]
+[^10]
 .nf
 !_ Table 3.1: Contributors to Wikipedia, January 2001 - June 2005
 
@@ -2404,7 +2403,7 @@ contain other documents.
 
 .BR
 Note: a secondary file of the composite document is built prior to processing
-with the same prefix and the suffix ._sst [^19]
+with the same prefix and the suffix ._sst [^11]
 .SH SISU INSERT FILES (.SSI)
 
 .BR
@@ -2594,7 +2593,7 @@ The default homepage may use homepage.css or html. css
 
 .BR
 Under consideration is to permit the placement of a CSS file with a different
-name in directory _sisu/css directory or equivalent.[^20]
+name in directory _sisu/css directory or equivalent.[^12]
 
 .SH ORGANISING CONTENT - DIRECTORY STRUCTURE AND MAPPING
 
@@ -3067,9 +3066,9 @@ output formats.
 .B SiSU
 feeds sisu markupd documents into sql type databases
 .I PostgreSQL
-[^21] and/or
+[^13] and/or
 .I SQLite
-[^22] database together with information related to document structure.
+[^14] database together with information related to document structure.
 
 .BR
 This is one of the more interesting output forms, as all the structural data of
@@ -3290,14 +3289,63 @@ removes specified document from sqlite database.
 
 .SH INTRODUCTION
 
+.SH SETUP SEARCH FORM
+
+
+.BR
+You will need a web server, httpd with cgi enabled, and a postgresql database
+to which you are able to create databases.
+
+.BR
+Setup postgresql, make sure you are able to create and write to the database,
+e.g.:
+.nf
+sudo su postgres
+  createuser -d -a ralph
+.fi
+
+
+.BR
+You then need to create the database that sisu will use, for sisu manual in the
+directory manual/en for example, (when you try to populate a database that does
+not exist sisu prompts as to whether it exists):
+.nf
+createdb SiSUv6a_manual
+.fi
+
+
+.BR
+
+.B SiSU
+is then able to create the required tables that allow you to populate the
+database with documents in the directory for which it has been created:
+.nf
+sisu --pg --createall -v
+.fi
+
+
+.BR
+You can then start to populate the database, in this example with a single
+document:
+.nf
+sisu --pg --update -v en/sisu_manual.ssm
+.fi
+
+
+.BR
+To create a sample search form, from within the same directory run:
+
+.BR
+A sample setup for nginx is provided that assumes data will be stored under
+/srv/www and cgi scripts under /srv/cgi
 .SH SEARCH - DATABASE FRONTEND SAMPLE, UTILISING DATABASE AND SISU FEATURES,
 INCLUDING OBJECT CITATION NUMBERING (BACKEND CURRENTLY POSTGRESQL)
 
 .BR
-Sample search frontend <http://search.sisudoc.org> [^23] A small database and
-sample query front-end (search from) that makes use of the citation system,
-.I object citation numbering
-to demonstrates functionality.[^24]
+Sample search frontend <http://search.sisudoc.org> [^15] A small database and
+sample query front-end (search from) that makes use of the citation system, .I
+object citation numbering
+to demonstrates functionality.[^16]
 
 .BR
 .B SiSU
@@ -3321,7 +3369,7 @@ documents matched.
 Note you may set results either for documents matched and object number
 locations within each matched document meeting the search criteria; or display
 the names of the documents matched along with the objects (paragraphs) that
-meet the search criteria.[^25]
+meet the search criteria.[^17]
 
 .TP
 .B sisu -F --webserv-webrick
@@ -3626,53 +3674,6 @@ possible representations that are quite different from those offered at
 present. For example objects could be saved individually and identified by
 their hashes, with an index of how the objects relate to each other to form a
 document.
-
-.TP
-.BI 1.
-objects include: headings, paragraphs, verse, tables, images, but not
-footnotes/endnotes which are numbered separately and tied to the object from
-which they are referenced.
-
-.BR
-.TP
-.BI 2.
-i.e. the HTML, PDF, EPUB, ODT outputs are each built individually and optimised for that form of
-presentation, rather than for example the html being a saved version of the
-odf, or the pdf being a saved version of the html.
-
-.BR
-.TP
-.BI 3.
-the different heading levels
-
-.BR
-.TP
-.BI 4.
-units of text, primarily paragraphs and headings, also any tables, poems,
-code-blocks
-
-.BR
-.TP
-.BI 5.
-An open standard format for e-books
-
-.BR
-.TP
-.BI 6.
-Open Document Format ( ODF ) text
-
-.BR
-.TP
-.BI 7.
-Specification submitted by Adobe to ISO to become a full open ISO
-specification <http://www.linux-watch.com/news/NS7542722606.html>
-
-.BR
-.TP
-.BI 8.
-ISO standard ISO/IEC 26300:2006
-
-.BR
 .TP
 .BI *1.
 square brackets
@@ -3689,33 +3690,33 @@ square brackets
 
 .BR
 .TP
-.BI 9.
+.BI 1.
 <http://www.jus.uio.no/sisu/man/>
 
 .BR
 .TP
-.BI 10.
+.BI 2.
 <http://www.jus.uio.no/sisu/man/sisu.1.html>
 
 .BR
 .TP
-.BI 11.
+.BI 3.
 From sometime after SiSU 0.58 it should be possible to describe SiSU markup
 using SiSU, which though not an original design goal is useful.
 
 .BR
 .TP
-.BI 12.
+.BI 4.
 files should be prepared using UTF-8 character encoding
 
 .BR
 .TP
-.BI 13.
+.BI 5.
 a footnote or endnote
 
 .BR
 .TP
-.BI 14.
+.BI 6.
 self contained endnote marker & endnote in one
 
 .BR
@@ -3740,23 +3741,23 @@ editors notes, numbered plus symbol footnote/endnote series
 
 .BR
 .TP
-.BI 15.
+.BI 7.
 <http://www.sisudoc.org/>
 
 .BR
 .TP
-.BI 16.
+.BI 8.
 <http://www.ruby-lang.org/en/>
 
 .BR
 .TP
-.BI 18.
+.BI 10.
 Table from the Wealth of Networks by Yochai Benkler
 <http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler>
 
 .BR
 .TP
-.BI 19.
+.BI 11.
 \.ssc (for composite) is under consideration but \._sst makes clear that this
 is not a regular file to be worked on, and thus less likely that people will
 have "accidents", working on a \.ssc file that is overwritten by subsequent
@@ -3765,37 +3766,37 @@ appropriate suffix to use.
 
 .BR
 .TP
-.BI 20.
+.BI 12.
 SiSU has worked this way in the past, though this was dropped as it was
 thought the complexity outweighed the flexibility, however, the balance was
 rather fine and this behaviour could be reinstated.
 
 .BR
 .TP
-.BI 21.
+.BI 13.
 <http://www.postgresql.org/> <http://advocacy.postgresql.org/>
 <http://en.wikipedia.org/wiki/Postgresql>
 
 .BR
 .TP
-.BI 22.
+.BI 14.
 <http://www.hwaci.com/sw/sqlite/> <http://en.wikipedia.org/wiki/Sqlite>
 
 .BR
 .TP
-.BI 23.
+.BI 15.
 <http://search.sisudoc.org>
 
 .BR
 .TP
-.BI 24.
+.BI 16.
 (which could be extended further with current back-end). As regards scaling
 of the database, it is as scalable as the database (here Postgresql) and
 hardware allow.
 
 .BR
 .TP
-.BI 25.
+.BI 17.
 of this feature when demonstrated to an IBM software innovations evaluator
 in 2004 he said to paraphrase: this could be of interest to us. We have large
 document management systems, you can search hundreds of thousands of documents