reorganising documentation

16 files changed, 580 insertions, 88 deletions

diff --git a/CHANGELOG b/CHANGELOG
index ed8f23d7..a860dc80 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -29,8 +29,11 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_0.60.0.orig.tar.gz
 
   * sysenv, sisurc.yml allow use of relative output paths, expand to absolute
 
-  * param, behavior changed to take in multi-lines, affects regex matching,
-    watch
+  * param, behavior for reading headers changed to take in multi-lines, affects
+    regex matching, watch
+
+  * vim syntax highlighting for sisu markup, change to take account of
+    possibility of multi-line headers
 
   * html segmented, bugfix: footnotes for headings levels :A,:B and :C
     correctly placed in first segment when batch-processing files/output
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/Rantfile b/data/doc/sisu/sisu_markup_samples/sisu_manual/Rantfile
index e9cba974..37198c7c 100644
--- a/data/doc/sisu/sisu_markup_samples/sisu_manual/Rantfile
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/Rantfile
@@ -147,11 +147,11 @@ def files_all
   files
 end
 def filelist_docs
-  files='sisu_manual.ssm sisu_introduction.sst sisu_help.sst sisu_help_sources.sst sisu_commands.sst sisu_markup.sst sisu_filetypes.sst sisu_config.ssi sisu_skin.sst sisu_css.ssi sisu_content_directories.ssi sisu_homepages.ssi sisu_examples.sst sisu_output_overview.sst sisu_webrick.sst sisu_quickstart.sst sisu_faq.sst sisu_syntax_highlighting.sst sisu_configuration.ssm sisu_description.sst sisu_remote.sst sisu_complete.sst sisu_postgresql.sst sisu_sqlite.sst sisu_pdf.sst sisu_search.ssm sisu_vim.sst sisu_doc.sst' # sisu_outpuman/man7/sisu_doc.7t_types.ssm sisu_sql.sst sisu_hyperestraier.sst sisu_latex.sst sisu_odf.sst sisu_xml.sst sisu_concordance.sst sisu_document_digest_certificate.sst document_digest_certificate.sst sisu_markup_source.sst sisupod.sst
+  files='sisu_manual.ssm sisu_introduction.ssm sisu_help.sst sisu_help_sources.sst sisu_commands.sst sisu_markup.sst sisu_filetypes.sst sisu_config.ssi sisu_skin.sst sisu_css.ssi sisu_content_directories.ssi sisu_homepages.ssi sisu_examples.sst sisu_output_overview.sst sisu_webrick.sst sisu_quickstart.sst sisu_faq.sst sisu_syntax_highlighting.sst sisu_configuration.ssm sisu_description.sst sisu_remote.sst sisu_complete.sst sisu_postgresql.sst sisu_sqlite.sst sisu_pdf.sst sisu_search.ssm sisu_vim.sst sisu_doc.sst' # sisu_outpuman/man7/sisu_doc.7t_types.ssm sisu_sql.sst sisu_hyperestraier.sst sisu_latex.sst sisu_odf.sst sisu_xml.sst sisu_concordance.sst sisu_document_digest_certificate.sst document_digest_certificate.sst sisu_markup_source.sst sisupod.sst
   files
 end
 def filelist_manpage
-  files='sisu.ssm sisu_introduction.sst sisu_help.sst sisu_help_sources.sst sisu_commands.sst sisu_markup.sst sisu_filetypes.sst sisu_config.ssi sisu_skin.sst sisu_css.ssi sisu_content_directories.ssi sisu_homepages.ssi sisu_examples.ssi sisu_output_overview.sst sisu_webrick.sst sisu_download.ssi sisu_installation.ssi sisu_quickstart.sst sisu_howto.sst sisu_faq.sst sisu_syntax_highlighting.sst sisu_configuration.ssm sisu_remote.sst sisu_complete.sst sisu_postgresql.sst sisu_sqlite.sst sisu_pdf.sst sisu_search.ssm sisu_vim.sst sisu_doc.sst' # sisu_output_types.ssm sisu_sql.sst sisu_hyperestraier.sst sisu_latex.sst sisu_odf.sst sisu_xml.sst sisu_concordance.sst sisu_document_digest_certificate.sst document_digest_certificate.sst sisu_markup_source.sst sisupod.sst
+  files='sisu.ssm sisu_introduction.ssm sisu_help.sst sisu_help_sources.sst sisu_commands.sst sisu_markup.sst sisu_filetypes.sst sisu_config.ssi sisu_skin.sst sisu_css.ssi sisu_content_directories.ssi sisu_homepages.ssi sisu_examples.ssi sisu_output_overview.sst sisu_webrick.sst sisu_download.ssi sisu_installation.ssi sisu_quickstart.sst sisu_howto.sst sisu_faq.sst sisu_syntax_highlighting.sst sisu_configuration.ssm sisu_remote.sst sisu_complete.sst sisu_postgresql.sst sisu_sqlite.sst sisu_pdf.sst sisu_search.ssm sisu_vim.sst sisu_doc.sst' # sisu_output_types.ssm sisu_sql.sst sisu_hyperestraier.sst sisu_latex.sst sisu_odf.sst sisu_xml.sst sisu_concordance.sst sisu_document_digest_certificate.sst document_digest_certificate.sst sisu_markup_source.sst sisupod.sst
   #puts files + "\n\n"
   files
 end
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu.ssm b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu.ssm
index 50bd7dc9..33fbc344 100644
--- a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu.ssm
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu.ssm
@@ -49,7 +49,7 @@ sisu [-CcFLSVvW]
 
 :B~ What is SiSU?
 
-<< |sisu_introduction.sst|@|^|
+<< |sisu_introduction.ssi|@|^|
 
 << |sisu_help.sst|@|^|
 
@@ -99,4 +99,8 @@ sisu [-CcFLSVvW]
 
 << |sisu_syntax_highlighting.sst|@|^|
 
+<< |sisu_how.ssi|@|^|
+
+<< |sisu_short_feature_summary.ssi|@|^|
+
 << |sisu_help_sources.sst|@|^|
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_complete.sst b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_complete.sst
index ac177878..75252e89 100644
--- a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_complete.sst
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_complete.sst
@@ -28,6 +28,10 @@
 
 @bold: /Gnu|Debian|Ruby|SiSU/
 
+@man: 8;
+name=sisu - documents: structuring, publishing in multiple formats, and search;
+synopsis=package for the installation of the whole of sisu with all its dependencies
+
 @links: { SiSU Manual }http://www.jus.uio.no/sisu/sisu_manual/
 { Book Samples and Markup Examples }http://www.jus.uio.no/sisu/SiSU/2.html
 { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_help_sources.sst b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_help_sources.sst
index 3006ef75..860b2173 100644
--- a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_help_sources.sst
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_help_sources.sst
@@ -87,45 +87,47 @@ _1 http://www.jus.uio.no/sisu/sisu_manual/sisu_help_sources/index.html
 
 _1 man sisu
 
-_1 man sisu_commands
+% _1 man sisu_commands
 
 _1 man 7 sisu_complete
 
-_1 man sisu_configuration
+% _1 man sisu_configuration
 
-_1 man 8 sisu_faq
+% _1 man sisu_faq
 
-_1 man sisu_filetypes
+% _1 man sisu_filetypes
 
-_1 man sisu_help
+% _1 man sisu_help
 
-_1 man sisu_help_sources
+% _1 man sisu_help_sources
 
-_1 man 8 sisu_howto
+% _1 man 8 sisu_howto
 
-_1 man sisu_introduction
+% _1 man sisu_introduction
 
-_1 man sisu_markup
+% _1 man sisu_markup
 
-_1 man sisu_output_overview
+% _1 man sisu_output_overview
 
 _1 man 7 sisu_pdf
 
 _1 man 7 sisu_postgresql
 
-_1 man 8 sisu_quickstart
+% _1 man 8 sisu_quickstart
 
-_1 man 8 sisu_remote
+% _1 man 8 sisu_remote
 
-_1 man 8 sisu_search
+% _1 man 8 sisu_search
 
-_1 man sisu_skin
+% _1 man sisu_skin
 
 _1 man 7 sisu_sqlite
 
-_1 man 8 sisu_syntax_highlighting
+% _1 man 8 sisu_syntax_highlighting
+
+_1 man sisu_termsheet
 
-_1 man 7 sisu_vim
+% _1 man 7 sisu_vim
 
 _1 man sisu_webrick
 
@@ -143,51 +145,53 @@ file:///usr/share/doc/sisu/sisu_manual/sisu_help_sources/index.html
 
 _1 /usr/share/doc/sisu/sisu_manual/sisu/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_commands/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_commands/index.html
 
 _1 /usr/share/doc/sisu/sisu_manual/sisu_complete/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_configuration/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_configuration/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_description/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_description/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_examples/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_examples/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_faq/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_faq/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_filetypes/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_filetypes/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_help/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_help/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_help_sources/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_help_sources/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_howto/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_howto/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_introduction/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_introduction/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_manual/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_manual/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_markup/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_markup/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_output_overview/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_output_overview/index.html
 
 _1 /usr/share/doc/sisu/sisu_manual/sisu_pdf/index.html
 
 _1 /usr/share/doc/sisu/sisu_manual/sisu_postgresql/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_quickstart/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_quickstart/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_remote/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_remote/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_search/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_search/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_skin/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_skin/index.html
 
 _1 /usr/share/doc/sisu/sisu_manual/sisu_sqlite/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_syntax_highlighting/index.html
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_syntax_highlighting/index.html
 
-_1 /usr/share/doc/sisu/sisu_manual/sisu_vim/index.html
+_1 /usr/share/doc/sisu/sisu_manual/sisu_termsheet/index.html
+
+% _1 /usr/share/doc/sisu/sisu_manual/sisu_vim/index.html
 
 _1 /usr/share/doc/sisu/sisu_manual/sisu_webrick/index.html
 
@@ -299,11 +303,11 @@ _1 http://www.jus.uio.no/sisu/sisu_manual/sisu_vim/index.html
 
 _1 http://www.jus.uio.no/sisu/sisu_manual/sisu_webrick/index.html
 
-3~ man2html
+2~ man2html
 
 3~ locally installed
 
-file:///usr/share/doc/sisu/html/sisu_manual.1.html
+file:///usr/share/doc/sisu/html/sisu.1.html
 
 file:///usr/share/doc/sisu/html/sisu_help.1.html
 
@@ -311,31 +315,31 @@ file:///usr/share/doc/sisu/html/sisu_help_sources.1.html
 
 _1 /usr/share/doc/sisu/html/sisu.1.html
 
-_1 /usr/share/doc/sisu/html/sisu_commands.1.html
+% _1 /usr/share/doc/sisu/html/sisu_commands.1.html
 
-_1 /usr/share/doc/sisu/html/sisu_complete.7.html
+% _1 /usr/share/doc/sisu/html/sisu_complete.7.html
 
-_1 /usr/share/doc/sisu/html/sisu_configuration.1.html
+% _1 /usr/share/doc/sisu/html/sisu_configuration.1.html
 
 % _1 /usr/share/doc/sisu/html/sisu_description.1.html
 
 % _1 /usr/share/doc/sisu/html/sisu_examples.1.html
 
-_1 /usr/share/doc/sisu/html/sisu_faq.8.html
+% _1 /usr/share/doc/sisu/html/sisu_faq.8.html
 
 % _1 /usr/share/doc/sisu/html/sisu_filetypes.1.html
 
-_1 /usr/share/doc/sisu/html/sisu_help.1.html
+% _1 /usr/share/doc/sisu/html/sisu_help.1.html
 
-_1 /usr/share/doc/sisu/html/sisu_help_sources.1.html
+% _1 /usr/share/doc/sisu/html/sisu_help_sources.1.html
 
-_1 /usr/share/doc/sisu/html/sisu_howto.8.html
+% _1 /usr/share/doc/sisu/html/sisu_howto.8.html
 
 % _1 /usr/share/doc/sisu/html/sisu_introduction.1.html
 
 % _1 /usr/share/doc/sisu/html/sisu_manual.1.html
 
-_1 /usr/share/doc/sisu/html/sisu_markup.1.html
+% _1 /usr/share/doc/sisu/html/sisu_markup.1.html
 
 % _1 /usr/share/doc/sisu/html/sisu_output_overview.1.html
 
@@ -343,19 +347,19 @@ _1 /usr/share/doc/sisu/html/sisu_pdf.7.html
 
 _1 /usr/share/doc/sisu/html/sisu_postgresql.7.html
 
-_1 /usr/share/doc/sisu/html/sisu_quickstart.8.html
+% _1 /usr/share/doc/sisu/html/sisu_quickstart.8.html
 
-_1 /usr/share/doc/sisu/html/sisu_remote.8.html
+% _1 /usr/share/doc/sisu/html/sisu_remote.8.html
 
-_1 /usr/share/doc/sisu/html/sisu_search.8.html
+% _1 /usr/share/doc/sisu/html/sisu_search.8.html
 
-_1 /usr/share/doc/sisu/html/sisu_skin.1.html
+% _1 /usr/share/doc/sisu/html/sisu_skin.1.html
 
 _1 /usr/share/doc/sisu/html/sisu_sqlite.7.html
 
-_1 /usr/share/doc/sisu/html/sisu_syntax_highlighting.8.html
+% _1 /usr/share/doc/sisu/html/sisu_syntax_highlighting.8.html
 
-_1 /usr/share/doc/sisu/html/sisu_vim.7.html
+% _1 /usr/share/doc/sisu/html/sisu_vim.7.html
 
 _1 /usr/share/doc/sisu/html/sisu_webrick.1.html
 
@@ -369,45 +373,45 @@ http:///sisudoc.org/man/sisu_help_sources.1.html
 
 _1 http://sisudoc.org/man/sisu.1.html
 
-_1 http://sisudoc.org/man/sisu_commands.1.html
+% _1 http://sisudoc.org/man/sisu_commands.1.html
 
 _1 http://sisudoc.org/man/sisu_complete.7.html
 
-_1 http://sisudoc.org/man/sisu_configuration.1.html
+% _1 http://sisudoc.org/man/sisu_configuration.1.html
 
-_1 http://sisudoc.org/man/sisu_faq.8.html
+% _1 http://sisudoc.org/man/sisu_faq.8.html
 
-_1 http://sisudoc.org/man/sisu_help.1.html
+% _1 http://sisudoc.org/man/sisu_help.1.html
 
-_1 http://sisudoc.org/man/sisu_help_sources.1.html
+% _1 http://sisudoc.org/man/sisu_help_sources.1.html
 
-_1 http://sisudoc.org/man/sisu_howto.8.html
+% _1 http://sisudoc.org/man/sisu_howto.8.html
 
-_1 http://sisudoc.org/man/sisu_markup.1.html
+% _1 http://sisudoc.org/man/sisu_markup.1.html
 
 _1 http://sisudoc.org/man/sisu_pdf.7.html
 
 _1 http://sisudoc.org/man/sisu_postgresql.7.html
 
-_1 http://sisudoc.org/man/sisu_quickstart.8.html
+% _1 http://sisudoc.org/man/sisu_quickstart.8.html
 
-_1 http://sisudoc.org/man/sisu_remote.8.html
+% _1 http://sisudoc.org/man/sisu_remote.8.html
 
-_1 http://sisudoc.org/man/sisu_search.8.html
+% _1 http://sisudoc.org/man/sisu_search.8.html
 
-_1 http://sisudoc.org/man/sisu_skin.1.html
+% _1 http://sisudoc.org/man/sisu_skin.1.html
 
 _1 http://sisudoc.org/man/sisu_sqlite.7.html
 
-_1 http://sisudoc.org/man/sisu_syntax_highlighting.8.html
+% _1 http://sisudoc.org/man/sisu_syntax_highlighting.8.html
 
-_1 http://sisudoc.org/man/sisu_vim.7.html
+% _1 http://sisudoc.org/man/sisu_vim.7.html
 
 _1 http://sisudoc.org/man/sisu_webrick.1.html
 
 3~ www.jus.uio.no/sisu
 
-http://www.jus.uio.no/sisu/man/sisu_manual.1.html
+http://www.jus.uio.no/sisu/man/sisu.1.html
 
 http://www.jus.uio.no/sisu/man/sisu_help.1.html
 
@@ -415,38 +419,38 @@ http://www.jus.uio.no/sisu/man/sisu_help_sources.1.html
 
 _1 http://www.jus.uio.no/sisu/man/sisu.1.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_commands.1.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_commands.1.html
 
 _1 http://www.jus.uio.no/sisu/man/sisu_complete.7.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_configuration.1.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_configuration.1.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_faq.8.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_faq.8.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_help.1.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_help.1.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_help_sources.1.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_help_sources.1.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_howto.8.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_howto.8.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_markup.1.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_markup.1.html
 
 _1 http://www.jus.uio.no/sisu/man/sisu_pdf.7.html
 
 _1 http://www.jus.uio.no/sisu/man/sisu_postgresql.7.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_quickstart.8.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_quickstart.8.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_remote.8.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_remote.8.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_search.8.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_search.8.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_skin.1.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_skin.1.html
 
 _1 http://www.jus.uio.no/sisu/man/sisu_sqlite.7.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_syntax_highlighting.8.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_syntax_highlighting.8.html
 
-_1 http://www.jus.uio.no/sisu/man/sisu_vim.7.html
+% _1 http://www.jus.uio.no/sisu/man/sisu_vim.7.html
 
 _1 http://www.jus.uio.no/sisu/man/sisu_webrick.1.html
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_introduction.sst b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_how.ssi
index 9a2e2ddd..9a2e2ddd 100644
--- a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_introduction.sst
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_how.ssi
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_introduction.ssi b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_introduction.ssi
new file mode 100644
index 00000000..9a2e2ddd
--- /dev/null
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_introduction.ssi
@@ -0,0 +1,133 @@
+% SiSU 0.58
+
+@title: SiSU
+
+@subtitle: Commands
+
+@creator: Ralph Amissah
+
+@rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3
+
+@type: information
+
+@subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+@date.created: 2002-08-28
+
+@date.issued: 2002-08-28
+
+@date.available: 2002-08-28
+
+@date.modified: 2007-09-16
+
+@date: 2007-09-16
+
+@level: new=C; break=1; num_top=1
+
+@skin: skin_sisu_manual
+
+@bold: /Gnu|Debian|Ruby|SiSU/
+
+@links: { SiSU Manual }http://www.jus.uio.no/sisu/sisu_manual/
+{ Book Samples and Markup Examples }http://www.jus.uio.no/sisu/SiSU/2.html
+{ SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
+{ SiSU @ Freshmeat }http://freshmeat.net/projects/sisu/
+{ SiSU @ Ruby Application Archive }http://raa.ruby-lang.org/project/sisu/
+{ SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html
+{ SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html
+{ SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html
+{ SiSU help }http://www.jus.uio.no/sisu/sisu_manual/sisu_help/
+{ SiSU help sources }http://www.jus.uio.no/sisu/sisu_manual/sisu_help_sources/
+
+:A~? @title @creator
+
+:B~? What is SiSU?
+
+:C~? Description
+
+1~sisu_intro Introduction - What is SiSU?
+
+SiSU is a system for document markup, publishing (in multiple open standard formats) and search
+
+SiSU~{ "SiSU information Structuring Universe" or "Structured information, Serialized Units".<br>also chosen for the meaning of the Finnish term "sisu". }~ is a~{ Unix command line oriented }~ framework for document structuring, publishing and search, comprising of (a) a lightweight document structure and presentation markup syntax and (b) an accompanying engine for generating standard document format outputs from documents prepared in sisu markup syntax, which is able to produce multiple standard outputs that (can) share a common numbering system for the citation of text within a document.
+
+SiSU is developed under an open source, software libre license (GPL3). It has been developed in the context of coping with large document sets with evolving markup related technologies, for which you want multiple output formats, a common mechanism for cross-output-format citation, and search.
+
+SiSU both defines a markup syntax and provides an engine that produces open standards format outputs from documents prepared with SiSU markup. From a single lightly prepared document sisu custom builds several standard output formats which share a common (text object) numbering system for citation of content within a document (that also has implications for search). The sisu engine works with an abstraction of the document's structure and content from which it is possible to generate different forms of representation of the document. Significantly SiSU markup is more sparse than html and outputs which include html, LaTeX, landscape and portrait pdfs, Open Document Format (ODF), all of which can be added to and updated. SiSU is also able to populate SQL type databases at an object level, which means that searches can be made with that degree of granularity. Results of objects (primarily paragraphs and headings) can be viewed directly in the database, or just the object numbers shown - your search criteria is met in these documents and at these locations within each document.
+
+Source document preparation and output generation is a two step process: (i) document source is prepared, that is, marked up in sisu markup syntax and (ii) the desired output subsequently generated by running the sisu engine against document source. Output representations if updated (in the sisu engine) can be generated by re-running the engine against the prepared source. Using SiSU markup applied to a document, SiSU custom builds various standard open output formats including plain text, HTML, XHTML, XML, OpenDocument, LaTeX or PDF files, and populate an SQL database with objects~{ 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. }~ (equating generally to paragraph-sized chunks) so searches may be performed and matches returned with that degree of granularity ( e.g. your search criteria is met by these documents and at these locations within each document). Document output formats share a common object numbering system for locating content. This is particularly suitable for "published" works (finalized texts as opposed to works that are frequently changed or updated) for which it provides a fixed means of reference of content.
+
+In preparing a SiSU document you optionally provide semantic information related to the document in a document header, and in marking up the substantive text provide information on the structure of the document, primarily indicating heading levels and footnotes. You also provide information on basic text attributes where used. The rest is automatic, sisu from this information custom builds~{ i.e. the html, pdf, odf 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. }~ the different forms of output requested.
+
+SiSU works with an abstraction of the document based on its structure which is comprised of its frame~{ the different heading levels }~ and the objects~{ units of text, primarily paragraphs and headings, also any tables, poems, code-blocks }~ it contains, which enables SiSU to represent the document in many different ways, and to take advantage of the strengths of different ways of presenting documents. The objects are numbered, and these numbers can be used to provide a common base for citing material within a document across the different output format types. This is significant as page numbers are not suited to the digital age, in web publishing, changing a browser's default font or using a different browser means that text appears on different pages; and in publishing in different formats, html, landscape and portrait pdf etc. again page numbers are of no use to cite text in a manner that is relevant against the different output types. Dealing with documents at an object level together with object numbering also has implications for search.
+
+One of the challenges of maintaining documents is to keep them in a format that would allow users to use them without depending on a proprietary software popular at the time. Consider the ease of dealing with legacy proprietary formats today and what guarantee you have that old proprietary formats will remain (or can be read without proprietary software/equipment) in 15 years time, or the way the way in which html has evolved over its relatively short span of existence. SiSU provides the flexibility of outputing documents in multiple non-proprietary open formats including html, pdf~{ Specification submitted by Adobe to ISO to become a full open ISO specification <br> http://www.linux-watch.com/news/NS7542722606.html }~ and the ISO standard ODF.~{ ISO/IEC 26300:2006 }~ Whilst SiSU relies on software, the markup is uncomplicated and minimalistic which guarantees that future engines can be written to run against it. It is also easily converted to other formats, which means documents prepared in SiSU can be migrated to other document formats. Further security is provided by the fact that the software itself, SiSU is available under GPL3 a licence that guarantees that the source code will always be open, and free as in libre which means that that code base can be used updated and further developed as required under the terms of its license. Another challenge is to keep up with a moving target. SiSU permits new forms of output to be added as they become important, (Open Document Format text was added in 2006), and existing output to be updated (html has evolved and the related module has been updated repeatedly over the years, presumably when the World Wide Web Consortium (w3c) finalises html 5 which is currently under development, the html module will again be updated allowing all existing documents to be regenerated as html 5).
+
+The document formats are written to the file-system and available for indexing by independent indexing tools, whether off the web like Google and Yahoo or on the site like Lucene and Hyperestraier.
+
+SiSU also provides other features such as concordance files and document content certificates, and the working against an abstraction of document structure has further possibilities for the research and development of other document representations, the availability of objects is useful for example for topic maps and the commercial law thesaurus by Vikki Rogers and Al Krtizer, together with the flexibility of SiSU offers great possibilities.
+
+SiSU is primarily for published works, which can take advantage of the citation system to reliably reference its documents. SiSU works well in a complementary manner with such collaborative technologies as Wikis, which can take advantage of and be used to discuss the substance of content prepared in SiSU.
+
+http://www.jus.uio.no/sisu
+
+% SiSU is a way of preparing, publishing, managing and searching documents.
+
+1~sisu_how How does sisu work?
+
+SiSU markup is fairly minimalistic, it consists of: a (largely optional) document header, made up of information about the document (such as when it was published, who authored it, and granting what rights) and any processing instructions; and markup within the substantive text of the document, which is related to document structure and typeface. SiSU must be able to discern the structure of a document, (text headings and their levels in relation to each other), either from information provided in the document header or from markup within the text (or from a combination of both). Processing is done against an abstraction of the document comprising of information on the document's structure and its objects,[2] which the program serializes (providing the object numbers) and which are assigned hash sum values based on their content. This abstraction of information about document structure, objects, (and hash sums), provides considerable flexibility in representing documents different ways and for different purposes (e.g. search, document layout, publishing, content certification, concordance etc.), and makes it possible to take advantage of some of the strengths of established ways of representing documents, (or indeed to create new ones).
+
+1~sisu_feature_summary Summary of features
+
+_* sparse/minimal markup (clean utf-8 source texts). Documents are prepared in a single UTF-8 file using a minimalistic mnemonic syntax. Typical literature, documents like "War and Peace" require almost no markup, and most of the headers are optional.
+
+_* markup is easily readable/parsable by the human eye, (basic markup is simpler and more sparse than the most basic HTML), [this may also be converted to XML representations of the same input/source document].
+
+_* markup defines document structure (this may be done once in a header pattern-match description, or for heading levels individually); basic text attributes (bold, italics, underscore, strike-through etc.) as required; and semantic information related to the document (header information, extended beyond the Dublin core and easily further extended as required); the headers may also contain processing instructions. SiSU markup is primarily an abstraction of document structure and document metadata to permit taking advantage of the basic strengths of existing alternative practical standard ways of representing documents [be that browser viewing, paper publication, sql search etc.] (html, xml, odf, latex, pdf, sql)
+
+_* for output produces reasonably elegant output of established industry and institutionally accepted open standard formats.[3] takes advantage of the different strengths of various standard formats for representing documents, amongst the output formats currently supported are:
+
+_1* html - both as a single scrollable text and a segmented document
+
+_1* xhtml
+
+_1* XML - both in sax and dom style xml structures for further development as required
+
+_1* ODF - open document format, the iso standard for document storage
+
+_1* LaTeX - used to generate pdf
+
+_1* pdf (via LaTeX)
+
+_1* sql - population of an sql database, (at the same object level that is used to cite text within a document)
+
+Also produces: concordance files; document content certificates (md5 or sha256 digests of headings, paragraphs, images etc.) and html manifests (and sitemaps of content). (b) takes advantage of the strengths implicit in these very different output types, (e.g. PDFs produced using typesetting of LaTeX, databases populated with documents at an individual object/paragraph level, making possible granular search (and related possibilities))
+
+_* ensuring content can be cited in a meaningful way regardless of selected output format. Online publishing (and publishing in multiple document formats) lacks a useful way of citing text internally within documents (important to academics generally and to lawyers) as page numbers are meaningless across browsers and formats. sisu seeks to provide a common way of pinpoint the text within a document, (which can be utilized for citation and by search engines). The outputs share a common numbering system that is meaningful (to man and machine) across all digital outputs whether paper, screen, or database oriented, (pdf, HTML, xml, sqlite, postgresql), this numbering system can be used to reference content.
+
+_* Granular search within documents. SQL databases are populated at an object level (roughly headings, paragraphs, verse, tables) and become searchable with that degree of granularity, the output information provides the object/paragraph numbers which are relevant across all generated outputs; it is also possible to look at just the matching paragraphs of the documents in the database; [output indexing also work well with search indexing tools like hyperestraier].
+
+_* long term maintainability of document collections in a world of changing formats, having a very sparsely marked-up source document base. there is a considerable degree of future-proofing, output representations are "upgradeable", and new document formats may be added. e.g. addition of odf (open document text) module in 2006 and in future html5 output sometime in future, without modification of existing prepared texts
+
+_* SQL search aside, documents are generated as required and static once generated.
+
+_* documents produced are static files, and may be batch processed, this needs to be done only once but may be repeated for various reasons as desired (updated content, addition of new output formats, updated technology document presentations/representations)
+
+_* document source (plaintext utf-8) if shared on the net may be used as input and processed locally to produce the different document outputs
+
+_* document source may be bundled together (automatically) with associated documents (multiple language versions or master document with inclusions) and images and sent as a zip file called a sisupod, if shared on the net these too may be processed locally to produce the desired document outputs
+
+_* generated document outputs may automatically be posted to remote sites.
+
+_* for basic document generation, the only software dependency is Ruby, and a few standard Unix tools (this covers plaintext, HTML, XML, ODF, LaTeX). To use a database you of course need that, and to convert the LaTeX generated to pdf, a latex processor like tetex or texlive.
+
+_* as a developers tool it is flexible and extensible
+
+Syntax highlighting for SiSU markup is available for a number of text editors.
+
+SiSU is less about document layout than about finding a way with little markup to be able to construct an abstract representation of a document that makes it possible to produce multiple representations of it which may be rather different from each other and used for different purposes, whether layout and publishing, or search of content
+
+i.e. to be able to take advantage from this minimal preparation starting point of some of the strengths of rather different established ways of representing documents for different purposes, whether for search (relational database, or indexed flat files generated for that purpose whether of complete documents, or say of files made up of objects), online viewing (e.g. html, xml, pdf), or paper publication (e.g. pdf)...
+
+the solution arrived at is by extracting structural information about the document (about headings within the document) and by tracking objects (which are serialized and also given hash values) in the manner described. It makes 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.
+
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_introduction.ssm b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_introduction.ssm
new file mode 100644
index 00000000..a0c25a78
--- /dev/null
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_introduction.ssm
@@ -0,0 +1,58 @@
+% SiSU 0.58
+
+@title: SiSU
+
+@subtitle: Commands
+
+@creator: Ralph Amissah
+
+@rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3
+
+@type: information
+
+@subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+@date.created: 2002-08-28
+
+@date.issued: 2002-08-28
+
+@date.available: 2002-08-28
+
+@date.modified: 2007-09-16
+
+@date: 2007-09-16
+
+@level: new=C; break=1; num_top=1
+
+@skin: skin_sisu_manual
+
+@bold: /Gnu|Debian|Ruby|SiSU/
+
+@links: { SiSU Manual }http://www.jus.uio.no/sisu/sisu_manual/
+{ Book Samples and Markup Examples }http://www.jus.uio.no/sisu/SiSU/2.html
+{ SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
+{ SiSU @ Freshmeat }http://freshmeat.net/projects/sisu/
+{ SiSU @ Ruby Application Archive }http://raa.ruby-lang.org/project/sisu/
+{ SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html
+{ SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html
+{ SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html
+{ SiSU help }http://www.jus.uio.no/sisu/sisu_manual/sisu_help/
+{ SiSU help sources }http://www.jus.uio.no/sisu/sisu_manual/sisu_help_sources/
+
+:A~? @title @creator
+
+:B~? What is SiSU?
+
+:C~? Description
+
+<< |sisu_introduction.ssi|@|^|
+
+<< |sisu_how.ssi|@|^|
+
+<< |sisu_short_feature_summary.ssi|@|^|
+
+<< |sisu_help.sst|@|^|
+
+<< |sisu_help_sources.sst|@|^|
+
+<< |sisu_help_sources.sst|@|^|
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_manual.ssm b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_manual.ssm
index 41d154a2..4a4ecef8 100644
--- a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_manual.ssm
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_manual.ssm
@@ -43,7 +43,11 @@
 
 :B~ What is SiSU?
 
-<< |sisu_introduction.sst|@|^|
+<< |sisu_introduction.ssi|@|^|
+
+<< |sisu_how.ssi|@|^|
+
+<< |sisu_short_feature_summary.ssi|@|^|
 
 << |sisu_help.sst|@|^|
 
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_pdf.sst b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_pdf.sst
index f78f470b..81e5f217 100644
--- a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_pdf.sst
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_pdf.sst
@@ -28,6 +28,10 @@
 
 @bold: /Gnu|Debian|Ruby|SiSU/
 
+@man: 8;
+name=sisu - package to install what sisu needs to generate pdf (latex to pdf dependency component)
+synopsis=sisu -pv [filename/wildcard ]
+
 @links: { SiSU Manual }http://www.jus.uio.no/sisu/sisu_manual/
 { Book Samples and Markup Examples }http://www.jus.uio.no/sisu/SiSU/2.html
 { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_postgresql.sst b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_postgresql.sst
index 3f61e728..09cb2785 100644
--- a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_postgresql.sst
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_postgresql.sst
@@ -28,6 +28,11 @@
 
 @bold: /Gnu|Debian|Ruby|SiSU/
 
+@man: 8;
+name=sisu - package to install what sisu needs to to populate a postgresql database (postgresql dependency component)
+synopsis=sisu -Dv [filename/wildcard ]
+sisu -Dv [instruction]
+
 @links: { SiSU Manual }http://www.jus.uio.no/sisu/sisu_manual/
 { Book Samples and Markup Examples }http://www.jus.uio.no/sisu/SiSU/2.html
 { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_short_feature_summary.ssi b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_short_feature_summary.ssi
new file mode 100644
index 00000000..9a2e2ddd
--- /dev/null
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_short_feature_summary.ssi
@@ -0,0 +1,133 @@
+% SiSU 0.58
+
+@title: SiSU
+
+@subtitle: Commands
+
+@creator: Ralph Amissah
+
+@rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3
+
+@type: information
+
+@subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+@date.created: 2002-08-28
+
+@date.issued: 2002-08-28
+
+@date.available: 2002-08-28
+
+@date.modified: 2007-09-16
+
+@date: 2007-09-16
+
+@level: new=C; break=1; num_top=1
+
+@skin: skin_sisu_manual
+
+@bold: /Gnu|Debian|Ruby|SiSU/
+
+@links: { SiSU Manual }http://www.jus.uio.no/sisu/sisu_manual/
+{ Book Samples and Markup Examples }http://www.jus.uio.no/sisu/SiSU/2.html
+{ SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
+{ SiSU @ Freshmeat }http://freshmeat.net/projects/sisu/
+{ SiSU @ Ruby Application Archive }http://raa.ruby-lang.org/project/sisu/
+{ SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html
+{ SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html
+{ SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html
+{ SiSU help }http://www.jus.uio.no/sisu/sisu_manual/sisu_help/
+{ SiSU help sources }http://www.jus.uio.no/sisu/sisu_manual/sisu_help_sources/
+
+:A~? @title @creator
+
+:B~? What is SiSU?
+
+:C~? Description
+
+1~sisu_intro Introduction - What is SiSU?
+
+SiSU is a system for document markup, publishing (in multiple open standard formats) and search
+
+SiSU~{ "SiSU information Structuring Universe" or "Structured information, Serialized Units".<br>also chosen for the meaning of the Finnish term "sisu". }~ is a~{ Unix command line oriented }~ framework for document structuring, publishing and search, comprising of (a) a lightweight document structure and presentation markup syntax and (b) an accompanying engine for generating standard document format outputs from documents prepared in sisu markup syntax, which is able to produce multiple standard outputs that (can) share a common numbering system for the citation of text within a document.
+
+SiSU is developed under an open source, software libre license (GPL3). It has been developed in the context of coping with large document sets with evolving markup related technologies, for which you want multiple output formats, a common mechanism for cross-output-format citation, and search.
+
+SiSU both defines a markup syntax and provides an engine that produces open standards format outputs from documents prepared with SiSU markup. From a single lightly prepared document sisu custom builds several standard output formats which share a common (text object) numbering system for citation of content within a document (that also has implications for search). The sisu engine works with an abstraction of the document's structure and content from which it is possible to generate different forms of representation of the document. Significantly SiSU markup is more sparse than html and outputs which include html, LaTeX, landscape and portrait pdfs, Open Document Format (ODF), all of which can be added to and updated. SiSU is also able to populate SQL type databases at an object level, which means that searches can be made with that degree of granularity. Results of objects (primarily paragraphs and headings) can be viewed directly in the database, or just the object numbers shown - your search criteria is met in these documents and at these locations within each document.
+
+Source document preparation and output generation is a two step process: (i) document source is prepared, that is, marked up in sisu markup syntax and (ii) the desired output subsequently generated by running the sisu engine against document source. Output representations if updated (in the sisu engine) can be generated by re-running the engine against the prepared source. Using SiSU markup applied to a document, SiSU custom builds various standard open output formats including plain text, HTML, XHTML, XML, OpenDocument, LaTeX or PDF files, and populate an SQL database with objects~{ 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. }~ (equating generally to paragraph-sized chunks) so searches may be performed and matches returned with that degree of granularity ( e.g. your search criteria is met by these documents and at these locations within each document). Document output formats share a common object numbering system for locating content. This is particularly suitable for "published" works (finalized texts as opposed to works that are frequently changed or updated) for which it provides a fixed means of reference of content.
+
+In preparing a SiSU document you optionally provide semantic information related to the document in a document header, and in marking up the substantive text provide information on the structure of the document, primarily indicating heading levels and footnotes. You also provide information on basic text attributes where used. The rest is automatic, sisu from this information custom builds~{ i.e. the html, pdf, odf 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. }~ the different forms of output requested.
+
+SiSU works with an abstraction of the document based on its structure which is comprised of its frame~{ the different heading levels }~ and the objects~{ units of text, primarily paragraphs and headings, also any tables, poems, code-blocks }~ it contains, which enables SiSU to represent the document in many different ways, and to take advantage of the strengths of different ways of presenting documents. The objects are numbered, and these numbers can be used to provide a common base for citing material within a document across the different output format types. This is significant as page numbers are not suited to the digital age, in web publishing, changing a browser's default font or using a different browser means that text appears on different pages; and in publishing in different formats, html, landscape and portrait pdf etc. again page numbers are of no use to cite text in a manner that is relevant against the different output types. Dealing with documents at an object level together with object numbering also has implications for search.
+
+One of the challenges of maintaining documents is to keep them in a format that would allow users to use them without depending on a proprietary software popular at the time. Consider the ease of dealing with legacy proprietary formats today and what guarantee you have that old proprietary formats will remain (or can be read without proprietary software/equipment) in 15 years time, or the way the way in which html has evolved over its relatively short span of existence. SiSU provides the flexibility of outputing documents in multiple non-proprietary open formats including html, pdf~{ Specification submitted by Adobe to ISO to become a full open ISO specification <br> http://www.linux-watch.com/news/NS7542722606.html }~ and the ISO standard ODF.~{ ISO/IEC 26300:2006 }~ Whilst SiSU relies on software, the markup is uncomplicated and minimalistic which guarantees that future engines can be written to run against it. It is also easily converted to other formats, which means documents prepared in SiSU can be migrated to other document formats. Further security is provided by the fact that the software itself, SiSU is available under GPL3 a licence that guarantees that the source code will always be open, and free as in libre which means that that code base can be used updated and further developed as required under the terms of its license. Another challenge is to keep up with a moving target. SiSU permits new forms of output to be added as they become important, (Open Document Format text was added in 2006), and existing output to be updated (html has evolved and the related module has been updated repeatedly over the years, presumably when the World Wide Web Consortium (w3c) finalises html 5 which is currently under development, the html module will again be updated allowing all existing documents to be regenerated as html 5).
+
+The document formats are written to the file-system and available for indexing by independent indexing tools, whether off the web like Google and Yahoo or on the site like Lucene and Hyperestraier.
+
+SiSU also provides other features such as concordance files and document content certificates, and the working against an abstraction of document structure has further possibilities for the research and development of other document representations, the availability of objects is useful for example for topic maps and the commercial law thesaurus by Vikki Rogers and Al Krtizer, together with the flexibility of SiSU offers great possibilities.
+
+SiSU is primarily for published works, which can take advantage of the citation system to reliably reference its documents. SiSU works well in a complementary manner with such collaborative technologies as Wikis, which can take advantage of and be used to discuss the substance of content prepared in SiSU.
+
+http://www.jus.uio.no/sisu
+
+% SiSU is a way of preparing, publishing, managing and searching documents.
+
+1~sisu_how How does sisu work?
+
+SiSU markup is fairly minimalistic, it consists of: a (largely optional) document header, made up of information about the document (such as when it was published, who authored it, and granting what rights) and any processing instructions; and markup within the substantive text of the document, which is related to document structure and typeface. SiSU must be able to discern the structure of a document, (text headings and their levels in relation to each other), either from information provided in the document header or from markup within the text (or from a combination of both). Processing is done against an abstraction of the document comprising of information on the document's structure and its objects,[2] which the program serializes (providing the object numbers) and which are assigned hash sum values based on their content. This abstraction of information about document structure, objects, (and hash sums), provides considerable flexibility in representing documents different ways and for different purposes (e.g. search, document layout, publishing, content certification, concordance etc.), and makes it possible to take advantage of some of the strengths of established ways of representing documents, (or indeed to create new ones).
+
+1~sisu_feature_summary Summary of features
+
+_* sparse/minimal markup (clean utf-8 source texts). Documents are prepared in a single UTF-8 file using a minimalistic mnemonic syntax. Typical literature, documents like "War and Peace" require almost no markup, and most of the headers are optional.
+
+_* markup is easily readable/parsable by the human eye, (basic markup is simpler and more sparse than the most basic HTML), [this may also be converted to XML representations of the same input/source document].
+
+_* markup defines document structure (this may be done once in a header pattern-match description, or for heading levels individually); basic text attributes (bold, italics, underscore, strike-through etc.) as required; and semantic information related to the document (header information, extended beyond the Dublin core and easily further extended as required); the headers may also contain processing instructions. SiSU markup is primarily an abstraction of document structure and document metadata to permit taking advantage of the basic strengths of existing alternative practical standard ways of representing documents [be that browser viewing, paper publication, sql search etc.] (html, xml, odf, latex, pdf, sql)
+
+_* for output produces reasonably elegant output of established industry and institutionally accepted open standard formats.[3] takes advantage of the different strengths of various standard formats for representing documents, amongst the output formats currently supported are:
+
+_1* html - both as a single scrollable text and a segmented document
+
+_1* xhtml
+
+_1* XML - both in sax and dom style xml structures for further development as required
+
+_1* ODF - open document format, the iso standard for document storage
+
+_1* LaTeX - used to generate pdf
+
+_1* pdf (via LaTeX)
+
+_1* sql - population of an sql database, (at the same object level that is used to cite text within a document)
+
+Also produces: concordance files; document content certificates (md5 or sha256 digests of headings, paragraphs, images etc.) and html manifests (and sitemaps of content). (b) takes advantage of the strengths implicit in these very different output types, (e.g. PDFs produced using typesetting of LaTeX, databases populated with documents at an individual object/paragraph level, making possible granular search (and related possibilities))
+
+_* ensuring content can be cited in a meaningful way regardless of selected output format. Online publishing (and publishing in multiple document formats) lacks a useful way of citing text internally within documents (important to academics generally and to lawyers) as page numbers are meaningless across browsers and formats. sisu seeks to provide a common way of pinpoint the text within a document, (which can be utilized for citation and by search engines). The outputs share a common numbering system that is meaningful (to man and machine) across all digital outputs whether paper, screen, or database oriented, (pdf, HTML, xml, sqlite, postgresql), this numbering system can be used to reference content.
+
+_* Granular search within documents. SQL databases are populated at an object level (roughly headings, paragraphs, verse, tables) and become searchable with that degree of granularity, the output information provides the object/paragraph numbers which are relevant across all generated outputs; it is also possible to look at just the matching paragraphs of the documents in the database; [output indexing also work well with search indexing tools like hyperestraier].
+
+_* long term maintainability of document collections in a world of changing formats, having a very sparsely marked-up source document base. there is a considerable degree of future-proofing, output representations are "upgradeable", and new document formats may be added. e.g. addition of odf (open document text) module in 2006 and in future html5 output sometime in future, without modification of existing prepared texts
+
+_* SQL search aside, documents are generated as required and static once generated.
+
+_* documents produced are static files, and may be batch processed, this needs to be done only once but may be repeated for various reasons as desired (updated content, addition of new output formats, updated technology document presentations/representations)
+
+_* document source (plaintext utf-8) if shared on the net may be used as input and processed locally to produce the different document outputs
+
+_* document source may be bundled together (automatically) with associated documents (multiple language versions or master document with inclusions) and images and sent as a zip file called a sisupod, if shared on the net these too may be processed locally to produce the desired document outputs
+
+_* generated document outputs may automatically be posted to remote sites.
+
+_* for basic document generation, the only software dependency is Ruby, and a few standard Unix tools (this covers plaintext, HTML, XML, ODF, LaTeX). To use a database you of course need that, and to convert the LaTeX generated to pdf, a latex processor like tetex or texlive.
+
+_* as a developers tool it is flexible and extensible
+
+Syntax highlighting for SiSU markup is available for a number of text editors.
+
+SiSU is less about document layout than about finding a way with little markup to be able to construct an abstract representation of a document that makes it possible to produce multiple representations of it which may be rather different from each other and used for different purposes, whether layout and publishing, or search of content
+
+i.e. to be able to take advantage from this minimal preparation starting point of some of the strengths of rather different established ways of representing documents for different purposes, whether for search (relational database, or indexed flat files generated for that purpose whether of complete documents, or say of files made up of objects), online viewing (e.g. html, xml, pdf), or paper publication (e.g. pdf)...
+
+the solution arrived at is by extracting structural information about the document (about headings within the document) and by tracking objects (which are serialized and also given hash values) in the manner described. It makes 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.
+
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_sqlite.sst b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_sqlite.sst
index 74f8c84f..a9252056 100644
--- a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_sqlite.sst
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_sqlite.sst
@@ -28,6 +28,11 @@
 
 @bold: /Gnu|Debian|Ruby|SiSU/
 
+@man: 8;
+name=sisu - package to install what sisu needs to to populate a postgresql database (postgresql dependency component)
+synopsis=sisu -dv [filename/wildcard ]
+sisu -dv [instruction]
+
 @links: { SiSU Manual }http://www.jus.uio.no/sisu/sisu_manual/
 { Book Samples and Markup Examples }http://www.jus.uio.no/sisu/SiSU/2.html
 { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_summary_of_features.ssi b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_summary_of_features.ssi
new file mode 100644
index 00000000..9a2e2ddd
--- /dev/null
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_summary_of_features.ssi
@@ -0,0 +1,133 @@
+% SiSU 0.58
+
+@title: SiSU
+
+@subtitle: Commands
+
+@creator: Ralph Amissah
+
+@rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3
+
+@type: information
+
+@subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+@date.created: 2002-08-28
+
+@date.issued: 2002-08-28
+
+@date.available: 2002-08-28
+
+@date.modified: 2007-09-16
+
+@date: 2007-09-16
+
+@level: new=C; break=1; num_top=1
+
+@skin: skin_sisu_manual
+
+@bold: /Gnu|Debian|Ruby|SiSU/
+
+@links: { SiSU Manual }http://www.jus.uio.no/sisu/sisu_manual/
+{ Book Samples and Markup Examples }http://www.jus.uio.no/sisu/SiSU/2.html
+{ SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
+{ SiSU @ Freshmeat }http://freshmeat.net/projects/sisu/
+{ SiSU @ Ruby Application Archive }http://raa.ruby-lang.org/project/sisu/
+{ SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html
+{ SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html
+{ SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html
+{ SiSU help }http://www.jus.uio.no/sisu/sisu_manual/sisu_help/
+{ SiSU help sources }http://www.jus.uio.no/sisu/sisu_manual/sisu_help_sources/
+
+:A~? @title @creator
+
+:B~? What is SiSU?
+
+:C~? Description
+
+1~sisu_intro Introduction - What is SiSU?
+
+SiSU is a system for document markup, publishing (in multiple open standard formats) and search
+
+SiSU~{ "SiSU information Structuring Universe" or "Structured information, Serialized Units".<br>also chosen for the meaning of the Finnish term "sisu". }~ is a~{ Unix command line oriented }~ framework for document structuring, publishing and search, comprising of (a) a lightweight document structure and presentation markup syntax and (b) an accompanying engine for generating standard document format outputs from documents prepared in sisu markup syntax, which is able to produce multiple standard outputs that (can) share a common numbering system for the citation of text within a document.
+
+SiSU is developed under an open source, software libre license (GPL3). It has been developed in the context of coping with large document sets with evolving markup related technologies, for which you want multiple output formats, a common mechanism for cross-output-format citation, and search.
+
+SiSU both defines a markup syntax and provides an engine that produces open standards format outputs from documents prepared with SiSU markup. From a single lightly prepared document sisu custom builds several standard output formats which share a common (text object) numbering system for citation of content within a document (that also has implications for search). The sisu engine works with an abstraction of the document's structure and content from which it is possible to generate different forms of representation of the document. Significantly SiSU markup is more sparse than html and outputs which include html, LaTeX, landscape and portrait pdfs, Open Document Format (ODF), all of which can be added to and updated. SiSU is also able to populate SQL type databases at an object level, which means that searches can be made with that degree of granularity. Results of objects (primarily paragraphs and headings) can be viewed directly in the database, or just the object numbers shown - your search criteria is met in these documents and at these locations within each document.
+
+Source document preparation and output generation is a two step process: (i) document source is prepared, that is, marked up in sisu markup syntax and (ii) the desired output subsequently generated by running the sisu engine against document source. Output representations if updated (in the sisu engine) can be generated by re-running the engine against the prepared source. Using SiSU markup applied to a document, SiSU custom builds various standard open output formats including plain text, HTML, XHTML, XML, OpenDocument, LaTeX or PDF files, and populate an SQL database with objects~{ 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. }~ (equating generally to paragraph-sized chunks) so searches may be performed and matches returned with that degree of granularity ( e.g. your search criteria is met by these documents and at these locations within each document). Document output formats share a common object numbering system for locating content. This is particularly suitable for "published" works (finalized texts as opposed to works that are frequently changed or updated) for which it provides a fixed means of reference of content.
+
+In preparing a SiSU document you optionally provide semantic information related to the document in a document header, and in marking up the substantive text provide information on the structure of the document, primarily indicating heading levels and footnotes. You also provide information on basic text attributes where used. The rest is automatic, sisu from this information custom builds~{ i.e. the html, pdf, odf 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. }~ the different forms of output requested.
+
+SiSU works with an abstraction of the document based on its structure which is comprised of its frame~{ the different heading levels }~ and the objects~{ units of text, primarily paragraphs and headings, also any tables, poems, code-blocks }~ it contains, which enables SiSU to represent the document in many different ways, and to take advantage of the strengths of different ways of presenting documents. The objects are numbered, and these numbers can be used to provide a common base for citing material within a document across the different output format types. This is significant as page numbers are not suited to the digital age, in web publishing, changing a browser's default font or using a different browser means that text appears on different pages; and in publishing in different formats, html, landscape and portrait pdf etc. again page numbers are of no use to cite text in a manner that is relevant against the different output types. Dealing with documents at an object level together with object numbering also has implications for search.
+
+One of the challenges of maintaining documents is to keep them in a format that would allow users to use them without depending on a proprietary software popular at the time. Consider the ease of dealing with legacy proprietary formats today and what guarantee you have that old proprietary formats will remain (or can be read without proprietary software/equipment) in 15 years time, or the way the way in which html has evolved over its relatively short span of existence. SiSU provides the flexibility of outputing documents in multiple non-proprietary open formats including html, pdf~{ Specification submitted by Adobe to ISO to become a full open ISO specification <br> http://www.linux-watch.com/news/NS7542722606.html }~ and the ISO standard ODF.~{ ISO/IEC 26300:2006 }~ Whilst SiSU relies on software, the markup is uncomplicated and minimalistic which guarantees that future engines can be written to run against it. It is also easily converted to other formats, which means documents prepared in SiSU can be migrated to other document formats. Further security is provided by the fact that the software itself, SiSU is available under GPL3 a licence that guarantees that the source code will always be open, and free as in libre which means that that code base can be used updated and further developed as required under the terms of its license. Another challenge is to keep up with a moving target. SiSU permits new forms of output to be added as they become important, (Open Document Format text was added in 2006), and existing output to be updated (html has evolved and the related module has been updated repeatedly over the years, presumably when the World Wide Web Consortium (w3c) finalises html 5 which is currently under development, the html module will again be updated allowing all existing documents to be regenerated as html 5).
+
+The document formats are written to the file-system and available for indexing by independent indexing tools, whether off the web like Google and Yahoo or on the site like Lucene and Hyperestraier.
+
+SiSU also provides other features such as concordance files and document content certificates, and the working against an abstraction of document structure has further possibilities for the research and development of other document representations, the availability of objects is useful for example for topic maps and the commercial law thesaurus by Vikki Rogers and Al Krtizer, together with the flexibility of SiSU offers great possibilities.
+
+SiSU is primarily for published works, which can take advantage of the citation system to reliably reference its documents. SiSU works well in a complementary manner with such collaborative technologies as Wikis, which can take advantage of and be used to discuss the substance of content prepared in SiSU.
+
+http://www.jus.uio.no/sisu
+
+% SiSU is a way of preparing, publishing, managing and searching documents.
+
+1~sisu_how How does sisu work?
+
+SiSU markup is fairly minimalistic, it consists of: a (largely optional) document header, made up of information about the document (such as when it was published, who authored it, and granting what rights) and any processing instructions; and markup within the substantive text of the document, which is related to document structure and typeface. SiSU must be able to discern the structure of a document, (text headings and their levels in relation to each other), either from information provided in the document header or from markup within the text (or from a combination of both). Processing is done against an abstraction of the document comprising of information on the document's structure and its objects,[2] which the program serializes (providing the object numbers) and which are assigned hash sum values based on their content. This abstraction of information about document structure, objects, (and hash sums), provides considerable flexibility in representing documents different ways and for different purposes (e.g. search, document layout, publishing, content certification, concordance etc.), and makes it possible to take advantage of some of the strengths of established ways of representing documents, (or indeed to create new ones).
+
+1~sisu_feature_summary Summary of features
+
+_* sparse/minimal markup (clean utf-8 source texts). Documents are prepared in a single UTF-8 file using a minimalistic mnemonic syntax. Typical literature, documents like "War and Peace" require almost no markup, and most of the headers are optional.
+
+_* markup is easily readable/parsable by the human eye, (basic markup is simpler and more sparse than the most basic HTML), [this may also be converted to XML representations of the same input/source document].
+
+_* markup defines document structure (this may be done once in a header pattern-match description, or for heading levels individually); basic text attributes (bold, italics, underscore, strike-through etc.) as required; and semantic information related to the document (header information, extended beyond the Dublin core and easily further extended as required); the headers may also contain processing instructions. SiSU markup is primarily an abstraction of document structure and document metadata to permit taking advantage of the basic strengths of existing alternative practical standard ways of representing documents [be that browser viewing, paper publication, sql search etc.] (html, xml, odf, latex, pdf, sql)
+
+_* for output produces reasonably elegant output of established industry and institutionally accepted open standard formats.[3] takes advantage of the different strengths of various standard formats for representing documents, amongst the output formats currently supported are:
+
+_1* html - both as a single scrollable text and a segmented document
+
+_1* xhtml
+
+_1* XML - both in sax and dom style xml structures for further development as required
+
+_1* ODF - open document format, the iso standard for document storage
+
+_1* LaTeX - used to generate pdf
+
+_1* pdf (via LaTeX)
+
+_1* sql - population of an sql database, (at the same object level that is used to cite text within a document)
+
+Also produces: concordance files; document content certificates (md5 or sha256 digests of headings, paragraphs, images etc.) and html manifests (and sitemaps of content). (b) takes advantage of the strengths implicit in these very different output types, (e.g. PDFs produced using typesetting of LaTeX, databases populated with documents at an individual object/paragraph level, making possible granular search (and related possibilities))
+
+_* ensuring content can be cited in a meaningful way regardless of selected output format. Online publishing (and publishing in multiple document formats) lacks a useful way of citing text internally within documents (important to academics generally and to lawyers) as page numbers are meaningless across browsers and formats. sisu seeks to provide a common way of pinpoint the text within a document, (which can be utilized for citation and by search engines). The outputs share a common numbering system that is meaningful (to man and machine) across all digital outputs whether paper, screen, or database oriented, (pdf, HTML, xml, sqlite, postgresql), this numbering system can be used to reference content.
+
+_* Granular search within documents. SQL databases are populated at an object level (roughly headings, paragraphs, verse, tables) and become searchable with that degree of granularity, the output information provides the object/paragraph numbers which are relevant across all generated outputs; it is also possible to look at just the matching paragraphs of the documents in the database; [output indexing also work well with search indexing tools like hyperestraier].
+
+_* long term maintainability of document collections in a world of changing formats, having a very sparsely marked-up source document base. there is a considerable degree of future-proofing, output representations are "upgradeable", and new document formats may be added. e.g. addition of odf (open document text) module in 2006 and in future html5 output sometime in future, without modification of existing prepared texts
+
+_* SQL search aside, documents are generated as required and static once generated.
+
+_* documents produced are static files, and may be batch processed, this needs to be done only once but may be repeated for various reasons as desired (updated content, addition of new output formats, updated technology document presentations/representations)
+
+_* document source (plaintext utf-8) if shared on the net may be used as input and processed locally to produce the different document outputs
+
+_* document source may be bundled together (automatically) with associated documents (multiple language versions or master document with inclusions) and images and sent as a zip file called a sisupod, if shared on the net these too may be processed locally to produce the desired document outputs
+
+_* generated document outputs may automatically be posted to remote sites.
+
+_* for basic document generation, the only software dependency is Ruby, and a few standard Unix tools (this covers plaintext, HTML, XML, ODF, LaTeX). To use a database you of course need that, and to convert the LaTeX generated to pdf, a latex processor like tetex or texlive.
+
+_* as a developers tool it is flexible and extensible
+
+Syntax highlighting for SiSU markup is available for a number of text editors.
+
+SiSU is less about document layout than about finding a way with little markup to be able to construct an abstract representation of a document that makes it possible to produce multiple representations of it which may be rather different from each other and used for different purposes, whether layout and publishing, or search of content
+
+i.e. to be able to take advantage from this minimal preparation starting point of some of the strengths of rather different established ways of representing documents for different purposes, whether for search (relational database, or indexed flat files generated for that purpose whether of complete documents, or say of files made up of objects), online viewing (e.g. html, xml, pdf), or paper publication (e.g. pdf)...
+
+the solution arrived at is by extracting structural information about the document (about headings within the document) and by tracking objects (which are serialized and also given hash values) in the manner described. It makes 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.
+
diff --git a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_webrick.sst b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_webrick.sst
index c7d450f2..e9454cba 100644
--- a/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_webrick.sst
+++ b/data/doc/sisu/sisu_markup_samples/sisu_manual/sisu_webrick.sst
@@ -28,6 +28,10 @@
 
 @bold: /Gnu|Debian|Ruby|SiSU/
 
+@man: 8;
+name=sisu - documents: structuring, publishing in multiple formats, and search;
+synopsis=sisu -W
+
 @links: { Book Samples and Markup Examples }http://www.jus.uio.no/sisu/SiSU/2.html
 { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
 { SiSU @ Freshmeat }http://freshmeat.net/projects/sisu/
diff --git a/data/sisu/conf/editor-syntax-etc/vim/syntax/sisu.vim b/data/sisu/conf/editor-syntax-etc/vim/syntax/sisu.vim
index c1a44ee5..791d0c47 100644
--- a/data/sisu/conf/editor-syntax-etc/vim/syntax/sisu.vim
+++ b/data/sisu/conf/editor-syntax-etc/vim/syntax/sisu.vim
@@ -42,10 +42,8 @@ syn match sisu_error             contains=sisu_error "<a href\|</a>]"
 "%   url/link
 syn region sisu_link contains=sisu_error,sisu_error_wspace matchgroup=sisu_action start="^<<\s*|[a-zA-Z0-9^._-]\+|@|[a-zA-Z0-9^._-]\+|"rs=s+2 end="$"
 "%   header
-syn region sisu_header_content contains=sisu_error,sisu_error_wspace,sisu_content_alt,sisu_link,sisu_linked,sisu_break matchgroup=sisu_header start="^0\~\(\S\+\|[^-]\)" end="$"
-syn region sisu_header_content contains=sisu_error,sisu_error_wspace,sisu_content_alt,sisu_link,sisu_linked,sisu_break matchgroup=sisu_header start="^0\~\(tags\?\|date\)\s\+"rs=e-1 end="\n$"
-syn region sisu_header_content contains=sisu_error,sisu_error_wspace,sisu_content_alt,sisu_link,sisu_linked,sisu_break matchgroup=sisu_header start="^@\S\+:[+-]\?\s"rs=e-1 end="$"
-syn region sisu_header_content contains=sisu_error,sisu_error_wspace,sisu_content_alt,sisu_link,sisu_linked,sisu_break matchgroup=sisu_header start="^@\(tags\?\|date\):\s\+"rs=e-1 end="\n$"
+syn region sisu_header_content contains=sisu_error,sisu_error_wspace,sisu_content_alt,sisu_link,sisu_linked,sisu_break matchgroup=sisu_header start="^0\~\(\S\+\|[^-]\)" end="\n$"
+syn region sisu_header_content contains=sisu_error,sisu_error_wspace,sisu_content_alt,sisu_link,sisu_linked,sisu_break matchgroup=sisu_header start="^@\S\+:[+-]\?\s"rs=e-1 end="\n$"
 "%   headings
 syn region sisu_heading contains=sisu_mark_endnote,sisu_content_endnote,sisu_marktail,sisu_strikeout,sisu_number,sisu_control,sisu_identifier,sisu_ocn,sisu_error,sisu_error_wspace matchgroup=sisu_structure start="^\([1-8]\|:\?[A-C]\)\~\(\S\+\|[^-]\)" end="$"
 "%   grouped text