#{title} by #{author}

} end @@ -977,7 +978,9 @@ WOK end def para_form_css(tag,attrib) # regular paragraphs shaped here ul=ulc='' - ul,ulc="

#{@p_num.ocn_display} @@ -1250,7 +1253,7 @@ WOK note=$1 note=note.gsub(/[\s]+/m,' ') txt=txt.gsub(/(?:#{Mx[:en_a_o]}.+?#{Mx[:en_a_c]}|#{Mx[:en_b_o]}.+?#{Mx[:en_b_c]})\s*/m,' '). - gsub(/ ^{\d+<\/sup> /m,'')
+ gsub(/ ^{\d+<\/sup> /m,'')
end
%{<#{tag} class="#{attrib}">
#{txt} #{note}
diff --git a/lib/sisu/v5/html_tune.rb b/lib/sisu/v5/html_tune.rb
index 84336861..39cbb708 100644
--- a/lib/sisu/v5/html_tune.rb
+++ b/lib/sisu/v5/html_tune.rb
@@ -104,6 +104,16 @@ module SiSU_HTML_Tune
def initialize(html='')
@html=html
end
+ def clean_for_html
+ html=@html
+ str=if html.is_a?(String)
+ html
+ else html.obj
+ end
+ str=str.gsub(/#{Mx[:gl_o]}(#[0-9]{3})#{Mx[:gl_c]}/u,'&\1;').
+ gsub(/#{Mx[:gl_o]}#([a-z]{2,4})#{Mx[:gl_c]}/u,'&\1;').
+ gsub(/[<]/m,'<').gsub(/[>]/m,'>')
+ end
def clean
html=@html
str=if html.is_a?(String)
@@ -111,7 +121,8 @@ module SiSU_HTML_Tune
else html.obj
end
str=str.gsub(/#{Mx[:gl_o]}(#[0-9]{3})#{Mx[:gl_c]}/u,'&\1;').
- gsub(/#{Mx[:gl_o]}#([a-z]{2,4})#{Mx[:gl_c]}/u,'&\1;')
+ gsub(/#{Mx[:gl_o]}#([a-z]{2,4})#{Mx[:gl_c]}/u,'&\1;').
+ gsub(/[\\]{2}/m,'
')
end
end
class Tune
diff --git a/lib/sisu/v6/html.rb b/lib/sisu/v6/html.rb
index f1651326..8c9869e2 100644
--- a/lib/sisu/v6/html.rb
+++ b/lib/sisu/v6/html.rb
@@ -623,7 +623,8 @@ WOK
toc_shared << format_txt_obj.center_bold
@segtoc << format_txt_obj.center_bold
if defined? @md.creator.author
- creator_endnote=@md.creator.author.gsub(/(\*+)/,
+ creator=SiSU_HTML_Tune::CleanHTML.new(@md.creator.author).clean_for_html
+ creator_endnote=creator.gsub(/(\*+)/,
%{ ^\\1})
tmp_head=creator_endnote + "\n"
txt_obj={ txt: tmp_head }
diff --git a/lib/sisu/v6/html_format.rb b/lib/sisu/v6/html_format.rb
index 63271d95..de5a7144 100644
--- a/lib/sisu/v6/html_format.rb
+++ b/lib/sisu/v6/html_format.rb
@@ -502,7 +502,8 @@ WOK
end
def rights
def all
- rights=@md.rights.all.gsub(/^\s*Copyright\s+$C$/,'Copyright ^© ')
+ rights=SiSU_HTML_Tune::CleanHTML.new(@md.rights.all).clean_for_html
+ rights=rights.gsub(/^\s*Copyright\s+$C$/,'Copyright ^© ')
%{Rights: #{rights}
}
end
@@ -977,7 +978,9 @@ WOK
end
def para_form_css(tag,attrib) # regular paragraphs shaped here
ul=ulc=''
- ul,ulc="
\n ","\n " if @tag =~/li/
+ if tag =~/li/
+ ul,ulc="\n ","\n "
+ end
%{

#{@p_num.ocn_display}
@@ -1250,7 +1253,7 @@ WOK
note=$1
note=note.gsub(/[\s]+/m,' ')
txt=txt.gsub(/(?:#{Mx[:en_a_o]}.+?#{Mx[:en_a_c]}|#{Mx[:en_b_o]}.+?#{Mx[:en_b_c]})\s*/m,' ').
- gsub(/ ^{\d+<\/sup> /m,'')
+ gsub(/ ^{\d+<\/sup> /m,'')
end
%{<#{tag} class="#{attrib}">
#{txt} #{note}
diff --git a/lib/sisu/v6/html_tune.rb b/lib/sisu/v6/html_tune.rb
index 516deaa5..42568a36 100644
--- a/lib/sisu/v6/html_tune.rb
+++ b/lib/sisu/v6/html_tune.rb
@@ -104,6 +104,16 @@ module SiSU_HTML_Tune
def initialize(html='')
@html=html
end
+ def clean_for_html
+ html=@html
+ str=if html.is_a?(String)
+ html
+ else html.obj
+ end
+ str=str.gsub(/#{Mx[:gl_o]}(#[0-9]{3})#{Mx[:gl_c]}/u,'&\1;').
+ gsub(/#{Mx[:gl_o]}#([a-z]{2,4})#{Mx[:gl_c]}/u,'&\1;').
+ gsub(/[<]/m,'<').gsub(/[>]/m,'>')
+ end
def clean
html=@html
str=if html.is_a?(String)
@@ -111,7 +121,8 @@ module SiSU_HTML_Tune
else html.obj
end
str=str.gsub(/#{Mx[:gl_o]}(#[0-9]{3})#{Mx[:gl_c]}/u,'&\1;').
- gsub(/#{Mx[:gl_o]}#([a-z]{2,4})#{Mx[:gl_c]}/u,'&\1;')
+ gsub(/#{Mx[:gl_o]}#([a-z]{2,4})#{Mx[:gl_c]}/u,'&\1;').
+ gsub(/[\\]{2}/m,'
')
end
end
class Tune
--
cgit v1.2.3

From 0cad9edcc02c9816759c348f8c483cfa5c54dcf8 Mon Sep 17 00:00:00 2001
From: Ralph Amissah
Date: Wed, 5 Feb 2014 01:11:53 -0500
Subject: v5 v6: cgi (pgsql & sqlite), fix

---
data/doc/sisu/CHANGELOG_v5 | 2 ++
data/doc/sisu/CHANGELOG_v6 | 2 ++
lib/sisu/v5/cgi_pgsql.rb | 26 +++++++++++++-------------
lib/sisu/v5/cgi_sqlite.rb | 18 +++++++++---------
lib/sisu/v6/cgi_pgsql.rb | 26 +++++++++++++-------------
lib/sisu/v6/cgi_sqlite.rb | 18 +++++++++---------
6 files changed, 48 insertions(+), 44 deletions(-)

diff --git a/data/doc/sisu/CHANGELOG_v5 b/data/doc/sisu/CHANGELOG_v5
index 654a8fa6..ce118aec 100644
--- a/data/doc/sisu/CHANGELOG_v5
+++ b/data/doc/sisu/CHANGELOG_v5
@@ -58,6 +58,8 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_5.3.1.orig.tar.xz
* txt
* odt

+* cgi (pgsql, sqlite) fixes
+
* error/warn messages, including wrappers round require

%% 5.3.0.orig.tar.xz (2014-01-26:03/7)
diff --git a/data/doc/sisu/CHANGELOG_v6 b/data/doc/sisu/CHANGELOG_v6
index 4634ce09..6a861ac4 100644
--- a/data/doc/sisu/CHANGELOG_v6
+++ b/data/doc/sisu/CHANGELOG_v6
@@ -48,6 +48,8 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_6.0.1.orig.tar.xz
* txt
* odt

+* cgi (pgsql, sqlite) fixes
+
* error/warn messages, including wrappers round require

%% 6.0.0.orig.tar.xz (2014-01-26:03/7)
diff --git a/lib/sisu/v5/cgi_pgsql.rb b/lib/sisu/v5/cgi_pgsql.rb
index 0a514672..4281d9d3 100644
--- a/lib/sisu/v5/cgi_pgsql.rb
+++ b/lib/sisu/v5/cgi_pgsql.rb
@@ -74,12 +74,12 @@ module SiSU_CGI_PgSQL
get_init=SiSU_Env::GetInit.new
@rc=get_init.sisu_yaml.rc
@name_of={}
- @name_of[:output_dir_structure]=if @opt.dir_structure_by.to_s =~/(?:language|filetype|filename)/
- @opt.dir_structure_by.to_s
+ @name_of[:output_dir_structure]=if opt.dir_structure_by.to_s =~/(?:language|filetype|filename)/
+ opt.dir_structure_by.to_s
else 'language'
end
- @name_of[:lingual]=if @opt.lingual.to_s =~/(?:mono|multi)/
- @opt.lingual.to_s
+ @name_of[:lingual]=if opt.lingual.to_s =~/(?:mono|multi)/
+ opt.lingual.to_s
else 'multi'
end
if defined? @rc['search'] \
@@ -93,13 +93,13 @@ module SiSU_CGI_PgSQL
@name_of[:db]=@env.path.stub_pwd #'sisu' #breaks if not present
false
end
- @name_of[:host_url_cgi]="#{@env.url.webserv_base_cgi(@opt)}/cgi-bin"
- @name_of[:host_url_docs]=@env.url.webserv_files_from_db(@opt)
- @name_of[:cgi_script]=@env.url.cgi_sample_search_form_name(@opt)
- @name_of[:user]=@db.psql.user(@opt)
+ @name_of[:host_url_cgi]="#{@env.url.webserv_base_cgi(opt)}/cgi-bin"
+ @name_of[:host_url_docs]=@env.url.webserv_files_from_db(opt)
+ @name_of[:cgi_script]=@env.url.cgi_sample_search_form_name(opt)
+ @name_of[:user]=@db.psql.user(opt)
@cgi_file_name=@name_of[:cgi_script]
- @image_src="#{@env.url.webserv_base_cgi(@opt)}/_sisu/image_sys"
- @common=SiSU_CGI_SQL::CGI_Common.new(@webserv,@opt,@image_src,@env)
+ @image_src="#{@env.url.webserv_base_cgi(opt)}/_sisu/image_sys"
+ @common=SiSU_CGI_SQL::CGI_Common.new(@webserv,opt,@image_src,@env)
end
def pgsql
serve=[]
@@ -174,13 +174,13 @@ module SiSU_CGI_PgSQL
sudo chmod -v 755 /usr/lib/cgi-bin/#{@cgi_file_name}
WOK
end
- SiSU_Screen::Ansi.new(opt.act[:color_state][:set],a).warn
+ SiSU_Screen::Ansi.new(@opt.act[:color_state][:set],a).warn
a=<<-WOK
#{@env.webserv_base_cgi(@opt)}/cgi-bin/#{@cgi_file_name}
WOK
- SiSU_Screen::Ansi.new(opt.act[:color_state][:set],a).print_blue
+ SiSU_Screen::Ansi.new(@opt.act[:color_state][:set],a).print_blue
a="\n\t(to create and populate postgresql database see 'man sisu' and in particular the --pg option)\n\t[the database to be used for this directory (#{@db.psql.db}) will have to be created manually if it does not exist,\n\tusing postgresql tools directly: 'createdb #{@db.psql.db}' for a list of existing databases try 'psql --list']"
- SiSU_Screen::Ansi.new(opt.act[:color_state][:set],a).txt_grey
+ SiSU_Screen::Ansi.new(@opt.act[:color_state][:set],a).txt_grey
else puts 'failed in attempt to write #{@cgi_file_name} to present directory, is directory writable?'
end
end
diff --git a/lib/sisu/v5/cgi_sqlite.rb b/lib/sisu/v5/cgi_sqlite.rb
index aa38e6f1..c4222ecb 100644
--- a/lib/sisu/v5/cgi_sqlite.rb
+++ b/lib/sisu/v5/cgi_sqlite.rb
@@ -69,18 +69,18 @@ module SiSU_CGI_SQLite
@opt,@webserv=opt,webserv
@cX=SiSU_Screen::Ansi.new(opt.act[:color_state][:set]).cX
@env=SiSU_Env::InfoEnv.new('',opt)
- @image_src="#{@env.url.webserv_cgi(@opt)}/_sisu/image_sys"
+ @image_src="#{@env.url.webserv_cgi(opt)}/_sisu/image_sys"
@name_of={}
- @name_of[:output_dir_structure]=if @opt.dir_structure_by.to_s =~/(?:language|filetype|filename)/
- @opt.dir_structure_by.to_s
+ @name_of[:output_dir_structure]=if opt.dir_structure_by.to_s =~/(?:language|filetype|filename)/
+ opt.dir_structure_by.to_s
else 'language'
end
- @name_of[:lingual]=if @opt.lingual.to_s =~/(?:mono|multi)/
- @opt.lingual.to_s
+ @name_of[:lingual]=if opt.lingual.to_s =~/(?:mono|multi)/
+ opt.lingual.to_s
else 'multi'
end
- @common=SiSU_CGI_SQL::CGI_Common.new(@webserv,@opt,@image_src,@env)
- @cgi_file_name=@env.url.cgi_sample_search_form_name(@opt)
+ @common=SiSU_CGI_SQL::CGI_Common.new(@webserv,opt,@image_src,@env)
+ @cgi_file_name=@env.url.cgi_sample_search_form_name(opt)
@name_of_sqlite_db_file='sisu_sqlite.db'
end
def sqlite
@@ -147,13 +147,13 @@ module SiSU_CGI_SQLite
WOK
end
b='(to create and populate sisu sqlite database see "man sisu" and in particular the -d flag)'
- SiSU_Screen::Ansi.new(opt.act[:color_state][:set],a,b).warn
+ SiSU_Screen::Ansi.new(@opt.act[:color_state][:set],a,b).warn
a=<<-WOK

#{@env.webserv_base_cgi(@opt)}/cgi-bin/#{@cgi_file_name}

WOK
- SiSU_Screen::Ansi.new(opt.act[:color_state][:set],a).print_blue
+ SiSU_Screen::Ansi.new(@opt.act[:color_state][:set],a).print_blue
else puts "failed in attempt to write #{@cgi_file_name} to present directory, is directory writable?"
end
end
diff --git a/lib/sisu/v6/cgi_pgsql.rb b/lib/sisu/v6/cgi_pgsql.rb
index 3b0b610b..26db0341 100644
--- a/lib/sisu/v6/cgi_pgsql.rb
+++ b/lib/sisu/v6/cgi_pgsql.rb
@@ -74,12 +74,12 @@ module SiSU_CGI_PgSQL
get_init=SiSU_Env::GetInit.new
@rc=get_init.sisu_yaml.rc
@name_of={}
- @name_of[:output_dir_structure]=if @opt.dir_structure_by.to_s =~/(?:language|filetype|filename)/
- @opt.dir_structure_by.to_s
+ @name_of[:output_dir_structure]=if opt.dir_structure_by.to_s =~/(?:language|filetype|filename)/
+ opt.dir_structure_by.to_s
else 'language'
end
- @name_of[:lingual]=if @opt.lingual.to_s =~/(?:mono|multi)/
- @opt.lingual.to_s
+ @name_of[:lingual]=if opt.lingual.to_s =~/(?:mono|multi)/
+ opt.lingual.to_s
else 'multi'
end
if defined? @rc['search'] \
@@ -93,13 +93,13 @@ module SiSU_CGI_PgSQL
@name_of[:db]=@env.path.stub_pwd #'sisu' #breaks if not present
false
end
- @name_of[:host_url_cgi]="#{@env.url.webserv_base_cgi(@opt)}/cgi-bin"
- @name_of[:host_url_docs]=@env.url.webserv_files_from_db(@opt)
- @name_of[:cgi_script]=@env.url.cgi_sample_search_form_name(@opt)
- @name_of[:user]=@db.psql.user(@opt)
+ @name_of[:host_url_cgi]="#{@env.url.webserv_base_cgi(opt)}/cgi-bin"
+ @name_of[:host_url_docs]=@env.url.webserv_files_from_db(opt)
+ @name_of[:cgi_script]=@env.url.cgi_sample_search_form_name(opt)
+ @name_of[:user]=@db.psql.user(opt)
@cgi_file_name=@name_of[:cgi_script]
- @image_src="#{@env.url.webserv_base_cgi(@opt)}/_sisu/image_sys"
- @common=SiSU_CGI_SQL::CGI_Common.new(@webserv,@opt,@image_src,@env)
+ @image_src="#{@env.url.webserv_base_cgi(opt)}/_sisu/image_sys"
+ @common=SiSU_CGI_SQL::CGI_Common.new(@webserv,opt,@image_src,@env)
end
def pgsql
serve=[]
@@ -174,13 +174,13 @@ module SiSU_CGI_PgSQL
sudo chmod -v 755 /usr/lib/cgi-bin/#{@cgi_file_name}
WOK
end
- SiSU_Screen::Ansi.new(opt.act[:color_state][:set],a).warn
+ SiSU_Screen::Ansi.new(@opt.act[:color_state][:set],a).warn
a=<<-WOK
#{@env.webserv_base_cgi(@opt)}/cgi-bin/#{@cgi_file_name}
WOK
- SiSU_Screen::Ansi.new(opt.act[:color_state][:set],a).print_blue
+ SiSU_Screen::Ansi.new(@opt.act[:color_state][:set],a).print_blue
a="\n\t(to create and populate postgresql database see 'man sisu' and in particular the --pg option)\n\t[the database to be used for this directory (#{@db.psql.db}) will have to be created manually if it does not exist,\n\tusing postgresql tools directly: 'createdb #{@db.psql.db}' for a list of existing databases try 'psql --list']"
- SiSU_Screen::Ansi.new(opt.act[:color_state][:set],a).txt_grey
+ SiSU_Screen::Ansi.new(@opt.act[:color_state][:set],a).txt_grey
else puts 'failed in attempt to write #{@cgi_file_name} to present directory, is directory writable?'
end
end
diff --git a/lib/sisu/v6/cgi_sqlite.rb b/lib/sisu/v6/cgi_sqlite.rb
index daf915e6..6db31b48 100644
--- a/lib/sisu/v6/cgi_sqlite.rb
+++ b/lib/sisu/v6/cgi_sqlite.rb
@@ -69,18 +69,18 @@ module SiSU_CGI_SQLite
@opt,@webserv=opt,webserv
@cX=SiSU_Screen::Ansi.new(opt.act[:color_state][:set]).cX
@env=SiSU_Env::InfoEnv.new('',opt)
- @image_src="#{@env.url.webserv_cgi(@opt)}/_sisu/image_sys"
+ @image_src="#{@env.url.webserv_cgi(opt)}/_sisu/image_sys"
@name_of={}
- @name_of[:output_dir_structure]=if @opt.dir_structure_by.to_s =~/(?:language|filetype|filename)/
- @opt.dir_structure_by.to_s
+ @name_of[:output_dir_structure]=if opt.dir_structure_by.to_s =~/(?:language|filetype|filename)/
+ opt.dir_structure_by.to_s
else 'language'
end
- @name_of[:lingual]=if @opt.lingual.to_s =~/(?:mono|multi)/
- @opt.lingual.to_s
+ @name_of[:lingual]=if opt.lingual.to_s =~/(?:mono|multi)/
+ opt.lingual.to_s
else 'multi'
end
- @common=SiSU_CGI_SQL::CGI_Common.new(@webserv,@opt,@image_src,@env)
- @cgi_file_name=@env.url.cgi_sample_search_form_name(@opt)
+ @common=SiSU_CGI_SQL::CGI_Common.new(@webserv,opt,@image_src,@env)
+ @cgi_file_name=@env.url.cgi_sample_search_form_name(opt)
@name_of_sqlite_db_file='sisu_sqlite.db'
end
def sqlite
@@ -147,13 +147,13 @@ module SiSU_CGI_SQLite
WOK
end
b='(to create and populate sisu sqlite database see "man sisu" and in particular the -d flag)'
- SiSU_Screen::Ansi.new(opt.act[:color_state][:set],a,b).warn
+ SiSU_Screen::Ansi.new(@opt.act[:color_state][:set],a,b).warn
a=<<-WOK

#{@env.webserv_base_cgi(@opt)}/cgi-bin/#{@cgi_file_name}

WOK
- SiSU_Screen::Ansi.new(opt.act[:color_state][:set],a).print_blue
+ SiSU_Screen::Ansi.new(@opt.act[:color_state][:set],a).print_blue
else puts "failed in attempt to write #{@cgi_file_name} to present directory, is directory writable?"
end
end
--
cgit v1.2.3

From d6b74b93452e024b36c0b36eb181944477c2d5e6 Mon Sep 17 00:00:00 2001
From: Ralph Amissah
Date: Wed, 5 Feb 2014 01:15:55 -0500
Subject: removed html man pages (man2html)

---
data/doc/sisu/CHANGELOG_v5 | 3 +
data/doc/sisu/CHANGELOG_v6 | 3 +
data/doc/sisu/html/README | 6 -
data/doc/sisu/html/sisu-concordance.1.html | 69 -
data/doc/sisu/html/sisu-epub.1.html | 69 -
data/doc/sisu/html/sisu-git.1.html | 69 -
data/doc/sisu/html/sisu-harvest.1.html | 71 -
data/doc/sisu/html/sisu-html.1.html | 69 -
data/doc/sisu/html/sisu-odf.1.html | 69 -
data/doc/sisu/html/sisu-pdf.1.html | 69 -
data/doc/sisu/html/sisu-pg.1.html | 69 -
data/doc/sisu/html/sisu-po.1.html | 73 -
data/doc/sisu/html/sisu-sqlite.1.html | 69 -
data/doc/sisu/html/sisu-txt.1.html | 69 -
data/doc/sisu/html/sisu.1.html | 3290 ----------------------------
data/doc/sisu/html/sisu_complete.7.html | 54 -
data/doc/sisu/html/sisu_pdf.7.html | 171 --
data/doc/sisu/html/sisu_postgresql.7.html | 198 --
data/doc/sisu/html/sisu_sqlite.7.html | 196 --
data/doc/sisu/html/sisu_termsheet.1.html | 76 -
data/doc/sisu/html/sisu_vim.7.html | 62 -
data/doc/sisu/html/sisu_webrick.1.html | 93 -
22 files changed, 6 insertions(+), 4911 deletions(-)
delete mode 100644 data/doc/sisu/html/README
delete mode 100644 data/doc/sisu/html/sisu-concordance.1.html
delete mode 100644 data/doc/sisu/html/sisu-epub.1.html
delete mode 100644 data/doc/sisu/html/sisu-git.1.html
delete mode 100644 data/doc/sisu/html/sisu-harvest.1.html
delete mode 100644 data/doc/sisu/html/sisu-html.1.html
delete mode 100644 data/doc/sisu/html/sisu-odf.1.html
delete mode 100644 data/doc/sisu/html/sisu-pdf.1.html
delete mode 100644 data/doc/sisu/html/sisu-pg.1.html
delete mode 100644 data/doc/sisu/html/sisu-po.1.html
delete mode 100644 data/doc/sisu/html/sisu-sqlite.1.html
delete mode 100644 data/doc/sisu/html/sisu-txt.1.html
delete mode 100644 data/doc/sisu/html/sisu.1.html
delete mode 100644 data/doc/sisu/html/sisu_complete.7.html
delete mode 100644 data/doc/sisu/html/sisu_pdf.7.html
delete mode 100644 data/doc/sisu/html/sisu_postgresql.7.html
delete mode 100644 data/doc/sisu/html/sisu_sqlite.7.html
delete mode 100644 data/doc/sisu/html/sisu_termsheet.1.html
delete mode 100644 data/doc/sisu/html/sisu_vim.7.html
delete mode 100644 data/doc/sisu/html/sisu_webrick.1.html

diff --git a/data/doc/sisu/CHANGELOG_v5 b/data/doc/sisu/CHANGELOG_v5
index ce118aec..0388ffe8 100644
--- a/data/doc/sisu/CHANGELOG_v5
+++ b/data/doc/sisu/CHANGELOG_v5
@@ -62,6 +62,9 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_5.3.1.orig.tar.xz

* error/warn messages, including wrappers round require

+* documentation, manpage README etc.
+ * removed html man pages (man2html)
+
%% 5.3.0.orig.tar.xz (2014-01-26:03/7)
http://sources.sisudoc.org/gitweb/?p=code/sisu.git;a=shortlog;h=refs/tags/sisu_5.3.0
http://sources.sisudoc.org/gitweb/?p=code/sisu.git;a=shortlog;h=refs/tags/debian/sisu_5.3.0-1
diff --git a/data/doc/sisu/CHANGELOG_v6 b/data/doc/sisu/CHANGELOG_v6
index 6a861ac4..b1ef302a 100644
--- a/data/doc/sisu/CHANGELOG_v6
+++ b/data/doc/sisu/CHANGELOG_v6
@@ -52,6 +52,9 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_6.0.1.orig.tar.xz

* error/warn messages, including wrappers round require

+* documentation, manpage README etc.
+ * removed html man pages (man2html)
+
%% 6.0.0.orig.tar.xz (2014-01-26:03/7)
http://sources.sisudoc.org/gitweb/?p=code/sisu.git;a=shortlog;h=refs/tags/sisu_6.0.0
http://sources.sisudoc.org/gitweb/?p=code/sisu.git;a=shortlog;h=refs/tags/debian/sisu_6.0.0-1
diff --git a/data/doc/sisu/html/README b/data/doc/sisu/html/README
deleted file mode 100644
index c8ebc4ad..00000000
--- a/data/doc/sisu/html/README
+++ /dev/null
@@ -1,6 +0,0 @@
-this "html" directory contains SiSU man pages in html
-- generated from man pages using man2html
-
-man pages are either created by sisu from sisu markup documents contained in
-the directory "sisu_markup_samples/sisu_manual"
-or manually crafted
diff --git a/data/doc/sisu/html/sisu-concordance.1.html b/data/doc/sisu/html/sisu-concordance.1.html
deleted file mode 100644
index ef456d75..00000000
--- a/data/doc/sisu/html/sisu-concordance.1.html
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
-
-
-SISU-CONCORDANCE(1) manual page
-
-
-Table of Contents
-
-

-
Name
-SiSU - Structured information, Serialized Units - a document publishing
-
-system
-

-
Synopsis
-sisu-concordance sisu_document.sst | sisu_document.ssm
-
-
Description
-SiSU
-is a lightweight markup based document structuring, publishing and search
-framework for document collections.
-The sisu-concordance command is an alias
-for sisu --concordance (or sisu -w) which produces an HTML concordance file
-(wordlist) of a SiSU markup file.
-

-
See Also
-sisu(1)
-,

-sisu-epub(1)
-,

-sisu-harvest(1)
-,

-sisu-html(1)
-,

-sisu-pdf(1)
-,

-sisu-odf(1)
-,

-sisu-pg(1)
-,

-sisu-sqlite(1)
-,

-sisu-txt(1)
-.
-
-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-
-

-Table of Contents

-

-Name
-Synopsis
-Description
-See Also
-Homepage
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu-epub.1.html b/data/doc/sisu/html/sisu-epub.1.html
deleted file mode 100644
index 6a84b876..00000000
--- a/data/doc/sisu/html/sisu-epub.1.html
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
-
-
-SISU-EPUB(1) manual page
-
-
-Table of Contents
-
-

-
Name
-SiSU - Structured information, Serialized Units - a document publishing
-
-system
-

-
Synopsis
-sisu-epub sisu_document.sst | sisu_document.ssm
-
-
Description
-SiSU
-is a lightweight markup based document structuring, publishing and search
-framework for document collections.
-The sisu-epub command is an alias for
-sisu --epub (or sisu -e) which produces EPUB output of a SiSU markup file.
-
-

-
See Also
-sisu(1)
-,

-sisu-concordance(1)
-,

-sisu-harvest(1)
-,

-sisu-html(1)
-,

-sisu-pdf(1)
-,

-sisu-odf(1)
-,

-sisu-pg(1)
-,

-sisu-sqlite(1)
-,

-sisu-txt(1)
-.
-
-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-
-

-Table of Contents

-

-Name
-Synopsis
-Description
-See Also
-Homepage
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu-git.1.html b/data/doc/sisu/html/sisu-git.1.html
deleted file mode 100644
index a23d0118..00000000
--- a/data/doc/sisu/html/sisu-git.1.html
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
-
-
-SISU-GIT(1) manual page
-
-
-Table of Contents
-
-

-
Name
-SiSU - Structured information, Serialized Units - a document publishing
-
-system
-

-
Synopsis
-sisu-git sisu_document.sst | sisu_document.ssm
-
-
Description
-SiSU
-is a lightweight markup based document structuring, publishing and search
-framework for document collections.
-The sisu-git command is an alias for
-sisu --git (or sisu -g) which produces a git repository of the sisu source
-document and associated parts (images, ).
-

-
See Also
-sisu(1)
-,

-sisu-concordance(1)
-,

-sisu-epub(1)
-,

-sisu-harvest(1)
-,

-sisu-html(1)
-,

-sisu-pdf(1)
-,

-sisu-pg(1)
-,

-sisu-sqlite(1)
-,

-sisu-txt(1)
-.
-
-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-
-

-Table of Contents

-

-Name
-Synopsis
-Description
-See Also
-Homepage
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu-harvest.1.html b/data/doc/sisu/html/sisu-harvest.1.html
deleted file mode 100644
index 8d264278..00000000
--- a/data/doc/sisu/html/sisu-harvest.1.html
+++ /dev/null
@@ -1,71 +0,0 @@
-
-
-
-
-
-SISU-HARVEST(1) manual page
-
-
-Table of Contents
-
-

-
Name
-SiSU - Structured information, Serialized Units - a document publishing
-
-system
-

-
Synopsis
-sisu-harvest sisu_document.sst | sisu_document.ssm
-
-
Description
-SiSU
-is a lightweight markup based document structuring, publishing and search
-framework for document collections.
-The sisu-harvest command is an alias
-for sisu --harvest which based on the @classify: :topic_register: headers
-in each SiSU markup file, produces HTML output in the form of an index
-of authors and their texts and an index of topics and related texts.
-

-
See
-Also
-sisu(1)
-,

-sisu-concordance(1)
-,

-sisu-epub(1)
-,

-sisu-html(1)
-,

-sisu-pdf(1)
-,

-sisu-odf(1)
-,

-sisu-pg(1)
-,

-sisu-sqlite(1)
-,

-sisu-txt(1)
-.
-
-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-
-

-Table of Contents

-

-Name
-Synopsis
-Description
-See Also
-Homepage
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu-html.1.html b/data/doc/sisu/html/sisu-html.1.html
deleted file mode 100644
index a95b7796..00000000
--- a/data/doc/sisu/html/sisu-html.1.html
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
-
-
-SISU-HTML(1) manual page
-
-
-Table of Contents
-
-

-
Name
-SiSU - Structured information, Serialized Units - a document publishing
-
-system
-

-
Synopsis
-sisu-html sisu_document.sst | sisu_document.ssm
-
-
Description
-SiSU
-is a lightweight markup based document structuring, publishing and search
-framework for document collections.
-The sisu-html command is an alias for
-sisu --html (or sisu -h) which produces HTML output of a SiSU markup file.
-
-

-
See Also
-sisu(1)
-,

-sisu-concordance(1)
-,

-sisu-epub(1)
-,

-sisu-harvest(1)
-,

-sisu-pdf(1)
-,

-sisu-odf(1)
-,

-sisu-pg(1)
-,

-sisu-sqlite(1)
-,

-sisu-txt(1)
-.
-
-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-
-

-Table of Contents

-

-Name
-Synopsis
-Description
-See Also
-Homepage
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu-odf.1.html b/data/doc/sisu/html/sisu-odf.1.html
deleted file mode 100644
index fddd3148..00000000
--- a/data/doc/sisu/html/sisu-odf.1.html
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
-
-
-SISU-ODF(1) manual page
-
-
-Table of Contents
-
-

-
Name
-SiSU - Structured information, Serialized Units - a document publishing
-
-system
-

-
Synopsis
-sisu-odf sisu_document.sst | sisu_document.ssm
-
-
Description
-SiSU
-is a lightweight markup based document structuring, publishing and search
-framework for document collections.
-The sisu-odf command is an alias for
-sisu --odt (or sisu -o) which produces OpenDocument output of a SiSU markup
-file.
-

-
See Also
-sisu(1)
-,

-sisu-concordance(1)
-,

-sisu-epub(1)
-,

-sisu-harvest(1)
-,

-sisu-html(1)
-,

-sisu-pdf(1)
-,

-sisu-pg(1)
-,

-sisu-sqlite(1)
-,

-sisu-txt(1)
-.
-
-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-
-

-Table of Contents

-

-Name
-Synopsis
-Description
-See Also
-Homepage
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu-pdf.1.html b/data/doc/sisu/html/sisu-pdf.1.html
deleted file mode 100644
index ec9f39d2..00000000
--- a/data/doc/sisu/html/sisu-pdf.1.html
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
-
-
-SISU-PDF(1) manual page
-
-
-Table of Contents
-
-

-
Name
-SiSU - Structured information, Serialized Units - a document publishing
-
-system
-

-
Synopsis
-sisu-pdf sisu_document.sst | sisu_document.ssm
-
-
Description
-SiSU
-is a lightweight markup based document structuring, publishing and search
-framework for document collections.
-The sisu-pdf command is an alias for
-sisu --pdf (or sisu -p) which produces PDF output of a SiSU markup file.
-

-
See
-Also
-sisu(1)
-,

-sisu-concordance(1)
-,

-sisu-epub(1)
-,

-sisu-harvest(1)
-,

-sisu-html(1)
-,

-sisu-odf(1)
-,

-sisu-pg(1)
-,

-sisu-sqlite(1)
-,

-sisu-txt(1)
-.
-
-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-
-

-Table of Contents

-

-Name
-Synopsis
-Description
-See Also
-Homepage
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu-pg.1.html b/data/doc/sisu/html/sisu-pg.1.html
deleted file mode 100644
index 056598f2..00000000
--- a/data/doc/sisu/html/sisu-pg.1.html
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
-
-
-SISU-PG(1) manual page
-
-
-Table of Contents
-
-

-
Name
-SiSU - Structured information, Serialized Units - a document publishing
-
-system
-

-
Synopsis
-sisu-pq sisu_document.sst | sisu_document.ssm
-
-
Description
-SiSU
-is a lightweight markup based document structuring, publishing and search
-framework for document collections.
-The sisu-pq command is an alias for sisu
---pg (or sisu -D) which populates a PostgreSQL database with SiSU content
-(for search) from a SiSU markup file.
-

-
See Also
-sisu(1)
-,

-sisu-concordance(1)
-,

-sisu-epub(1)
-,

-sisu-harvest(1)
-,

-sisu-html(1)
-,

-sisu-pdf(1)
-,

-sisu-odf(1)
-,

-sisu-sqlite(1)
-,

-sisu-txt(1)
-.
-
-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-
-

-Table of Contents

-

-Name
-Synopsis
-Description
-See Also
-Homepage
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu-po.1.html b/data/doc/sisu/html/sisu-po.1.html
deleted file mode 100644
index ea1c5b43..00000000
--- a/data/doc/sisu/html/sisu-po.1.html
+++ /dev/null
@@ -1,73 +0,0 @@
-
-
-
-
-
-SISU-PO(1) manual page
-
-
-Table of Contents
-
-

-
Name
-SiSU - Structured information, Serialized Units - a document publishing
-
-system
-

-
Synopsis
-sisu-po sisu_document.sst | sisu_document.ssm
-
-
Description
-SiSU
-is a lightweight markup based document structuring, publishing and search
-framework for document collections.
-The sisu-po command is an alias for sisu
---po4a (or sisu -o) which provided two sisu markup files of the same document
-in different languages produces .pot and .po output of a SiSU markup file.
-Experimental, and under development.
-

-
See Also
-sisu(1)
-,

-sisu-concordance(1)
-,

-sisu-epub(1)
-,

-sisu-harvest(1)
-,

-sisu-html(1)
-,

-sisu-odf(1)
-,

-sisu-pdf(1)
-,

-sisu-pg(1)
-,

-sisu-sqlite(1)
-,

-sisu-txt(1)
-.
-
-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-

-
-

-Table of Contents

-

-Name
-Synopsis
-Description
-See Also
-Homepage
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu-sqlite.1.html b/data/doc/sisu/html/sisu-sqlite.1.html
deleted file mode 100644
index f40c3a8b..00000000
--- a/data/doc/sisu/html/sisu-sqlite.1.html
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
-
-
-SISU-SQLITE(1) manual page
-
-
-Table of Contents
-
-

-
Name
-SiSU - Structured information, Serialized Units - a document publishing
-
-system
-

-
Synopsis
-sisu-sqlite sisu_document.sst | sisu_document.ssm
-
-
Description
-SiSU
-is a lightweight markup based document structuring, publishing and search
-framework for document collections.
-The sisu-sqlite command is an alias for
-sisu --sqlite (or sisu -d) which populates a SQLite database with SiSU content
-(for search) from a SiSU markup file.
-

-
See Also
-sisu(1)
-,

-sisu-concordance(1)
-,

-sisu-epub(1)
-,

-sisu-harvest(1)
-,

-sisu-html(1)
-,

-sisu-pdf(1)
-,

-sisu-odf(1)
-,

-sisu-pg(1)
-,

-sisu-txt(1)
-.
-
-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-
-

-Table of Contents

-

-Name
-Synopsis
-Description
-See Also
-Homepage
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu-txt.1.html b/data/doc/sisu/html/sisu-txt.1.html
deleted file mode 100644
index dbfc71f4..00000000
--- a/data/doc/sisu/html/sisu-txt.1.html
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
-
-
-SISU-TXT(1) manual page
-
-
-Table of Contents
-
-

-
Name
-SiSU - Structured information, Serialized Units - a document publishing
-
-system
-

-
Synopsis
-sisu-txt sisu_document.sst | sisu_document.ssm
-
-
Description
-SiSU
-is a lightweight markup based document structuring, publishing and search
-framework for document collections.
-The sisu-txt command is an alias for
-sisu --txt (or sisu -t) which produces plain text output of a SiSU markup
-file.
-

-
See Also
-sisu(1)
-,

-sisu-concordance(1)
-,

-sisu-epub(1)
-,

-sisu-harvest(1)
-,

-sisu-html(1)
-,

-sisu-pdf(1)
-,

-sisu-odf(1)
-,

-sisu-pg(1)
-,

-sisu-sqlite(1)
-.
-
-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-
-

-Table of Contents

-

-Name
-Synopsis
-Description
-See Also
-Homepage
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu.1.html b/data/doc/sisu/html/sisu.1.html
deleted file mode 100644
index 65a92c9a..00000000
--- a/data/doc/sisu/html/sisu.1.html
+++ /dev/null
@@ -1,3290 +0,0 @@
-
-
-
-
-
-"sisu"("1") manual page
-
-
-Table of Contents
-

-
-
Name
-

-sisu - documents: markup, structuring, publishing in multiple standard formats,
-and search

-
-Synopsis
-

-sisu [-short-options|--long-options] [filename/wildcard]
-

-sisu [-abCcDdeFGghIikLMmNnoPpQqRrSsTtUuVvWwXxYyZ_0-9] [filename/wildcard]
-
-

-sisu --txt --html --epub --odt --pdf --wordmap --sqlite --manpage --texinfo --sisupod --source
---qrcode [filename/wildcard]
-

-sisu [-Ddcv] [instruction] [filename/wildcard]
-

-sisu --pg (--createdb|update [filename/wildcard]|--dropall)
-

-sisu [operations]
-

-sisu [-CcFLSVvW]
-

-sisu (--configure|--webrick|--sample-search-form)
-
Sisu - Manual,
-RALPH AMISSAH
-
-
What
-is Sisu?
-
-
-
Introduction - What is Sisu?
-
-
-
SiSU is a framework for document
-structuring, publishing (in multiple open standard formats) 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 (including the population of
-sql databases) 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 ( GPLv3 ). Its use case for development is work with medium
-to large document sets and cope with evolving document formats/ representation
-technologies. Documents are prepared once, and generated as need be to update
-the technical presentation or add additional output formats. Various output
-formats (including search related output) share a common mechanism for
-cross-output-format citation.
-
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, EPUB, ODT (Open Document Format
-text), LaTeX, landscape and portrait PDF, 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.
-
-
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 (to
-take advantage of the strengths of different ways of representing documents)
-various standard open output formats including plain text, HTML, XHTML,
-XML, EPUB, ODT, LaTeX or PDF files, and populate an SQL database with objects[^1]
-(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[^2] the
-different forms of output requested.
-
SiSU works with an abstraction of
-the document based on its structure which is comprised of its headings[^3]
-and objects[^4], 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 basis for citing material within a document across the different
-output format types. This is significant as page numbers are not well suited
-to the digital age, in web publishing, changing a browser’s default font
-or using a different browser can mean that text will appear on a different
-page; and publishing in different formats, html, landscape and portrait
-pdf etc. again page numbers are not useful to cite text. Dealing with documents
-at an object level together with object numbering also has implications
-for search that SiSU is able to take advantage of.
-
One of the challenges
-of maintaining documents is to keep them in a format that allows use of
-them independently of proprietary platforms. Consider issues related to
-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 producing documents in multiple non-proprietary open formats
-including HTML, EPUB, [^5] ODT, [^6] PDF [^7] ODF, [^8]. 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 GPLv3 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 when it became an ISO standard for office applications and the
-archival of documents), EPUB was introduced in 2009; and allows the technical
-representations 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 thesauri, 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.sisudoc.org/
->
-
<http://www.jus.uio.no/sisu
->
-
-
Commands Summary
-
-
-
Description
-
- SiSU is a document publishing system, that
-from a simple single marked-up document, produces multiple output formats
-including: plaintext, HTML, XHTML, XML, EPUB, ODT ( OpenDocument ( ODF
-) text), LaTeX, PDF, info, and SQL ( PostgreSQL and SQLite ) , which share
-text object numbers ("object citation numbering") and the same document
-structure information. For more see: <http://sisudoc.org
-> or <http://www.jus.uio.no/sisu
->
-
-
Document Processing Command Flags
-
-
-

-
--a [filename/wildcard]
-produces plaintext
-with Unix linefeeds and without markup, (object numbers are omitted), has
-footnotes at end of each paragraph that contains them [ -A for equivalent
-dos (linefeed) output file] [see -e for endnotes]. (Options include: --endnotes
-for endnotes --footnotes for footnotes at the end of each paragraph --unix
-for unix linefeed (default) --msdos for msdos linefeed)
-
--b [filename/wildcard]
-
-see --xhtml
-
---by-*
-see --output-by-*
-
--C
-configure/initialise shared output directory
-files initialize shared output directory (config files such as css and
-dtd files are not updated if they already exist unless modifier is used).
--C --init-site configure/initialise site more extensive than -C on its own,
-shared output directory files/force update, existing shared output config
-files such as css and dtd files are updated if this modifier is used.
-
--CC
-
-see --configure
-
--c [filename/wildcard]
-see --color-toggle
-
---color
-see --color-on
-
---color-off
-
-turn off color in output to terminal
-
---color-on
-turn on color in output to
-terminal
-
---color-toggle [filename/wildcard]
-screen toggle ansi screen colour
-on or off depending on default set (unless -c flag is used: if sisurc colour
-default is set to ’true’, output to screen will be with colour, if sisurc
-colour default is set to ’false’ or is undefined screen output will be without
-colour). Alias -c
-
---configure
-configure/initialise shared output directory
-files initialize shared output directory (config files such as css and
-dtd files are not updated if they already exist unless modifier is used).
-The equivalent of: -C --init-site configure/initialise site, more extensive
-than -C on its own, shared output directory files/force update, existing
-shared output config files such as css and dtd files are updated if -CC
-is used.
-
---concordance [filename/wildcard]
-produces concordance (wordmap)
-a rudimentary index of all the words in a document. (Concordance files are
-not generated for documents of over 260,000 words unless this limit is
-increased in the file sisurc.yml). Alias -w
-
--D [instruction] [filename]
-see
---pg
-
--d [--db-[database type (sqlite|pg)]] --[instruction] [filename]
-see --sqlite
-
-
---dal [filename/wildcard/url]
-assumed for most other flags, creates new intermediate
-files for processing (document abstraction) that is used in all subsequent
-processing of other output. This step is assumed for most processing flags.
-To skip it see -n. Alias -m
-
---delete [filename/wildcard]
-see --zap
-
---dump[=directory_path]
-[filename/wildcard]
-places output in directory specified, if none is specified
-in the current directory (pwd). Unlike using default settings HTML files
-have embedded css. Compare --redirect
-
--e [filename/wildcard]
-see --epub
-
---epub
-[filename/wildcard]
-produces an epub document, [sisu version >=2 ] (filename.epub).
-Alias -e
-
---exc-*
-exclude output feature, overrides configuration settings --exc-ocn,
-(exclude object citation numbering, (switches off object citation numbering
-) , affects html (seg, scroll), epub, xhtml, xml, pdf) ; --exc-toc, (exclude
-table of contents, affects html (scroll), epub, pdf) ; --exc-links-to-manifest,
---exc-manifest-links, (exclude links to manifest, affects html (seg, scroll));
---exc-search-form, (exclude search form, affects html (seg, scroll), manifest);
---exc-minitoc, (exclude mini table of contents, affects html (seg), concordance,
-manifest); --exc-manifest-minitoc, (exclude mini table of contents, affects
-manifest); --exc-html-minitoc, (exclude mini table of contents, affects html
-(seg), concordance); --exc-html-navigation, (exclude navigation, affects html
-(seg)); --exc-html-navigation-bar, (exclude navigation bar, affects html (seg));
---exc-html-search-form, (exclude search form, affects html (seg, scroll)); --exc-html-right-pane,
-(exclude right pane/column, affects html (seg, scroll)); --exc-html-top-band,
-(exclude top band, affects html (seg, scroll), concordance (minitoc forced
-on to provide seg navigation)); --exc-segsubtoc (exclude sub table of contents,
-affects html (seg), epub) ; see also --inc-*
-
--F [--webserv=webrick]
-see --sample-search-form
-
-
--f [optional string part of filename]
-see --find
-
---find [optional string part
-of filename]
-without match string, glob all .sst .ssm files in directory
-(including language subdirectories). With match string, find files that
-match given string in directory (including language subdirectories). Alias
--f, --glob, -G
-
--G [optional string part of filename]
-see --find
-
--g [filename/wildcard]
-
-see --git
-
---git [filename/wildcard]
-produces or updates markup source file
-structure in a git repo (experimental and subject to change). Alias -g
-
---glob
-[optional string part of filename]
-see --find
-
--h [filename/wildcard]
-see --html
-
-
---harvest *.ss[tm]
-makes two lists of sisu output based on the sisu markup
-documents in a directory: list of author and authors works (year and titles),
-and; list by topic with titles and author. Makes use of header metadata
-fields (author, title, date, topic_register). Can be used with maintenance
-(-M) and remote placement (-R) flags.
-
---help [topic]
-provides help on the selected
-topic, where topics (keywords) include: list, (com)mands, short(cuts),
-(mod)ifiers, (env)ironment, markup, syntax, headers, headings, endnotes,
-tables, example, customise, skin, (dir)ectories, path, (lang)uage, db,
-install, setup, (conf)igure, convert, termsheet, search, sql, features,
-license.
-
---html [filename/wildcard]
-produces html output, in two forms (i)
-segmented text with table of contents (toc.html and index.html) and (ii)
-the document in a single file (scroll.html). Alias -h
-
---html-scroll [filename/wildcard]
-
-produces html output, the document in a single file (scroll.html) only. Compare
---html-seg and --html
-
---html-seg [filename/wildcard]
-produces html output, segmented
-text with table of contents (toc.html and index.html). Compare --html-scroll
-and --html
-
--I [filename/wildcard]
-see --texinfo
-
--i [filename/wildcard]
-see --manpage
-
-
---i18n-*
-these flags affect output by filetype and filename): --i18n-mono (--monolingual)
-output filenames without language code for default language (’en’ or as set);
---i18n-multi (--multilingual) language code provided as part of the output filename,
-this is the default. Where output is in one language only the language code
-may not be desired. see also --output-by-*
-
---inc-*
-include output feature, overrides
-configuration settings, (usually the default if none set), has precedence
-over --exc-* (exclude output feature). Some detail provided under --exc-*, see
---exc-*
-
--j [filename/wildcard]
-copies images associated with a file for use
-by html, xhtml & xml outputs (automatically invoked by --dump & redirect).
-
--k
-
-see --color-off
-
---keep-processing-files [filename/wildcard/url]
-see --maintenance
-
-
--M [filename/wildcard/url]
-see --maintenance
-
--m [filename/wildcard/url]
-see
---dal (document abstraction level/layer)
-
---machine [filename/wildcard/url]
-
-see --dal (document abstraction level/layer)
-
---maintenance [filename/wildcard/url]
-
-maintenance mode, interim processing files are preserved and their locations
-indicated. (also see -V). Aliases -M and --keep-processing-files.
-
---manpage [filename/wildcard]
-
-produces man page of file, not suitable for all outputs. Alias -i
-
---monolingual
-
-see --i18n-*
-
---multilingual
-see --i18n-*
-
--N [filename/wildcard/url]
-document digest
-or document content certificate ( DCC ) as md5 digest tree of the document:
-the digest for the document, and digests for each object contained within
-the document (together with information on software versions that produced
-it) (digest.txt). -NV for verbose digest output to screen.
-
--n [filename/wildcard/url]
-
-skip the creation of intermediate processing files (document abstraction)
-if they already exist, this skips the equivalent of -m which is otherwise
-assumed by most processing flags.
-
---no-*
-see --exc-*
-
--o [filename/wildcard/url]
-
-see --odt
-
---odf [filename/wildcard/url]
-see --odt
-
---odt [filename/wildcard/url]
-
-output basic document in opendocument file format (opendocument.odt). Alias
--o
-
---output-by-*
-select output directory structure from 3 alternatives: --output-by-language,
-(language directory (based on language code) with filetype (html, epub,
-pdf etc.) subdirectories); --output-by-filetype, (filetype directories with
-language code as part of filename); --output-by-filename, (filename directories
-with language code as part of filename). This is configurable. Alias --by-*
-
-
--P [language_directory/filename language_directory]
-see --po4a
-
--p [filename/wildcard]
-
-see --pdf
-
---papersize-(a4|a5|b5|letter|legal)
-in conjunction with --pdf set pdf papersize,
-overriding any configuration settings, to set more than one papersize repeat
-the option --pdf --papersize-a4 --papersize-letter. See also --papersize=*
-
-
--papersize=a4,a5,b5,letter,legal
-in conjunction with --pdf set pdf papersize, overriding any configuration
-settings, to set more than one papersize list after the equal sign with
-a comma separator --papersize=a4,letter. See also --papersize-*
-
---pdf [filename/wildcard]
-
-produces LaTeX pdf (portrait.pdf & landscape.pdf). Orientation and papersize
-may be set on the command-line. Default paper size is set in config file,
-or document header, or provided with additional command line parameter,
-e.g. --papersize-a4 preset sizes include: ’A4’, U.S. ’letter’ and ’legal’ and book sizes
-’A5’ and ’B5’ (system defaults to A4), and; --landscape or --portrait, so: e.g. "sisu
---pdf-a4 --pdf-letter --landscape --verbose [filename/wildcard]" or "sisu --pdf --landscape
---a4 --letter --verbose [filename/wildcard]". --pdf defaults to both landscape &
-portrait output, and a4 if no other papersizes are configured. Related options
---pdf-landscape --pdf-portrait --pdf-papersize-* --pdf-papersize=[list]. Alias -p
-
---pdf-l
-[filename/wildcard]
-See --pdf-landscape
-
---pdf-landscape [filename/wildcard]
-sets
-orientation, produces LaTeX pdf landscape.pdf. Default paper size is set
-in config file, or document header, or provided with additional command
-line parameter, e.g. --papersize-a4 preset sizes include: ’A4’, U.S. ’letter’ and
-’legal’ and book sizes ’A5’ and --papersize-* or --papersize=[list]. Alias --pdf-l
-or in conjunction with --pdf --landscape
-
---pdf-p [filename/wildcard]
-See --pdf-portrait
-
-
---pdf-portrait [filename/wildcard]
-sets orientation, produces LaTeX pdf portrait.pdf.pdf.
-Default paper size is set in config file, or document header, or provided
-with additional command line parameter, e.g. --papersize-a4 preset sizes include:
-’A4’, U.S. ’letter’ and ’legal’ and book sizes ’A5’ and --papersize-* or --papersize=[list].
-Alias --pdf-p or in conjunction with --pdf --portrait
-
---pg [instruction] [filename]
-
-database PostgreSQL ( --pgsql may be used instead) possible instructions,
-include: --createdb; --create; --dropall; --import [filename]; --update [filename];
---remove [filename]; see database section below. Alias -D
-
---po [language_directory/filename
-language_directory]
-see --po4a
-
---po4a [language_directory/filename language_directory]
-
-produces .pot and po files for the file in the languages specified by the
-language directory. SiSU markup is placed in subdirectories named with the
-language code, e.g. en/ fr/ es/. The sisu config file must set the output
-directory structure to multilingual. v3, experimental
-
--Q [filename/wildcard]
-
-see --qrcode
-
--q [filename/wildcard]
-see --quiet
-
---qrcode [filename/wildcard]
-generate
-QR code image of metadata (used in manifest). v3 only.
-
---quiet [filename/wildcard]
-
-quiet less output to screen.
-
--R [filename/wildcard]
-see --rsync
-
--r [filename/wildcard]
-
-see --scp
-
---redirect[=directory_path] [filename/wildcard]
-places output in
-subdirectory under specified directory, subdirectory uses the filename
-(without the suffix). If no output directory is specified places the subdirectory
-under the current directory (pwd). Unlike using default settings HTML files
-have embedded css. Compare --dump
-
---rsync [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 --scp. Alias -R
-
--S
-see --sisupod
-
--S [filename/wildcard]
-
-see --sisupod
-
--s [filename/wildcard]
-see --source
-
---sample-search-form [--db=(pgsql|sqlite)]
-[--webserv=webrick]
-generate examples of (naive) cgi search form for SQLite
-or PgSQL depends on your already having used sisu to populate an SQLite
-or PgSQL database, (the SQLite version scans the output directories for
-existing sisu_sqlite databases, so it is first necessary to create them,
-before generating the search form) see --sqlite & --pg and the database section
-below. Optional additional parameters include: url location of webserver
-search form and db: --webserv-search=’[url]’; location of webserver output:
---webserv-output=’[url]’; cgi search form link name: --cgi-search-form-name=’[name.cgi]’;
-for pgsql, database user: --db-user=’[username]’. If the optional parameter --webserv=webrick
-is passed, the cgi examples created will be set up to use the default port
-set for use by the webrick server, (otherwise the port is left blank and
-the system setting used, usually 80). The samples are dumped in the present
-work directory which must be writable, (with screen instructions given
-that they be copied to the cgi-bin directory). Alias -F
-
---scp [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 --rsync. Alias -r
-
---sqlite --[instruction]
-[filename]
-database type set to SQLite, this produces one of two possible
-databases, without additional database related instructions it produces
-a discreet SQLite file for the document processed; with additional instructions
-it produces a common SQLite database of all processed documents that (come
-from the same document preparation directory and as a result) share the
-same output directory base path (possible instructions include: --createdb;
---create; --dropall; --import [filename]; --update [filename]; --remove [filename]);
-see database section below. Alias -d
-
---sisupod
-produces a sisupod a zipped
-sisu directory of markup files including sisu markup source files and the
-directories local configuration file, images and skins. Note: this only
-includes the configuration files or skins contained in is tested only
-with zsh). Alias -S
-
---sisupod [filename/wildcard]
-produces a zipped file of
-the prepared document specified along with associated images, by default
-named sisupod.zip they may alternatively be named with the filename extension
-.ssp This provides a quick way of gathering the relevant parts of a sisu
-document which can then for example be emailed. A sisupod includes sisu
-markup source file, (along with associated documents if a master file,
-or available in multilingual versions), together with related images and
-skin. SiSU commands can be run directly against a sisupod contained in a
-local directory, or provided as a url on a remote site. As there is a security
-issue with skins provided by other users, they are not applied unless the
-flag --trust or --trusted is added to the command instruction, it is recommended
-that file that are not your own are treated as untrusted. The directory
-structure of the unzipped file is understood by sisu, and sisu commands
-can be run within it. Note: if you wish to send multiple files, it quickly
-becomes more space efficient to zip the sisu markup directory, rather than
-the individual files for sending). See the -S option without [filename/wildcard].
-Alias -S
-
---source [filename/wildcard]
-copies sisu markup file to output directory.
-Alias -s
-
--T [filename/wildcard (*.termsheet.rb)]
-standard form document builder,
-preprocessing feature
-
--t [filename/wildcard]
-see --txt
-
---texinfo [filename/wildcard]
-
-produces texinfo and info file, (view with pinfo). Alias -I
-
---txt [filename/wildcard]
-
-produces plaintext with Unix linefeeds and without markup, (object numbers
-are omitted), has footnotes at end of each paragraph that contains them
-[ -A for equivalent dos (linefeed) output file] [see -e for endnotes]. (Options
-include: --endnotes for endnotes --footnotes for footnotes at the end of each
-paragraph --unix for unix linefeed (default) --msdos for msdos linefeed). Alias
--t
-
--U [filename/wildcard]
-see --urls
-
--u [filename/wildcard]
-provides url mapping
-of output files for the flags requested for processing, also see -U
-
---urls
-[filename/wildcard]
-prints url output list/map for the available processing
-flags options and resulting files that could be requested, (can be used
-to get a list of processing options in relation to a file, together with
-information on the output that would be produced), -u provides url output
-mapping for those flags requested for processing. The default assumes sisu_webrick
-is running and provides webrick url mappings where appropriate, but these
-can be switched to file system paths in sisurc.yml. Alias -U
-
--V
-on its own,
-provides SiSU version and environment information (sisu --help env)
-
--V [filename/wildcard]
-
-even more verbose than the -v flag.
-
--v
-on its own, provides SiSU version information
-
-
--v [filename/wildcard]
-see --verbose
-
---v3 [filename/wildcard]
-invokes the sisu
-v3 document parser/generator. You may run sisu3 instead.
-
---v4 [filename/wildcard]
-
-invokes the sisu v4 document parser/generator. This is the default and is
-normally omitted.
-
---verbose [filename/wildcard]
-provides verbose output of
-what is being generated, where output is placed (and error messages if
-any), as with -u flag provides a url mapping of files created for each of
-the processing flag requests. Alias -v
-
--W
-see --webrick
-
--w [filename/wildcard]
-
-see --concordance
-
---webrick
-starts ruby’ s webrick webserver points at sisu
-output directories, the default port is set to 8081 and can be changed
-in the resource configuration files. [tip: the webrick server requires link
-suffixes, so html output should be created using the -h option rather than
--H ; also, note -F webrick ]. Alias -W
-
---wordmap [filename/wildcard]
-see --concordance
-
-
---xhtml [filename/wildcard]
-produces xhtml/ XML output for browser viewing
-(sax parsing). Alias -b
-
---xml-dom [filename/wildcard]
-produces XML output with
-deep document structure, in the nature of dom. Alias -X
-
---xml-sax [filename/wildcard]
-
-produces XML output shallow structure (sax parsing). Alias -x
-
--X [filename/wildcard]
-
-see --xml-dom
-
--x [filename/wildcard]
-see --xml-sax
-
--Y [filename/wildcard]
-produces
-a short sitemap entry for the document, based on html output and the sisu_manifest.
---sitemaps generates/updates the sitemap index of existing sitemaps. (Experimental,
-[g,y,m announcement this week])
-
--y [filename/wildcard]
-produces an html
-summary of output generated (hyperlinked to content) and document specific
-metadata (sisu_manifest.html). This step is assumed for most processing flags.
-
-
--Z [filename/wildcard]
-see --zap
-
---zap [filename/wildcard]
-Zap, if used with
-other processing flags deletes output files of the type about to be processed,
-prior to processing. If -Z is used as the lone processing related flag (or
-in conjunction with a combination of -[mMvVq]), will remove the related
-document output directory. Alias -Z
-
-
-Command Line Modifiers
-
-
-

-
---no-ocn
-[with --html
---pdf or --epub] switches off object citation numbering. Produce output without
-identifying numbers in margins of html or LaTeX /pdf output.
-
---no-annotate
-
-strips output text of editor endnotes[^*1] denoted by asterisk or dagger/plus
-sign
-
---no-asterisk
-strips output text of editor endnotes[^*2] denoted by asterisk
-sign
-
---no-dagger
-strips output text of editor endnotes[^+1] denoted by dagger/plus
-sign
-
-
-Database Commands
-
- dbi - database interface
-
-D or --pgsql set for PostgreSQL
--d or --sqlite default set for SQLite -d is modifiable with --db=[database type
-(PgSQL or SQLite ) ]
-

-
---pg -v --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) [ -dv --createall SQLite equivalent] it may be necessary to run sisu
--Dv --createdb initially NOTE: at the present time for PostgreSQL it may be
-necessary to manually create the database. The command would be directory
-name (without path)]. Please use only alphanumerics and underscores.
-
---pg -v
---import
-[filename/wildcard] imports data specified to PostgreSQL db (rb.dbi)
-[ -dv --import SQLite equivalent]
-
---pg -v --update
-[filename/wildcard] updates/imports
-specified data to PostgreSQL db (rb.dbi) [ -dv --update SQLite equivalent]
-
-
---pg --remove
-[filename/wildcard] removes specified data to PostgreSQL db (rb.dbi)
-[ -d --remove SQLite equivalent]
-
---pg --dropall
-kills data" and drops ( PostgreSQL
-or SQLite ) db, tables & indexes [ -d --dropall SQLite equivalent]
- The -v
-is for verbose output.
-
-
-Shortcuts, Shorthand for Multiple Flags
-
-
-

-
---update [filename/wildcard]
-
-Checks existing file output and runs the flags required to update this
-output. This means that if only html and pdf output was requested on previous
-runs, only the -hp files will be applied, and only these will be generated
-this time, together with the summary. This can be very convenient, if you
-offer different outputs of different files, and just want to do the same
-again.
-
--0 to -5 [filename or wildcard]
-Default shorthand mappings (for v3,
-note that the defaults can be changed/configured in the sisurc.yml file):
-
-
--0
--NQhewpotbxXyYv [this is the default action run when no options are give,
-i.e. on ’sisu [filename]’]
-
--1
--Qhewpoty
-
--2
--NQhewpotbxXy
-
--3
--NQhewpotbxXyY
-
--4
--NQhewpotbxXDyY
---update
-
--5
--NQhewpotbxXDyYv --update
- add -v for verbose mode and -c to toggle
-color state, e.g. sisu -2vc [filename or wildcard]
-
consider -u for appended
-
-
url info or -v for verbose output
-

-
-
-Command Line with Flags - Batch Processing
-
-
- In the data directory run sisu -mh filename or wildcard eg. "sisu -h cisg.sst"
-or "sisu -h *.{sst,ssm}" to produce html version of all documents.
-
Running
-sisu (alone without any flags, filenames or wildcards) brings up the interactive
-help, as does any sisu command that is not recognised. Enter to escape.
-
Help
-
-
-
-
Sisu Manual
-
- The most up to date information on sisu should be contained
-in the sisu_manual, available at:
-
<http://sisudoc.org/sisu/sisu_manual/
->
-
-
The manual can be generated from source, found respectively, either within
-the SiSU tarball or installed locally at:
-
./data/doc/sisu/markup-samples/sisu_manual
-
-
/usr/share/doc/sisu/markup-samples/sisu_manual
-
move to the respective
-directory and type e.g.:
-
sisu sisu_manual.ssm
-
Sisu Man Pages
-
- If SiSU is
-installed on your system usual man commands should be available, try:
-

- man sisu
-
Most SiSU man pages are generated directly from sisu documents
-that are used to prepare the sisu manual, the sources files for which are
-located within the SiSU tarball at:
-
./data/doc/sisu/markup-samples/sisu_manual

-
-
Once installed, directory equivalent to:
-
/usr/share/doc/sisu/markup-samples/sisu_manual

-
-
Available man pages are converted back to html using man2html:
-
/usr/share/doc/sisu/html/

-
-
./data/doc/sisu/html

-
-
An online version of the sisu man page is available here:
-
* various
-sisu man pages <http://www.jus.uio.no/sisu/man/
-> [^9]
-
* sisu.1 <http://www.jus.uio.no/sisu/man/sisu.1.html
->
-[^10]
-

-
Sisu Built-in Interactive Help, [discontinued]
-
- This fell out of date
-and has been discontinued.
-
Introduction to Sisu Markup[^11]
-
-
-
Summary
-
- SiSU
-source documents are plaintext ( UTF-8 )[^12] files
-
All paragraphs are
-separated by an empty line.
-
Markup is comprised of:
-
* at the top of
-a document, the document header made up of semantic meta-data about the
-document and if desired additional processing instructions (such an instruction
-to automatically number headings from a particular level down)
-
* followed
-by the prepared substantive text of which the most important single characteristic
-is the markup of different heading levels, which define the primary outline
-of the document structure. Markup of substantive text includes:
-
* heading
-levels defines document structure

-
-
* text basic attributes, italics, bold etc.

-
-
* grouped text (objects), which are to be treated differently, such
-as code

- blocks or poems.

-
-
* footnotes/endnotes

-
-
* linked text and images
-
* paragraph actions, such as indent, bulleted,
-numbered-lists, etc.
-
Some interactive help on markup is available, by typing
-
-
sisu and selecting markup or sisu --help markup
-
To check the markup in
-a file:
-
sisu --identify [filename].sst
-
For brief descriptive summary of
-
-
markup history
-
sisu --query-history
-
or if for a particular version:
-

-sisu --query-0.38
-
Markup Examples
-
-
-
Online
-
- Online markup examples are available
-together with the respective outputs produced from <http://www.jus.uio.no/sisu/SiSU/examples.html
->
-or from <http://www.jus.uio.no/sisu/sisu_examples/
->
-
There is of course this
-document, which provides a cursory overview of sisu markup and the respective
-output produced: <http://www.jus.uio.no/sisu/sisu_markup/
->
-
an alternative
-presentation of markup syntax: /usr/share/doc/sisu/on_markup.txt.gz
-

-
Installed
-
-
- With SiSU installed sample skins may be found in: /usr/share/doc/sisu/markup-samples
-(or equivalent directory) and if sisu -markup-samples is installed also under:
-
-
/usr/share/doc/sisu/markup-samples-non-free
-

-
Markup of Headers
-
-
-
Headers contain
-either: semantic meta-data about a document, which can be used by any output
-module of the program, or; processing instructions.
-
Note: the first line
-of a document may include information on the markup version used in the
-form of a comment. Comments are a percentage mark at the start of a paragraph
-(and as the first character in a line of text) followed by a space and
-the comment:
-

-
% this would be a comment
-
-
-
Sample Header
-
- This current document is loaded by a master document that
-has a header similar to this one:
-

-
% SiSU master 4.0
-@title: SiSU
- :subtitle: Manual
-@creator:
- :author: Amissah, Ralph
-@publisher: [publisher name]
-@rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation,
-License GPL 3
-@classify:
- :topic_register: SiSU:manual;electronic documents:SiSU:manual
- :subject: ebook, epublishing, electronic book, electronic publishing,
- electronic document, electronic citation, data structure,
- citation systems, search
-% used_by: manual
-@date:
- :published: 2008-05-22
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2010-03-03
-@make:
- :num_top: 1
- :breaks: new=C; break=1
- :bold: /Gnu|Debian|Ruby|SiSU/
- :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
- :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
- :manpage: name=sisu - documents: markup, structuring, publishing in multiple
-standard formats, and search;
- synopsis=sisu [-abcDdeFhIiMmNnopqRrSsTtUuVvwXxYyZz0-9] [filename/wildcard
-]
- . sisu [-Ddcv] [instruction]
- . sisu [-CcFLSVvW]
- . sisu --v4 [operations]
- . sisu --v3 [operations]
-@links:
- { SiSU Homepage }http://www.sisudoc.org/
- { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/
- { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html
- { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html
- { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html
- { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary
- { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/
- { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html
- { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org
- { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
-
-
-
Available Headers
-
- Header tags appear at the beginning of a document and
-provide meta information on the document (such as the Dublin Core ) , or
-information as to how the document as a whole is to be processed. All header
-instructions take the form @headername: or on the next line and indented
-by once space :subheadername: All Dublin Core meta tags are available
-

- @indentifier: information or instructions
-
where the "identifier" is
-a tag recognised by the program, and the "information" or "instructions"
-
-
belong to the tag/identifier specified
-
Note: a header where used should
-only be used once; all headers apart from @title: are optional; the @structure:
-header is used to describe document structure, and can be useful to know.
-
-
This is a sample header
-

-
% SiSU 2.0 [declared file-type identifier with markup version]
-
-

-
@title: [title text] [this header is the only one that is mandatory]
- :subtitle: [subtitle if any]
- :language: English
-
-

-
@creator:
- :author: [Lastname, First names]
- :illustrator: [Lastname, First names]
- :translator: [Lastname, First names]
- :prepared_by: [Lastname, First names]
-
-

-
@date:
- :published: [year or yyyy-mm-dd]
- :created: [year or yyyy-mm-dd]
- :issued: [year or yyyy-mm-dd]
- :available: [year or yyyy-mm-dd]
- :modified: [year or yyyy-mm-dd]
- :valid: [year or yyyy-mm-dd]
- :added_to_site: [year or yyyy-mm-dd]
- :translated: [year or yyyy-mm-dd]
-
-

-
@rights:
- :copyright: Copyright (C) [Year and Holder]
- :license: [Use License granted]
- :text: [Year and Holder]
- :translation: [Name, Year]
- :illustrations: [Name, Year]
-
-

-
@classify:
- :topic_register: SiSU:markup sample:book;book:novel:fantasy
- :type:
- :subject:
- :description:
- :keywords:
- :abstract:
- :loc: [Library of Congress classification]
- :dewey: [Dewey classification
-
-

-
@identify:
- :isbn: [ISBN]
- :oclc:
-
-

-
@links: { SiSU }http://www.sisudoc.org
- { FSF }http://www.fsf.org
-
-

-
@make:
- :num_top: 1
- :headings: [text to match for each level
- (e.g. PART; Chapter; Section; Article; or another: none; BOOK|FIRST|SECOND;
-none; CHAPTER;)
- :breaks: new=:C; break=1
- :promo: sisu, ruby, sisu_search_libre, open_society
- :bold: [regular expression of words/phrases to be made bold]
- :italics: [regular expression of words/phrases to italicise]
- :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
- :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
-
-

-
@original:
- :language: [language]
-
-

-
@notes:
- :comment:
- :prefix: [prefix is placed just after table of contents]
-
-
-
Markup of Substantive Text
-
-
-
Heading Levels
-
- Heading levels are :A~ ,:B~
-,:C~ ,1~ ,2~ ,3~ ... :A - :C being part / section headings, followed by other
-heading levels, and 1 -6 being headings followed by substantive text or
-sub-headings. :A~ usually the title :A~? conditional level 1 heading (used
-where a stand-alone document may be imported into another)
-
:A~ [heading
-text] Top level heading [this usually has similar content to the title
-@title: ] NOTE: the heading levels described here are in 0.38 notation,
-
-
see heading
-
:B~ [heading text] Second level heading [this is a heading
-level divider]
-
:C~ [heading text] Third level heading [this is a heading
-level divider]
-
1~ [heading text] Top level heading preceding substantive
-text of document or sub-heading 2, the heading level that would normally
-be marked 1. or 2. or 3. etc. in a document, and the level on which sisu by
-default would break html output into named segments, names are provided
-automatically if none are given (a number), otherwise takes the form 1~my_filename_for_this_segment
-
-
2~ [heading text] Second level heading preceding substantive text of
-document or sub-heading 3 , the heading level that would normally be marked
-1.1 or 1.2 or 1.3 or 2.1 etc. in a document.
-
3~ [heading text] Third level
-heading preceding substantive text of document, that would normally be
-marked 1.1.1 or 1.1.2 or 1.2.1 or 2.1.1 etc. in a document
-

-
1~filename level 1 heading,
-% the primary division such as Chapter that is followed by substantive
-text, and may be further subdivided (this is the level on which by default
-html segments are made)
-
-
-
Font Attributes
-
- markup example:
-

-
normal text, *{emphasis}*, !{bold text}!, /{italics}/, _{underscore}_,
-"{citation}",
-^{superscript}^, ,{subscript},, +{inserted text}+, -{strikethrough}-, #{monospace}#
-normal text
-*{emphasis}* [note: can be configured to be represented by bold, italics
-or underscore]
-!{bold text}!
-/{italics}/
-_{underscore}_
-"{citation}"
-^{superscript}^
-,{subscript},
-+{inserted text}+
--{strikethrough}-
-#{monospace}#
-
- resulting output:
-
normal text, emphasis, bold text , italics, underscore,
-"citation", ^superscript^, [subscript], ++inserted text++, --strikethrough--,
-
-
monospace
-
normal text
-
emphasis [note: can be configured to be represented
-by bold, italics or underscore]
-
bold text
-
italics
-
underscore
-
"citation"
-
-
^superscript^
-
[subscript]
-
++inserted text++
-
--strikethrough--
-
monospace
-
-

-
Indentation and Bullets
-
- markup example:
-

-
ordinary paragraph
-_1 indent paragraph one step
-_2 indent paragraph two steps
-_9 indent paragraph nine steps
-
- resulting output:
-
ordinary paragraph
-
indent paragraph one step

-
-
indent paragraph two steps

-
-
indent paragraph nine steps

-
-
markup example:
-

-
_* bullet text
-_1* bullet text, first indent
-_2* bullet text, two step indent
-
- resulting output:
-
* bullet text
-
* bullet text, first indent

-
-
* bullet text, two step indent

-
-
Numbered List (not to be confused with headings/titles, (document structure))
-
-
markup example:
-

-
# numbered list numbered list 1., 2., 3, etc.
-_# numbered list numbered list indented a., b., c., d., etc.
-
-
-
Hanging Indents
-
- markup example:
-

-
_0_1 first line no indent,
-rest of paragraph indented one step
-_1_0 first line indented,
-rest of paragraph no indent
-in each case level may be 0-9
-
- resulting output:
-
first line no indent, rest of paragraph indented
-one step; first line no indent, rest of paragraph indented one step;
-first line no indent, rest of

- paragraph indented one step; first line no indent, rest of paragraph
-indented

- one step; first line no indent, rest of paragraph indented one step;
-first

- line no indent, rest of paragraph indented one step; first line no indent,

- rest of paragraph indented one step; first line no indent, rest of paragraph

- indented one step; first line no indent, rest of paragraph indented
-one step;

-
-
A regular paragraph.
-
first line indented, rest of paragraph no indent
-first line indented, rest of paragraph no indent first line indented, rest
-of paragraph no indent first line indented, rest of paragraph no indent
-first line indented, rest of paragraph no indent first line indented, rest
-of paragraph no indent first line indented, rest of paragraph no indent
-first line indented, rest of paragraph no indent first line indented, rest
-of paragraph no indent first line indented, rest of paragraph no indent
-first line indented, rest of paragraph no indent
-
in each case level may
-
-
be 0-9
-

-
live-build A collection of scripts used to build customized

- Debian
-
Livesystems.

- .I live-build

- was formerly known as live-helper, and even earlier known as live-package.

-
-

-
live-build
-
A collection of scripts used to build customized

- Debian Livesystems.

- live-build was formerly known as live-helper, and even earlier known as
-live-package.

-
-

-
Footnotes / Endnotes
-
- Footnotes and endnotes are marked up at the location
-where they would be indicated within a text. They are automatically numbered.
-
-
The output type determines whether footnotes or endnotes will be produced
-
-
markup example:
-

-
~{ a footnote or endnote }~
-
- resulting output:
-
[^13]
-
markup example:
-

-
normal text~{ self contained endnote marker & endnote in one }~ continues
-
- resulting output:
-
normal text[^14] continues
-
markup example:
-

-
normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks
-if required }~ continues
-normal text ~{** another unnumbered asterisk footnote/endnote }~ continues
-
- resulting output:
-
normal text [^*] continues
-
normal text [^**] continues
-
-
markup example:
-

-
normal text ~[* editors notes, numbered asterisk footnote/endnote series
-]~ continues
-normal text ~[+ editors notes, numbered asterisk footnote/endnote series
-]~ continues
-
- resulting output:
-
normal text [^*3] continues
-
normal text [^+2] continues
-
-
Alternative endnote pair notation for footnotes/endnotes:
-

-
% note the endnote marker "~^"
-normal text~^ continues
-^~ endnote text following the paragraph in which the marker occurs
-
- the standard and pair notation cannot be mixed in the same document
-

-
-
Links
-
-
-
Naked Urls Within Text, Dealing with Urls
-
- urls found within text
-are marked up automatically. A url within text is automatically hyperlinked
-to itself and by default decorated with angled braces, unless they are
-contained within a code block (in which case they are passed as normal
-text), or escaped by a preceding underscore (in which case the decoration
-is omitted).
-
markup example:
-

-
normal text http://www.sisudoc.org/ continues
-
- resulting output:
-
normal text <http://www.sisudoc.org/
-> continues
-
An
-
-
escaped url without decoration
-
markup example:
-

-
normal text _http://www.sisudoc.org/ continues
-deb _http://www.jus.uio.no/sisu/archive unstable main non-free
-
- resulting output:
-
normal text <_http://www.sisudoc.org/
-> continues
-
deb
-<_http://www.jus.uio.no/sisu/archive
-> unstable main non-free
-
where a code block
-is used there is neither decoration nor hyperlinking, code blocks are discussed
-
-
later in this document
-
resulting output:
-

-
deb http://www.jus.uio.no/sisu/archive unstable main non-free
-deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
-
-
-
Linking Text
-
- To link text or an image to a url the markup is as follows
-
-
markup example:
-

-
about { SiSU }http://url.org markup
-
- resulting output:
-
aboutSiSU <http://www.sisudoc.org/
-> markup
-
A shortcut
-
-
notation is available so the url link may also be provided automatically
-
-
as a footnote
-
markup example:
-

-
about {~^ SiSU }http://url.org markup
-
- resulting output:
-
aboutSiSU <http://www.sisudoc.org/
-> [^15] markup
-
Internal
-document links to a tagged location, including an ocn
-
markup example:
-
-

-
about { text links }#link_text
-
- resulting output:
-
about ⌠text links⌡⌈link_text⌋
-
Shared document
-
-
collection link
-
markup example:
-

-
about { SiSU book markup examples }:SiSU/examples.html
-
- resulting output:
-
about ⌠ SiSU book markup examples⌡⌈:SiSU/examples.html⌋
-
-

-
Linking Images
-
- markup example:
-

-
{ tux.png 64x80 }image
-% various url linked images
-{tux.png 64x80 "a better way" }http://www.sisudoc.org/
-{GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian
-and Ruby" }http://www.sisudoc.org/
-{~^ ruby_logo.png "Ruby" }http://www.ruby-lang.org/en/
-
- resulting output:
-
[ tux.png ]
-
tux.png 64x80 "Gnu/Linux - a better way"
-<http://www.sisudoc.org/
->
-
GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better
-- with Gnu/Linux, Debian and Ruby" <http://www.sisudoc.org/
->
-
ruby_logo.png
-70x90 "Ruby" <http://www.ruby-lang.org/en/
-> [^16]
-
linked url footnote shortcut
-
-

-
{~^ [text to link] }http://url.org
-% maps to: { [text to link] }http://url.org ~{ http://url.org }~
-% which produces hyper-linked text within a document/paragraph, with an
-endnote providing the url for the text location used in the hyperlink
-
-

-
text marker *~name
-
- note at a heading level the same is automatically achieved by providing
-names to headings 1, 2 and 3 i.e. 2~[name] and 3~[name] or in the case of
-auto-heading numbering, without further intervention.
-
Link Shortcut for Multiple
-Versions of a Sisu Document in the Same Directory
-TREE
- markup example:
-
-

-
!_ /{"Viral Spiral"}/, David Bollier
-{ "Viral Spiral", David Bollier [3sS]}viral_spiral.david_bollier.sst
-
- Viral Spiral, David Bollier
-
"Viral Spiral", David Bollier <http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html
->
- document manifest <http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html
->

- ⌠html, segmented text⌡「http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」
-

- ⌠html, scroll, document in one⌡「http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」
-

- ⌠epub⌡「http://corundum/sisu_manual/en/epub/viral_spiral.david_bollier.epub」
-

- ⌠pdf, landscape⌡「http://corundum/sisu_manual/en/pdf/viral_spiral.david_bollier.pdf」
-

- ⌠pdf, portrait⌡「http://corundum/sisu_manual/en/pdf/viral_spiral.david_bollier.pdf」
-

- ⌠odf: odt, open document text⌡「http://corundum/sisu_manual/en/odt/viral_spiral.david_bollier.odt」
-

- ⌠xhtml scroll⌡「http://corundum/sisu_manual/en/xhtml/viral_spiral.david_bollier.xhtml」
-

- ⌠xml, sax⌡「http://corundum/sisu_manual/en/xml/viral_spiral.david_bollier.xml」
-

- ⌠xml, dom⌡「http://corundum/sisu_manual/en/xml/viral_spiral.david_bollier.xml」
-

- ⌠concordance⌡「http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」
-

- ⌠dcc, document content certificate (digests)⌡「http://corundum/sisu_manual/en/digest/viral_spiral.david_bollier.txt」
-

- ⌠markup source text⌡「http://corundum/sisu_manual/en/src/viral_spiral.david_bollier.sst」
-

- ⌠markup source (zipped) pod⌡「http://corundum/sisu_manual/en/pod/viral_spiral.david_bollier.sst.zip」
-

-
-

-
Grouped Text
-
-
-
Tables
-
- Tables may be prepared in two either of two forms
-
-
markup example:
-

-
table{ c3; 40; 30; 30;
-This is a table
-this would become column two of row one
-column three of row one is here
-And here begins another row
-column two of row two
-column three of row two, and so on
-}table
-
- resulting output:
-
This is a table|this would become column two of row
-one|column three of row one is here』And here begins another row|column
-two of row two|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: [^17]

-
!_ Table 3.1: Contributors to Wikipedia, January 2001 - June 2005
-{table~h 24; 12; 12; 12; 12; 12; 12;}
- |Jan. 2001|Jan. 2002|Jan. 2003|Jan. 2004|July 2004|June
-2006
-Contributors* | 10| 472| 2,188| 9,653|
-25,011| 48,721
-Active contributors** | 9| 212| 846| 3,228|
- 8,442| 16,945
-Very active contributors*** | 0| 31| 190| 692|
- 1,639| 3,016
-No. of English language articles| 25| 16,000| 101,000| 190,000| 320,000|
- 630,000
-No. of articles, all languages | 25| 19,000| 138,000| 490,000| 862,000|1,600,000
-* Contributed at least ten times; ** at least 5 times in last month; ***
-more than 100 times in last month.
-
- resulting output:
-
Table 3.1: Contributors to Wikipedia, January 2001
-- June 2005 |Jan. 2001|Jan. 2002|Jan. 2003|Jan. 2004|July 2004|June 2006』Contributors*|10|472|2,188|9,653|25,011|48,721』Active
-contributors**|9|212|846|3,228|8,442|16,945』Very active contributors***|0|31|190|692|1,639|3,016』No.
-of English language articles|25|16,000|101,000|190,000|320,000|630,000』No. of
-articles, all languages|25|19,000|138,000|490,000|862,000|1,600,000』
-
* Contributed
-at least ten times; ** at least 5 times in last month; *** more than 100
-times in last month.
-

-
Poem
-
- basic markup:
-

-
poem{
- Your poem here
-}poem
-Each verse in a poem is given an object number.
-
- markup example:
-

-
poem{
- ‘Fury said to a
- mouse, That he
- met in the
- house,
- "Let us
- both go to
- law: I will
- prosecute
- YOU. --Come,
- I’ll take no
- denial; We
- must have a
- trial: For
- really this
- morning I’ve
- nothing
- to do."
- Said the
- mouse to the
- cur, "Such
- a trial,
- dear Sir,
- With
- no jury
- or judge,
- would be
- wasting
- our
- breath."
- "I’ll be
- judge, I’ll
- be jury,"
- Said
- cunning
- old Fury:
- "I’ll
- try the
- whole
- cause,
- and
- condemn
- you
- to
- death."’
-}poem
-
- resulting output:
-
‘Fury said to a

- mouse, That he

- met in the

- house,

- "Let us

- both go to

- law: I will

- prosecute

- YOU. --Come,

- I’ll take no

- denial; We

- must have a

- trial: For

- really this

- morning I’ve

- nothing

- to do."

- Said the

- mouse to the

- cur, "Such

- a trial,

- dear Sir,

- With

- no jury

- or judge,

- would be

- wasting

- our

- breath."

- "I’ll be

- judge, I’ll

- be jury,"

- Said

- cunning

- old Fury:

- "I’ll

- try the

- whole

- cause,

- and

- condemn

- you

- to

- death."’

-
-

-
Group
-
- basic markup:
-

-
group{
- Your grouped text here
-}group
-A group is treated as an object and given a single object number.
-
- markup example:
-

-
group{
- ‘Fury said to a
- mouse, That he
- met in the
- house,
- "Let us
- both go to
- law: I will
- prosecute
- YOU. --Come,
- I’ll take no
- denial; We
- must have a
- trial: For
- really this
- morning I’ve
- nothing
- to do."
- Said the
- mouse to the
- cur, "Such
- a trial,
- dear Sir,
- With
- no jury
- or judge,
- would be
- wasting
- our
- breath."
- "I’ll be
- judge, I’ll
- be jury,"
- Said
- cunning
- old Fury:
- "I’ll
- try the
- whole
- cause,
- and
- condemn
- you
- to
- death."’
-}group
-
- resulting output:
-
‘Fury said to a

- mouse, That he

- met in the

- house,

- "Let us

- both go to

- law: I will

- prosecute

- YOU. --Come,

- I’ll take no

- denial; We

- must have a

- trial: For

- really this

- morning I’ve

- nothing

- to do."

- Said the

- mouse to the

- cur, "Such

- a trial,

- dear Sir,

- With

- no jury

- or judge,

- would be

- wasting

- our

- breath."

- "I’ll be

- judge, I’ll

- be jury,"

- Said

- cunning

- old Fury:

- "I’ll

- try the

- whole

- cause,

- and

- condemn

- you

- to

- death."’

-
-

-
Code
-
- Code tags code{ ... }code (used as with other group tags described
-above) are used to escape regular sisu markup, and have been used extensively
-within this document to provide examples of SiSU markup. You cannot however
-use code tags to escape code tags. They are however used in the same way
-as group or poem tags.
-
A code-block is treated as an object and given a
-single object number. [an option to number each line of code may be considered
-at some later time]
-
use of code tags instead of poem compared, resulting
-output:
-

-
‘Fury said to a
- mouse, That he
- met in the
- house,
- "Let us
- both go to
- law: I will
- prosecute
- YOU. --Come,
- I’ll take no
- denial; We
- must have a
- trial: For
- really this
- morning I’ve
- nothing
- to do."
- Said the
- mouse to the
- cur, "Such
- a trial,
- dear Sir,
- With
- no jury
- or judge,
- would be
- wasting
- our
- breath."
- "I’ll be
- judge, I’ll
- be jury,"
- Said
- cunning
- old Fury:
- "I’ll
- try the
- whole
- cause,
- and
- condemn
- you
- to
- death."’
-
- From SiSU 2.7.7 on you can number codeblocks by placing a hash after the
-opening code tag code{# as demonstrated here:
-

-
1 | ‘Fury said to a
-2 | mouse, That he
-3 | met in the
-4 | house,
-5 | "Let us
-6 | both go to
-7 | law: I will
-8 | prosecute
-9 | YOU. --Come,
-10 | I’ll take no
-11 | denial; We
-12 | must have a
-13 | trial: For
-14 | really this
-15 | morning I’ve
-16 | nothing
-17 | to do."
-18 | Said the
-19 | mouse to the
-20 | cur, "Such
-21 | a trial,
-22 | dear Sir,
-23 | With
-24 | no jury
-25 | or judge,
-26 | would be
-27 | wasting
-28 | our
-29 | breath."
-30 | "I’ll be
-31 | judge, I’ll
-32 | be jury,"
-33 | Said
-34 | cunning
-35 | old Fury:
-36 | "I’ll
-37 | try the
-38 | whole
-39 | cause,
-40 | and
-41 | condemn
-42 | you
-43 | to
-44 | death."’
-
-
-
Additional Breaks - Linebreaks Within Objects, Column and Page-breaks
-
-
-
Line-breaks
-
-
- To break a line within a "paragraph object", two backslashes \\ with a space
-before and a space or newline after them may be used.
-

-
To break a line within a "paragraph object",
-two backslashes \\ with a space before
-and a space or newline after them \\
-may be used.
-
- The html break br enclosed in angle brackets (though undocumented) is
-available in versions prior to 3.0.13 and 2.9.7 (it remains available for the
-time being, but is depreciated).
-

-
Page Breaks
-
- Page breaks are only relevant
-and honored in some output formats. A page break or a new page may be inserted
-manually using the following markup on a line on its own:
-
page new =\=
-or breaks the page, starts a new page.
-
page break -\- or breaks a column,
-starts a new column, if using columns, else breaks the page, starts a new
-page.
-
page break line across page -..- draws a dividing line, dividing paragraphs
-
-
page break:

-
-\\-
-or
-<:pb>
-
-
-
page (break) new:

-
=\\=
-or
-<:pn>
-
-
-
page (break) line across page (dividing paragraphs):

-
-..-
-
-
-
Book Index
-
- To make an index append to paragraph the book index term relates
-to it, using an equal sign and curly braces.
-
Currently two levels are
-provided, a main term and if needed a sub-term. Sub-terms are separated from
-the main term by a colon.

-
Paragraph containing main term and sub-term.
- ={Main term:sub-term}
-
- The index syntax starts on a new line, but there should not be an empty
-line between paragraph and index markup.
-
The structure of the resulting
-index would be:
-

-
Main term, 1
- sub-term, 1
-
- Several terms may relate to a paragraph, they are separated by a semicolon.
-If the term refers to more than one paragraph, indicate the number of paragraphs.
-
-

-
Paragraph containing main term, second term and sub-term.
- ={first term; second term: sub-term}
-
- The structure of the resulting index would be:
-

-
First term, 1,
- Second term, 1,
- sub-term, 1
-
- If multiple sub-terms appear under one paragraph, they are separated under
-the main term heading from each other by a pipe symbol.
-

-
Paragraph containing main term, second term and sub-term.
- ={Main term:sub-term+1|second sub-term}
- A paragraph that continues discussion of the first sub-term
-
- The plus one in the example provided indicates the first sub-term spans
-one additional paragraph. The logical structure of the resulting index would
-be:
-

-
Main term, 1,
- sub-term, 1-3,
- second sub-term, 1,
-
-
-
Composite Documents Markup
-
- It is possible to build a document by creating
-a master document that requires other documents. The documents required
-may be complete documents that could be generated independently, or they
-could be markup snippets, prepared so as to be easily available to be placed
-within another text. If the calling document is a master document (built
-from other documents), it should be named with the suffix .ssm Within this
-document you would provide information on the other documents that should
-be included within the text. These may be other documents that would be
-processed in a regular way, or markup bits prepared only for inclusion
-within a master document .sst regular markup file, or .ssi (insert/information)
-
-
A secondary file of the composite document is built prior to processing
-
-
with the same prefix and the suffix ._sst
-
basic markup for importing a
-
-
document into a master document
-

-
<< filename1.sst
-<< filename2.ssi
-
- The form described above should be relied on. Within the Vim editor it
-results in the text thus linked becoming hyperlinked to the document it
-is calling in which is convenient for editing.
-

-
Sisu Filetypes
-
- SiSU has
-plaintext and binary filetypes, and can process either type of document.
-
-

-
.sst .ssm .ssi Marked Up Plain Text
-
-
-

-
-SiSU
-documents are prepared as plain-text
-(utf-8) files with SiSU markup. They may make reference to and contain images
-(for example), which are stored in the directory beneath them _sisu/image.
-〔b¤SiSU plaintext markup files are of three types that may be distinguished
-by the file extension used: regular text .sst; master documents, composite
-documents that incorporate other text, which can be any regular text or
-text insert; and inserts the contents of which are like regular text except
-these are marked .ssi and are not processed.
- SiSU processing can be done
-directly against a sisu documents; which may be located locally or on a
-remote server for which a url is provided.
-
SiSU source markup can be shared
-with the command:
-
sisu -s [filename]
-

-
-
-Sisu Text - Regular Files (.sst)
-
-
-The most common form of document in SiSU, see the section on SiSU markup.
-
-

-
Sisu Master Files (.ssm)
-
- Composite documents which incorporate other SiSU
-documents which may be either regular SiSU text .sst which may be generated
-independently, or inserts prepared solely for the purpose of being incorporated
-into one or more master documents.
-
The mechanism by which master files
-incorporate other documents is described as one of the headings under under
-SiSU markup in the SiSU manual.
-
Note: Master documents may be prepared
-in a similar way to regular documents, and processing will occur normally
-if a .sst file is renamed .ssm without requiring any other documents; the
-.ssm marker flags that the document may contain other documents.
-
Note:
-a secondary file of the composite document is built prior to processing
-with the same prefix and the suffix ._sst [^19]
-
Sisu Insert Files (.ssi)
-
-
-Inserts are documents prepared solely for the purpose of being incorporated
-into one or more master documents. They resemble regular SiSU text files
-except they are ignored by the SiSU processor. Making a file a .ssi file
-is a quick and convenient way of flagging that it is not intended that
-the file should be processed on its own.
-

-
Sisupod, Zipped Binary Container
-(sisupod.zip, .ssp)
-
- A sisupod is a zipped SiSU text file or set of SiSU
-text files and any associated images that they contain (this will be extended
-to include sound and multimedia-files)
-

-

-
-SiSU
-plaintext files rely on a recognised
-directory structure to find contents such as images associated with documents,
-but all images for example for all documents contained in a directory are
-located in the sub-directory _sisu/image. Without the ability to create a
-sisupod it can be inconvenient to manually identify all other files associated
-with a document. A sisupod automatically bundles all associated files with
-the document that is turned into a pod.
- The structure of the sisupod is
-such that it may for example contain a single document and its associated
-images; a master document and its associated documents and anything else;
-or the zipped contents of a whole directory of prepared SiSU documents.
-
-
The command to create a sisupod is:
-
sisu -S [filename]
-
Alternatively,
-make a pod of the contents of a whole directory:
-
sisu -S
-
SiSU processing
-can be done directly against a sisupod; which may be located locally or
-on a remote server for which a url is provided.
-
<http://www.sisudoc.org/sisu/sisu_commands
->
-
-
<http://www.sisudoc.org/sisu/sisu_manual
->
-

-
-
-Configuration
-
-
-
Configuration Files
-
-
-
-
Config.yml
-
- SiSU configration parameters are adjusted in the configuration
-file, which can be used to override the defaults set. This includes such
-things as which directory interim processing should be done in and where
-the generated output should be placed.
-
The SiSU configuration file is
-a yaml file, which means indentation is significant.
-
SiSU resource configuration
-is determined by looking at the following files if they exist:
-
./_sisu/v4/sisurc.yml

-
-
./_sisu/sisurc.yml

-
-
~/.sisu/v4/sisurc.yml

-
-
~/.sisu/sisurc.yml

-
-
/etc/sisu/v4/sisurc.yml

-
-
/etc/sisu/sisurc.yml

-
-
The search is in the order listed, and the first one found is used.
-

- In the absence of instructions in any of these it falls back to the internal
-program defaults.
-
Configuration determines the output and processing directories
-and the database access details.
-
If SiSU is installed a sample sisurc.yml
-
-
may be found in /etc/sisu/sisurc.yml
-

-
Sisu_document_make
-
- Most sisu document
-headers relate to metadata, the exception is the @make: header which provides
-processing related information. The default contents of the @make header
-may be set by placing them in a file sisu_document_make.
-
The search order
-is as for resource configuration:
-
./_sisu/v4/sisu_document_make

-
-
./_sisu/sisu_document_make

-
-
~/.sisu/v4/sisu_document_make

-
-
~/.sisu/sisu_document_make

-
-
/etc/sisu/v4/sisu_document_make

-
-
/etc/sisu/sisu_document_make

-
-
A sample sisu_document_make can be found in the _sisu/ directory under
-along with the provided sisu markup samples.
-

-
Css - Cascading Style Sheets
-(for Html, Xhtml and Xml)
-
- CSS files to modify the appearance of SiSU html,
-XHTML or XML may be placed in the configuration directory: ./_sisu/css ;
-~/.sisu/css or; /etc/sisu/css and these will be copied to the output directories
-with the command sisu -CC.
-
The basic CSS file for html output is html. css,
-placing a file of that name in directory _sisu/css or equivalent will result
-in the default file of that name being overwritten.
-
HTML: html. css
-
XML
-DOM: dom.css
-
XML SAX: sax.css
-
XHTML: xhtml. css
-
The default homepage
-may use homepage.css or html. css
-
Under consideration is to permit the
-placement of a CSS file with a different name in directory _sisu/css directory
-or equivalent.[^20]
-

-
Organising Content - Directory Structure and Mapping
-
-
- SiSU v3 has new options for the source directory tree, and output directory
-structures of which there are 3 alternatives.
-

-
Document Source Directory
-
-
- The document source directory is the directory in which sisu processing
-commands are given. It contains the sisu source files (.sst .ssm .ssi), or
-(for sisu v3 may contain) subdirectories with language codes which contain
-the sisu source files, so all English files would go in subdirectory en/,
-French in fr/, Spanish in es/ and so on. ISO 639-1 codes are used (as varied
-by po4a). A list of available languages (and possible sub-directory names)
-can be obtained with the command "sisu --help lang" The list of languages
-is limited to langagues supported by XeTeX polyglosia.
-

-
General Directories
-
-
-

-
% files stored at this level e.g. sisu_manual.sst or
-% for sisu v3 may be under language sub-directories
-% e.g.
- ./subject_name/en
- ./subject_name/fr
- ./subject_name/es
- ./subject_name/_sisu
- ./subject_name/_sisu/css
- ./subject_name/_sisu/image
-
-
-
Document Output Directory Structures
-
-
-
Output Directory Root
-
- The output
-directory root can be set in the sisurc.yml file. Under the root, subdirectories
-are made for each directory in which a document set resides. If you have
-a directory named poems or conventions, that directory will be created
-under the output directory root and the output for all documents contained
-in the directory of a particular name will be generated to subdirectories
-beneath that directory (poem or conventions). A document will be placed
-in a subdirectory of the same name as the document with the filetype identifier
-stripped (.sst .ssm)
-
The last part of a directory path, representing the
-sub-directory in which a document set resides, is the directory name that
-will be used for the output directory. This has implications for the organisation
-of document collections as it could make sense to place documents of a
-particular subject, or type within a directory identifying them. This grouping
-as suggested could be by subject (sales_law, english_literature); or just
-as conveniently by some other classification (X University). The mapping
-means it is also possible to place in the same output directory documents
-that are for organisational purposes kept separately, for example documents
-on a given subject of two different institutions may be kept in two different
-directories of the same name, under a directory named after each institution,
-and these would be output to the same output directory. Skins could be associated
-with each institution on a directory basis and resulting documents will
-take on the appropriate different appearance.
-

-
Alternative Output Structures
-
-
- There are 3 possibile output structures described as being, by language,
-by filetype or by filename, the selection is made in sisurc.yml
-

-
#% output_dir_structure_by: language; filetype; or filename
-output_dir_structure_by: language #(language & filetype, preferred?)
-#output_dir_structure_by: filetype
-#output_dir_structure_by: filename #(default, closest to original v1 &
-v2)
-
-
-
by Language
-
- The by language directory structure places output files
-

- The by language directory structure separates output files by language
-code (all files of a given language), and within the language directory
-by filetype.
-
Its selection is configured in sisurc.yml
-
output_dir_structure_by:
-
-
language
-

-
|-- en
- |-- epub
- |-- hashes
- |-- html
- | |-- viral_spiral.david_bollier
- | |-- manifest
- | |-- qrcode
- | |-- odt
- | |-- pdf
- | |-- sitemaps
- | |-- txt
- | |-- xhtml
- | ‘-- xml
- |-- po4a
- | ‘-- live-manual
- | |-- po
- | |-- fr
- | ‘-- pot
- ‘-- _sisu
- |-- css
- |-- image
- |-- image_sys -> ../../_sisu/image_sys
- ‘-- xml
- |-- rnc
- |-- rng
- ‘-- xsd
-
- #by: language subject_dir/en/manifest/filename.html
-

-
by Filetype
-
- The
-by filetype directory structure separates output files by filetype, all
-html files in one directory pdfs in another and so on. Filenames are given
-a language extension.
-
Its selection is configured in sisurc.yml
-
output_dir_structure_by:
-
-
filetype
-

-
|-- epub
- |-- hashes
- |-- html
- |-- viral_spiral.david_bollier
- |-- manifest
- |-- qrcode
- |-- odt
- |-- pdf
- |-- po4a
- |-- live-manual
- | |-- po
- | |-- fr
- | ‘-- pot
- |-- _sisu
- | |-- css
- | |-- image
- | |-- image_sys -> ../../_sisu/image_sys
- | ‘-- xml
- | |-- rnc
- | |-- rng
- | ‘-- xsd
- |-- sitemaps
- |-- txt
- |-- xhtml
- ‘-- xml
-
- #by: filetype subject_dir/html/filename/manifest.en.html
-

-
by Filename
-
-
-The by filename directory structure places most output of a particular
-file (the different filetypes) in a common directory.
-
Its selection is
-
-
configured in sisurc.yml
-
output_dir_structure_by: filename
-

-
|-- epub
- |-- po4a
- |-- live-manual
- | |-- po
- | |-- fr
- | ‘-- pot
- |-- _sisu
- | |-- css
- | |-- image
- | |-- image_sys -> ../../_sisu/image_sys
- | ‘-- xml
- | |-- rnc
- | |-- rng
- | ‘-- xsd
- |-- sitemaps
- |-- src
- |-- pod
- ‘-- viral_spiral.david_bollier
-
- #by: filename subject_dir/filename/manifest.en.html
-

-
Remote Directories
-
-
-

-
./subject_name/
-% containing sub_directories named after the generated files from which
-they are made
- ./subject_name/src
-% contains shared source files text and binary e.g. sisu_manual.sst and sisu_manual.sst.zip
- ./subject_name/_sisu
-% configuration file e.g. sisurc.yml
- ./subject_name/_sisu/skin
-% skins in various skin directories doc, dir, site, yml
- ./subject_name/_sisu/css
- ./subject_name/_sisu/image
-% images for documents contained in this directory
- ./subject_name/_sisu/mm
-
-
-
Sisupod
-
-

-
./sisupod/
-% files stored at this level e.g. sisu_manual.sst
- ./sisupod/_sisu
-% configuration file e.g. sisurc.yml
- ./sisupod/_sisu/skin
-% skins in various skin directories doc, dir, site, yml
- ./sisupod/_sisu/css
- ./sisupod/_sisu/image
-% images for documents contained in this directory
- ./sisupod/_sisu/mm
-
-
-
Organising Content
-
-
-
Homepages
-
- SiSU is about the ability to auto-generate
-documents. Home pages are regarded as custom built items, and are not created
-by SiSU. More accurately, SiSU has a default home page, which will not be
-appropriate for use with other sites, and the means to provide your own
-home page instead in one of two ways as part of a site’s configuration,
-these being:
-
1. through placing your home page and other custom built
-documents in the subdirectory _sisu/home/ (this probably being the easier
-and more convenient option)
-
2. through providing what you want as the
-home page in a skin,
-
Document sets are contained in directories, usually
-organised by site or subject. Each directory can/should have its own homepage.
-See the section on directory structure and organisation of content.
-

-
Home
-Page and Other Custom Built Pages in a Sub-directory
-
- Custom built pages,
-including the home page index.html may be placed within the configuration
-directory _sisu/home/ in any of the locations that is searched for the
-configuration directory, namely ./_sisu ; ~/_sisu ; /etc/sisu From there
-they are copied to the root of the output directory with the command:
-

- sisu -CC
-
Markup and Output Examples
-
-
-
Markup Examples
-
- Current markup examples
-and document output samples are provided off <http://sisudoc.org
-> or <http://www.jus.uio.no/sisu
->
-and in the sisu -markup-sample package available off <http://sources.sisudoc.org
->
-
-
For some documents hardly any markup at all is required at all, other
-than a header, and an indication that the levels to be taken into account
-by the program in generating its output are.
-

-
Sisu Markup Samples
-
- A few
-additional sample books prepared as sisu markup samples, output formats
-to be generated using SiSU are contained in a separate package sisu -markup-samples.
-sisu -markup-samples contains books (prepared using sisu markup), that were
-released by their authors various licenses mostly different Creative Commons
-licences that do not permit inclusion in the Debian Project as they have
-requirements that do not meet the Debian Free Software Guidelines for various
-reasons, most commonly that they require that the original substantive
-text remain unchanged, and sometimes that the works be used only non-commercially.
-
-
Accelerando, Charles Stross (2005) accelerando.charles_stross.sst
-
Alice’s
-Adventures in Wonderland, Lewis Carroll (1865) alices_adventures_in_wonderland.lewis_carroll.sst
-
-
CONTENT, Cory Doctorow (2008) content.cory_doctorow.sst
-
Democratizing
-Innovation, Eric von Hippel (2005) democratizing_innovation.eric_von_hippel.sst
-
-
Down and Out in the Magic Kingdom, Cory Doctorow (2003) down_and_out_in_the_magic_kingdom.cory_doctorow.sst
-
-
For the Win, Cory Doctorow (2010) for_the_win.cory_doctorow.sst
-
Free
-as in Freedom - Richard Stallman’s Crusade for Free Software, Sam Williams
-(2002) free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst
-
-
Free as in Freedom 2.0 - Richard Stallman and the Free Software Revolution,
-Sam Williams (2002), Richard M. Stallman (2010) free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst
-
-
Free Culture - How Big Media Uses Technology and the Law to Lock Down
-Culture and Control Creativity, Lawrence Lessig (2004) free_culture.lawrence_lessig.sst
-
-
Free For All - How Linux and the Free Software Movement Undercut the High
-Tech Titans, Peter Wayner (2002) free_for_all.peter_wayner.sst
-
GNU GENERAL
-PUBLIC LICENSE v2, Free Software Foundation (1991) gpl2.fsf.sst
-
GNU GENERAL
-PUBLIC LICENSE v3, Free Software Foundation (2007) gpl3.fsf.sst
-
Gulliver’s
-Travels, Jonathan Swift (1726 / 1735) gullivers_travels.jonathan_swift.sst
-
-
Little Brother, Cory Doctorow (2008) little_brother.cory_doctorow.sst
-

- The Cathederal and the Bazaar, Eric Raymond (2000) the_cathedral_and_the_bazaar.eric_s_raymond.sst
-
-
The Public Domain - Enclosing the Commons of the Mind, James Boyle (2008)
-
-
the_public_domain.james_boyle.sst
-
The Wealth of Networks - How Social Production
-Transforms Markets and Freedom, Yochai Benkler (2006) the_wealth_of_networks.yochai_benkler.sst
-
-
Through the Looking Glass, Lewis Carroll (1871) through_the_looking_glass.lewis_carroll.sst
-
-
Two Bits - The Cultural Significance of Free Software, Christopher Kelty
-(2008) two_bits.christopher_kelty.sst
-
UN Contracts for International Sale
-of Goods, UN (1980) un_contracts_international_sale_of_goods_convention_1980.sst
-
-
Viral Spiral, David Bollier (2008) viral_spiral.david_bollier.sst
-

-
Sisu
-Search - Introduction
-
- 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.
-
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.
-

-
Sql
-
-
-
Populating Sql Type Databases
-
- SiSU feeds
-sisu markupd documents into sql type databases PostgreSQL [^21] and/or SQLite
-[^22] 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:
-
* one containing semantic (and other) headers,
-including, title, author, subject, (the

- .I Dublin Core.

- ..);

-
-
* another the substantive texts by individual "paragraph" (or object)
-- along with structural information, each paragraph being identifiable
-by its

- paragraph number (if it has one which almost all of them do), and the

- substantive text of each paragraph quite naturally being searchable
-(both in

- formatted and clean text versions for searching); and

-
-
* a third containing endnotes cross-referenced back to the paragraph
-from which they are referenced (both in formatted and clean text versions
-for

- searching).

-
-
* a fourth table with a one to one relation with the headers table contains
- full text versions of output, eg. pdf, html, xml, and

- .I ascii.

-
-
There is of course the possibility to add further structures.
-
At this
-level SiSU loads a relational database with documents chunked into objects,
-their smallest logical structurally constituent parts, as text objects,
-with their object citation number and all other structural information
-needed to construct the document. Text is stored (at this text object level)
-with and without elementary markup tagging, the stripped version being
-so as to facilitate ease of searching.
-
Being able to search a relational
-database at an object level with the SiSU citation system is an effective
-way of locating content generated by SiSU. As individual text objects of
-a document stored (and indexed) together with object numbers, and all versions
-of the document have the same numbering, complex searches can be tailored
-to return just the locations of the search results relevant for all available
-output formats, with live links to the precise locations in the database
-or in html/xml documents; or, the structural information provided makes
-it possible to search the full contents of the database and have headings
-in which search content appears, or to search only headings etc. (as the
-Dublin Core is incorporated it is easy to make use of that as well).
-

-
Postgresql
-
-
-
-
Name
-
- SiSU - Structured information, Serialized Units - a document publishing
-system, postgresql dependency package
-

-
Description
-
- Information related
-to using postgresql with sisu (and related to the sisu_postgresql dependency
-package, which is a dummy package to install dependencies needed for SiSU
-to populate a postgresql database, this being part of SiSU - man sisu) .
-
-

-
Synopsis
-
- sisu -D [instruction] [filename/wildcard if required]
-
sisu
--D --pg --[instruction] [filename/wildcard if required]
-

-
Commands
-
- Mappings
-to two databases are provided by default, postgresql and sqlite, the same
-commands are used within sisu to construct and populate databases however
--d (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, alternatively
-
-
-
-
-
-
sqlite or --pgsql may be used
-
-D or --pgsql may be used interchangeably.
-

-
Create
-and Destroy Database
-
-
-

-
---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
-creates database where no database existed before
-
-
-
-sisu -D --create
-creates database tables where no database tables existed
-before
-
-
-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
-destroys existing database
-
-and builds a new empty database structure
-

-
-
-Import and Remove Documents
-
-
-
-

-
-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]
-updates file contents
-
-in database
-

-
-sisu -D --remove -v [filename/wildcard]
-removes specified document
-from postgresql database.
-
-
-
-Sqlite
-
-
-
Name
-
- SiSU - Structured information, Serialized
-Units - a document publishing system.
-

-
Description
-
- Information related to
-using sqlite with sisu (and related to the sisu_sqlite dependency package,
-which is a dummy package to install dependencies needed for SiSU to populate
-an sqlite database, this being part of SiSU - man sisu) .
-

-
Synopsis
-
- sisu
--d [instruction] [filename/wildcard if required]
-
sisu -d --(sqlite|pg) --[instruction]
-[filename/wildcard if required]
-

-
Commands
-
- Mappings to two databases are
-provided by default, postgresql and sqlite, the same commands are used
-within sisu to construct and populate databases however -d (lowercase) denotes
-sqlite and -D (uppercase) denotes postgresql, alternatively --sqlite or --pgsql
-
-
may be used
-
-d or --sqlite may be used interchangeably.
-

-
Create and Destroy
-Database
-
-
-

-
---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
-creates database where no database existed before
-
-
-sisu -d --create
-
-
-creates database tables where no database tables existed before
-

-
-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
-destroys existing database and builds
-a new empty database structure
-
-
-
-Import and Remove Documents
-
-
-

-
-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]
-updates file contents in database
-
-
-
-sisu -d --remove -v [filename/wildcard]
-removes specified document from sqlite
-database.
-
-
-
-Introduction
-
-
-
Search - Database Frontend Sample, Utilising Database
-and Sisu Features,
-INCLUDING OBJECT CITATION NUMBERING (BACKEND CURRENTLY
-POSTGRESQL)
- 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, object citation numbering to demonstrates functionality.[^24]
-
-
SiSU can provide information on which documents are matched and at what
-locations within each document the matches are found. These results are
-relevant across all outputs using object citation numbering, which includes
-html, XML, EPUB, LaTeX, PDF and indeed the SQL database. You can then refer
-to one of the other outputs or in the SQL database expand the text within
-the matched objects (paragraphs) in the 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]
-

-

-
-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:
-
sisu --help sql

-
Postgresql
- user: ralph
- current db set: SiSU_sisu
- port: 5432
- dbi connect: DBI:Pg:database=SiSU_sisu;port=5432
-sqlite
- current db set: /home/ralph/sisu_www/sisu/sisu_sqlite.db
- dbi connect DBI:SQLite:/home/ralph/sisu_www/sisu/sisu_sqlite.db
-
- Note on databases built
-
By default, [unless otherwise specified] databases
-are built on a directory basis, from collections of documents within that
-directory. The name of the directory you choose to work from is used as
-the database name, i.e. if you are working in a directory called /home/ralph/ebook
-the database SiSU_ebook is used. [otherwise a manual mapping for the collection
-is necessary]
-
-
-Search Form
-
-
-

-
-sisu -F
-generates a sample search form, which
-
-must be copied to the web-server cgi directory
-

-
-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
-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
-
-

-
-
-Sisu_webrick
-
-
-
Name
-
- SiSU - Structured information, Serialized Units - a document
-
-
publishing system
-

-
Synopsis
-
- sisu_webrick [port]
-
or
-
sisu -W [port]
-

-
-
Description
-
- sisu_webrick is part of SiSU (man sisu) sisu_webrick starts
-Ruby SiSU output is written, providing a list of these directories (assuming
-SiSU is in use and they exist).
-
The default port for sisu_webrick is set
-to 8081, this may be modified in the yaml file: ~/.sisu/sisurc.yml a sample
-of which is provided as /etc/sisu/sisurc.yml (or in the equivalent directory
-on your system).
-

-
Summary of Man Page
-
- sisu_webrick, may be started on it’s
-own with the command: sisu_webrick [port] or using the sisu command with
-the -W flag: sisu -W [port]
-
where no port is given and settings are unchanged
-
-
the default port is 8081
-

-
Document Processing Command Flags
-
- sisu -W [port]
-starts Ruby Webrick web-server, serving SiSU output directories, on the
-port provided, or if no port is provided and the defaults have not been
-
-
changed in ~/.sisu/sisurc.yaml then on port 8081
-

-
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, epub, 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:
-
* HTML - both as a single scrollable
-
-
text and a segmented document
-
* XHTML
-
* EPUB
-
* XML - both in sax and
-
-
dom style xml structures for further development as required
-
* ODT - Open
-Document Format text, the iso standard for document storage
-
* LaTeX -
-
-
used to generate pdf
-
* PDF (via LaTeX )
-
* SQL - population of an sql
-database ( PostgreSQL or SQLite ) , (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, EPUB, 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, epub in 2009 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, EPUB, 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.
-

-

-.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.
-
.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.
-
.the different
-
-heading levels
-

.units of text, primarily paragraphs and headings, also
-any tables, poems, code-blocks
-
.An open standard format for e-books
-
.Open
-Document Format ( ODF ) text
-
.Specification submitted by Adobe to ISO
-to become a full open ISO specification <http://www.linux-watch.com/news/NS7542722606.html
->
-
-
.ISO standard ISO/IEC 26300:2006
-
-
-
*1.
-square brackets
-
-
-*2.
-square brackets
-
-
-
-+1.
-square brackets
-
.<http://www.jus.uio.no/sisu/man/
->
-
.<http://www.jus.uio.no/sisu/man/sisu.1.html
->
-
-
.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.
-
.files
-
-should be prepared using UTF-8 character encoding
-

.a footnote or endnote
-
-
.self contained endnote marker & endnote in one
-
-
-
*.
-unnumbered asterisk
-footnote/endnote, insert multiple asterisks if required
-
-
-**.
-another unnumbered
-
-asterisk footnote/endnote
-

-
-*3.
-editors notes, numbered asterisk footnote/endnote
-
-series
-

-
-+2.
-editors notes, numbered asterisk footnote/endnote series
-
-
.<http://www.sisudoc.org/
->
-
.<http://www.ruby-lang.org/en/
->
-
.Table from the Wealth
-of Networks by Yochai Benkler <http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler
->
-
-
..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
-processing. It may be however that when the resulting file is shared .ssc
-is an appropriate suffix to use.
-
.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.
-
.<http://www.postgresql.org/
-> <http://advocacy.postgresql.org/
->
-<http://en.wikipedia.org/wiki/Postgresql
->
-
.<http://www.hwaci.com/sw/sqlite/
-> <http://en.wikipedia.org/wiki/Sqlite
->
-
-
.<http://search.sisudoc.org
->
-
.(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.
-
.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 and we can tell you which
-documents meet your search criteria, but there is no way we can tell you
-without opening each document where within each your matches are found.
-
-
-

-
-
-See Also
- sisu(1)
-,

- sisu-epub(1)
-,

- sisu-harvest(1)
-,

- sisu-html(1)
-,

- sisu-odf(1)
-,

- sisu-pdf(1)
-,

- sisu-pg(1)
-,

- sisu-sqlite(1)
-,

- sisu-txt(1)
-.

- sisu_vim(7)
-

-
-Homepage
- More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->

-
-Source
- <http://sources.sisudoc.org/
->

-
-Author
- SiSU is written by Ralph Amissah <ralph@amissah.com>

-
-
-

-Table of Contents

-

-Name
-Synopsis
-Sisu - Manual,
-What is Sisu?
-Introduction - What is Sisu?
-Commands Summary
-Description
-Document Processing Command Flags
-Command Line Modifiers
-Database Commands
-Shortcuts, Shorthand for Multiple Flags
-Command Line with Flags - Batch Processing
-Help
-Sisu Manual
-Sisu Man Pages
-Sisu Built-in Interactive Help, [discontinued]
-Introduction to Sisu Markup[^11]
-Summary
-Markup Examples
-Online
-Installed
-Markup of Headers
-Sample Header
-Available Headers
-Markup of Substantive Text
-Heading Levels
-Font Attributes
-Indentation and Bullets
-Hanging Indents
-Footnotes / Endnotes
-Links
-Naked Urls Within Text, Dealing with Urls
-Linking Text
-Linking Images
-Link Shortcut for Multiple Versions of a Sisu Document in the Same Directory
-Grouped Text
-Tables
-Poem
-Group
-Code
-Additional Breaks - Linebreaks Within Objects, Column and Page-breaks
-Line-breaks
-Page Breaks
-Book Index
-Composite Documents Markup
-Sisu Filetypes
-.sst .ssm .ssi Marked Up Plain Text
-Sisu Text - Regular Files (.sst)
-Sisu Master Files (.ssm)
-Sisu Insert Files (.ssi)
-Sisupod, Zipped Binary Container (sisupod.zip, .ssp)
-Configuration
-Configuration Files
-Config.yml
-Sisu_document_make
-Css - Cascading Style Sheets (for Html, Xhtml and Xml)
-Organising Content - Directory Structure and Mapping
-Document Source Directory
-General Directories
-Document Output Directory Structures
-Output Directory Root
-Alternative Output Structures
-by Language
-by Filetype
-by Filename
-Remote Directories
-Sisupod
-Organising Content
-Homepages
-Home Page and Other Custom Built Pages in a Sub-directory
-Markup and Output Examples
-Markup Examples
-Sisu Markup Samples
-Sisu Search - Introduction
-Sql
-Populating Sql Type Databases
-Postgresql
-Name
-Description
-Synopsis
-Commands
-Create and Destroy Database
-Import and Remove Documents
-Sqlite
-Name
-Description
-Synopsis
-Commands
-Create and Destroy Database
-Import and Remove Documents
-Introduction
-Search - Database Frontend Sample, Utilising Database and Sisu Features,
-Search Form
-Sisu_webrick
-Name
-Synopsis
-Description
-Summary of Man Page
-Document Processing Command Flags
-Summary of Features
-See Also
-Homepage
-Source
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu_complete.7.html b/data/doc/sisu/html/sisu_complete.7.html
deleted file mode 100644
index 1a1e025d..00000000
--- a/data/doc/sisu/html/sisu_complete.7.html
+++ /dev/null
@@ -1,54 +0,0 @@
-
-
-
-
-
-sisu_complete(7) manual page
-
-
-Table of Contents
-
-
Name
-SiSU - Structured information, Serialized Units - a document
-publishing system, complete dependency package
-
-
Synopsis
-Dummy package installs
-the whole of SiSU, excluding sisu-examples
-sisu-complete together with sisu-examples
-is the whole of sisu
-
Further Information
-
-For more information on SiSU see:
-<http://www.jus.uio.no/sisu
->

-or man sisu
-
Author
-Ralph Amissah <ralph@amissah.com>
-or <ralph.amissah@gmail.com>
-See
-sisu(1)
-, sisu(8)
-,
-Also
-sisu_webrick(1)
-, sisu_pdf(7)
-
-sisu_sqlite(7)
- sisu_postgresql(7)
- sisu_vim(7)
- sisu_termsheet(1)
-,
-
-

-Table of Contents

-

-Name
-Synopsis
-Further Information
-Author
-See
-Also
-
-
-
diff --git a/data/doc/sisu/html/sisu_pdf.7.html b/data/doc/sisu/html/sisu_pdf.7.html
deleted file mode 100644
index e2e41bda..00000000
--- a/data/doc/sisu/html/sisu_pdf.7.html
+++ /dev/null
@@ -1,171 +0,0 @@
-
-
-
-
-
-"sisu_pdf"("1") manual page
-
-
-Table of Contents
-
-
Name
-sisu - package to install what sisu needs to generate pdf (latex to
-pdf dependency component)
-Synopsis
-sisu -pv [filename/wildcard ] SISU - PDF,
-RALPH AMISSAH
- 1. SISU PDF
-
1.1 NAME
-
SiSU - Structured information, Serialized
-Units - a document publishing system.
-
1.2 DESCRIPTION
-
Information creating
-pdf output with sisu (and related to the sisu_pdf dependency package, which
-is a dummy package to install dependencies needed for SiSU to generate
-pdfs (primarily related to LaTeX), sisu_pdf being part of SiSU - man sisu).
-
-
SiSU generates LaTeX which is converted by LaTeX tools to pdf.
-
1.3 SYNOPSIS
-
-
sisu -pv [filename/wildcard]

-
-
1.4 COMMANDS
-

-

-
- sisu -pv   [filename/wildcard]
-creates two pdf documents: vertical
-(portrait.pdf) and; horizontal (landscape.pdf). SiSU generates LaTeX output
-which is converted to pdf if the appropriate LaTeX dependencies are met
-on the system.
-
-
- sisu -pv --papersize-a4   [filename/wildcard]
-overrides the default
-papersize set to A4. Preset alternative sizes include: ’A4’, U.S. ’letter’ and
-’legal’ and book sizes ’A5’ and ’B5’ (system defaults to A4).
-
-
-1.5 SETTING PAPER
-
-SIZE
-
The paper-size may be set to any of the following sizes: ’A4’, U.S. ’letter’
-and ’legal’ and book sizes: ’A5’ and ’B5’
-
1. The preset default if not otherwise
-given in the configuration file or elsewhere is A4.
-
2. The default paper
-size may be set in the configuration file sisurc.yml. See sisu_configuration:
-
-

-

-
#% papersize, (LaTeX/pdf) current values A4, US_letter, book_b5, book_a5,
-US_legal
- default:
- papersize: ’A4’
-
- 3. Paper size may be set in a document header:
-

-

-
@papersize: (A4|US_letter|book_B5|book_A5|US_legal)
-
- 4. or provided with additional command line parameter, e.g.
-
sisu -pv
---papersize-a4 [filename/wildcard]

-
-
DOCUMENT INFORMATION (METADATA)
-
METADATA
-
Document Manifest @ <http://sisudoc.org/sisu_manual/sisu_pdf/sisu_manifest.html
->
-
-
Dublin Core (DC)
-
DC tags included with this document are provided here.
-
-
DC Title: SiSU - PDF
-
DC Creator: Ralph Amissah
-
DC Rights: Copyright
-(C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3
-
DC
-Type: information
-
DC Date created: 2002-08-28
-
DC Date issued: 2002-08-28
-
-
DC Date available: 2002-08-28
-
DC Date modified: 2007-09-16
-
DC Date: 2007-09-16
-
-
Version Information
-
Sourcefile: sisu_pdf.sst
-
Filetype: SiSU text 0.58
-
-
Sourcefile Digest, MD5(sisu_pdf.sst)= bed13854370b5daf1b1541527e8946b7
-
-
Skin_Digest: MD5(skin_sisu_manual.rb)= 20fc43cf3eb6590bc3399a1aef65c5a9
-
-
Generated
-
Document (metaverse) last generated: Sat Sep 29 17:05:37
-
-
+0100 2007
-
Generated by: SiSU 0.59.1 of 2007w39/2 (2007-09-25)
-
Ruby version:
-ruby 1.8.6 (2007-06-07 patchlevel 36) [i486-linux]
-

-

-

-
-Other versions of this
-document:
-
-
-manifest: <http://www.jus.uio.no/sisu/sisu_pdf/sisu_manifest.html
-
->
-
-
-
-html: <http://www.jus.uio.no/sisu/sisu_pdf/toc.html
-
->
-
-
-pdf: <http://www.jus.uio.no/sisu/sisu_pdf/portrait.pdf
-
->
-
-
-
-pdf: <http://www.jus.uio.no/sisu/sisu_pdf/landscape.pdf
-
->
-
-
-at: <http://www.jus.uio.no/sisu
-
->
-
-
-
-* Generated by: SiSU 0.59.1 of 2007w39/2 (2007-09-25)
-
-
-* Ruby version: ruby
-1.8.6 (2007-06-07 patchlevel 36) [i486-linux]
-
-
-* Last Generated on: Sat Sep 29
-17:05:39 +0100 2007
-
-
-* SiSU http://www.jus.uio.no/sisu
-
-
-
-
-
-

-Table of Contents

-

-Name
-Synopsis
-
-
-
diff --git a/data/doc/sisu/html/sisu_postgresql.7.html b/data/doc/sisu/html/sisu_postgresql.7.html
deleted file mode 100644
index 6bc6be80..00000000
--- a/data/doc/sisu/html/sisu_postgresql.7.html
+++ /dev/null
@@ -1,198 +0,0 @@
-
-
-
-
-
-"sisu_postgresql"("1") manual page
-
-
-Table of Contents
-
-
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] SISU - SEARCH, RALPH AMISSAH
- 1. POSTGRESQL
-
1.1
-
-
NAME
-
SiSU - Structured information, Serialized Units - a document publishing
-system, postgresql dependency package
-
1.2 DESCRIPTION
-
Information related
-to using postgresql with sisu (and related to the sisu_postgresql dependency
-package, which is a dummy package to install dependencies needed for SiSU
-to populate a postgresql database, this being part of SiSU - man sisu).
-

-
-
1.3 SYNOPSIS
-
sisu -D [instruction] [filename/wildcard if required]

-
-
sisu -D --pg --[instruction] [filename/wildcard if required]

-
-
1.4 COMMANDS
-
Mappings to two databases are provided by default, postgresql
-and sqlite, the same commands are used within sisu to construct and populate
-databases however -d (lowercase) denotes sqlite and -D (uppercase) denotes
-postgresql, alternatively --sqlite or --pgsql may be used
-
-D or --pgsql may
-be used interchangeably.
-
1.4.1 CREATE AND DESTROY DATABASE
-

-

-
- --pgsql --createall
-
- initial step, creates required relations (tables, indexes) in existing
- (postgresql) database (a database should be created (postgresql dependency
-component) manually and given the same name as working directory, as requested)
- (rb.dbi) the same name as working directory, as
-
-
- sisu -D --createdb
- creates
- database where no database existed before as
-
-
- sisu -D --create
- creates database
- tables where no database tables existed before database tables where no
- database tables existed
-
-
- 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). a
-
-
- sisu -D --recreate
-
-
- destroys existing database and builds a new empty database structure
-

-
-1.4.2
-
-IMPORT AND REMOVE DOCUMENTS
-

-

-
- 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]
-
-
-updates file contents in database
-

-
- sisu -D --remove -v   [filename/wildcard]
-
-removes specified document from postgresql database.
-
-
-DOCUMENT INFORMATION
-(METADATA)
- METADATA
-
Document Manifest @ <http://sisudoc.org/sisu_manual/sisu_postgresql/sisu_manifest.html
->
-
-
Dublin Core (DC)
-
DC tags included with this document are provided here.
-
-
DC Title: SiSU - Search
-
DC Creator: Ralph Amissah
-
DC Rights: Copyright
-(C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3
-
DC
-Type: information
-
DC Date created: 2002-08-28
-
DC Date issued: 2002-08-28
-
-
DC Date available: 2002-08-28
-
DC Date modified: 2007-09-16
-
DC Date: 2007-09-16
-
-
Version Information
-
Sourcefile: sisu_postgresql.sst
-
Filetype: SiSU
-
-
text 0.58
-
Sourcefile Digest, MD5(sisu_postgresql.sst)= 9010e85001c50e30ba2ab69f9097825a
-
-
Skin_Digest: MD5(skin_sisu_manual.rb)= 20fc43cf3eb6590bc3399a1aef65c5a9
-
-
Generated
-
Document (metaverse) last generated: Sat Sep 29 17:05:38
-
-
+0100 2007
-
Generated by: SiSU 0.59.1 of 2007w39/2 (2007-09-25)
-
Ruby version:
-ruby 1.8.6 (2007-06-07 patchlevel 36) [i486-linux]
-

-

-

-
-Other versions of this
-document:
-
-
-manifest: <http://www.jus.uio.no/sisu/sisu_postgresql/sisu_manifest.html
-
->
-
-
-
-html: <http://www.jus.uio.no/sisu/sisu_postgresql/toc.html
-
->
-
-
-pdf: <http://www.jus.uio.no/sisu/sisu_postgresql/portrait.pdf
-
->
-
-
-
-pdf: <http://www.jus.uio.no/sisu/sisu_postgresql/landscape.pdf
-
->
-
-
-at: <http://www.jus.uio.no/sisu
-
->
-
-
-
-* Generated by: SiSU 0.59.1 of 2007w39/2 (2007-09-25)
-
-
-* Ruby version: ruby
-1.8.6 (2007-06-07 patchlevel 36) [i486-linux]
-
-
-* Last Generated on: Sat Sep 29
-17:05:39 +0100 2007
-
-
-* SiSU http://www.jus.uio.no/sisu
-
-
-
-
-
-

-Table of Contents

-

-Name
-Synopsis
-
-
-
diff --git a/data/doc/sisu/html/sisu_sqlite.7.html b/data/doc/sisu/html/sisu_sqlite.7.html
deleted file mode 100644
index b6f8b59b..00000000
--- a/data/doc/sisu/html/sisu_sqlite.7.html
+++ /dev/null
@@ -1,196 +0,0 @@
-
-
-
-
-
-"sisu_sqlite"("1") manual page
-
-
-Table of Contents
-
-
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] SISU - SEARCH, RALPH AMISSAH
- 1. SQLITE
-
1.1 NAME
-
-
SiSU - Structured information, Serialized Units - a document publishing
-system.
-
1.2 DESCRIPTION
-
Information related to using sqlite with sisu
-(and related to the sisu_sqlite dependency package, which is a dummy package
-to install dependencies needed for SiSU to populate an sqlite database,
-this being part of SiSU - man sisu).
-
1.3 SYNOPSIS
-
sisu -d [instruction]
- [filename/wildcard if required]

-
-
sisu -d --(sqlite|pg) --[instruction] [filename/wildcard if

- required]

-
-
1.4 COMMANDS
-
Mappings to two databases are provided by default, postgresql
-and sqlite, the same commands are used within sisu to construct and populate
-databases however -d (lowercase) denotes sqlite and -D (uppercase) denotes
-postgresql, alternatively --sqlite or --pgsql may be used
-
-d or --sqlite may
-be used interchangeably.
-
1.4.1 CREATE AND DESTROY DATABASE
-

-

-
- --sqlite --createall
-
- initial step, creates required relations (tables, indexes) in existing
- (sqlite) database (a database should be created as requested) (rb.dbi) the
- same name as working directory, as
-
-
- sisu -d --createdb
- creates database where
- no database existed before as
-
-
- sisu -d --create
- creates database tables where
- no database tables existed before database tables where no database tables
- existed
-
-
- 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). a
-
-
- sisu -d --recreate
- destroys
-
- existing database and builds a new empty database structure
-

-
-1.4.2 IMPORT
-
-AND REMOVE DOCUMENTS
-

-

-
- 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]
-updates
-
-file contents in database
-

-
- sisu -d --remove -v   [filename/wildcard]
-removes
-specified document from sqlite database.
-
-
-DOCUMENT INFORMATION (METADATA)
-
- METADATA
-
Document Manifest @ <http://sisudoc.org/sisu_manual/sisu_sqlite/sisu_manifest.html
->
-
-
Dublin Core (DC)
-
DC tags included with this document are provided here.
-
-
DC Title: SiSU - Search
-
DC Creator: Ralph Amissah
-
DC Rights: Copyright
-(C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3
-
DC
-Type: information
-
DC Date created: 2002-08-28
-
DC Date issued: 2002-08-28
-
-
DC Date available: 2002-08-28
-
DC Date modified: 2007-09-16
-
DC Date: 2007-09-16
-
-
Version Information
-
Sourcefile: sisu_sqlite.sst
-
Filetype: SiSU text
-
-
0.58
-
Sourcefile Digest, MD5(sisu_sqlite.sst)= c4717fcab8a43de498d41a916bb99551
-
-
Skin_Digest: MD5(skin_sisu_manual.rb)= 20fc43cf3eb6590bc3399a1aef65c5a9
-
-
Generated
-
Document (metaverse) last generated: Sat Sep 29 17:05:38
-
-
+0100 2007
-
Generated by: SiSU 0.59.1 of 2007w39/2 (2007-09-25)
-
Ruby version:
-ruby 1.8.6 (2007-06-07 patchlevel 36) [i486-linux]
-

-

-

-
-Other versions of this
-document:
-
-
-manifest: <http://www.jus.uio.no/sisu/sisu_sqlite/sisu_manifest.html
-
->
-
-
-
-html: <http://www.jus.uio.no/sisu/sisu_sqlite/toc.html
-
->
-
-
-pdf: <http://www.jus.uio.no/sisu/sisu_sqlite/portrait.pdf
-
->
-
-
-
-pdf: <http://www.jus.uio.no/sisu/sisu_sqlite/landscape.pdf
-
->
-
-
-at: <http://www.jus.uio.no/sisu
-
->
-
-
-
-* Generated by: SiSU 0.59.1 of 2007w39/2 (2007-09-25)
-
-
-* Ruby version: ruby
-1.8.6 (2007-06-07 patchlevel 36) [i486-linux]
-
-
-* Last Generated on: Sat Sep 29
-17:05:39 +0100 2007
-
-
-* SiSU http://www.jus.uio.no/sisu
-
-
-
-
-
-

-Table of Contents

-

-Name
-Synopsis
-
-
-
diff --git a/data/doc/sisu/html/sisu_termsheet.1.html b/data/doc/sisu/html/sisu_termsheet.1.html
deleted file mode 100644
index d4f2b698..00000000
--- a/data/doc/sisu/html/sisu_termsheet.1.html
+++ /dev/null
@@ -1,76 +0,0 @@
-
-
-
-
-
-sisu_termsheet(1) manual page
-
-
-Table of Contents
-
-
Name
-SiSU - Structured information, Serialized Units - a document
-publishing system
-Synopsis
-
-sisu -t [termsheet-name(s)]
-
Description
-sisu_termsheet
-is part of SiSU is invoked through the sisu command (man sisu)
-
-
Summary
-of man page
-
-sisu_termsheet, is started with the command: sisu --termsheet
-[termsheet-name(s)]
-
Document Processing Command Flags
-
-sisu -t [termsheet-name(s)]
-(runs sisu_termsheet) merges the termsheet(s) specified on the commandline
-with the documents it is instructed to merge in the termsheet(s), and produces
-regular SiSU output documents from the merged results.

-[further documentation
-on termsheets required]
-
Further Information
-
-For more information on SiSU
-see: <http://www.jus.uio.no/sisu
->

-or man sisu
-
Author
-Ralph Amissah <ralph@amissah.com>
-or <ralph.amissah@gmail.com>
-See Also
-sisu(1)
-, sisu(8)
-, sisu_webrick(1)
-, sisu_vim(7)
-
-
-
-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-
-

-Table of Contents

-

-Name
-Synopsis
-Description
-Summary of man page
-Document Processing Command Flags
-Further Information
-Author
-See Also
-Homepage
-Author
-
-
-
diff --git a/data/doc/sisu/html/sisu_vim.7.html b/data/doc/sisu/html/sisu_vim.7.html
deleted file mode 100644
index b7ee2028..00000000
--- a/data/doc/sisu/html/sisu_vim.7.html
+++ /dev/null
@@ -1,62 +0,0 @@
-
-
-
-
-
-"sisu_vim"("1") manual page
-
-
-Table of Contents
-
-
Name
- sisu_vim - vim syntax and folds file for sisu: markup, structuring,
-publishing in multiple standard formats, and search

- SISU - VIM, RALPH AMISSAH
- SISU VIM
-
1. SISU VIM
-
Synopsis
-
SiSU has
-syntax highlighting for a number of editors including vim which are documented
-under:
-
/usr/share/doc/sisu/markup-samples/sisu_manual/sisu_syntax_highlighting.sst

-
-
<http://www.sisudoc.org/sisu/sisu_manual/sisu_syntax_highlighting/index.html
->

-
-
SiSU also provides an ftplugin to provide vim folds for SiSU markup,
-and to set some defaults for SiSU markup in installed by sisu.
-
Vim 7 includes
-sisu markup syntax highlighting.
-
Vim related files are included in: /usr/share/sisu/conf/editor-syntax-etc/vim
-(including the syntax highlighter, together with an ftplugin which may
-be sourced if so desired from your vimrc).
-
sisu-vim actions are activated
-on files with the suffix .sst .ssm .ssi .-sst ._sst (and the same with a further
-.meta extension)

-
-

-

-
<ctrl>F activate folds on headings matched in a document
- (also provides folds when sourced on a ruby program file),
- also :F
- <ctrl>S search and replace down
- <ctrl>G search and replace globally within file
- <ctrl>X ruby regex global search and replace within file
- <ctrl>C set color scheme to slate which is provided
-
- FURTHER INFORMATION
-
For more information on SiSU see:
-
<http://sisudoc.org/
->
-
-
<http://www.jus.uio.no/sisu
->
-
or man sisu

-
-

-Table of Contents

-

-Name
-
-
-
diff --git a/data/doc/sisu/html/sisu_webrick.1.html b/data/doc/sisu/html/sisu_webrick.1.html
deleted file mode 100644
index c1efc98d..00000000
--- a/data/doc/sisu/html/sisu_webrick.1.html
+++ /dev/null
@@ -1,93 +0,0 @@
-
-
-
-
-
-"sisu_webrick"("1") manual page
-
-
-Table of Contents
-
-
Name
-sisu - documents: structuring, publishing in multiple formats, and search
-
-Synopsis
-sisu -W SISU - SISU_WEBRICK, RALPH AMISSAH
- SISU WEBRICK
-
1. SISU_WEBRICK
-
-
1.1 NAME
-
SiSU - Structured information, Serialized Units - a document
-
-
publishing system
-
1.2 SYNOPSIS
-
sisu_webrick [port]
-
or
-
sisu --Webrick
- [port]
-
or
-
sisu -W [port]
-
1.3 DESCRIPTION
-
sisu_webrick is part of SiSU
-(man sisu) sisu_webrick starts Ruby ’s Webrick web-server and points it to
-the directories to which SiSU output is written, providing a list of these
-directories (assuming SiSU is in use and they exist).
-
The default port
-for sisu_webrick is set to 8081, this may be modified in the yaml file:
-~/.sisu/sisurc.yml a sample of which is provided as /etc/sisu/sisurc.yml (or
-in the equivalent directory on your system).
-
1.4 SUMMARY OF MAN PAGE
-
sisu_webrick,
-may be started on it’s own with the command: sisu_webrick or using the sisu
-command with the -W flag: sisu -W [port]
-
where no port is given and settings
-
-
are unchanged the default port is 8081
-
1.5 DOCUMENT PROCESSING COMMAND
-
-
FLAGS
-
sisu -W [port] starts Ruby Webrick web-server, serving SiSU output
-directories, on the port provided, or if no port is provided and the defaults
-
-
have not been changed in ~/.sisu/sisurc.yaml then on port 8081
-
1.6 FURTHER
-
-
INFORMATION
-
For more information on SiSU see: <http://www.jus.uio.no/sisu
->
-
-
or man sisu
-
1.7 AUTHOR
-
Ralph Amissah ralph@amissah.com or ralph.amissah@gmail.com
-
-
1.8 SEE ALSO
-
sisu(1)
-

-
-
sisu_vim(7)
-

-
-
sisu(8)
-

-
-

-
Homepage
-More information about SiSU can be found at <http://www.sisudoc.org/
->
-or <http://www.jus.uio.no/sisu/
->.
-
-
Author
-SiSU is written by Ralph Amissah <ralph@amissah.com>.
-
-
-

-Table of Contents

-

-Name
-Synopsis
-Homepage
-Author
-
-
-
--
cgit v1.2.3

From e4ef7cc28d4c4e3360ac8dab749827f4a741698d Mon Sep 17 00:00:00 2001
From: Ralph Amissah
Date: Wed, 5 Feb 2014 01:19:15 -0500
Subject: sisu manual directory moved

---
data/doc/sisu/CHANGELOG_v5 | 1 +
data/doc/sisu/CHANGELOG_v6 | 1 +
data/doc/sisu/markup-samples/manual/Rakefile | 404 ++++++
.../_sisu/image/GnuDebianLinuxRubyBetterWay.png | Bin 0 -> 33396 bytes
.../manual/_sisu/image/ruby_logo.png | Bin 0 -> 8634 bytes
.../markup-samples/manual/_sisu/image/sisu.png | Bin 0 -> 3260 bytes
.../sisu/markup-samples/manual/_sisu/image/tux.png | Bin 0 -> 6297 bytes
.../manual/_sisu/rc/sisurc_by_fn.yml | 137 ++
.../manual/_sisu/rc/sisurc_by_fn_monolingual.yml | 137 ++
.../manual/_sisu/rc/sisurc_by_ft.yml | 137 ++
.../manual/_sisu/rc/sisurc_by_ft_monolingual.yml | 137 ++
.../manual/_sisu/rc/sisurc_by_lng.yml | 135 ++
.../markup-samples/manual/_sisu/sisu_document_make | 20 +
.../sisu/markup-samples/manual/_sisu/v5/sisurc.yml | 1 +
.../sisu/markup-samples/manual/_sisu/v6/sisurc.yml | 1 +
data/doc/sisu/markup-samples/manual/en/sisu.ssm | 73 ++
.../markup-samples/manual/en/sisu_commands.sst | 497 ++++++++
.../sisu/markup-samples/manual/en/sisu_config.ssi | 75 ++
.../manual/en/sisu_content_directories.ssi | 264 ++++
.../doc/sisu/markup-samples/manual/en/sisu_css.ssi | 42 +
.../markup-samples/manual/en/sisu_description.sst | 527 ++++++++
.../markup-samples/manual/en/sisu_download.ssi | 133 ++
.../markup-samples/manual/en/sisu_examples.ssi | 97 ++
.../doc/sisu/markup-samples/manual/en/sisu_faq.sst | 200 +++
.../markup-samples/manual/en/sisu_filetypes.sst | 143 +++
.../sisu/markup-samples/manual/en/sisu_help.sst | 77 ++
.../markup-samples/manual/en/sisu_help_sources.sst | 108 ++
.../markup-samples/manual/en/sisu_homepages.ssi | 39 +
.../doc/sisu/markup-samples/manual/en/sisu_how.ssi | 26 +
.../sisu/markup-samples/manual/en/sisu_howto.sst | 1326 ++++++++++++++++++++
.../markup-samples/manual/en/sisu_installation.ssi | 368 ++++++
.../manual/en/sisu_interesting_to_whom.ssi | 32 +
.../markup-samples/manual/en/sisu_introduction.sst | 55 +
.../sisu/markup-samples/manual/en/sisu_manual.ssm | 96 ++
.../sisu/markup-samples/manual/en/sisu_markup.sst | 1312 +++++++++++++++++++
.../manual/en/sisu_markup_syntax_history.sst | 244 ++++
.../manual/en/sisu_output_overview.sst | 142 +++
.../markup-samples/manual/en/sisu_postgresql.sst | 82 ++
.../markup-samples/manual/en/sisu_quickstart.sst | 256 ++++
.../sisu/markup-samples/manual/en/sisu_remote.sst | 88 ++
.../sisu/markup-samples/manual/en/sisu_search.ssm | 35 +
.../markup-samples/manual/en/sisu_search_cgi.ssi | 75 ++
.../markup-samples/manual/en/sisu_search_intro.ssi | 31 +
.../manual/en/sisu_short_feature_summary.ssi | 81 ++
.../doc/sisu/markup-samples/manual/en/sisu_sql.ssi | 50 +
.../sisu/markup-samples/manual/en/sisu_sqlite.sst | 82 ++
.../markup-samples/manual/en/sisu_synopsis.ssi | 48 +
.../manual/en/sisu_syntax_highlighting.sst | 151 +++
.../sisu/markup-samples/manual/en/sisu_webrick.sst | 59 +
.../manual/en/sisu_work_needed_and_wishlist.ssi | 59 +
.../markup-samples/manual/translation_languages | 1 +
data/doc/sisu/markup-samples/sisu_manual/Rakefile | 404 ------
.../_sisu/image/GnuDebianLinuxRubyBetterWay.png | Bin 33396 -> 0 bytes
.../sisu_manual/_sisu/image/ruby_logo.png | Bin 8634 -> 0 bytes
.../sisu_manual/_sisu/image/sisu.png | Bin 3260 -> 0 bytes
.../markup-samples/sisu_manual/_sisu/image/tux.png | Bin 6297 -> 0 bytes
.../sisu_manual/_sisu/rc/sisurc_by_fn.yml | 137 --
.../_sisu/rc/sisurc_by_fn_monolingual.yml | 137 --
.../sisu_manual/_sisu/rc/sisurc_by_ft.yml | 137 --
.../_sisu/rc/sisurc_by_ft_monolingual.yml | 137 --
.../sisu_manual/_sisu/rc/sisurc_by_lng.yml | 135 --
.../sisu_manual/_sisu/sisu_document_make | 20 -
.../markup-samples/sisu_manual/_sisu/v5/sisurc.yml | 1 -
.../markup-samples/sisu_manual/_sisu/v6/sisurc.yml | 1 -
.../sisu/markup-samples/sisu_manual/en/sisu.ssm | 73 --
.../sisu_manual/en/sisu_commands.sst | 497 --------
.../markup-samples/sisu_manual/en/sisu_config.ssi | 75 --
.../sisu_manual/en/sisu_content_directories.ssi | 264 ----
.../markup-samples/sisu_manual/en/sisu_css.ssi | 42 -
.../sisu_manual/en/sisu_description.sst | 527 --------
.../sisu_manual/en/sisu_download.ssi | 133 --
.../sisu_manual/en/sisu_examples.ssi | 97 --
.../markup-samples/sisu_manual/en/sisu_faq.sst | 200 ---
.../sisu_manual/en/sisu_filetypes.sst | 143 ---
.../markup-samples/sisu_manual/en/sisu_help.sst | 77 --
.../sisu_manual/en/sisu_help_sources.sst | 108 --
.../sisu_manual/en/sisu_homepages.ssi | 39 -
.../markup-samples/sisu_manual/en/sisu_how.ssi | 26 -
.../markup-samples/sisu_manual/en/sisu_howto.sst | 1326 --------------------
.../sisu_manual/en/sisu_installation.ssi | 368 ------
.../sisu_manual/en/sisu_interesting_to_whom.ssi | 32 -
.../sisu_manual/en/sisu_introduction.sst | 55 -
.../markup-samples/sisu_manual/en/sisu_manual.ssm | 96 --
.../markup-samples/sisu_manual/en/sisu_markup.sst | 1312 -------------------
.../sisu_manual/en/sisu_markup_syntax_history.sst | 244 ----
.../sisu_manual/en/sisu_output_overview.sst | 142 ---
.../sisu_manual/en/sisu_postgresql.sst | 82 --
.../sisu_manual/en/sisu_quickstart.sst | 256 ----
.../markup-samples/sisu_manual/en/sisu_remote.sst | 88 --
.../markup-samples/sisu_manual/en/sisu_search.ssm | 35 -
.../sisu_manual/en/sisu_search_cgi.ssi | 75 --
.../sisu_manual/en/sisu_search_intro.ssi | 31 -
.../sisu_manual/en/sisu_short_feature_summary.ssi | 81 --
.../markup-samples/sisu_manual/en/sisu_sql.ssi | 50 -
.../markup-samples/sisu_manual/en/sisu_sqlite.sst | 82 --
.../sisu_manual/en/sisu_synopsis.ssi | 48 -
.../sisu_manual/en/sisu_syntax_highlighting.sst | 151 ---
.../markup-samples/sisu_manual/en/sisu_webrick.sst | 59 -
.../en/sisu_work_needed_and_wishlist.ssi | 59 -
.../sisu_manual/translation_languages | 1 -
100 files changed, 8085 insertions(+), 8083 deletions(-)
create mode 100644 data/doc/sisu/markup-samples/manual/Rakefile
create mode 100644 data/doc/sisu/markup-samples/manual/_sisu/image/GnuDebianLinuxRubyBetterWay.png
create mode 100644 data/doc/sisu/markup-samples/manual/_sisu/image/ruby_logo.png
create mode 100644 data/doc/sisu/markup-samples/manual/_sisu/image/sisu.png
create mode 100644 data/doc/sisu/markup-samples/manual/_sisu/image/tux.png
create mode 100644 data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_fn.yml
create mode 100644 data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_fn_monolingual.yml
create mode 100644 data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_ft.yml
create mode 100644 data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_ft_monolingual.yml
create mode 100644 data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_lng.yml
create mode 100644 data/doc/sisu/markup-samples/manual/_sisu/sisu_document_make
create mode 120000 data/doc/sisu/markup-samples/manual/_sisu/v5/sisurc.yml
create mode 120000 data/doc/sisu/markup-samples/manual/_sisu/v6/sisurc.yml
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu.ssm
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_commands.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_config.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_content_directories.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_css.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_description.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_download.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_examples.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_faq.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_filetypes.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_help.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_help_sources.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_homepages.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_how.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_howto.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_installation.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_interesting_to_whom.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_introduction.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_manual.ssm
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_markup.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_markup_syntax_history.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_output_overview.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_postgresql.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_quickstart.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_remote.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_search.ssm
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_search_cgi.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_search_intro.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_short_feature_summary.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_sql.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_sqlite.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_synopsis.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_syntax_highlighting.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_webrick.sst
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_work_needed_and_wishlist.ssi
create mode 100644 data/doc/sisu/markup-samples/manual/translation_languages
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/Rakefile
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/_sisu/image/GnuDebianLinuxRubyBetterWay.png
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/_sisu/image/ruby_logo.png
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/_sisu/image/sisu.png
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/_sisu/image/tux.png
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_fn.yml
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_fn_monolingual.yml
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_ft.yml
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_ft_monolingual.yml
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_lng.yml
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/_sisu/sisu_document_make
delete mode 120000 data/doc/sisu/markup-samples/sisu_manual/_sisu/v5/sisurc.yml
delete mode 120000 data/doc/sisu/markup-samples/sisu_manual/_sisu/v6/sisurc.yml
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu.ssm
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_commands.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_config.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_content_directories.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_css.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_description.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_download.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_examples.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_faq.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_filetypes.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_help.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_help_sources.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_homepages.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_how.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_howto.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_installation.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_interesting_to_whom.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_introduction.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_manual.ssm
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_markup.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_markup_syntax_history.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_output_overview.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_postgresql.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_quickstart.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_remote.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_search.ssm
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_search_cgi.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_search_intro.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_short_feature_summary.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_sql.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_sqlite.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_synopsis.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_syntax_highlighting.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_webrick.sst
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/en/sisu_work_needed_and_wishlist.ssi
delete mode 100644 data/doc/sisu/markup-samples/sisu_manual/translation_languages

diff --git a/data/doc/sisu/CHANGELOG_v5 b/data/doc/sisu/CHANGELOG_v5
index 0388ffe8..890f1758 100644
--- a/data/doc/sisu/CHANGELOG_v5
+++ b/data/doc/sisu/CHANGELOG_v5
@@ -63,6 +63,7 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_5.3.1.orig.tar.xz
* error/warn messages, including wrappers round require

* documentation, manpage README etc.
+ * sisu manual directory moved
* removed html man pages (man2html)

%% 5.3.0.orig.tar.xz (2014-01-26:03/7)
diff --git a/data/doc/sisu/CHANGELOG_v6 b/data/doc/sisu/CHANGELOG_v6
index b1ef302a..c09040a6 100644
--- a/data/doc/sisu/CHANGELOG_v6
+++ b/data/doc/sisu/CHANGELOG_v6
@@ -53,6 +53,7 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_6.0.1.orig.tar.xz
* error/warn messages, including wrappers round require

* documentation, manpage README etc.
+ * sisu manual directory moved
* removed html man pages (man2html)

%% 6.0.0.orig.tar.xz (2014-01-26:03/7)
diff --git a/data/doc/sisu/markup-samples/manual/Rakefile b/data/doc/sisu/markup-samples/manual/Rakefile
new file mode 100644
index 00000000..1d9b5414
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/Rakefile
@@ -0,0 +1,404 @@
+#!/usr/bin/env ruby
+raise 'Please, use ruby1.9.3 or later.' if RUBY_VERSION < '1.9.3'
+=begin
+ Common Rakefile, Rantfile to place sisu markup translation under
+ po4a management softlink Rakefile and Rantfile to this file
+
+ * Homepage:
+
+ * Download:
+
+ Copyright (C) 2013 Ralph Amissah
+
+ * License: LGPL - GNU Lesser General Public License
+ [same license as Rant provided within the Rant package]
+
+ * Ralph Amissah
+ Ralph Amissah
+
+ Rake is a Ruby build program by Jim Weirich
+ * Rake may be downloaded and installed from:
+
+
+ Rant is a Ruby build program by Stefan Lang
+ * Rant may be downloaded and installed from:
+
+
+ Notes on use:
+ rake -T
+ [if rant is preferred and installed]
+ rant -T
+=end
+require 'find'
+require 'fileutils'
+#require 'ftools'
+require 'rbconfig.rb'
+#include RbConfig
+require 'yaml'
+include FileUtils
+def project_details
+ def name
+ 'SiSU translations under po4a management'
+ end
+ def name_warning
+ <<-WOK
+#{name}
+
+WARNING all sisu markup files (.ssm, .sst, .ssi) in languages other than #{language.source}
+are managed by po4a, through translations of the source language to other languages.
+
+#{language.info_on_selection}
+ WOK
+ end
+ def rake_project
+ "Rakefile for placing #{name}"
+ end
+ self
+end
+def query
+ def answer?(ask)
+ resp='redo'
+ print ask + %{ ['yes', 'no' or 'quit']: }
+ resp=File.new('/dev/tty').gets.strip
+ if resp == 'yes'; true
+ elsif resp == 'no'; false
+ elsif resp =~/^quit|exit$/; exit
+ else
+ puts %{[please type: 'yes', 'no' or 'quit']}
+ answer?(ask)
+ end
+ end
+ self
+end
+def notice
+ def warn_and_proceed?
+ %{WARNING: This Software is used entirely at your own risk.
+ PROCEED?}
+ end
+ def default(selection=nil)
+ ans= if selection
+ case selection
+ when selection.is_a?(String)
+ <<-WOK
+ #{project_details.rake_project}
+ Information on alternative actions is available using: "rake help" or "rake -T"
+ Default action selected - "#{selection} #{project_details.name}"
+ #{warn_and_proceed?}
+ WOK
+ when :make
+ <<-WOK
+ #{project_details.rake_project}
+ Information on alternative actions is available using: "rake help" or "rake -T"
+ #{selection.upcase} selected - #{selection} #{project_details.name}
+ WARNING: this action assumes (and places) this project is under po4a
+ (translation) management. It will create the sub-directories:
+ #{language.translations_available_str}
+ & file: #{filename.po4a_cfg}
+ in the current directory:
+ #{Dir.pwd}
+ It will populate the sub-directories with translation files created from
+ the pot and po files found under the corresponding language sub-directories,
+ (under #{dir.pot}/ & #{dir.po}/). (OVERWRITING any existing translated
+ .ssm .sst .ssi files in language subdirectories that are not under po4a
+ management).
+ #{warn_and_proceed?}
+ WOK
+ when :clean
+ <<-WOK
+ #{project_details.rake_project}
+ Information on alternative actions is available using: "rake help" or "rake -T"
+ #{selection.upcase} selected - #{selection} #{project_details.name}
+ #{warn_and_proceed?}
+ WOK
+ when :distclean
+ <<-WOK
+ #{project_details.rake_project}
+ Information on alternative actions is available using: "rake help" or "rake -T"
+ #{selection.upcase} selected - #{selection} #{project_details.name}
+ WARNING: this action assumes (and places) this project is under po4a
+ (translation) management. It will remove the sub-directories:
+ #{language.translations_available_str}
+ & file: #{filename.po4a_cfg}
+ in the current directory:
+ #{Dir.pwd}
+ Note: these sub-directories & the config file #{filename.po4a_cfg}
+ should be auto-generated from pot and po files if this project translation
+ is under po4a management.
+ This query is to give you the chance to make sure you know what you are doing.
+ #{warn_and_proceed?}
+ WOK
+ when :rebuild
+ <<-WOK
+ #{project_details.rake_project}
+ Information on alternative actions is available using: "rake help" or "rake -T"
+ #{selection.upcase} selected - #{selection} #{project_details.name}
+ WARNING: this action assumes (and places) this project is under po4a
+ (translation) management. It will destroy/clobber and then create again the
+ sub-directories:
+ #{language.translations_available_str}
+ populating them with translation files created from the pot and po files
+ found under the corresponding language sub-directories in (#{dir.pot}/
+ & #{dir.po}/).
+ It will also generate the file: #{filename.po4a_cfg}
+ These actions will be taken in the current directory:
+ #{Dir.pwd}
+ This query is to give you the chance to make sure you know what you are doing.
+ #{warn_and_proceed?}
+ WOK
+ else
+ <<-WOK
+ #{project_details.rake_project}
+ Information on alternative actions is available using: "rake help" or "rake -T"
+ Default action selected - "#{selection} #{project_details.name}"
+ #{warn_and_proceed?}
+ WOK
+ end
+ else
+ <<-WOK
+ #{project_details.rake_project}
+ Information on alternative actions is available using: "rake help" or "rake -T"
+ Default action selected - "install and to setup #{project_details.name}"
+ #{warn_and_proceed?}
+ WOK
+ end
+ resp=query.answer?(ans)
+ exit unless resp
+ end
+ def project_help
+ puts <<-WOK
+#{project_details.name}
+#{project_details.rake_project}
+
+This rake file is to assist with having sisu markup files under po4a
+translation management. It assumes that the source language files are placed
+under the sub-directory identifying the source language set, which is currently
+#{language.source}
+The files there are used to make the source translation file in the directory #{dir.pot}/
+Which is then used to create files for translation under the directory #{dir.po}/
+in sub-directories bearing the translation languages ISO code.
+
+The current language translation selection is: #{translations_selected_str}
+The languages selected are located in the file: #{filename.languages}
+
+sisu available language list: #{sisu_available_str}
+
+For a more detailed and up to date task list use:
+
+ rake -T
+
+ WOK
+ end
+ self
+end
+def tasks
+ system('rake -T')
+end
+def filename
+ def languages
+ 'translation_languages'
+ end
+ def po4a_cfg
+ 'po4a.cfg'
+ end
+ self
+end
+def dir
+ def pwd
+ Dir.pwd
+ end
+ def po4a_
+ 'po4a/' # ''
+ end
+ def pot
+ po4a_ + 'pot'
+ end
+ def po
+ po4a_ + 'po'
+ end
+ self
+end
+def dir_mk(dir)
+ FileUtils::mkdir_p(dir) unless FileTest.directory?(dir)
+end
+def po4a_flags
+ def debug
+ '-d -v'
+ end
+ def normal
+ ''
+ end
+ def quiet
+ '-q'
+ end
+ self
+end
+def language
+ def source #source_language
+ 'en'
+ end
+ def translations_selected #translation_languages
+ IO.read(filename.languages, mode: 'r:utf-8').split(/\s+/)
+ end
+ def translations_available
+ translations_selected & sisu_available
+ end
+ def info_on_selection
+ if translations_selected != translations_available
+ <<-WOK
+WARNING: language selections mismatch
+
+The current language translation selection appears to be: #{translations_selected_str}
+Of which the following are valid (available) selections: #{translations_available_str}
+
+sisu available language list: #{sisu_available_str}
+
+the following will be used: #{translations_available_str}
+The languages selected are located in the file: #{filename.languages}
+ WOK
+ else
+ <<-WOK
+The current language translation selection is: #{translations_selected_str}
+The languages selected are located in the file: #{filename.languages}
+
+sisu available language list: #{sisu_available_str}
+ WOK
+ end
+ end
+ def sisu_available
+ %w[am bg bn br ca cs cy da de el en eo es et eu fi fr ga gl he hi hr hy ia is it ja ko la lo lt lv ml mr nl nn no oc pl pt pt_BR ro ru sa se sk sl sq sr sv ta te th tk tr uk ur us vi zh]
+ end
+ def translations_selected_str
+ language.translations_selected.join(' ')
+ end
+ def translations_available_str
+ language.translations_available.join(' ')
+ end
+ def sisu_available_str
+ language.sisu_available.join(' ')
+ end
+ self
+end
+def files_src
+ def ssm
+ Dir.glob("#{language.source}/*.ssm").sort
+ end
+ def sst
+ Dir.glob("#{language.source}/*.sst").sort
+ end
+ def ssi
+ Dir.glob("#{language.source}/*.ssi").sort
+ end
+ def all
+ Dir.glob("#{language.source}/*{.ssm,.sst,.ssi}").sort
+ end
+ self
+end
+def po4a_cfg_file
+ File.open("#{Dir.pwd}/#{filename.po4a_cfg}",'w')
+end
+def po4a
+ def configure #po4a_cfg
+ po4a_cfg_arr=[]
+ po4a_cfg_arr << "[po4a_langs] #{language.translations_available_str}"
+ po4a_cfg_arr << "[po4a_paths] #{dir.pot}/$master.pot $lang:#{dir.po}/$lang/$master.po"
+ files_src.ssm.each do |file_src|
+ file_src_fn=file_src.gsub(/#{language.source}\//,'')
+ po4a_cfg_arr << "[type: text] #{file_src} $lang:$lang/#{file_src_fn}"
+ end
+ files_src.sst.each do |file_src|
+ file_src_fn=file_src.gsub(/#{language.source}\//,'')
+ po4a_cfg_arr << "[type: text] #{file_src} $lang:$lang/#{file_src_fn}"
+ end
+ files_src.ssi.each do |file_src|
+ file_src_fn=file_src.gsub(/#{language.source}\//,'')
+ po4a_cfg_arr << "[type: text] #{file_src} $lang:$lang/#{file_src_fn}"
+ end
+ file=po4a_cfg_file
+ po4a_cfg_arr.each do |txt|
+ puts txt
+ file << txt << "\n"
+ end
+ file.close
+ system("po4a --keep 0 --no-backups --package-name sisu-manual #{po4a_flags.normal} #{filename.po4a_cfg}")
+ end
+ self
+end
+def project
+ dir_mk(dir.pot)
+ language.translations_available.each do |lang_dir|
+ dir_lang="#{Dir.pwd}/#{dir.po}/#{lang_dir}"
+ dir_mk(dir_lang)
+ end
+ po4a.configure
+end
+def clean
+ #rm -rf ../build
+ FileUtils.rm_f Dir.glob("#{dir.po}/*/*.po~")
+end
+def distclean
+ FileUtils::rm_f(filename.po4a_cfg)
+ FileUtils::rm_r(language.translations_available,:force => true)
+end
+
+#% task lists
+desc "runs make (see its description below)"
+task :default => [:make]
+desc "assist with having sisu markup files managed by po4a
+ create configuration files, and language directories and
+ populate them with po4a pot & po files for translation and
+ from those (as translated) create translated sisu markup
+ .ssm .sst & .ssi files in corresponding language sub-directories"
+task :make => [:notice_make_,:build_]
+desc "help"
+task :help => [:project_help_,:tasks_]
+desc "clean temporary files"
+task :clean => [:notice_clean_,:clean_]
+desc "removes auto-generated files under po4a management
+ including translated .ssm .sst & .ssi files,
+ that are created from po4a pot and po files"
+task :distclean => [:notice_distclean_,:distclean_]
+desc "runs 'distclean' and 'make' (see their descriptions above)"
+task :rebuild => [:notice_rebuild_,:distclean_,:build_]
+if File.directory?(dir.pot) \
+and File.directory?(dir.po)
+ #desc ""
+ task :clean! => [:clean_]
+ task :distclean! => [:distclean_]
+ task :rebuild! => [:distclean_,:build_]
+ task :make! => [:build_]
+else
+ task :make! => [:build_]
+end
+
+#% task actions
+task :project_help_ do
+ notice.project_help
+end
+task :tasks_ do
+ tasks
+end
+task :build_ do
+ project
+end
+task :clean_ do
+ clean
+end
+task :distclean_ do
+ distclean
+end
+task :notice_default_ do
+ notice.default
+end
+task :notice_make_ do
+ notice.default(:make)
+end
+task :notice_clean_ do
+ notice.default(:clean)
+end
+task :notice_distclean_ do
+ notice.default(:distclean)
+end
+task :notice_rebuild_ do
+ notice.default(:rebuild)
+end
+__END__
diff --git a/data/doc/sisu/markup-samples/manual/_sisu/image/GnuDebianLinuxRubyBetterWay.png b/data/doc/sisu/markup-samples/manual/_sisu/image/GnuDebianLinuxRubyBetterWay.png
new file mode 100644
index 00000000..ce5b8830
Binary files /dev/null and b/data/doc/sisu/markup-samples/manual/_sisu/image/GnuDebianLinuxRubyBetterWay.png differ
diff --git a/data/doc/sisu/markup-samples/manual/_sisu/image/ruby_logo.png b/data/doc/sisu/markup-samples/manual/_sisu/image/ruby_logo.png
new file mode 100644
index 00000000..829e2458
Binary files /dev/null and b/data/doc/sisu/markup-samples/manual/_sisu/image/ruby_logo.png differ
diff --git a/data/doc/sisu/markup-samples/manual/_sisu/image/sisu.png b/data/doc/sisu/markup-samples/manual/_sisu/image/sisu.png
new file mode 100644
index 00000000..b449fa6b
Binary files /dev/null and b/data/doc/sisu/markup-samples/manual/_sisu/image/sisu.png differ
diff --git a/data/doc/sisu/markup-samples/manual/_sisu/image/tux.png b/data/doc/sisu/markup-samples/manual/_sisu/image/tux.png
new file mode 100644
index 00000000..15fd152b
Binary files /dev/null and b/data/doc/sisu/markup-samples/manual/_sisu/image/tux.png differ
diff --git a/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_fn.yml b/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_fn.yml
new file mode 100644
index 00000000..f12e3144
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_fn.yml
@@ -0,0 +1,137 @@
+# Name: SiSU - Simple information Structuring Universe
+# Author: ralph@amissah.com
+# Description: Site wide environment defaults set here
+# system environment info / resource configuration file, for sisu
+# License: GPL v3 or later
+# site environment configuration file
+# this file should be configured and live in
+# /etc/sisu #per environment settings, overridden by:
+# ~/.sisu #per user settings, overridden by:
+# ./_sisu #per local markup directory settings
+#% #image source directory, main path and subdirectories
+#image:
+# path: 'sisu_working'
+# public: '_sisu/image'
+# #all: 'image'
+#% presentation/web directory, main path and subdirectories (most subdirectories are created automatically based on markup directory name)
+#webserv:
+# url_root: 'http://www.your.url' #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
+# images: '_sisu/image'
+# man: 'man'
+# cgi: '/usr/local/lib/sisu-cgi'
+# feed: 'feed'
+# sqlite: 'sisu/sqlite'
+# webrick_url: true
+#show_output_on: 'filesystem' #for -v and -u url information, alternatives: 'filesystem','webserver','remote_webserver','local:8111','localhost','localhost:8080','webrick','path'
+#show_output_on: 'local:8111'
+#webserv_cgi:
+# host: localhost
+# base_path: ~
+# port: '8081'
+# user: ~
+# file_links: webserv
+
+show_output_on: 'filesystem_url'
+#texinfo display output
+#texinfo:
+# stub: 'texinfo'
+
+##% processing directories, main path and subdirectories (appended to $HOME), using defaults set in sysenv
+#processing:
+# path: 'sisu_processing'
+# metaverse: 'metaverse'
+# tune: 'tune'
+# latex: 'tex'
+# texinfo: 'texinfo'
+# concord_max: 400000
+
+#% flag - set (non-default) processing flag shortcuts -1, -2 etc. (here adding colour and verbosity as default)
+flag:
+ color: true # making colour default -c is toggle, and will now toggle colour off
+# default: '-NQdhewpotbxXyYv' # includes verbose; -m would in any event be run by default
+# i: '-NQdhewpoty' # -m run by default
+# ii: '-NQdhewpotbxXy' # -m run by default
+# iii: '-NQdhewpotbxXyY' # -m run by default
+# iv: '-NQhewpotbxXYDy --update' # -m run by default
+# v: '-NQhewpotbxXYDyv --update' # includes verbose; -m run by default
+
+#% papersize, (LaTeX/pdf) available values: A4, US_letter, book_b5, book_a5, US_legal
+default:
+ papersize: 'a4,letter'
+ #language: 'en'
+ #texpdf_font: 'Liberation Sans' # 'Liberation Sans' 'Liberation Serif'
+ #texpdf_font_mono: 'Liberation Mono' #'Inconsolata'
+ #text_wrap: 78
+ #emphasis: 'bold' #make *{emphasis}* 'bold', 'italics' or 'underscore', default if not configured is 'bold'
+ #digest: 'sha' #sha is sha256, default is md5
+ #language: 'English'
+ #emphasis: 'italics'
+
+#% settings used by ssh scp
+#remote:
+# -
+# user: '[usrname]'
+# host: '[remote.hostname]'
+# path: '.' #no trailing slash eg 'sisu/www'
+# -
+# user: '[usrname]'
+# host: '[remote.hostname]'
+# path: '.' #no trailing slash eg 'sisu/www'
+
+#% webrick information
+#webrick:
+# port: '8081'
+
+#sql database info, postgresql and sqlite
+db:
+ postgresql:
+ port: '5432' # '5432'
+ #host: # '[if not localhost, provide host tcp/ip address or domain name]''
+ #user: # '[(if different from user) provide username]'
+ #password: # '[password if required]'
+# sqlite:
+# path: ~ # './sisu_sqlite.db'
+# port: "**"
+
+#% output_dir_structure_by: language (language_and_filetype); filetype; or filename (original v1 & v2)
+output_dir_structure_by: filename
+#% lingual: 'multi' | 'mono' (multi default)
+#lingual: mono
+#% language_default: lng_lst: %w[am bg bn br ca cs cy da de el en eo es et eu fi fr ga gl he hi hr hy ia is it ja ko la lo lt lv ml mr nl nn no oc pl pt pt_BR ro ru sa se sk sl sq sr sv ta te th tk tr uk ur us vi zh] ('en' default)
+#language_default: 'en'
+
+permission_set:
+ zap: true
+ css_modify: true
+ remote_base_site: true
+
+program_set:
+ rmagick: true
+# wc: true
+# editor: true
+# postgresql: true
+# sqlite: true
+# tidy: true
+# rexml: true
+# pdflatex: true
+
+#program_select:
+# editor: 'vim'
+# pdf_viewer: 'evince'
+# web_browser: 'iceweasel'
+# console_web_browser: 'links2' #'elinks' #'w3m' #'lynx' #'links'
+# odf_viewer: 'lowriter' #'oowriter' #'abiword'
+# xml_viewer: 'xml-viewer'
+# epub_viewer: 'ebook-viewer' #'calibre' #'fbreader' #'okular'
+# info_viewer: 'pinfo -f'
+# man: 'man' #'groff -man -Tascii' # 'nroff -man'
+
+#search:
+# sisu:
+# flag: true
+## action: http://localhost:8081/cgi-bin/sisu_pgsql.cgi
+# action: http://search.sisudoc.org
+# db: sisu
+# title: sample search form
+#promo: sisu_search_libre, sisu_icon, sisu, open_society, fsf, ruby
diff --git a/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_fn_monolingual.yml b/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_fn_monolingual.yml
new file mode 100644
index 00000000..b3c49ca1
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_fn_monolingual.yml
@@ -0,0 +1,137 @@
+# Name: SiSU - Simple information Structuring Universe
+# Author: ralph@amissah.com
+# Description: Site wide environment defaults set here
+# system environment info / resource configuration file, for sisu
+# License: GPL v3 or later
+# site environment configuration file
+# this file should be configured and live in
+# /etc/sisu #per environment settings, overridden by:
+# ~/.sisu #per user settings, overridden by:
+# ./_sisu #per local markup directory settings
+#% #image source directory, main path and subdirectories
+#image:
+# path: 'sisu_working'
+# public: '_sisu/image'
+# #all: 'image'
+#% presentation/web directory, main path and subdirectories (most subdirectories are created automatically based on markup directory name)
+#webserv:
+# url_root: 'http://www.your.url' #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
+# images: '_sisu/image'
+# man: 'man'
+# cgi: '/usr/local/lib/sisu-cgi'
+# feed: 'feed'
+# sqlite: 'sisu/sqlite'
+# webrick_url: true
+#show_output_on: 'filesystem' #for -v and -u url information, alternatives: 'filesystem','webserver','remote_webserver','local:8111','localhost','localhost:8080','webrick','path'
+#show_output_on: 'local:8111'
+#webserv_cgi:
+# host: localhost
+# base_path: ~
+# port: '8081'
+# user: ~
+# file_links: webserv
+
+show_output_on: 'filesystem_url'
+#texinfo display output
+#texinfo:
+# stub: 'texinfo'
+
+##% processing directories, main path and subdirectories (appended to $HOME), using defaults set in sysenv
+#processing:
+# path: 'sisu_processing'
+# metaverse: 'metaverse'
+# tune: 'tune'
+# latex: 'tex'
+# texinfo: 'texinfo'
+# concord_max: 400000
+
+#% flag - set (non-default) processing flag shortcuts -1, -2 etc. (here adding colour and verbosity as default)
+flag:
+ color: true # making colour default -c is toggle, and will now toggle colour off
+# default: '-NQdhewpotbxXyYv' # includes verbose; -m would in any event be run by default
+# i: '-NQdhewpoty' # -m run by default
+# ii: '-NQdhewpotbxXy' # -m run by default
+# iii: '-NQdhewpotbxXyY' # -m run by default
+# iv: '-NQhewpotbxXYDy --update' # -m run by default
+# v: '-NQhewpotbxXYDyv --update' # includes verbose; -m run by default
+
+#% papersize, (LaTeX/pdf) available values: A4, US_letter, book_b5, book_a5, US_legal
+default:
+ papersize: 'a4,letter'
+ #language: 'en'
+ #texpdf_font: 'Liberation Sans' # 'Liberation Sans' 'Liberation Serif'
+ #texpdf_font_mono: 'Liberation Mono' #'Inconsolata'
+ #text_wrap: 78
+ #emphasis: 'bold' #make *{emphasis}* 'bold', 'italics' or 'underscore', default if not configured is 'bold'
+ #digest: 'sha' #sha is sha256, default is md5
+ #language: 'English'
+ #emphasis: 'italics'
+
+#% settings used by ssh scp
+#remote:
+# -
+# user: '[usrname]'
+# host: '[remote.hostname]'
+# path: '.' #no trailing slash eg 'sisu/www'
+# -
+# user: '[usrname]'
+# host: '[remote.hostname]'
+# path: '.' #no trailing slash eg 'sisu/www'
+
+#% webrick information
+#webrick:
+# port: '8081'
+
+#sql database info, postgresql and sqlite
+db:
+ postgresql:
+ port: '5432' # '5432'
+ #host: # '[if not localhost, provide host tcp/ip address or domain name]''
+ #user: # '[(if different from user) provide username]'
+ #password: # '[password if required]'
+# sqlite:
+# path: ~ # './sisu_sqlite.db'
+# port: "**"
+
+#% output_dir_structure_by: language (language_and_filetype); filetype; or filename (original v1 & v2)
+output_dir_structure_by: filename
+#% lingual: 'multi' | 'mono' (multi default)
+lingual: mono
+#% language_default: lng_lst: %w[am bg bn br ca cs cy da de el en eo es et eu fi fr ga gl he hi hr hy ia is it ja ko la lo lt lv ml mr nl nn no oc pl pt pt_BR ro ru sa se sk sl sq sr sv ta te th tk tr uk ur us vi zh] ('en' default)
+#language_default: 'en'
+
+permission_set:
+ zap: true
+ css_modify: true
+ remote_base_site: true
+
+program_set:
+ rmagick: true
+# wc: true
+# editor: true
+# postgresql: true
+# sqlite: true
+# tidy: true
+# rexml: true
+# pdflatex: true
+
+#program_select:
+# editor: 'vim'
+# pdf_viewer: 'evince'
+# web_browser: 'iceweasel'
+# console_web_browser: 'links2' #'elinks' #'w3m' #'lynx' #'links'
+# odf_viewer: 'lowriter' #'oowriter' #'abiword'
+# xml_viewer: 'xml-viewer'
+# epub_viewer: 'ebook-viewer' #'calibre' #'fbreader' #'okular'
+# info_viewer: 'pinfo -f'
+# man: 'man' #'groff -man -Tascii' # 'nroff -man'
+
+#search:
+# sisu:
+# flag: true
+## action: http://localhost:8081/cgi-bin/sisu_pgsql.cgi
+# action: http://search.sisudoc.org
+# db: sisu
+# title: sample search form
+#promo: sisu_search_libre, sisu_icon, sisu, open_society, fsf, ruby
diff --git a/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_ft.yml b/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_ft.yml
new file mode 100644
index 00000000..71faa3e0
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_ft.yml
@@ -0,0 +1,137 @@
+# Name: SiSU - Simple information Structuring Universe
+# Author: ralph@amissah.com
+# Description: Site wide environment defaults set here
+# system environment info / resource configuration file, for sisu
+# License: GPL v3 or later
+# site environment configuration file
+# this file should be configured and live in
+# /etc/sisu #per environment settings, overridden by:
+# ~/.sisu #per user settings, overridden by:
+# ./_sisu #per local markup directory settings
+#% #image source directory, main path and subdirectories
+#image:
+# path: 'sisu_working'
+# public: '_sisu/image'
+# #all: 'image'
+#% presentation/web directory, main path and subdirectories (most subdirectories are created automatically based on markup directory name)
+#webserv:
+# url_root: 'http://www.your.url' #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
+# images: '_sisu/image'
+# man: 'man'
+# cgi: '/usr/local/lib/sisu-cgi'
+# feed: 'feed'
+# sqlite: 'sisu/sqlite'
+# webrick_url: true
+#show_output_on: 'filesystem' #for -v and -u url information, alternatives: 'filesystem','webserver','remote_webserver','local:8111','localhost','localhost:8080','webrick','path'
+#show_output_on: 'local:8111'
+#webserv_cgi:
+# host: localhost
+# base_path: ~
+# port: '8081'
+# user: ~
+# file_links: webserv
+
+show_output_on: 'filesystem_url'
+#texinfo display output
+#texinfo:
+# stub: 'texinfo'
+
+##% processing directories, main path and subdirectories (appended to $HOME), using defaults set in sysenv
+#processing:
+# path: 'sisu_processing'
+# metaverse: 'metaverse'
+# tune: 'tune'
+# latex: 'tex'
+# texinfo: 'texinfo'
+# concord_max: 400000
+
+#% flag - set (non-default) processing flag shortcuts -1, -2 etc. (here adding colour and verbosity as default)
+flag:
+ color: true # making colour default -c is toggle, and will now toggle colour off
+# default: '-NQdhewpotbxXyYv' # includes verbose; -m would in any event be run by default
+# i: '-NQdhewpoty' # -m run by default
+# ii: '-NQdhewpotbxXy' # -m run by default
+# iii: '-NQdhewpotbxXyY' # -m run by default
+# iv: '-NQhewpotbxXYDy --update' # -m run by default
+# v: '-NQhewpotbxXYDyv --update' # includes verbose; -m run by default
+
+#% papersize, (LaTeX/pdf) available values: A4, US_letter, book_b5, book_a5, US_legal
+default:
+ papersize: 'a4,letter'
+ #language: 'en'
+ #texpdf_font: 'Liberation Sans' # 'Liberation Sans' 'Liberation Serif'
+ #texpdf_font_mono: 'Liberation Mono' #'Inconsolata'
+ #text_wrap: 78
+ #emphasis: 'bold' #make *{emphasis}* 'bold', 'italics' or 'underscore', default if not configured is 'bold'
+ #digest: 'sha' #sha is sha256, default is md5
+ #language: 'English'
+ #emphasis: 'italics'
+
+#% settings used by ssh scp
+#remote:
+# -
+# user: '[usrname]'
+# host: '[remote.hostname]'
+# path: '.' #no trailing slash eg 'sisu/www'
+# -
+# user: '[usrname]'
+# host: '[remote.hostname]'
+# path: '.' #no trailing slash eg 'sisu/www'
+
+#% webrick information
+#webrick:
+# port: '8081'
+
+#sql database info, postgresql and sqlite
+db:
+ postgresql:
+ port: '5432' # '5432'
+ #host: # '[if not localhost, provide host tcp/ip address or domain name]''
+ #user: # '[(if different from user) provide username]'
+ #password: # '[password if required]'
+# sqlite:
+# path: ~ # './sisu_sqlite.db'
+# port: "**"
+
+#% output_dir_structure_by: language (language_and_filetype); filetype; or filename (original v1 & v2)
+output_dir_structure_by: filetype
+#% lingual: 'multi' | 'mono' (multi default)
+#lingual: mono
+#% language_default: lng_lst: %w[am bg bn br ca cs cy da de el en eo es et eu fi fr ga gl he hi hr hy ia is it ja ko la lo lt lv ml mr nl nn no oc pl pt pt_BR ro ru sa se sk sl sq sr sv ta te th tk tr uk ur us vi zh] ('en' default)
+#language_default: 'en'
+
+permission_set:
+ zap: true
+ css_modify: true
+ remote_base_site: true
+
+program_set:
+ rmagick: true
+# wc: true
+# editor: true
+# postgresql: true
+# sqlite: true
+# tidy: true
+# rexml: true
+# pdflatex: true
+
+#program_select:
+# editor: 'vim'
+# pdf_viewer: 'evince'
+# web_browser: 'iceweasel'
+# console_web_browser: 'links2' #'elinks' #'w3m' #'lynx' #'links'
+# odf_viewer: 'lowriter' #'oowriter' #'abiword'
+# xml_viewer: 'xml-viewer'
+# epub_viewer: 'ebook-viewer' #'calibre' #'fbreader' #'okular'
+# info_viewer: 'pinfo -f'
+# man: 'man' #'groff -man -Tascii' # 'nroff -man'
+
+#search:
+# sisu:
+# flag: true
+## action: http://localhost:8081/cgi-bin/sisu_pgsql.cgi
+# action: http://search.sisudoc.org
+# db: sisu
+# title: sample search form
+#promo: sisu_search_libre, sisu_icon, sisu, open_society, fsf, ruby
diff --git a/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_ft_monolingual.yml b/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_ft_monolingual.yml
new file mode 100644
index 00000000..adf144d5
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_ft_monolingual.yml
@@ -0,0 +1,137 @@
+# Name: SiSU - Simple information Structuring Universe
+# Author: ralph@amissah.com
+# Description: Site wide environment defaults set here
+# system environment info / resource configuration file, for sisu
+# License: GPL v3 or later
+# site environment configuration file
+# this file should be configured and live in
+# /etc/sisu #per environment settings, overridden by:
+# ~/.sisu #per user settings, overridden by:
+# ./_sisu #per local markup directory settings
+#% #image source directory, main path and subdirectories
+#image:
+# path: 'sisu_working'
+# public: '_sisu/image'
+# #all: 'image'
+#% presentation/web directory, main path and subdirectories (most subdirectories are created automatically based on markup directory name)
+#webserv:
+# url_root: 'http://www.your.url' #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
+# images: '_sisu/image'
+# man: 'man'
+# cgi: '/usr/local/lib/sisu-cgi'
+# feed: 'feed'
+# sqlite: 'sisu/sqlite'
+# webrick_url: true
+#show_output_on: 'filesystem' #for -v and -u url information, alternatives: 'filesystem','webserver','remote_webserver','local:8111','localhost','localhost:8080','webrick','path'
+#show_output_on: 'local:8111'
+#webserv_cgi:
+# host: localhost
+# base_path: ~
+# port: '8081'
+# user: ~
+# file_links: webserv
+
+show_output_on: 'filesystem_url'
+#texinfo display output
+#texinfo:
+# stub: 'texinfo'
+
+##% processing directories, main path and subdirectories (appended to $HOME), using defaults set in sysenv
+#processing:
+# path: 'sisu_processing'
+# metaverse: 'metaverse'
+# tune: 'tune'
+# latex: 'tex'
+# texinfo: 'texinfo'
+# concord_max: 400000
+
+#% flag - set (non-default) processing flag shortcuts -1, -2 etc. (here adding colour and verbosity as default)
+flag:
+ color: true # making colour default -c is toggle, and will now toggle colour off
+# default: '-NQdhewpotbxXyYv' # includes verbose; -m would in any event be run by default
+# i: '-NQdhewpoty' # -m run by default
+# ii: '-NQdhewpotbxXy' # -m run by default
+# iii: '-NQdhewpotbxXyY' # -m run by default
+# iv: '-NQhewpotbxXYDy --update' # -m run by default
+# v: '-NQhewpotbxXYDyv --update' # includes verbose; -m run by default
+
+#% papersize, (LaTeX/pdf) available values: A4, US_letter, book_b5, book_a5, US_legal
+default:
+ papersize: 'a4,letter'
+ #language: 'en'
+ #texpdf_font: 'Liberation Sans' # 'Liberation Sans' 'Liberation Serif'
+ #texpdf_font_mono: 'Liberation Mono' #'Inconsolata'
+ #text_wrap: 78
+ #emphasis: 'bold' #make *{emphasis}* 'bold', 'italics' or 'underscore', default if not configured is 'bold'
+ #digest: 'sha' #sha is sha256, default is md5
+ #language: 'English'
+ #emphasis: 'italics'
+
+#% settings used by ssh scp
+#remote:
+# -
+# user: '[usrname]'
+# host: '[remote.hostname]'
+# path: '.' #no trailing slash eg 'sisu/www'
+# -
+# user: '[usrname]'
+# host: '[remote.hostname]'
+# path: '.' #no trailing slash eg 'sisu/www'
+
+#% webrick information
+#webrick:
+# port: '8081'
+
+#sql database info, postgresql and sqlite
+db:
+ postgresql:
+ port: '5432' # '5432'
+ #host: # '[if not localhost, provide host tcp/ip address or domain name]''
+ #user: # '[(if different from user) provide username]'
+ #password: # '[password if required]'
+# sqlite:
+# path: ~ # './sisu_sqlite.db'
+# port: "**"
+
+#% output_dir_structure_by: language (language_and_filetype); filetype; or filename (original v1 & v2)
+output_dir_structure_by: filetype
+#% lingual: 'multi' | 'mono' (multi default)
+lingual: mono
+#% language_default: lng_lst: %w[am bg bn br ca cs cy da de el en eo es et eu fi fr ga gl he hi hr hy ia is it ja ko la lo lt lv ml mr nl nn no oc pl pt pt_BR ro ru sa se sk sl sq sr sv ta te th tk tr uk ur us vi zh] ('en' default)
+#language_default: 'en'
+
+permission_set:
+ zap: true
+ css_modify: true
+ remote_base_site: true
+
+program_set:
+ rmagick: true
+# wc: true
+# editor: true
+# postgresql: true
+# sqlite: true
+# tidy: true
+# rexml: true
+# pdflatex: true
+
+#program_select:
+# editor: 'vim'
+# pdf_viewer: 'evince'
+# web_browser: 'iceweasel'
+# console_web_browser: 'links2' #'elinks' #'w3m' #'lynx' #'links'
+# odf_viewer: 'lowriter' #'oowriter' #'abiword'
+# xml_viewer: 'xml-viewer'
+# epub_viewer: 'ebook-viewer' #'calibre' #'fbreader' #'okular'
+# info_viewer: 'pinfo -f'
+# man: 'man' #'groff -man -Tascii' # 'nroff -man'
+
+#search:
+# sisu:
+# flag: true
+## action: http://localhost:8081/cgi-bin/sisu_pgsql.cgi
+# action: http://search.sisudoc.org
+# db: sisu
+# title: sample search form
+#promo: sisu_search_libre, sisu_icon, sisu, open_society, fsf, ruby
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
new file mode 100644
index 00000000..ca1cf424
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/_sisu/rc/sisurc_by_lng.yml
@@ -0,0 +1,135 @@
+# Name: SiSU - Simple information Structuring Universe
+# Author: ralph@amissah.com
+# Description: Site wide environment defaults set here
+# system environment info / resource configuration file, for sisu
+# License: GPL v3 or later
+# site environment configuration file
+# this file should be configured and live in
+# /etc/sisu #per environment settings, overridden by:
+# ~/.sisu #per user settings, overridden by:
+# ./_sisu #per local markup directory settings
+#% #image source directory, main path and subdirectories
+#image:
+# path: 'sisu_working'
+# public: '_sisu/image'
+# #all: 'image'
+#% presentation/web directory, main path and subdirectories (most subdirectories are created automatically based on markup directory name)
+#webserv:
+# url_root: 'http://www.your.url' #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
+# images: '_sisu/image'
+# man: 'man'
+# cgi: '/usr/local/lib/sisu-cgi'
+# feed: 'feed'
+# sqlite: 'sisu/sqlite'
+# webrick_url: true
+#show_output_on: 'filesystem' #for -v and -u url information, alternatives: 'filesystem','webserver','remote_webserver','local:8111','localhost','localhost:8080','webrick','path'
+#show_output_on: 'local:8111'
+#webserv_cgi:
+# host: localhost
+# base_path: ~
+# port: '8081'
+# user: ~
+# file_links: webserv
+
+show_output_on: 'filesystem_url'
+#texinfo display output
+#texinfo:
+# stub: 'texinfo'
+
+##% processing directories, main path and subdirectories (appended to $HOME), using defaults set in sysenv
+#processing:
+# path: 'sisu_processing'
+# metaverse: 'metaverse'
+# tune: 'tune'
+# latex: 'tex'
+# texinfo: 'texinfo'
+# concord_max: 400000
+
+#% flag - set (non-default) processing flag shortcuts -1, -2 etc. (here adding colour and verbosity as default)
+flag:
+ color: true # making colour default -c is toggle, and will now toggle colour off
+# default: '-NQdhewpotbxXyYv' # includes verbose; -m would in any event be run by default
+# i: '-NQdhewpoty' # -m run by default
+# ii: '-NQdhewpotbxXy' # -m run by default
+# iii: '-NQdhewpotbxXyY' # -m run by default
+# iv: '-NQhewpotbxXYDy --update' # -m run by default
+# v: '-NQhewpotbxXYDyv --update' # includes verbose; -m run by default
+
+#% papersize, (LaTeX/pdf) available values: A4, US_letter, book_b5, book_a5, US_legal
+default:
+ papersize: 'a4,letter'
+ #language: 'en'
+ #texpdf_font: 'Liberation Sans' # 'Liberation Sans' 'Liberation Serif'
+ #texpdf_font_mono: 'Liberation Mono' #'Inconsolata'
+ #text_wrap: 78
+ #emphasis: 'bold' #make *{emphasis}* 'bold', 'italics' or 'underscore', default if not configured is 'bold'
+ #digest: 'sha' #sha is sha256, default is md5
+ #language: 'English'
+ #emphasis: 'italics'
+
+#% settings used by ssh scp
+#remote:
+# -
+# user: '[usrname]'
+# host: '[remote.hostname]'
+# path: '.' #no trailing slash eg 'sisu/www'
+# -
+# user: '[usrname]'
+# host: '[remote.hostname]'
+# path: '.' #no trailing slash eg 'sisu/www'
+
+#% webrick information
+#webrick:
+# port: '8081'
+
+#sql database info, postgresql and sqlite
+db:
+ postgresql:
+ port: '5432' # '5432'
+ #host: # '[if not localhost, provide host tcp/ip address or domain name]''
+ #user: # '[(if different from user) provide username]'
+ #password: # '[password if required]'
+# sqlite:
+# path: ~ # './sisu_sqlite.db'
+# port: "**"
+
+#% output_dir_structure_by: language (language_and_filetype); filetype; or filename (original v1 & v2)
+output_dir_structure_by: language
+#% language_default: lng_lst: %w[am bg bn br ca cs cy da de el en eo es et eu fi fr ga gl he hi hr hy ia is it ja ko la lo lt lv ml mr nl nn no oc pl pt pt_BR ro ru sa se sk sl sq sr sv ta te th tk tr uk ur us vi zh] ('en' default)
+#language_default: 'en'
+
+permission_set:
+ zap: true
+ css_modify: true
+ remote_base_site: true
+
+program_set:
+ rmagick: true
+# wc: true
+# editor: true
+# postgresql: true
+# sqlite: true
+# tidy: true
+# rexml: true
+# pdflatex: true
+
+#program_select:
+# editor: 'vim'
+# pdf_viewer: 'evince'
+# web_browser: 'iceweasel'
+# console_web_browser: 'links2' #'elinks' #'w3m' #'lynx' #'links'
+# odf_viewer: 'lowriter' #'oowriter' #'abiword'
+# xml_viewer: 'xml-viewer'
+# epub_viewer: 'ebook-viewer' #'calibre' #'fbreader' #'okular'
+# info_viewer: 'pinfo -f'
+# man: 'man' #'groff -man -Tascii' # 'nroff -man'
+
+#search:
+# sisu:
+# flag: true
+## action: http://localhost:8081/cgi-bin/sisu_pgsql.cgi
+# action: http://search.sisudoc.org
+# db: sisu
+# title: sample search form
+#promo: sisu_search_libre, sisu_icon, sisu, open_society, fsf, ruby
diff --git a/data/doc/sisu/markup-samples/manual/_sisu/sisu_document_make b/data/doc/sisu/markup-samples/manual/_sisu/sisu_document_make
new file mode 100644
index 00000000..72706d10
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/_sisu/sisu_document_make
@@ -0,0 +1,20 @@
+@make:
+ :num_top: 1
+ :breaks: new=C; break=1
+ :bold: /Debian|Ruby|SiSU/
+ :italics: /Linux|GPL|GPLv3|LaTeX|PostgreSQL|SQLite|SQL|Vim|ascii|plaintext|UTF-?8|HTML|XHTML|XML|EPUB|OpenDocument|ODF|ODT|PDF|pgSQL|TeXinfo|YAML|YML|OCN|object citation system|object citation numbering|granular search|Dublin Core/
+ :substitute: /${debian_stable}/,'*{Wheezy}*' /${debian_testing}/,'*{Jessie}*'
+ :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
+ :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
+
+@links:
+ { SiSU Homepage }http://www.sisudoc.org/
+ { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/
+ { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html
+ { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html
+ { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html
+ { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary
+ { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/
+ { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html
+ { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org
+ { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
diff --git a/data/doc/sisu/markup-samples/manual/_sisu/v5/sisurc.yml b/data/doc/sisu/markup-samples/manual/_sisu/v5/sisurc.yml
new file mode 120000
index 00000000..e492f789
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/_sisu/v5/sisurc.yml
@@ -0,0 +1 @@
+../rc/sisurc_by_lng.yml
\ No newline at end of file
diff --git a/data/doc/sisu/markup-samples/manual/_sisu/v6/sisurc.yml b/data/doc/sisu/markup-samples/manual/_sisu/v6/sisurc.yml
new file mode 120000
index 00000000..e492f789
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/_sisu/v6/sisurc.yml
@@ -0,0 +1 @@
+../rc/sisurc_by_lng.yml
\ No newline at end of file
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu.ssm b/data/doc/sisu/markup-samples/manual/en/sisu.ssm
new file mode 100644
index 00000000..79703fef
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu.ssm
@@ -0,0 +1,73 @@
+% SiSU master 4.0
+
+@title: SiSU
+ :subtitle: Manual
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2008-05-22
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2012
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: SiSU:manual;electronic documents:SiSU:manual
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+@make:
+ :manpage: name=sisu - documents: markup, structuring, publishing in multiple standard formats, and search; synopsis=sisu [-short-options|--long-options] [filename/wildcard] . sisu [-abCcDdeFGghIikLMmNnoPpQqRrSsTtUuVvWwXxYyZ_0-9] [filename/wildcard] . sisu --txt --html --epub --odt --pdf --wordmap --sqlite --manpage --texinfo --sisupod --source --qrcode [filename/wildcard] . sisu [-Ddcv] [instruction] [filename/wildcard] . sisu --pg (--createdb|update [filename/wildcard]|--dropall) . sisu [operations] . sisu [-CcFLSVvW] . sisu (--configure|--webrick|--sample-search-form)
+
+:A~ @title @creator
+
+:B~ What is SiSU?
+
+% << sisu_synopsis.ssi
+
+<< sisu_introduction.sst
+
+% :B~? SiSU Commands
+
+<< sisu_commands.sst
+
+<< sisu_help.sst
+
+% :B~? SiSU Markup
+
+<< sisu_markup.sst
+
+<< sisu_filetypes.sst
+
+% :B~? SiSU Configuration
+
+<< sisu_config.ssi
+
+<< sisu_css.ssi
+
+<< sisu_content_directories.ssi
+
+<< sisu_homepages.ssi
+
+% :B~? SiSU Output and Markup Examples
+
+<< sisu_examples.ssi
+
+<< sisu_search_intro.ssi
+
+<< sisu_sql.ssi
+
+<< sisu_postgresql.sst
+
+<< sisu_sqlite.sst
+
+<< sisu_search_cgi.ssi
+
+<< sisu_webrick.sst
+
+<< sisu_short_feature_summary.ssi
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_commands.sst b/data/doc/sisu/markup-samples/manual/en/sisu_commands.sst
new file mode 100644
index 00000000..2ca43a43
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_commands.sst
@@ -0,0 +1,497 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: Commands
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :published: 2007-09-16
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2012
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: electronic documents:SiSU:document:commands;SiSU:manual:commands;electronic documents:SiSU:manual:commands;SiSU:document:commands;SiSU:document:commands
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? SiSU Commands
+
+1~commands Commands Summary
+
+2~ Description
+
+SiSU is a document publishing system, that from a simple single marked-up document, produces multiple output formats including: plaintext, HTML, XHTML, XML, EPUB, ODT (OpenDocument (ODF) text), LaTeX, PDF, info, and SQL (PostgreSQL and SQLite), which share text object numbers ("object citation numbering") and the same document structure information. For more see: http://sisudoc.org or http://www.jus.uio.no/sisu
+
+% 2~ Summary of man page
+
+% This man page covers a number of subjects in brief, including: document processing command flags; document markup (basic markup and headers); configuration files; directory structure; skins; document naming; interactive help and other information.
+
+2~ Document Processing Command Flags
+
+!_ -a [filename/wildcard] \\
+produces plaintext with Unix linefeeds and without markup, (object numbers are omitted), has footnotes at end of each paragraph that contains them [ -A for equivalent dos (linefeed) output file] [see -e for endnotes]. (Options include: --endnotes for endnotes --footnotes for footnotes at the end of each paragraph --unix for unix linefeed (default) --msdos for msdos linefeed)
+
+!_ --ao [filename/wildcard/url] \\
+assumed for most other flags, creates new intermediate files for processing (abstract objects, document abstraction) that is used in all subsequent processing of other output. This step is assumed for most processing flags. To skip it see -n. Alias -m. (sisu v5)
+
+!_ -b [filename/wildcard] \\
+see --xhtml
+
+!_ --by-* \\
+see --output-by-*
+
+!_ -C \\
+configure/initialise shared output directory files initialize shared output directory (config files such as css and dtd files are not updated if they already exist unless modifier is used). -C --init-site configure/initialise site more extensive than -C on its own, shared output directory files/force update, existing shared output config files such as css and dtd files are updated if this modifier is used.
+
+!_ -CC \\
+see --configure
+
+!_ -c [filename/wildcard] \\
+see --color-toggle
+
+!_ --color \\
+see --color-on
+
+!_ --color-off \\
+turn off color in output to terminal
+
+!_ --color-on \\
+turn on color in output to terminal
+
+!_ --color-toggle [filename/wildcard] \\
+screen toggle ansi screen colour on or off depending on default set (unless -c flag is used: if sisurc colour default is set to 'true', output to screen will be with colour, if sisurc colour default is set to 'false' or is undefined screen output will be without colour). Alias -c
+
+!_ --configure \\
+configure/initialise shared output directory files initialize shared output directory (config files such as css and dtd files are not updated if they already exist unless modifier is used). The equivalent of: -C --init-site configure/initialise site, more extensive than -C on its own, shared output directory files/force update, existing shared output config files such as css and dtd files are updated if -CC is used.
+
+!_ --concordance [filename/wildcard] \\
+produces concordance (wordmap) a rudimentary index of all the words in a document. (Concordance files are not generated for documents of over 260,000 words unless this limit is increased in the file sisurc.yml). Alias -w
+
+!_ -D [instruction] [filename] \\
+see --pg
+
+!_ -d [--db-[database type (sqlite|pg)]] --[instruction] [filename] \\
+see --sqlite
+
+!_ --dal [filename/wildcard/url] \\
+assumed for most other flags, creates new intermediate files for processing (abstract objects, document abstraction) that is used in all subsequent processing of other output. This step is assumed for most processing flags. To skip it see -n. Renamed --ao (abstract objects) in sisu v5. Alias -m
+
+!_ --delete [filename/wildcard] \\
+see --zap
+
+!_ --docbook [filename/wildcard/url] \\
+docbook smart text (sisu v5)
+
+!_ --dump[=directory_path] [filename/wildcard] \\
+places output in directory specified, if none is specified in the current directory (pwd). Unlike using default settings HTML files have embedded css. Compare --redirect
+
+!_ -e [filename/wildcard] \\
+see --epub
+
+!_ --epub [filename/wildcard] \\
+produces an epub document, [sisu version >=2 ] (filename.epub). Alias -e
+
+!_ --exc-* \\
+exclude output feature, overrides configuration settings
+ --exc-ocn, (exclude object citation numbering, (switches off object citation numbering), affects html (seg, scroll), epub, xhtml, xml, pdf);
+ --exc-toc, (exclude table of contents, affects html (scroll), epub, pdf);
+ --exc-links-to-manifest, --exc-manifest-links, (exclude links to manifest, affects html (seg, scroll));
+ --exc-search-form, (exclude search form, affects html (seg, scroll), manifest);
+ --exc-minitoc, (exclude mini table of contents, affects html (seg), concordance, manifest);
+ --exc-manifest-minitoc, (exclude mini table of contents, affects manifest);
+ --exc-html-minitoc, (exclude mini table of contents, affects html (seg), concordance);
+ --exc-html-navigation, (exclude navigation, affects html (seg));
+ --exc-html-navigation-bar, (exclude navigation bar, affects html (seg));
+ --exc-html-search-form, (exclude search form, affects html (seg, scroll));
+ --exc-html-right-pane, (exclude right pane/column, affects html (seg, scroll));
+ --exc-html-top-band, (exclude top band, affects html (seg, scroll), concordance (minitoc forced on to provide seg navigation));
+ --exc-segsubtoc (exclude sub table of contents, affects html (seg), epub);
+see also --inc-*
+
+!_ -F [--webserv=webrick] \\
+see --sample-search-form
+
+!_ -f [optional string part of filename] \\
+see --find
+
+!_ --fictionbook [filename/wildcard/url] \\
+fictionbook smart text (sisu v5)
+
+!_ --find [optional string part of filename] \\
+without match string, glob all .sst .ssm files in directory (including language subdirectories). With match string, find files that match given string in directory (including language subdirectories). Alias -f, --glob, -G
+
+!_ -G [optional string part of filename] \\
+see --find
+
+!_ -g [filename/wildcard] \\
+see --git
+
+!_ --git [filename/wildcard] \\
+produces or updates markup source file structure in a git repo (experimental and subject to change). Alias -g
+
+!_ --glob [optional string part of filename] \\
+see --find
+
+!_ -h [filename/wildcard] \\
+see --html
+
+!_ --harvest *.ss[tm] \\
+makes two lists of sisu output based on the sisu markup documents in a directory: list of author and authors works (year and titles), and; list by topic with titles and author. Makes use of header metadata fields (author, title, date, topic_register). Can be used with maintenance (-M) and remote placement (-R) flags.
+
+!_ --help [topic] \\
+provides help on the selected topic, where topics (keywords) include: list, (com)mands, short(cuts), (mod)ifiers, (env)ironment, markup, syntax, headers, headings, endnotes, tables, example, customise, skin, (dir)ectories, path, (lang)uage, db, install, setup, (conf)igure, convert, termsheet, search, sql, features, license.
+
+!_ --html [filename/wildcard] \\
+produces html output, in two forms (i) segmented text with table of contents (toc.html and index.html) and (ii) the document in a single file (scroll.html). Alias -h
+
+!_ --html-scroll [filename/wildcard] \\
+produces html output, the document in a single file (scroll.html) only. Compare --html-seg and --html
+
+!_ --html-seg [filename/wildcard] \\
+produces html output, segmented text with table of contents (toc.html and index.html). Compare --html-scroll and --html
+
+!_ -I [filename/wildcard] \\
+see --texinfo
+
+!_ -i [filename/wildcard] \\
+see --manpage
+
+!_ --i18n-* \\
+these flags affect output by filetype and filename):
+--i18n-mono (--monolingual) output filenames without language code for default language ('en' or as set);
+--i18n-multi (--multilingual) language code provided as part of the output filename, this is the default.
+Where output is in one language only the language code may not be desired.
+see also --output-by-*
+
+!_ --inc-* \\
+include output feature, overrides configuration settings, (usually the default if none set), has precedence over --exc-* (exclude output feature). Some detail provided under --exc-*,
+see --exc-*
+
+!_ -j [filename/wildcard] \\
+copies images associated with a file for use by html, xhtml & xml outputs (automatically invoked by --dump & redirect).
+
+!_ -k \\
+see --color-off
+
+!_ --keep-processing-files [filename/wildcard/url] \\
+see --maintenance
+
+!_ -M [filename/wildcard/url] \\
+see --maintenance
+
+!_ -m [filename/wildcard/url] \\
+see --dal (document abstraction level/layer)
+
+!_ --machine [filename/wildcard/url] \\
+see --dal (document abstraction level/layer)
+
+!_ --maintenance [filename/wildcard/url] \\
+maintenance mode, interim processing files are preserved and their locations indicated. (also see -V). Aliases -M and --keep-processing-files.
+
+!_ --markdown [filename/wildcard/url] \\
+markdown smart text (sisu v5)
+
+!_ --manpage [filename/wildcard] \\
+produces man page of file, not suitable for all outputs. Alias -i
+
+!_ --monolingual \\
+see --i18n-*
+
+!_ --multilingual \\
+see --i18n-*
+
+!_ -N [filename/wildcard/url] \\
+document digest or document content certificate ( DCC ) as md5 digest tree of the document: the digest for the document, and digests for each object contained within the document (together with information on software versions that produced it) (digest.txt). -NV for verbose digest output to screen.
+
+!_ -n [filename/wildcard/url] \\
+skip the creation of intermediate processing files (document abstraction) if they already exist, this skips the equivalent of -m which is otherwise assumed by most processing flags.
+
+!_ --no-* \\
+see --exc-*
+
+!_ -o [filename/wildcard/url] \\
+see --odt
+
+!_ --odf [filename/wildcard/url] \\
+see --odt
+
+!_ --odt [filename/wildcard/url] \\
+output basic document in opendocument file format (opendocument.odt). Alias -o
+
+!_ --output-by-* \\
+select output directory structure from 3 alternatives:
+--output-by-language, (language directory (based on language code) with filetype (html, epub, pdf etc.) subdirectories);
+--output-by-filetype, (filetype directories with language code as part of filename);
+--output-by-filename, (filename directories with language code as part of filename).
+This is configurable. Alias --by-*
+
+!_ -P [language_directory/filename language_directory] \\
+see --po4a
+
+!_ -p [filename/wildcard] \\
+see --pdf
+
+!_ --papersize-(a4|a5|b5|letter|legal) \\
+in conjunction with --pdf set pdf papersize, overriding any configuration settings, to set more than one papersize repeat the option --pdf --papersize-a4 --papersize-letter. See also --papersize=*
+
+!_ --papersize=a4,a5,b5,letter,legal
+in conjunction with --pdf set pdf papersize, overriding any configuration settings, to set more than one papersize list after the equal sign with a comma separator --papersize=a4,letter. See also --papersize-*
+
+!_ --pdf [filename/wildcard] \\
+produces LaTeX pdf (portrait.pdf & landscape.pdf). Orientation and papersize may be set on the command-line. Default paper size is set in config file, or document header, or provided with additional command line parameter, e.g. --papersize-a4 preset sizes include: 'A4', U.S. 'letter' and 'legal' and book sizes 'A5' and 'B5' (system defaults to A4), and; --landscape or --portrait, so: e.g. "sisu --pdf-a4 --pdf-letter --landscape --verbose [filename/wildcard]" or "sisu --pdf --landscape --a4 --letter --verbose [filename/wildcard]". --pdf defaults to both landscape & portrait output, and a4 if no other papersizes are configured. Related options --pdf-landscape --pdf-portrait --pdf-papersize-* --pdf-papersize=[list]. Alias -p
+
+!_ --pdf-l [filename/wildcard] \\
+See --pdf-landscape
+
+!_ --pdf-landscape [filename/wildcard] \\
+sets orientation, produces LaTeX pdf landscape.pdf. Default paper size is set in config file, or document header, or provided with additional command line parameter, e.g. --papersize-a4 preset sizes include: 'A4', U.S. 'letter' and 'legal' and book sizes 'A5' and 'B5' (system defaults to A4). Related options --pdf --pdf-portrait. See also --papersize-* or --papersize=[list]. Alias --pdf-l or in conjunction with --pdf --landscape
+
+!_ --pdf-p [filename/wildcard] \\
+See --pdf-portrait
+
+!_ --pdf-portrait [filename/wildcard] \\
+sets orientation, produces LaTeX pdf portrait.pdf.pdf. Default paper size is set in config file, or document header, or provided with additional command line parameter, e.g. --papersize-a4 preset sizes include: 'A4', U.S. 'letter' and 'legal' and book sizes 'A5' and 'B5' (system defaults to A4). Related options --pdf --pdf-landscape. See also --papersize-* or --papersize=[list]. Alias --pdf-p or in conjunction with --pdf --portrait
+
+!_ --pg [instruction] [filename] \\
+database PostgreSQL ( --pgsql may be used instead) possible instructions, include: --createdb; --create; --dropall; --import [filename]; --update [filename]; --remove [filename]; see database section below. Alias -D
+
+!_ --po [language_directory/filename language_directory] \\
+see --po4a
+
+!_ --po4a [language_directory/filename language_directory] \\
+produces .pot and po files for the file in the languages specified by the language directory. SiSU markup is placed in subdirectories named with the language code, e.g. en/ fr/ es/. The sisu config file must set the output directory structure to multilingual. v3, experimental
+
+!_ -Q [filename/wildcard] \\
+see --qrcode
+
+!_ -q [filename/wildcard] \\
+see --quiet
+
+!_ --qrcode [filename/wildcard] \\
+generate QR code image of metadata (used in manifest). v3 only.
+
+!_ --quiet [filename/wildcard] \\
+quiet less output to screen.
+
+!_ -R [filename/wildcard] \\
+see --rsync
+
+!_ -r [filename/wildcard] \\
+see --scp
+
+!_ --redirect[=directory_path] [filename/wildcard] \\
+places output in subdirectory under specified directory, subdirectory uses the filename (without the suffix). If no output directory is specified places the subdirectory under the current directory (pwd). Unlike using default settings HTML files have embedded css. Compare --dump
+
+!_ --rst [filename/wildcard/url] \\
+ReST (rST restructured text) smart text (sisu v5)
+
+!_ --rsync [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 --scp. Alias -R
+
+!_ -S \\
+see --sisupod
+
+!_ -S [filename/wildcard] \\
+see --sisupod
+
+!_ -s [filename/wildcard] \\
+see --source
+
+!_ --sample-search-form [--db=(pgsql|sqlite)] [--webserv=webrick] \\
+generate examples of (naive) cgi search form for SQLite or PgSQL depends on your already having used sisu to populate an SQLite or PgSQL database, (the SQLite version scans the output directories for existing sisu_sqlite databases, so it is first necessary to create them, before generating the search form) see --sqlite & --pg and the database section below. Optional additional parameters include: url location of webserver search form and db: --webserv-search='[url]'; location of webserver output: --webserv-output='[url]'; cgi search form link name: --cgi-search-form-name='[name.cgi]'; for pgsql, database user: --db-user='[username]'. If the optional parameter --webserv=webrick is passed, the cgi examples created will be set up to use the default port set for use by the webrick server, (otherwise the port is left blank and the system setting used, usually 80). The samples are dumped in the present work directory which must be writable, (with screen instructions given that they be copied to the cgi-bin directory). Alias -F
+
+!_ --scp [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 --rsync. Alias -r
+
+!_ --sqlite --[instruction] [filename] \\
+database type set to SQLite, this produces one of two possible databases, without additional database related instructions it produces a discreet SQLite file for the document processed; with additional instructions it produces a common SQLite database of all processed documents that (come from the same document preparation directory and as a result) share the same output directory base path (possible instructions include: --createdb; --create; --dropall; --import [filename]; --update [filename]; --remove [filename]); see database section below. Alias -d
+
+!_ --sisupod \\
+produces a sisupod a zipped sisu directory of markup files including sisu markup source files and the directories local configuration file, images and skins. Note: this only includes the configuration files or skins contained in ./_sisu not those in ~/.sisu -S [filename/wildcard] option. Note: (this option is tested only with zsh). Alias -S
+
+!_ --sisupod [filename/wildcard] \\
+produces a zipped file of the prepared document specified along with associated images, by default named sisupod.zip they may alternatively be named with the filename extension .ssp This provides a quick way of gathering the relevant parts of a sisu document which can then for example be emailed. A sisupod includes sisu markup source file, (along with associated documents if a master file, or available in multilingual versions), together with related images and skin. SiSU commands can be run directly against a sisupod contained in a local directory, or provided as a url on a remote site. As there is a security issue with skins provided by other users, they are not applied unless the flag --trust or --trusted is added to the command instruction, it is recommended that file that are not your own are treated as untrusted. The directory structure of the unzipped file is understood by sisu, and sisu commands can be run within it. Note: if you wish to send multiple files, it quickly becomes more space efficient to zip the sisu markup directory, rather than the individual files for sending). See the -S option without [filename/wildcard]. Alias -S
+
+!_ --source [filename/wildcard] \\
+copies sisu markup file to output directory. Alias -s
+
+!_ -T [filename/wildcard (*.termsheet.rb)] \\
+standard form document builder, preprocessing feature
+
+!_ -t [filename/wildcard] \\
+see --txt
+
+!_ --texinfo [filename/wildcard] \\
+produces texinfo and info file, (view with pinfo). Alias -I
+
+!_ --textile [filename/wildcard/url] \\
+textile smart text (sisu v5)
+
+!_ --txt [filename/wildcard] \\
+produces plaintext with Unix linefeeds and without markup, (object numbers are omitted), has footnotes at end of each paragraph that contains them [ -A for equivalent dos (linefeed) output file] [see -e for endnotes]. (Options include: --endnotes for endnotes --footnotes for footnotes at the end of each paragraph --unix for unix linefeed (default) --msdos for msdos linefeed). Alias -t
+
+!_ --txt-asciitext [filename/wildcard] \\
+see --asciitext
+
+!_ --txt-markdown [filename/wildcard] \\
+see --markdown
+
+!_ --txt-rst [filename/wildcard] \\
+see --rst
+
+!_ --txt-textile [filename/wildcard] \\
+see --textile
+
+!_ -U [filename/wildcard] \\
+see --urls
+
+!_ -u [filename/wildcard] \\
+provides url mapping of output files for the flags requested for processing, also see -U
+
+!_ --urls [filename/wildcard] \\
+prints url output list/map for the available processing flags options and resulting files that could be requested, (can be used to get a list of processing options in relation to a file, together with information on the output that would be produced), -u provides url output mapping for those flags requested for processing. The default assumes sisu_webrick is running and provides webrick url mappings where appropriate, but these can be switched to file system paths in sisurc.yml. Alias -U
+
+!_ -V \\
+on its own, provides SiSU version and environment information (sisu --help env)
+
+!_ -V [filename/wildcard] \\
+even more verbose than the -v flag.
+
+!_ -v \\
+on its own, provides SiSU version information
+
+!_ -v [filename/wildcard] \\
+see --verbose
+
+!_ --v3 [filename/wildcard] \\
+invokes the sisu v3 document parser/generator. You may run sisu3 instead.
+
+!_ --v4 [filename/wildcard] \\
+invokes the sisu v4 document parser/generator. This is the default and is normally omitted.
+
+!_ --verbose [filename/wildcard] \\
+provides verbose output of what is being generated, where output is placed (and error messages if any), as with -u flag provides a url mapping of files created for each of the processing flag requests. Alias -v
+
+!_ -W \\
+see --webrick
+
+!_ -w [filename/wildcard] \\
+see --concordance
+
+!_ --webrick \\
+starts ruby's webrick webserver points at sisu output directories, the default port is set to 8081 and can be changed in the resource configuration files. [tip: the webrick server requires link suffixes, so html output should be created using the -h option rather than -H ; also, note -F webrick ]. Alias -W
+
+!_ --wordmap [filename/wildcard] \\
+see --concordance
+
+!_ --xhtml [filename/wildcard] \\
+produces xhtml/XML output for browser viewing (sax parsing). Alias -b
+
+!_ --xml-dom [filename/wildcard] \\
+produces XML output with deep document structure, in the nature of dom. Alias -X
+
+!_ --xml-sax [filename/wildcard] \\
+produces XML output shallow structure (sax parsing). Alias -x
+
+!_ -X [filename/wildcard] \\
+see --xml-dom
+
+!_ -x [filename/wildcard] \\
+see --xml-sax
+
+!_ -Y [filename/wildcard] \\
+produces a short sitemap entry for the document, based on html output and the sisu_manifest. --sitemaps generates/updates the sitemap index of existing sitemaps. (Experimental, [g,y,m announcement this week])
+
+!_ -y [filename/wildcard] \\
+produces an html summary of output generated (hyperlinked to content) and document specific metadata (sisu_manifest.html). This step is assumed for most processing flags.
+
+!_ -Z [filename/wildcard] \\
+see --zap
+
+!_ --zap [filename/wildcard] \\
+Zap, if used with other processing flags deletes output files of the type about to be processed, prior to processing. If -Z is used as the lone processing related flag (or in conjunction with a combination of -[mMvVq]), will remove the related document output directory. Alias -Z
+
+1~command_modifiers command line modifiers
+
+!_ --no-ocn \\
+[with --html --pdf or --epub] switches off object citation numbering. Produce output without identifying numbers in margins of html or LaTeX/pdf output.
+
+!_ --no-annotate \\
+strips output text of editor endnotes~[* square brackets ]~ denoted by asterisk or dagger/plus sign
+
+!_ --no-asterisk \\
+strips output text of editor endnotes~[* square brackets ]~ denoted by asterisk sign
+
+!_ --no-dagger \\
+strips output text of editor endnotes~[+ square brackets ]~ denoted by dagger/plus sign
+
+1~commands_database database commands
+
+!_ dbi - database interface
+
+!_ -D or --pgsql
+set for PostgreSQL
+!_ -d or --sqlite
+default set for SQLite -d is modifiable with --db=[database type (PgSQL or SQLite)]
+
+!_ --pg -v --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) [ -dv --createall SQLite equivalent] it may be necessary to run sisu -Dv --createdb initially NOTE: at the present time for PostgreSQL it may be necessary to manually create the database. The command would be 'createdb [database name]' where database name would be SiSU_[present working directory name (without path)]. Please use only alphanumerics and underscores.
+
+!_ --pg -v --import \\
+[filename/wildcard] imports data specified to PostgreSQL db (rb.dbi) [ -dv --import SQLite equivalent]
+
+!_ --pg -v --update \\
+[filename/wildcard] updates/imports specified data to PostgreSQL db (rb.dbi) [ -dv --update SQLite equivalent]
+
+!_ --pg --remove \\
+[filename/wildcard] removes specified data to PostgreSQL db (rb.dbi) [ -d --remove SQLite equivalent]
+
+!_ --pg --dropall \\
+kills data" and drops (PostgreSQL or SQLite) db, tables & indexes [ -d --dropall SQLite equivalent]
+
+The -v is for verbose output.
+
+1~command_shorcuts Shortcuts, Shorthand for multiple flags
+
+!_ --update [filename/wildcard] \\
+Checks existing file output and runs the flags required to update this output. This means that if only html and pdf output was requested on previous runs, only the -hp files will be applied, and only these will be generated this time, together with the summary. This can be very convenient, if you offer different outputs of different files, and just want to do the same again.
+
+!_ -0 to -5 [filename or wildcard] \\
+Default shorthand mappings (for v3, note that the defaults can be changed/configured in the sisurc.yml file):
+
+!_ -0 \\
+-NQhewpotbxXyYv [this is the default action run when no options are give, i.e. on 'sisu [filename]']
+
+!_ -1 \\
+-Qhewpoty
+
+!_ -2 \\
+-NQhewpotbxXy
+
+!_ -3 \\
+-NQhewpotbxXyY
+
+!_ -4 \\
+-NQhewpotbxXDyY --update
+
+!_ -5 \\
+-NQhewpotbxXDyYv --update
+
+add -v for verbose mode and -c to toggle color state, e.g. sisu -2vc [filename or wildcard]
+
+consider -u for appended url info or -v for verbose output
+
+2~ Command Line with Flags - Batch Processing
+
+In the data directory run sisu -mh filename or wildcard eg. "sisu -h cisg.sst" or "sisu -h *.{sst,ssm}" to produce html version of all documents.
+
+Running sisu (alone without any flags, filenames or wildcards) brings up the interactive help, as does any sisu command that is not recognised. Enter to escape.
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_config.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_config.ssi
new file mode 100644
index 00000000..3c29f995
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_config.ssi
@@ -0,0 +1,75 @@
+% SiSU insert 2.0
+
+@title: SiSU
+ :subtitle: Configuration
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2011-12-12
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? Configuration
+
+:B~? Configure Environment
+
+1~config Configuration
+
+2~ Configuration files
+
+3~ config.yml
+
+SiSU configration parameters are adjusted in the configuration file, which can be used to override the defaults set. This includes such things as which directory interim processing should be done in and where the generated output should be placed.
+
+The SiSU configuration file is a yaml file, which means indentation is significant.
+
+SiSU resource configuration is determined by looking at the following files if they exist:
+
+_1 ./_sisu/v4/sisurc.yml
+
+_1 ./_sisu/sisurc.yml
+
+_1 ~/.sisu/v4/sisurc.yml
+
+_1 ~/.sisu/sisurc.yml
+
+_1 /etc/sisu/v4/sisurc.yml
+
+_1 /etc/sisu/sisurc.yml
+
+The search is in the order listed, and the first one found is used.
+
+In the absence of instructions in any of these it falls back to the internal program defaults.
+
+Configuration determines the output and processing directories and the database access details.
+
+If SiSU is installed a sample sisurc.yml may be found in /etc/sisu/sisurc.yml
+
+3~ sisu_document_make
+
+Most sisu document headers relate to metadata, the exception is the @make: header which provides processing related information. The default contents of the @make header may be set by placing them in a file sisu_document_make.
+
+The search order is as for resource configuration:
+
+_1 ./_sisu/v4/sisu_document_make
+
+_1 ./_sisu/sisu_document_make
+
+_1 ~/.sisu/v4/sisu_document_make
+
+_1 ~/.sisu/sisu_document_make
+
+_1 /etc/sisu/v4/sisu_document_make
+
+_1 /etc/sisu/sisu_document_make
+
+A sample sisu_document_make can be found in the _sisu/ directory under along with the provided sisu markup samples.
+
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_content_directories.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_content_directories.ssi
new file mode 100644
index 00000000..182b176d
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_content_directories.ssi
@@ -0,0 +1,264 @@
+% SiSU insert 2.0
+
+@title: SiSU
+ :subtitle: Content Directories, Organising Content
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2007-08-28
+ :published: 2007-09-16
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? Organisation of Content
+
+:B~? Content Directories
+
+1~organising_content Organising Content - Directory Structure and Mapping
+
+SiSU v3 has new options for the source directory tree, and output directory structures of which there are 3 alternatives.
+
+2~ Document Source Directory
+
+The document source directory is the directory in which sisu processing commands are given. It contains the sisu source files (.sst .ssm .ssi), or (for sisu v3 may contain) subdirectories with language codes which contain the sisu source files, so all English files would go in subdirectory en/, French in fr/, Spanish in es/ and so on. ISO 639-1 codes are used (as varied by po4a). A list of available languages (and possible sub-directory names) can be obtained with the command "sisu --help lang" The list of languages is limited to langagues supported by XeTeX polyglosia.
+
+3~ General Directories
+
+code{
+
+./subject_name/
+
+% files stored at this level e.g. sisu_manual.sst or
+% for sisu v3 may be under language sub-directories
+% e.g.
+
+./subject_name/en
+
+./subject_name/fr
+
+./subject_name/es
+
+./subject_name/_sisu
+
+./subject_name/_sisu/css
+
+./subject_name/_sisu/image
+
+}code
+
+2~ Document Output Directory Structures
+
+3~ Output Directory Root
+
+The output directory root can be set in the sisurc.yml file. Under the root, subdirectories are made for each directory in which a document set resides. If you have a directory named poems or conventions, that directory will be created under the output directory root and the output for all documents contained in the directory of a particular name will be generated to subdirectories beneath that directory (poem or conventions). A document will be placed in a subdirectory of the same name as the document with the filetype identifier stripped (.sst .ssm)
+
+The last part of a directory path, representing the sub-directory in which a document set resides, is the directory name that will be used for the output directory. This has implications for the organisation of document collections as it could make sense to place documents of a particular subject, or type within a directory identifying them. This grouping as suggested could be by subject (sales_law, english_literature); or just as conveniently by some other classification (X University). The mapping means it is also possible to place in the same output directory documents that are for organisational purposes kept separately, for example documents on a given subject of two different institutions may be kept in two different directories of the same name, under a directory named after each institution, and these would be output to the same output directory. Skins could be associated with each institution on a directory basis and resulting documents will take on the appropriate different appearance.
+
+3~ Alternative Output Structures
+
+There are 3 possibile output structures described as being, by language, by filetype or by filename, the selection is made in sisurc.yml
+
+code{
+
+#% output_dir_structure_by: language; filetype; or filename
+output_dir_structure_by: language #(language & filetype, preferred?)
+#output_dir_structure_by: filetype
+#output_dir_structure_by: filename #(default, closest to original v1 & v2)
+
+}code
+
+3~ By Language
+
+The by language directory structure places output files
+
+The by language directory structure separates output files by language code (all files of a given language), and within the language directory by filetype.
+
+Its selection is configured in sisurc.yml
+
+output_dir_structure_by: language
+
+% works for html epub odf, pdf, sortof for info NOT for man pages
+
+code{
+
+ |-- en
+ |-- epub
+ |-- hashes
+ |-- html
+ | |-- viral_spiral.david_bollier
+ | |-- manifest
+ | |-- qrcode
+ | |-- odt
+ | |-- pdf
+ | |-- sitemaps
+ | |-- txt
+ | |-- xhtml
+ | `-- xml
+ |-- po4a
+ | `-- live-manual
+ | |-- po
+ | |-- fr
+ | `-- pot
+ `-- _sisu
+ |-- css
+ |-- image
+ |-- image_sys -> ../../_sisu/image_sys
+ `-- xml
+ |-- rnc
+ |-- rng
+ `-- xsd
+
+}code
+
+#by: language
+subject_dir/en/manifest/filename.html
+
+3~ By Filetype
+
+The by filetype directory structure separates output files by filetype, all html files in one directory pdfs in another and so on. Filenames are given a language extension.
+
+Its selection is configured in sisurc.yml
+
+output_dir_structure_by: filetype
+
+% works for html epub odf, pdf, sortof for info NOT for man pages
+
+code{
+
+ |-- epub
+ |-- hashes
+ |-- html
+ |-- viral_spiral.david_bollier
+ |-- manifest
+ |-- qrcode
+ |-- odt
+ |-- pdf
+ |-- po4a
+ |-- live-manual
+ | |-- po
+ | |-- fr
+ | `-- pot
+ |-- _sisu
+ | |-- css
+ | |-- image
+ | |-- image_sys -> ../../_sisu/image_sys
+ | `-- xml
+ | |-- rnc
+ | |-- rng
+ | `-- xsd
+ |-- sitemaps
+ |-- txt
+ |-- xhtml
+ `-- xml
+
+}code
+
+#by: filetype
+subject_dir/html/filename/manifest.en.html
+
+3~ By Filename
+
+The by filename directory structure places most output of a particular file (the different filetypes) in a common directory.
+
+Its selection is configured in sisurc.yml
+
+output_dir_structure_by: filename
+
+% works for html epub odf, pdf, sortof for info NOT for man pages
+
+code{
+
+ |-- epub
+ |-- po4a
+ |-- live-manual
+ | |-- po
+ | |-- fr
+ | `-- pot
+ |-- _sisu
+ | |-- css
+ | |-- image
+ | |-- image_sys -> ../../_sisu/image_sys
+ | `-- xml
+ | |-- rnc
+ | |-- rng
+ | `-- xsd
+ |-- sitemaps
+ |-- src
+ |-- pod
+ `-- viral_spiral.david_bollier
+
+}code
+
+#by: filename
+subject_dir/filename/manifest.en.html
+
+3~ Remote Directories
+
+code{
+
+./subject_name/
+
+% containing sub_directories named after the generated files from which they are made
+
+./subject_name/src
+
+% contains shared source files text and binary e.g. sisu_manual.sst and sisu_manual.sst.zip
+
+./subject_name/_sisu
+
+% configuration file e.g. sisurc.yml
+
+./subject_name/_sisu/skin
+
+% skins in various skin directories doc, dir, site, yml
+
+./subject_name/_sisu/css
+
+./subject_name/_sisu/image
+
+% images for documents contained in this directory
+
+./subject_name/_sisu/mm
+
+}code
+
+3~ Sisupod
+
+code{
+
+./sisupod/
+
+% files stored at this level e.g. sisu_manual.sst
+
+./sisupod/_sisu
+
+% configuration file e.g. sisurc.yml
+
+./sisupod/_sisu/skin
+
+% skins in various skin directories doc, dir, site, yml
+
+./sisupod/_sisu/css
+
+./sisupod/_sisu/image
+
+% images for documents contained in this directory
+
+./sisupod/_sisu/mm
+
+}code
+
+2~ Organising Content
+
+
+
+% .SH "SKINS \- document, directory and site skins"
+
+
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_css.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_css.ssi
new file mode 100644
index 00000000..7ffc654b
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_css.ssi
@@ -0,0 +1,42 @@
+% SiSU insert 2.0
+
+@title: SiSU
+ :subtitle: CSS - Cascading Style Sheets
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2007-08-28
+ :issued: 2007-08-28
+ :available: 2007-08-28
+ :published: 2007-09-16
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? CSS
+
+1~css CSS - Cascading Style Sheets (for html, XHTML and XML)
+
+CSS files to modify the appearance of SiSU html, XHTML or XML may be placed in the configuration directory: ./_sisu/css ; ~/.sisu/css or; /etc/sisu/css and these will be copied to the output directories with the command sisu -CC.
+
+The basic CSS file for html output is html.css, placing a file of that name in directory _sisu/css or equivalent will result in the default file of that name being overwritten.
+
+HTML:
+html.css
+
+XML DOM:
+dom.css
+
+XML SAX:
+sax.css
+
+XHTML:
+xhtml.css
+
+The default homepage may use homepage.css or html.css
+
+Under consideration is to permit the placement of a CSS file with a different name in directory _sisu/css directory or equivalent.~{ 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. }~
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_description.sst b/data/doc/sisu/markup-samples/manual/en/sisu_description.sst
new file mode 100644
index 00000000..9f8fdcd8
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_description.sst
@@ -0,0 +1,527 @@
+% SiSU 4.0
+
+@title: SiSU - SiSU information Structuring Universe / Structured information, Serialized Units
+ :subtitle: Description
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-11-12
+ :issued: 2002-11-12
+ :available: 2002-11-12
+ :published: 2007-08-30
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: electronic documents;SiSU:document:description;sisu:document:description
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? SiSU an attempt to describe
+
+1~ Description
+
+2~ Outline
+
+SiSU is a flexible document preparation, generation publishing and search system.~{ This information was first placed on the web 12 November 2002; with predating material taken from http://www.jus.uio.no/lm/lm.information/toc.html part of a site started and developed since 1993. See document metadata section http://www.jus.uio.no/sisu/SiSU/metadata.html or manifest page http://www.jus.uio.no/sisu/SiSU/sisu_manifest.html for information on this version. Dates related to the development of SiSU may be tracked in the http://www.jus.uio.no/sisu/SiSU/changelog.html or the Git repository http://git.sisudoc.org/?p=code/sisu.git;a=summary some of the more significant events may be contained within the Chronology section of this document http://www.jus.uio.no/sisu/sisu_chronology }~
+
+SiSU ("SiSU information Structuring Universe" or "Structured information, Serialized Units"),~{ also chosen for the meaning of the Finnish term "sisu". }~ is a Unix command line oriented framework for document structuring, publishing and search. Featuring minimalistic markup, multiple standard outputs, a common citation system, and granular search.
+
+Using markup applied to a document, SiSU can produce plain text, HTML, XHTML, XML, OpenDocument, EPUB, 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.
+
+SiSU is the data/information structuring and transforming tool, that has resulted from work on one of the oldest law web projects. It makes possible the one time, simple human readable markup of documents, that SiSU can then publish in various forms, suitable for paper~{ PDF via LaTeX }~, web~{ currently HTML (two forms of HTML presentation one based on css the other on tables), and /PHP/; potentially structured XML }~ and relational database~{ any SQL - currently PostgreSQL and SQLite (for portability, testing and development) }~ presentations, retaining common data-structure and meta-information across the output/presentation formats. Several requirements of legal and scholarly publication on the web have been addressed, including the age old need to be able to reliably cite/pinpoint text within a document, to easily make footnotes/endnotes, to allow for semantic document meta-tagging, and to keep required markup to a minimum. These and other features of interest are listed and described below. A few points are worth making early (and will be repeated a number of times):
+
+_1 (i) The SiSU document generator was the first to place material on the web with a system that makes possible citation across different document types, with paragraph, or rather object citation numbering~{ previously called "text object numbering" }~ a text positioning system, available for the pinpointing of text, 1997, a simple idea from which much benefit, and SiSU remains today, to the best of my knowledge, the only multiple format e-book/ electronic-document system on the web that gives you this possibility (including for relational databases).
+
+_1 (ii) Markup is done once for the multiple formats produced.
+
+_1 (iii) Markup is simple, and human readable (with a little practice), in almost all cases there is less and simpler markup required than basic HTML. In any event the markup required is very much simpler than the HTML, EPUB, LaTeX, [lout], structured XML, ODT (Open Document Format text), PostgreSQL or SQLite feed etc. that you can have SiSU generate for you.
+
+_1 (iv) SiSU is a batch processor, dealing with as many files as you need to generate at a time.
+
+_1 (v) Scalability is dependent on your file system, the database (currently PostgreSQL and/or SQLite) and your hardware.
+
+SiSU Sabaki~{ SiSU Sabaki, release version. Pre-release version SiSU Scribe, and version prior to that SiSU nicknamed Scribbler. Pre-release versions go back several years. Both Scribbler and Scribe (still maintained) made system calls to SiSU's various parts, instead of using libraries. }~ (or just SiSU) is the provisional name given to the software described here that helps structure documents for web and other publication. The name SiSU is a loose anagram for something along the lines of *{/{"SiSU is structuring unit"}/}*, or /{"SiSU, information structuring unit"}/ or the more descriptive /{"Structured information, Serialized Units"}/ or *{/{"simple - information structuring unit"}/}* or the more descriptive /{"Structured information, Serialized Units"}/ or what it may be directed towards /{"*semantic* and *{information structuring universe}*"}/,~{ A little universe it may be, but semantic you may have a hard time getting away with, given the meaning the word has taken on with markup. On a document wide basis semantic information may be provided, which can be really useful, (and meaningful, especially) if you have a large document set, and use this with rss feeds or in an sql database etc. On a markup level, I have little inclination to add semantic markup formally beyond references, title, author [Dublin Core entities? addresses?] etc. Actually this deserves a bit of thought possibly use letter tags (including letter alias/synonyms for font faces) to create a small set of default semantic tags, with the possibility for per document adjustments. Will seek to permit XML entity tagging, within SiSU markup and have that ignored/removed by the parts of the program that have no use for it. }~ tongue in cheek, only just. Guess I'll get away with *{/{"Simple - information Structuring Universe"}/}*. SiSU is also a Finnish word roughly meaning guts, inner strength and perseverance.~{ "Sisu refers not to the courage of optimism, but to a concept of life that says, 'I may not win, but I will gladly give my life for what I believe.'" Aini Rajanen, Of Finnish Ways, 1981, p. 10. \\ http://www.humanlanguages.com/finnishenglish/rlfs.htm \\ "Every Finn has his own pet definition. To me, sisu means patience without passion. But there are many varieties of sisu. Sisu can be a sudden outburst or it can be the kind that lasts. A man can have both kinds. It is outside reason. It is something in the soul. It comes from oneself. For instance, it makes a soldier do things because he himself must, not because he has been told." Paavo Nurmi \\ http://personalweb.smcvt.edu/tmatikainen/finnishtraditions.htm }~
+
+SiSU was born of the need to find a way, with minimal effort, and for as wide a range of document types as possible, to produce high quality publishing output in a variety of document formats. As such it was necessary to find a simple document representation that would work across a large number of document types, and the most convenient way(s) to produce acceptable output formats. The project leading to this program was started in 1993 (together with the trade law project now known as Lex Mercatoria) as an investigation of how to effectively/efficiently place documents on the web. The unified document handling, together with features such as paragraph numbering, endnote handling and tables... appeared in 1996/97. SiSU was originally written in Perl,~{ http://www.perl.org/ }~ and converted to Ruby,~{ http://www.ruby-lang.org/en/ }~ in 2000, one of the most impressive programming languages in existence! In its current form it has been written to run on the Gnu/Linux platform, and in particular on Debian,~{ http://www.debian.org/ }~ taking advantage of many of the wonderful projects that are available there.
+
+SiSU markup is based on requiring the minimum markup needed to determine the structure of a document. (This can be as little as saying in a header to look for the word Book at a specified level and the word Chapter at another level). SiSU then breaks a document into its smallest parts (at a heading, and paragraph level) while retaining all structural information. This break up of the document and information on its structure is taken advantage of in the transformations made in generating the very different output types that can be created, and in providing as much as can be for what each output type is best at doing, e.g. LaTeX (professional document typesetting, easy conversion to PDF or Postscript), EPUB, XML (in this case, structural representation), ODF (Open Document Format text), SQL (e.g. document search; representing constituent parts of documents based on their structure, headings, chapters, paragraphs as required; user control).~{ where explicit structure is provided through the use of tagging headings, it could be reduced (still) further, for example by reducing the number of characters used to identify heading levels; but in many cases even that information is not required as regular expressions can be used to extract the implicit structure. }~
+
+From markup that is simpler and more sparse than HTML you get:
+
+_* far greater output possibilities, including HTML, EPUB, XML, ODF (Open Document Format text), LaTeX (PDF), and SQL;
+
+_* the advantages implicit in the very different output possibilities;
+
+_* a common citation system (for all outputs - including the relational database, search results are relevant for all outputs);
+
+For more see the short summary of features provided below.
+
+SiSU processes files with minimal tagging to produce various document outputs including HTML, EPUB, ODF, LaTeX (which is converted to PDF) and if required loads the structured information into an SQL database (PostgreSQL and SQLite have been used for this). SiSU produces an intermediate processing format.~{ This proved to be the easiest way to develop syntax, changes could be made, or alternatives provided for the markup syntax whilst the intermediate markup syntax was largely held constant. There is actually an optional second intermediate markup format in YAML http://www.yaml.org/ }~
+
+SiSU was originally used in constructing Lex Mercatoria http://lexmercatoria.org/ or http://www.jus.uio.no/lm/ (one of the oldest law web sites), and considerable thought went into producing output that would be suitable for legal and academic writings (that do not have formulae) given the limitations of HTML, and publication in a wide variety of "formats", in particular in relation to the convenient and accurate citation of text. However, the construction of Lex Mercatoria uses only a fraction of the features available from SiSU today, /vis/ generation of flat file structures, rather than in addition the building of ("granular") SQL database content, (at an object level with relevant relational tables, and other outputs also available).
+
+2~ Short summary of features *~summary
+
+!_ (i)
+markup syntax: (a) simpler than html, (b) mnemonic, influenced by mail/messaging/wiki markup practices, (c) human readable, and easily writable,
+
+!_ (ii)
+(a) minimal markup requirement, (b) single file marked up for multiple outputs,
+
+notes:
+
+* 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/parsed 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.
+
+!_ (iii)
+(a) multiple outputs primarily industry established and institutionally accepted open standard formats, include amongst others: plaintext (UTF-8); html; EPUB; (structured) XML; ODF (Open Document text)l; LaTeX; PDF (via LaTeX); SQL type databases (currently PostgreSQL and SQLite). 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))
+
+!_ (iv)
+outputs share a common numbering system (dubbed "object citation numbering" (ocn)) that is meaningful (to man and machine) across various digital outputs whether paper, screen, or database oriented, (PDF, html, EPUB, XML, Opendocument, SQLite, PostgreSQL), this numbering system can be used to reference content.
+
+!_ (v)
+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 hyperesteier].
+
+!_ (vi)
+use of semantic meta-tags in headers permit the addition of semantic information on documents, (the available fields are easily extended)
+
+!_ (vii)
+creates organised directory/file structure for (file-system) output, easily mapped with its clearly defined structure, with all text objects numbered, you know in advance where in each document output type, a bit of text will be found (e.g. from an SQL search, you know where to go to find the prepared html output or PDF etc.)... there is more; easy directory management and document associations, the document preparation (sub-)directory may be used to determine output (sub-)directory, the skin used, and the SQL database used,
+
+!_ (viii)
+"Concordance file" wordmap, consisting of all the words in a document and their (text/ object) locations within the text, (and the possibility of adding vocabularies),
+
+!_ (ix)
+document content certification and comparison considerations: the document and each object within it stamped with an md5 hash making it possible to easily check or guarantee that the substantive content of a document is unchanged.
+
+!_ (x)
+SiSU's minimalist markup makes for meaningful "diffing" of the substantive content of markup-files,
+
+!_ (xi)
+easily skinnable, document appearance on a project/site wide, directory wide, or document instance level easily controlled/changed,
+
+!_ (xii)
+in many cases a regular expression may be used (once in the document header) to define all or part of a documents structure obviating or reducing the need to provide structural markup within the document,
+
+!_ (xiii)
+prepared files may be batch process, documents produced are static files so 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)
+
+!_ (xiv)
+possible to pre-process, which permits: the easy creation of standard form documents, and templates/term-sheets, or; building of composite documents (master documents) from other sisu marked up documents, or marked up parts, i.e. import documents or parts of text into a main document should this be desired
+
+there is a considerable degree of future-proofing, output representations are "upgradeable", and new document formats may be added.
+
+!_ (xv)
+there is a considerable degree of future-proofing, output representations are "upgradeable", and new document formats may be added: (a) modular, (thanks in no small part to Ruby) another output format required, write another module.... (b) easy to update output formats (eg html, XHTML, EPUB, LaTeX/PDF produced can be updated in program and run against whole document set), (c) easy to add, modify, or have alternative syntax rules for input, should you need to,
+
+!_ (xvi)
+scalability, dependent on your file-system and on the relational database used (currently PostgreSQL and SQLite), and your hardware,
+
+!_ (xvii)
+only marked up files need be backed up, to secure the larger document set produced,
+
+!_ (xviii)
+document management,
+
+!_ (xix)
+Syntax highlighting for SiSU markup is available for a number of text editors.
+
+!_ (xx)
+remote operations: (a) run SiSU on a remote server, (having prepared sisu markup documents locally or on that server, i.e. this solution where sisu is installed on the remote server, would work whatever type of machine you chose to prepare your markup documents on), (b) generated document outputs may be posted by sisu to remote sites (using rsync/scp) (c)document source (plaintext utf-8) if shared on the net may be identified by its url and processed locally to produce the different document outputs.
+
+!_ (xxi)
+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, these may be downloaded, shared as email attachments, or processed by running sisu against them, either using a url or the filename.
+
+!_ (xxii)
+for basic document generation, the only software dependency is Ruby, and a few standard Unix tools (this covers plaintext, html, EPUB, 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
+
+SiSU was developed in relation to legal documents, and is strong across a wide variety of texts (law, literature...). SiSU handles images but is not suitable for formulae/ statistics, or for technical writing at this time.
+
+SiSU has been developed and has been in use for several years. Requirements to cover a wide range of documents within its use domain have been explored.
+
+Some modules are more mature than others, the most mature being html and LaTeX / pdf. PostgreSQL and search functions are useable and together with /ocn/ unique (to the best of my knowledge). The XML output document set is "well formed" but largely proof of concept.
+
+2~ How it works
+
+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 text 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 instruction 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,~{ 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. }~ 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).
+
+2~ Simple markup
+
+SiSU markup is based on requiring the minimum markup needed to determine the structure of a document. (This can be as little as saying in a header to look for the word Book at a specified level and the word Chapter at another level). SiSU then breaks a document into its smallest parts (at a heading, and paragraph level) while retaining all structural information. This break up of the document and information on its structure is taken advantage of in the transformations made in generating the very different output types that can be created, and in providing as much as can be for what each output type is best at doing, e.g. LaTeX (professional document typesetting, easy conversion to pdf or Postscript), EPUB, XML (in this case, structural representation), ODF (OpenDocument), SQL (e.g. document search; representing constituent parts of documents based on their structure, headings, chapters, paragraphs as required; user control).~{ where explicit structure is provided through the use of tagging headings, it could be reduced (still) further, for example by reducing the number of characters used to identify heading levels; but in many cases even that information is not required as regular expressions can be used to extract the implicit structure. }~
+
+3~ Sparse markup requirement, try to get the most out of markup
+
+One of its strengths is that very small amounts of initial tagging is required for the program to generate its output.
+
+This is a basic markup example:
+
+_* { basic markup example, text file - an international convention }http://www.jus.uio.no/sisu/src/un_contracts_international_sale_of_goods_convention_1980.sst ~{ http://www.jus.uio.no/sisu/src/un_contracts_international_sale_of_goods_convention_1980.sst output provided as example in the next section }~
+
+Emphasis has been on simplicity and minimalism in markup requirements. Design philosophy is to try keep the amount of markup required low, for whatever has been determined to be acceptable output.~{ seems there are several "smart ASCIIs" available, primarily for ascii to html conversion, that make this, and reasonable looking ascii their goal \\ http://webseitz.fluxent.com/wiki/SmartAscii \\ http://daringfireball.net/projects/markdown/ \\ http://www.textism.com/tools/textile/ }~
+
+SiSU's markup is more minimalistic and simpler than (the equivalent) html and for it, you get considerably more than just html, as this preparation gives you all available output formats, upon request.
+
+3~ Single markup file provides multiple output formats
+
+For each document, there is only one (input, minimalistically marked up) file from which all the available output types are generated.~{ These include richly laid out and linked html (table or css variants), /PHP/, LaTeX (from which pdf portrait and landscape documents are produced), texinfo (for info files etc.), and PostgreSQL and/or SQLite. And the opportunity to fairly easily build additional modules, such as XML. See the examples provided in this document. }~
+
+Eg. the markup example:
+
+_* {~^ original text file - an international convention }http://www.jus.uio.no/sisu/src/un_contracts_international_sale_of_goods_convention_1980.sst
+
+Produces the following output:
+
+_* {~^ Manifest of output presentations generated }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/sisu_manifest.html
+
+_* {~^ Segmented html version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/toc.html
+
+_* {~^ Full length html document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/doc.html
+
+_* {~^ EPUB version of document }http://www.jus.uio.no/sisu/epub/un_contracts_international_sale_of_goods_convention_1980.epub
+
+_* {~^ pdf landscape version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/landscape.letter.pdf
+
+_* {~^ pdf portrait version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/portrait.letter.pdf
+
+_* {~^ odt open document format text version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/opendocument.odt
+
+_* {~^ xml sax version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/sax.xml
+
+_* {~^ xml dom version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/dom.xml
+
+_* {~^ clean tex ascii version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/plain.txt
+
+_* {~^ Concordance }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/concordance.html
+
+(and in addition to these: PostgreSQL, SQLite, texinfo and -{YAML}- ~{ discontinued for the time being }~ versions if desired)
+
+3~ Syntax relatively easy to read and remember
+
+Syntax is kept simple and mnemonic.~{ SiSU markup syntax, an incomplete summary: http://www.jus.uio.no/sisu/sisu_markup/toc.html \\ Visual check of elementary font face modifiers: *bold* *{bold}* !{emphasis}! /{italics}/ _{underscore}_ -{strikethrough}- ^{superscript}^ ,{subscript}, }~
+
+3~ Kept simple by having a limited publishing feature set, and features identified as most important, are available across several document types
+
+To keep SiSU markup sparse and simple SiSU deliberately provides a limited publishing feature set, including: indent levels; bold; italics; superscript; subscript; simple tables; images; tables of contents and; endnotes. Which in most cases are available across the different output formats.
+
+The publishing feature set may be expanded as required.
+
+2~ Designed with usability in mind
+
+Output is designed to be uniform, easy to read, navigate and cite.
+
+2~ Code separate from content
+
+Code~{ the program that generates the documents }~ is separated from content. This means that when changes are desired in the output presentation, the code that produces them, and not the marked up text data set (which could be thousands of documents) is modified. Separating code from content makes large scale changes to output appearance trivial, and permits the easy addition of new output modules.
+
+2~ Object citation numbering, a text or object positioning / citation system - "paragraph" (or text object) numbering, that remains same and usable across all output formats by people and machine *~citation *~ocn
+
+Object citation numbering is a simple object (text) positioning and cition system that is human relevant and machine useable, used by SiSU for all manner of presentations, and that is available for use in all text mappings. It is based on the automated sequential numbering of objects (roughly paragraphs, (headings, tables, verse) or other blocks of text or images etc.). The text positioning system (in which I claim copyright) is invaluable for publishing requiring the citing text across multiple output formats, and for the general mapping of text within a document:
+
+_* in html, html not being easily citeable (change font size, or use a different browser and the page on which specific text appears has changed), and
+
+_* across multiple formats being common to all output formats html/xml/pdf/sql output,
+
+_* the results of an sql search can just be "live" citation references to the documents in which the text is found, {~^ much like an index (see image examples provided). }http://www.jus.uio.no/sisu/SiSU/1.html#search
+
+I claim copyright on the system I use which is the most basic of all, numbering all text in headings and paragraphs sequentially (with tables and images being treated as a single paragraph) and only footnotes/endnotes not following this numbering, as their position in text is not strictly determined, (a change from footnotes to endnotes would change their numbering), footnotes instead "belong" to the paragraph from which they are referenced, and have sequential numbers of their own.
+
+SiSU has a paragraph numbering system, that remains the same regardless of the output format. This provides an effective means of citation, pinpointing text accurately in all output formats, using the same reference. This is particularly useful where text has to be located across different output formats - for example once html is printed the number of pages and pages on which given text is found will vary depending on the browser, its settings the font size setting etc. Similarly SiSU produces pdf in different forms, eg. on the example site Lex Mercatoria as portrait and landscape documents - here too page numbering varies, but paragraph numbering is the same, /{vis a vis}/ all versions of the text (portrait and landscape pdf and the html versions of the text, and as stored (with "paragraphs" as records) to the PostgreSQL or SQLite database).
+
+These numbers are placed in the text margins and are intended to be independent of and not to interfere with authors tagging. [The citation system (object citation numbering system, automated "paragraph numbering") which is automatically generated and is common and identical across all document formats] The paragraph numbering system is more accurately described as an (text) object numbering system, as headings are also numbered... all headings and paragraphs are numbered sequentially. Endnotes are automatically numbered independently and rather "belong" to the paragraph from which they are referenced, as an endnote does not (necessarily) form a part of a documents sequence, (they may be produced as either endnotes or footnotes (or both depending on what output you choose to look at - if you take the segmented html version document provided as an example, you will find that the endnotes are placed both at the end of each section, and in a separate section of their own called endnotes, and these are hyper-linked)). An attractive feature of providing citation numbering in this way is that it is independent of the document structure... it remains the same regardless of what is done about the document structure.
+
+The rules have been kept very simple, unique incremental object citation numbers are assigned to headings, paragraphs, verse, tables and images. It is possible to manually override this feature on a per heading or comment basis though this should be used exceptionally, it may be of use where there a substantive text, and the addition of a minor comment by the publisher that should not be mapped as part of the text.
+
+The object citation number markers contain additional numbering information with regard to the document structure, that can be used for alternative presentations, including such detail as the type of object (heading, paragraph, table, image, etc.), numbered sequentially.
+
+An advantage is that the numbering remains the same regardless of document structure.
+
+Text object ("paragraph") numbering is the same for all output versions of the same document, vis HTML, EPUB, PDF, PgSQL, etc.
+
+In the relational database, as individual text objects of a document stored (and indexed) together with object numbers, and all versions of the document have the same numbering, the results of searches may be tailored just to provide the location of the search result in all available document formats.
+
+/{ Note: there is a bug in the released behaviour of object citation numbering, (not certain when it was introduced) tables should be numbered, ie each table gets an ocn, required amongst other things for relational database. This will be corrected in a future release. Citation numbering of existing documents that contain tables will changed. }/
+
+2~ Handling of Dublin Core meta-tags making use of the Resource Description Framework
+
+SiSU is able to use meta tags based on the Dublin Core~{ http://dublincore.org/ }~ and Resource Description Framework~{ http://www.w3.org/RDF/ }~
+
+This provides the means of providing semantic information about a document, both as computer processable meta-tags, and as human readable information that may be of value for classification purposes.
+
+This information is provided both in html metatags, and (where available) under the section titled "Document Information - Metadata", near the end of a document, for example in the segmented html version of this text at: http://www.jus.uio.no/sisu/SiSU/metadata.html
+
+2~ Easy directory management
+
+#1 Directory file association, skins and special image management, made simpler.~{ The previous way was directory associations for file output were set up in the configuration file. The present system is a more natural way to work requireing less configuration. }~
+
+The last part of the name of the work directory in which markup is being done, or rather from where SiSU is run in order to generate document output, is used in determining the sub-directory name for output files, that is created in the document output directory. This provides a rather easy way to associate documents e.g. of a given subject, or by owner.
+
+code{
+
+/www/docs
+ /intellectual_property
+ /arbitration
+ /contract_law
+
+/www/docs
+ /ralph
+ /sisu
+
+}code
+
+all are placed in their own directories within the directory structure created. Similar rules are used in the creation of sql type databases (though they can be overridden).
+
+There are a couple of further associations with these directories.
+
+# If the working directory has within it a sub-directory called image_local, the images within that directory are used for references to images, that are not part of the default site build.
+
+2~ Document Version Control Information
+
+The possibility of citing an exact document version.
+
+Permits the inclusion of document version control information to the document body and metatags.~{ from a version control system such as CVS }~ This provides a much more certain method of referring to the exact version of a particular document, (assuming that the document is from a trusted source, that will retain earlier versions of a document).~{ The version control system must be run, so the version number is obtained, prior to the SiSU document generation, and subsequent posting of the document. }~
+
+This information (where available) is provided under the section of the document titled "Document Information - MetaData", near the end of a document, for example in the segmented html version of this text at: http://www.jus.uio.no/sisu/SiSU/metadata.html
+
+2~ Table of contents
+
+SiSU produces a rudimentary a table of contents based on document headings.
+
+2~ Auto-numbering of headings
+
+Headings can be automatically numbered, (and automatically named for hyper-linking)
+
+2~ Numbering and cross-hyperlinking of endnotes
+
+SiSU can automatically number footnotes/endnotes. This is the default operation where no number is provided.
+
+Footnotes/endnotes may also be manually numbered. Where a number, or numbers are provided for a footnote/endnote, this does not increment the automatic footnote/endnote number counter.
+
+In the html output footnotes/endnotes are cross-hyper-linked (to their reference point and vice versa). In th pdf output footnotes are linked from their reference point only.
+
+2~ "Skinnable"
+
+SiSU is skinnable, on a site-wide, directory-wide and per document basis, so different looking versions of things may be produced with little difficulty. There is a default skin which may be modified, as the background site skin, and each working directory may have a skin associated with it, as may each individual document. The hierarchy of application is document, directory, then site... ie if a document skin exists it gets precedence.
+
+Whilst it is skinnable, the default output styles are selected to work across the widest possible range of document types.
+
+2~ Multiple Outputs
+
+From markup that is simpler and more sparse than html you get:
+
+_* far greater output possibilities, including multiple html types, XML (different structured types), LaTeX (pdf landscape, portrait), and SQL (PostgreSQL or SQLite or other);
+
+_* the advantages implicit in these very different output possibilities;~{ e.g. LaTeX (professional document typesetting, easy conversion to pdf or Postscript), XML (in this case, structural representation), SQL (e.g. document set searches; representation of the constituent parts of documents based on their structure, headings, chapters, paragraphs as desired; control of use) }~
+
+_* a common citation system
+
+As many output formats/presentations as one cares to write modules for - several types of html (e.g. structure based on css, or structure based on tables); /{LaTeX/pdf}/ and /{Lout/pdf}/; PgSQL other databases easily added; yaml...
+
+3~ html - several presentations: full length & segmented; css & table based
+
+Most documents are produced in single and segmented html versions, described below:
+
+!_ The Scroll (full length text presentations)
+
+The full length of the text in a single scrollable document.~{ CISG http://www.jus.uio.no/lm/un.contracts.international.sale.of.goods.convention.1980/doc.html \\ The Unidroit Contract Principles http://www.jus.uio.no/lm/unidroit.contract.principles.1994/doc.html or \\ The Autonomous Contract http://www.jus.uio.no/lm/autonomous.contract.2000.amissah/doc.html }~ As a rule the files they are saved in are named: /doc/ or more precisely /{doc.html}/
+
+For various reasons texts may only be provided in this form (such as this one which is short), though most are also provided as segmented texts.
+
+"Scroll" is a reference to the historical scroll, a single long document/ parchment, and also no doubt to what you will have to do to get to the bottom of the text.~{ Scrolling is not however necessarily confined to full length documents as you will have to scroll to get to the bottom of any long segment (eg. chapter) of a segmented text. }~
+
+!_ The Segmented Text
+
+The text divided into segments (such as articles or chapters depending on the text)~{ CISG http://www.jus.uio.no/lm/un.contracts.international.sale.of.goods.convention.1980/toc.html \\ The Unidroit Principles http://www.jus.uio.no/lm/unidroit.contract.principles.1994/toc.html \\ The Autonomous Contract http://www.jus.uio.no/lm/autonomous.contract.2000.amissah/toc.html or \\ WTA 1994 http://www.jus.uio.no/lm/wta.1994 }~ As a rule the files they are saved in are named: /toc/ and /index/ or more precisely /{toc.html}/ and /{index.html}/
+
+If you know exactly what you are looking for, loading a segment of text is faster (the segments being smaller). Occasionally longer documents such as the WTA 1994 http://www.jus.uio.no/lm/wta.1994/toc are only provided in segmented form.
+
+!_ Cascading Style Sheet, and Table based html
+
+SiSU outputs html, two current standard forms available are:
+
+{ css based }http://www.jus.uio.no/sisu/SiSU/toc.html
+
+and
+
+table based [largely discontinued]~{ formatting possibility still exists in code tree but maintenance has been largely discontinuted. }~
+
+!_ The html is tested across several browsers
+
+I like to remind you that there are other excellent browsers out there, many of which have long supported practical features like tabbing.
+
+The html is tested across several browsers, including:
+
+_* {~^ *Firefox* (Mozilla-Firefox) }http://www.mozilla.org/products/firefox/
+
+_* {~^ Kazehakase }http://kazehakase.sourceforge.jp/
+
+_* {~^ Konqueror }http://www.konqueror.org/
+
+_* {~^ Mozilla }http://www.mozilla.org/
+
+_* {~^ MS Internet Explorer }http://www.microsoft.com/windows/ie/default.asp
+
+_* {~^ Netscape }http://home.netscape.com/comprod/mirror/client_download.html
+
+_* {~^ Opera }http://www.opera.com/
+
+Also lighter weight graphical browsers:
+
+_* {~^ Dillo }http://www.dillo.org/
+
+_* {~^ *Epiphany* }http://www.gnome.org/projects/epiphany/
+
+_* {~^ *Galeon* }http://galeon.sourceforge.net/
+
+And for console/text browsing:
+
+_* {~^ *elinks* }http://elinks.or.cz/
+
+_* {~^ *links2* }http://links.twibright.com/
+
+_* {~^ *w3m* }http://w3m.sourceforge.net/
+
+The html tables output is rendered more accurately across a wider variety set and older versions of browsers (than the html css output).
+
+3~ EPUB
+
+SiSU generates EPUB documents.
+
+3~ XML
+
+SiSU generates well formed XML, and multiple versions. An XML SAX version with a flat/shallow structure, and XML DOM version with a deeper (embedded) structure. There is also a released working xhtml module. Examples of SAX and DOM versions are provided within this document.
+
+3~ ODT:ODF, Open Document Format - ISO/IEC 26300:2006
+
+SiSU generates Open Document Output format.
+
+3~ PDF - portrait and landscape, (through the generation of LaTeX output which is then transformed to pdf)
+
+SiSU outputs LaTeX if required which is easily transformed to PDF.~{ LaTeX and pdf features introduced 18^th^ June 2001, Landscape and portrait pdfs introduced 7^th^ October 2001., Lout is a more recent addition 22^th^ April 2003 }~ PDF documents are generated on the site from the same source files and Ruby program that produce html. Landscape oriented pdf introduced, providing easier screen viewing, they are also (paper saving, being currently) formatted to have fewer pages than their portrait equivalents.
+
+_* {~^ Adobe Reader }http://www.adobe.com/products/acrobat/readstep2.html
+
+_* {~^ *Evince* }http://www.gnome.org/projects/evince/
+
+_* {~^ xpdf }http://www.foolabs.com/xpdf/
+
+3~ Search - loading/populating of relational database while retaining document structure information, object citation numbering and other features (currently PostgreSQL and/or SQLite)
+
+SiSU (from the same markup input file) automatically feeds into 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 (could be any other of the better relational databases)~{ Relational database features retaining document structure and citation introduced 15^th^ July 2002 }~ - together with all additional information related to document structure, and the alternative ways in which it is generated on the site retained. As regards scaling of the database, it is as scalable as the database (here Postgresql or SQLite) and hardware allow. I will prune the images later.
+
+This is one of the more interesting output forms, as all the structural data for 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 PgSQL database tables:
+
+_1* one containing semantic (and other) headers, including, title, author, subject, (the Dublin Core...);
+
+_1* another the substantive texts by individual "paragraph" (or object) - along with structural information, each paragraph being identifiable by its paragraph number (if it has one which almost all of them do), and the substantive text of each paragraph quite naturally being searchable (both in formatted and clean text versions for searching); and
+
+_1* a third containing endnotes cross-referenced back to the paragraph from which they are referenced (both in formatted and clean text versions for searching).
+
+_1* a fourth table with a one to one relation with the headers table contains full text versions of output, eg. pdf, html, xml, and ascii.
+
+There is of course the possibility to add further structures.
+
+At this level SiSU loads a relational database with documents broken in to their smallest logical structurally constituent parts, as text objects, with their object citation number and all other structural information needed to construct the structured document. Text is stored (at this text object level) with and without elementary markup tagging, the stripped version being so as to facilitate ease of searching.
+
+Because the document structure of sites created is clearly defined, and the text object citation system is available 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.
+
+The combination of the SiSU citation system with a relational database is pretty powerful, giving rise to several possibilities. As individual text objects of a document stored (and indexed) together with object numbers, and all versions of the document have the same numbering, complex searches can be tailored to return just the locations of the search results relevant for all available output formats, with live links to the precise locations in the database or in html/xml documents; or, the structural information provided makes it possible to search the full contents of the database and have headings in which search content appears, or to search only headings etc. (as the Dublin Core is incorporated it is easy to make use of that as well).
+
+This is a larger scale project, (with little development on the front end largely ignored), though the "infrastructure" has been in place since 2002.
+
+3~ Search - database frontend sample, utilising database and SiSU features, including object citation numbering (backend currently PostgreSQL) *~search
+
+{~^ Sample search frontend }http://search.sisudoc.org
+A small database and sample query front-end (search from) that makes use of the citation system, _{object citation numbering}_ to demonstrates functionality.~{ (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. }~
+
+SiSU can provide information on which documents are matched and at what locations within each document the matches are found. These results are relevant across all outputs using object citation numbering, which includes html, EPUB, XML, LaTeX, PDF and indeed the SQL database. You can then refer to one of the other outputs or in the SQL database expand the text within the matched objects (paragraphs) in the documents matched.
+
+(further work needs to be done on the sample search form, which is rudimentary and only passes simple booleans correctly at present to the SQL engine)
+
+A few canned searches, showing object numbers. Search for:
+
+{ English documents matching Linux OR Debian }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=Linux%2BOR%2BDebian&db=SiSUv2c_sisu&view=index
+
+{ GPL OR Stallman }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=GPL%2BOR%2BStallman&db=SiSUv2c_sisu&view=index
+
+{ invention OR innovation }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=invention%2BOR%2Binnovation&db=SiSUv2c_sisu&view=index
+
+{ copyright in English language documents }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=copyright&db=SiSUv2c_sisu&view=index
+
+Note that the searches done in this form are case sensitive.
+
+Expand those same searches, showing the matching text in each document:
+
+{ English documents matching Linux OR Debian }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=Linux%2BOR%2BDebian&db=SiSUv2c_sisu&view=text
+
+{ GPL OR Stallman }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=GPL%2BOR%2BStallman&db=SiSUv2c_sisu&view=text
+
+{ invention OR innovation }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=invention%2BOR%2Binnovation&db=SiSUv2c_sisu&view=text
+
+{ copyright }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=copyright&db=SiSUv2c_sisu&view=text
+
+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.~{ 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 and we can tell you which documents meet your search criteria, but there is no way we can tell you without opening each document where within each your matches are found. }~
+
+!_ OCN index mode,
+(object citation number) the numbers displayed are relevant (and may be used to reference the match) in any sisu generated rendition of the text~{ OCN are provided for HTML, XML, EPUB, pdf ... though currently omitted in plain-text and opendocument format output }~ the links provided are to the locations of matches within the html generated by SiSU.
+
+!_ Paragraph mode,
+you may alternatively display the text of each paragraph in which the match was made, again the object/paragraph numbers are relevant to any SiSU generated/published text.
+
+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].
+
+Simple search, results with files in which search found, and text object (paragraph or endnote) where found within files.
+
+3~ Other forms
+
+There are other forms as well, YAML file, Ruby Marshal dumps, document pre-processing (processing of documents prior to the steps described here, to produce input suitable for the program) snap in a new module as required/desired, well formed XML, no problem.
+
+2~ Concordance / Word Map or rudimentary index
+
+Concordance /WordMaps:~{ Concordance/ WordMaps introduced 15^th^ August 2002 }~ SiSU produces a rudimentary index based on the words within the text, making use of paragraph numbers to identify text locations. This is generated in html and hyper-linked but identifies these words locations in the other document formats. Though it is possible to search using a search engine, this is a means for browsing an alphabetical list of words which may suggest other useful content.
+
+% Concordance files may be built using a document vocabulary. The vocabulary to be used may be specified on a per document basis.
+
+2~ Managed (document) directory, database, or site structure
+
+SiSU builds the web site (or more generically provides a suitable directory structure) - placing various output texts in the hierarchy of the web-site (or db), which (for directories) is a sub-directory with the name of the text file.
+
+2~ Batch processing
+
+SiSU is a batch processing tool, handling and transforming multiple (or individual) documents (in many ways) with a single instruction.
+
+2~ Integration to superior Gnu/Linux and Unix tools
+
+As should have been noted by the above description of SiSU, it makes use of existing programs found on Gnu/Linux and Unix, amongst those already mentioned include the LaTeX to pdf converters and the database PostgreSQL or SQLite.
+
+3~ Backup and version control
+
+Unix provides many tools for version control. For documents Subversion, CVS and even the old RCS are useful for the per-document histories they provide.
+
+For writing code superior (more recent) version control system exist. These can also be used for documents though they tend to take stamps of changes across the repository as a whole, rather than for each individual file that is tracked, (as CVS and RCS do). My personal preference is for distributed systems such as Git, Mercurial or Darcs, of which I use Git for both code and documents.
+
+Several backup tools exist. At the base level I tend to use rdiff.
+
+3~ Editor support
+
+SiSU documents are prepared / marked up in utf-8 text _{you are free to use the text editor of your choice.}_
+
+Syntax highlighting for a number of editors are provided. Amongst them Vim, Kwrite, Kate, Gedit and diakonos. These may be found with configuration instructions at http://www.sisudoc.org/sisu/sisu_syntax_highlighting/doc.html {~^ Vim }http://www.vim.org/ as of version 7 has built in sytax highlighting for SiSU.
+
+2~ Modular design, need something new add a module
+
+Need a new output format that does not already exist, write a new module.
+
+Prefer a new input syntax, you could write a new syntax matching the existing design, though my personal preference is some uniformity in entry appearance. If necessary has been fairly easy to extend the design parameters. It is intended to incorporate some additional basic semantic tagging, (book, article, author etc.) However, keeping the requirements for input minimal, and relatively simple has been a design goal.
+
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_download.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_download.ssi
new file mode 100644
index 00000000..96c97985
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_download.ssi
@@ -0,0 +1,133 @@
+% SiSU insert 2.0
+
+@title: SiSU - SiSU information Structuring Universe / Structured information, Serialized Units
+ :subtitle: Download, Stable and Development Branches
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-11-12
+ :issued: 2002-11-12
+ :available: 2002-11-12
+ :published: 2009-01-18
+ :modified: 2011-03-11
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? @title @creator
+
+:B~? SiSU Downloads, Stable and Development Branches
+
+:C~ Download information
+
+1~download Download SiSU - Linux/Unix
+
+2~current- SiSU Current Version - Linux/Unix
+
+3~source- Source (tarball tar.gz)
+
+_* {~^ sisu_[version].orig.tar.gz }http://www.jus.uio.no/sisu/pkg/src/
+
+_* {~^ sisu-markup-samples_[version].orig.tar.gz }http://www.jus.uio.no/sisu/pkg/src/
+
+For more general use see http://sisudoc.org/sisu/sisu_manual
+
+For changelogs see http://www.jus.uio.no/sisu/SiSU/changelog.html
+
+3~git- Git (source control management)
+
+Git repository currently at:
+
+_* git clone git://git.sisudoc.org/git/code/sisu.git
+
+_* git clone _http://git.sisudoc.org/git/code/sisu.git
+
+_* http://git.sisudoc.org/?p=code/sisu.git;a=summary
+
+On using git, see
+
+!_ Git documentation:
+{~^ Git User's Manual }http://www.kernel.org/pub/software/scm/git/docs/user-manual.html, {~^ Everyday GIT With 20 Commands Or So }http://www.kernel.org/pub/software/scm/git/docs/everyday.html, {~^ A tutorial introduction to git }http://www.kernel.org/pub/software/scm/git/docs/v1.4.4.4/tutorial.html, {~^ A tutorial introduction to git: part two }http://www.kernel.org/pub/software/scm/git/docs/v1.4.4.4/tutorial-2.html
+
+!_ User contributed texts:
+{~^ The Git Community Book }http://book.git-scm.com/index.html, {~^ Git Magic }http://www-cs-students.stanford.edu/~blynn/gitmagic/, {~^ Git From the Bottom Up (pdf) }http://www.newartisans.com/blog_assets/git.from.bottom.up.pdf
+
+3~debian- Debian
+
+This section contains information on the latest SiSU release. For installation notes see http://sisudoc.org/sisu/sisu_manual/installation.html
+
+SiSU is updated fairly regularly in Debian testing and unstable, and should be available therefrom.
+
+To add this archive, should you still choose to do so, add the following lines to your /etc/apt/sources.list
+
+code{
+
+deb http://www.jus.uio.no/sisu/archive unstable main non-free
+deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
+
+}code
+
+*{Source}* available from
+
+http://www.jus.uio.no/sisu/pkg/src/
+
+http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/
+
+http://www.sisudoc.org/sisu/archive/pool/main/s/sisu/
+
+sisu_[version].orig.tar.gz
+
+sisu_[version].debian.tar.gz
+
+sisu_[version].dsc
+
+group{
+
+*{Debs}*
+
+{~^ sisu_[version]_all.deb }http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/ ~{ \\ sisu, the base code, (the main package on which the others depend), without any dependencies other than ruby (and for convenience the ruby webrick web server), this generates a number of types of output on its own, other packages provide additional functionality, and have their dependencies \\ Depends: ruby (>=1.8.7), libwebrick-ruby \\ Recommends: sisu-pdf, sisu-sqlite, sisu-postgresql, sisu-examples, vim-sisu, librmagick-ruby, trang, tidy, libtidy, librexml-ruby, zip, unzip, openssl }~
+
+{~^ sisu-complete_[version]_all.deb }http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/ ~{ \\ a package that pulls in other packages to build the whole of sisu (excluding sisu-examples) \\ Depends: ruby (>=1.8.7), sisu, sisu-pdf, sisu-postgresql, sisu-remote, sisu-sqlite, vim-sisu \\ Recommends: sisu-examples }~
+
+{~^ sisu-pdf_[version]_all.deb }http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/ ~{ \\ dependencies used by sisu to produce PDF from LaTeX generated \\ Depends: sisu, tetex-bin, tetex-extra, latex-ucs \\ Suggests: evince, xpdf }~
+
+{~^ sisu-postgresql_[version]_all.deb }http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/ ~{ \\ dependencies used by sisu to populate postgresql database (further configuration is necessary) \\ Depends: sisu, postgresql, libdbi-ruby, libdbm-ruby, libdbd-pg-ruby \\ Suggests: pgaccess, libdbd-pgsql, postgresql-contrib }~
+
+{~^ sisu-sqlite_[version]_all.deb }http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/ ~{ \\ dependencies used by sisu to populate sqlite database \\ Depends: sisu, sqlite, libdbi-ruby, libdbm-ruby, libdbd-sqlite-ruby \\ Suggests: libdbd-sqlite }~
+
+}group
+
+For changelogs see:
+
+_1 http://www.sisudoc.org/sisu/SiSU/changelog.html
+
+_1 http://www.jus.uio.no/sisu/SiSU/changelog.html
+
+!_ non-free
+
+Book markup samples have been moved to non-free as the substantive text of the documents are available under the author or original publisher's license, and usually do not comply with the Debian Free Software Guidelines.
+
+_* {~^ sisu-markup-samples_[version]_all.deb }http://www.jus.uio.no/sisu/archive/pool/non-free/s/sisu-markup-samples/ ~{ \\ marked up documents and other examples related to sisu, a larger package containing a number of texts \\ Depends: sisu }~
+
+_* {~^ sisu-markup-samples_[version].dsc }http://www.jus.uio.no/sisu/pkg/src/ ~{ \\ sisu-markup-samples_[version].dsc }~
+
+For changelogs see:
+
+_1 http://www.jus.uio.no/sisu/SiSU/changelog_markup_samples.html
+
+3~rpm- RPM
+
+The RPM is generated from the source file using Alien.~{ http://www.kitenet.net/programs/alien/ }~ Dependencies are not handled, not even that of the essential Ruby.
+
+sudo rpm -i [package name]
+
+_* {~^ sisu-[version].noarch.rpm }http://www.jus.uio.no/sisu/pkg/rpm/ ~{ \\ created using alien }~
+
+_* {~^ sisu-markup-samples_[version].noarch.rpm }http://www.jus.uio.no/sisu/pkg/rpm/ ~{ \\ http://www.jus.uio.no/sisu/archive/pool/non-free/s/sisu-markup-samples/ \\ created using: alien -r sisu_[version]_all.deb }~
+
+For changelogs see:
+
+_1 http://www.jus.uio.no/sisu/SiSU/changelog_markup_samples.html
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_examples.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_examples.ssi
new file mode 100644
index 00000000..cf9df9d5
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_examples.ssi
@@ -0,0 +1,97 @@
+% SiSU insert 2.0
+
+@title: SiSU
+ :subtitle: Markup Samples, Output Examples
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-11-12
+ :issued: 2002-11-12
+ :available: 2002-11-12
+ :published: 2007-09-16
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+A~? @title @creator
+
+B~? SiSU Markup and Output Examples
+
+1~examples Markup and Output Examples
+
+2~ Markup examples *~markup
+
+Current markup examples and document output samples are provided off http://sisudoc.org or http://www.jus.uio.no/sisu and in the sisu-markup-sample package available off http://sources.sisudoc.org
+
+For some documents hardly any markup at all is required at all, other than a header, and an indication that the levels to be taken into account by the program in generating its output are.
+
+2~sisu-markup-samples SiSU Markup Samples
+
+A few additional sample books prepared as sisu markup samples, output formats to be generated using SiSU are contained in a separate package sisu-markup-samples. sisu-markup-samples contains books (prepared using sisu markup), that were released by their authors various licenses mostly different Creative Commons licences that do not permit inclusion in the Debian Project as they have requirements that do not meet the Debian Free Software Guidelines for various reasons, most commonly that they require that the original substantive text remain unchanged, and sometimes that the works be used only non-commercially.
+
+/{Accelerando}/, Charles Stross (2005) \\
+accelerando.charles_stross.sst
+
+/{Alice's Adventures in Wonderland}/, Lewis Carroll (1865) \\
+alices_adventures_in_wonderland.lewis_carroll.sst
+
+/{CONTENT}/, Cory Doctorow (2008) \\
+content.cory_doctorow.sst
+
+/{Democratizing Innovation}/, Eric von Hippel (2005) \\
+democratizing_innovation.eric_von_hippel.sst
+
+/{Down and Out in the Magic Kingdom}/, Cory Doctorow (2003) \\
+down_and_out_in_the_magic_kingdom.cory_doctorow.sst
+
+/{For the Win}/, Cory Doctorow (2010) \\
+for_the_win.cory_doctorow.sst
+
+/{Free as in Freedom - Richard Stallman's Crusade for Free Software}/, Sam Williams (2002) \\
+free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst
+
+/{Free as in Freedom 2.0 - Richard Stallman and the Free Software Revolution}/, Sam Williams (2002), Richard M. Stallman (2010) \\
+free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst
+
+/{Free Culture - How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity}/, Lawrence Lessig (2004) \\
+free_culture.lawrence_lessig.sst
+
+/{Free For All - How Linux and the Free Software Movement Undercut the High Tech Titans}/, Peter Wayner (2002) \\
+free_for_all.peter_wayner.sst
+
+/{GNU GENERAL PUBLIC LICENSE v2}/, Free Software Foundation (1991) \\
+gpl2.fsf.sst
+
+/{GNU GENERAL PUBLIC LICENSE v3}/, Free Software Foundation (2007) \\
+gpl3.fsf.sst
+
+/{Gulliver's Travels}/, Jonathan Swift (1726 / 1735) \\
+gullivers_travels.jonathan_swift.sst
+
+/{Little Brother}/, Cory Doctorow (2008) \\
+little_brother.cory_doctorow.sst
+
+/{The Cathederal and the Bazaar}/, Eric Raymond (2000) \\
+the_cathedral_and_the_bazaar.eric_s_raymond.sst
+
+/{The Public Domain - Enclosing the Commons of the Mind}/, James Boyle (2008) \\
+the_public_domain.james_boyle.sst
+
+/{The Wealth of Networks - How Social Production Transforms Markets and Freedom}/, Yochai Benkler (2006) \\
+the_wealth_of_networks.yochai_benkler.sst
+
+/{Through the Looking Glass}/, Lewis Carroll (1871) \\
+through_the_looking_glass.lewis_carroll.sst
+
+/{Two Bits - The Cultural Significance of Free Software}/, Christopher Kelty (2008) \\
+two_bits.christopher_kelty.sst
+
+/{UN Contracts for International Sale of Goods}/, UN (1980) \\
+un_contracts_international_sale_of_goods_convention_1980.sst
+
+/{Viral Spiral}/, David Bollier (2008) \\
+viral_spiral.david_bollier.sst
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_faq.sst b/data/doc/sisu/markup-samples/manual/en/sisu_faq.sst
new file mode 100644
index 00000000..966cea5f
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_faq.sst
@@ -0,0 +1,200 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: FAQ - Frequently Asked/Answered Questions
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2008-03-12
+ :created: 2006-09-06
+ :available: 2006-09-06
+ :issued: 2006-09-06
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: electronic documents;SiSU:document:FAQ;sisu:document:FAQ;SiSU:manual:FAQ;electronic documents:SiSU:manual:FAQ
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+1~faq FAQ - Frequently Asked/Answered Questions
+
+2~ Why are urls produced with the -v (and -u) flag that point to a web server on port 8081 ?
+
+Try the following rune:
+
+_* sisu -W
+
+This should start the ruby webserver. It should be done after having produced some output as it scans the output directory for what to serve.
+
+2~ I cannot find my output, where is it?
+
+The following should provide help on output paths:
+
+_* sisu --help env
+
+_* sisu -V [same as the previous command]
+
+_* sisu --help directory
+
+_* sisu --help path
+
+_* sisu -U [filename]
+
+_* man sisu
+
+2~ I do not get any pdf output, why?
+
+SiSU produces LaTeX and pdflatex is run against that to generate pdf files.
+
+If you use Debian the following will install the required dependencies
+
+_* aptitude install sisu-pdf
+
+the following packages are required: tetex-bin, tetex-extra, latex-ucs
+
+2~ Where is the latex (or some other interim) output?
+
+Try adding -M (for maintenance) to your command flags, e.g.:
+
+_* sisu -HpMv [filename]
+
+this should result in the interim processing output being retained, and information being provided on where to find it.
+
+_* sisu --help directory
+
+_* sisu --help path
+
+should also provide some relevant information as to where it is placed.
+
+2~ Why isn't SiSU markup XML
+
+I worked with text and (though I find XML immensely valuable) disliked noise
+... better to sidestep the question and say:
+
+SiSU currently "understands" three XML input representations - or more accurately, converts from three forms of XML to native SiSU markup for processing. The three types correspond to SAX (structure described), DOM (structure embedded, whole document must be read before structure is correctly discernable) and node based (a tree) forms of XML document structure representation. Problem is I use them very seldom and check that all is as it should be with them seldom, so I would not be surprised if something breaks there, but as far as I know they are working. I will check and add an XML markup help page before the next release. There already is a bit of information in the man page under the title SiSU VERSION CONVERSION
+
+_1 sisu --to-sax [filename/wildcard]
+
+_1 sisu --to-dom [filename/wildcard]
+
+_1 sisu --to-node [filename/wildcard]
+
+The XML should be well formed... must check, but lacks sensible headers. Suggestions welcome as to what to make of them. [For the present time I am satisfied that I can convert (both ways) between 3 forms of XML representation and SiSU markup].
+
+_1 sisu --from-xml2sst [filename/wildcard]
+
+2~ LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU?
+
+% what are some similarities and differences between LaTex and SiSU?
+
+SiSU is not really about type-setting.
+
+LaTeX is the ultimate computer instruction type-setting language for paper based publication.
+
+LaTeX is able to control just about everything that happens on page and pixel, position letters kerning, space variation between characters, words, paragraphs etc. formula.
+
+SiSU is not really about type-setting at all. It is about a lightweight markup instruction that provides enough information for an abstraction of the documents structure and objects, from which different forms of representation of the document can be generated.
+
+SiSU with very little markup instruction is able to produce relatively high quality pdf by virtue of being able to generate usable default LaTeX; it produces "quality" html by generating the html directly; likewise it populates an SQL database in a useful way with the document in object sized chunks and its meta-data. But SiSU works on an abstraction of the document's structure and content and custom builds suitable uniform output. The html for browser viewing and pdf for paper viewing/publishing are rather different things with different needs for layout - as indeed is what is needed to store information in a database in searchable objects.
+
+% SiSU is a lightweight document abstraction, meta-(structure and markup) syntax designed to make use of a minimal amount of preparation detail that can be used across very different ways of representing documents
+
+The pdfs or html produced for example by open office based on open document format and other office/word processor suits usually attempt to have similar looking outputs - your document rendered in html looks much the same, or in pdf... sisu is less this way, it seeks to have a starting point with as little information about appearance as possible, and to come up with the best possible appearance for each output that can be derived based on this minimal information.
+
+Where there are large document sets, it provides consistency in appearance in each output format for the documents.
+
+The excuse for going this way is, it is a waste of time to think much about appearance when working on substantive content, it is the substantive content that is relevant, not the way it looks beyond the basic informational tags - and yet you want to be able to take advantage of as many useful different ways of representing documents as are available, and for various types of output to to be/look as good as it can for each medium/format in which it is presented, (with different mediums having different focuses) and SiSU tries to achieve this from minimal markup.
+
+2~ Can the SiSU markup be used to prepare for a LaTex automatic building of an index to the work?
+
+Has not been, is of interest though the question on introducing such possibilities is how to keep them as unobtrusive as possible, and as generically relevant as possible to other output formats (which is why the focus on object numbers). Unobtrusive refers both to the markup (where there is no big problem with introducing optional extras); and, more challengingly how to minimise impact on competing ideas/interests, such allowing the addition of semantic tags which could be tied to objects, mapped against the objects that contain them, (permitting mapping and mining of content in various ways that would be largely agnostic of output format - object numbering being an attempt to move beyond output format based content locators (such as page numbers). The desire being to (be a meta markup and) maintain agnosticism as to what is being generated and in development to favor solutions of that nature. Keep bridging LaTeX, XML, SQL ... make use of objects and serialisation for mapping whether against content or meta-content (such as semantic [or additional structural] markers).
+
+2~ Can the conversion from SiSU to LaTeX be modified if we have special needs for the LaTeX, or do we need to modify the LaTeX manually?
+
+Should be possible to modify code, it is GPLv3, should be possible either to modify existing modules or write an independent module for generating bespoke latex. Generic improvements are welcome for inclusion/incorporation in the existing code base.
+
+If there are tools to generate mathematical/scientific formula from latex to images (jpg, png), the latex parser could conceivably be used to make these available to other output formats.
+
+2~ How do I create GIN or GiST index in Postgresql for use in SiSU
+
+This at present needs to be done "manually" and it is probably necessary to alter the sample search form. The following is a helpful response from one of the contributors of GiN to Postgresql Oleg Bartunov 2006-12-06:
+
+"I have tsearch2 slides which introduces tsearch2
+http://www.sai.msu.su/~megera/wiki/tsearch2slides
+
+FTS in PostgreSQL is provided by tsearch2, which should works without
+any indices (GiST or GIN) ! Indices provide performance, not functionality.
+
+In your example I'd do ( simple way, just for demo):
+
+!_ 0.
+compile, install tsearch2 and load tsearch2 into your database
+
+_1 cd contrib/tsearch2; make&&make&&install&&make installcheck; psql DB < tsearch2.sql
+
+!_ 1.
+Add column fts, which holds tsvector
+
+_1 alter table documents add column fts tsvector;
+
+!_ 2.
+Fill fts column
+
+_1 update document set fts = to_tsvector(clean);
+
+!_ 3.
+create index - just for performance !
+
+_1 create index fts_gin_idx on document using gin(fts);
+
+!_ 4.
+Run vacuum
+
+_1 vacuum analyze document;
+
+That's all.
+
+Now you can search:
+
+select lid, metadata_tid, rank_cd(fts, q,2)as rank from document, plainto_tsquery('markup syntax') q where q @@ fts order by rank desc limit 10;
+
+2~ Are there some examples of using Ferret Search with a SiSU repository?
+
+Heard good things about Ferret, but have not used it. The output directory structure and content produced by SiSU is very uniform. Have looked at a couple of other engines (hyperestraier, lucene). There it was enough to identify the files that needed to be indexed and pass them to the search indexing tool. Some Unix rune doing the job, such as:
+
+code{
+
+find /home/ralph/sisu_www -type f | \
+egrep '/sisu_www/(sisu|document_archive)/.+?.html$' | \
+egrep -v '(doc|concordance).html$' | \
+estcmd gather -sd casket -
+
+}code
+
+you would have to experiment with what gives the desired result, the file doc.html is the complete text in html (there are additional smaller html segments), and plain.txt the document as a text file. It may be possible to index the text file and return the html document.
+
+
+2~ Have you had any reports of building SiSU from tar on Mac OS 10.4?
+
+None. In the early days of its release a Mac friend built and run the ruby code part that did not rely on system calls to bits like the latex engine. That is already some years back. He was not into writing or document markup, and did it as a favour at the time. I have not followed up that thread of development.
+
+It should however be possible, much of the output relies on plain ruby, and the system commands to latex etc. could be made appropriate for the underlying OS.
+
+2~ Where is version 1?
+
+Version 1 was finally released on December 21, 2009, and largely to make a version 1 branch available as version 2 was in the pipeline with an imminent release. Most of SiSU was mature and stable long before the release of version 1.
+
+2~ What is the difference between version 1 and 2?
+
+Input and output of version 1 and 2 are largely the same with the following significant exceptions. On the input side, document headers, that is metadata and processing instructions have changed in version 2. On the output side, version 2 was introduced with EPUB documents as a possible output, and over time is likely to be developed further.
+
+Version 2 introduces a new processing layer, which relies more on the programming language Ruby's objects (and regular expressions), than version 1 does which relies on regular expressions. The thinking behind version 1 use of regular expressions was that it made it more straightforward to switch languages for processing, as many languages support regular expressions; the thinking behind version 2 was version 1 was more complicated than it need be, and since Ruby was the language used, why not make programming more straightforward, as it would be easier to develop further.
+
+Version 1 was removed with the introduction of the version 3 development branch
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_filetypes.sst b/data/doc/sisu/markup-samples/manual/en/sisu_filetypes.sst
new file mode 100644
index 00000000..d36acac0
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_filetypes.sst
@@ -0,0 +1,143 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: Filetypes
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: SiSU:manual:filetypes;electronic documents:SiSU:manual:filetypes
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+1~filetypes SiSU filetypes
+
+SiSU has plaintext and binary filetypes, and can process either type of document.
+
+2~ .sst .ssm .ssi marked up plain text
+
+SiSU documents are prepared as plain-text (utf-8) files with SiSU markup. They may make reference to and contain images (for example), which are stored in the directory beneath them _sisu/image. SiSU plaintext markup files are of three types that may be distinguished by the file extension used: regular text .sst; master documents, composite documents that incorporate other text, which can be any regular text or text insert; and inserts the contents of which are like regular text except these are marked .ssi and are not processed.
+
+SiSU processing can be done directly against a sisu documents; which may be located locally or on a remote server for which a url is provided.
+
+SiSU source markup can be shared with the command:
+
+_1 sisu -s [filename]
+
+3~ sisu text - regular files (.sst)
+
+The most common form of document in SiSU, see the section on SiSU markup.
+
+3~ sisu master files (.ssm)
+
+Composite documents which incorporate other SiSU documents which may be either regular SiSU text .sst which may be generated independently, or inserts prepared solely for the purpose of being incorporated into one or more master documents.
+
+The mechanism by which master files incorporate other documents is described as one of the headings under under SiSU markup in the SiSU manual.
+
+Note: Master documents may be prepared in a similar way to regular documents, and processing will occur normally if a .sst file is renamed .ssm without requiring any other documents; the .ssm marker flags that the document may contain other documents.
+
+Note: a secondary file of the composite document is built prior to processing with the same prefix and the suffix ._sst ~{ .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 processing. It may be however that when the resulting file is shared .ssc is an appropriate suffix to use. }~
+
+3~ sisu insert files (.ssi)
+
+Inserts are documents prepared solely for the purpose of being incorporated into one or more master documents. They resemble regular SiSU text files except they are ignored by the SiSU processor. Making a file a .ssi file is a quick and convenient way of flagging that it is not intended that the file should be processed on its own.
+
+2~ sisupod, zipped binary container (sisupod.zip, .ssp)
+
+A sisupod is a zipped SiSU text file or set of SiSU text files and any associated images that they contain (this will be extended to include sound and multimedia-files)
+
+SiSU plaintext files rely on a recognised directory structure to find contents such as images associated with documents, but all images for example for all documents contained in a directory are located in the sub-directory _sisu/image. Without the ability to create a sisupod it can be inconvenient to manually identify all other files associated with a document. A sisupod automatically bundles all associated files with the document that is turned into a pod.
+
+The structure of the sisupod is such that it may for example contain a single document and its associated images; a master document and its associated documents and anything else; or the zipped contents of a whole directory of prepared SiSU documents.
+
+The command to create a sisupod is:
+
+_1 sisu -S [filename]
+
+Alternatively, make a pod of the contents of a whole directory:
+
+_1 sisu -S
+
+SiSU processing can be done directly against a sisupod; which may be located locally or on a remote server for which a url is provided.
+
+http://www.sisudoc.org/sisu/sisu_commands
+
+http://www.sisudoc.org/sisu/sisu_manual
+
+% 1~alt Experimental Alternative Input Representations
+%
+% 2~ Alternative XML
+%
+% SiSU offers alternative XML input representations of documents as a proof of concept, experimental feature. They are however not strictly maintained, and incomplete and should be handled with care.
+%
+% !_ convert from sst to simple xml representations (sax, dom and node):
+%
+% _1 sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard]
+%
+% _1 sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard]
+%
+% _1 sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard]
+%
+% !_ convert to sst from any sisu xml representation (sax, dom and node):
+%
+% _1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
+%
+% or the same:
+%
+% _1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
+%
+% 3~ XML SAX representation
+%
+% To convert from sst to simple xml (sax) representation:
+%
+% _1 sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard]
+%
+% To convert from any sisu xml representation back to sst
+%
+% _1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
+%
+% or the same:
+%
+% _1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
+%
+% 3~ XML DOM representation
+%
+% To convert from sst to simple xml (dom) representation:
+%
+% _1 sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard]
+%
+% To convert from any sisu xml representation back to sst
+%
+% _1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
+%
+% or the same:
+%
+% _1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
+%
+% 3~ XML Node representation
+%
+% To convert from sst to simple xml (node) representation:
+%
+% _1 sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard]
+%
+% To convert from any sisu xml representation back to sst
+%
+% _1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
+%
+% or the same:
+%
+% _1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
+
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_help.sst b/data/doc/sisu/markup-samples/manual/en/sisu_help.sst
new file mode 100644
index 00000000..69535085
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_help.sst
@@ -0,0 +1,77 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: Help
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :published: 2007-08-30
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: SiSU:manual:help;electronic documents:manual:SiSU:help
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? SiSU Help
+
+1~help Help
+
+2~ SiSU Manual
+
+The most up to date information on sisu should be contained in the sisu_manual, available at:
+
+_1 http://sisudoc.org/sisu/sisu_manual/
+
+The manual can be generated from source, found respectively, either within the SiSU tarball
+or installed locally at:
+
+_1 ./data/doc/sisu/markup-samples/sisu_manual
+
+_1 /usr/share/doc/sisu/markup-samples/sisu_manual
+
+move to the respective directory and type e.g.:
+
+_1 sisu sisu_manual.ssm
+
+% The manual pages provided with SiSU are also available online, and there is an interactive help, which is being superseded by the man page, and possibly some document which contains this component.
+
+2~ SiSU man pages *~man
+
+If SiSU is installed on your system usual man commands should be available, try:
+
+_1 man sisu
+
+Most SiSU man pages are generated directly from sisu documents that are used to prepare the sisu manual, the sources files for which are located within the SiSU tarball at:
+
+_1 ./data/doc/sisu/markup-samples/sisu_manual
+
+Once installed, directory equivalent to:
+
+_1 /usr/share/doc/sisu/markup-samples/sisu_manual
+
+Available man pages are converted back to html using man2html:
+
+_1 /usr/share/doc/sisu/html/
+
+_1 ./data/doc/sisu/html
+
+An online version of the sisu man page is available here:
+
+_* {~^ various sisu man pages }http://www.jus.uio.no/sisu/man/
+
+_* {~^ sisu.1 }http://www.jus.uio.no/sisu/man/sisu.1.html
+
+2~ SiSU built-in interactive help, [discontinued]
+
+This fell out of date and has been discontinued.
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_help_sources.sst b/data/doc/sisu/markup-samples/manual/en/sisu_help_sources.sst
new file mode 100644
index 00000000..bee5ed78
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_help_sources.sst
@@ -0,0 +1,108 @@
+% SiSU insert 4.0
+
+@title: SiSU
+ :subtitle: References
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-11-12
+ :issued: 2002-11-12
+ :available: 2002-11-12
+ :published: 2007-09-16
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: SiSU:manual:help sources;electronic documents:SiSU:manual:help sources
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? SiSU Help Sources
+
+1~help_sources Help Sources
+
+2~ man pages
+
+_1 man sisu
+
+_1 man sisu-concordance
+
+_1 man sisu-epub
+
+_1 man sisu-git
+
+_1 man sisu-harvest
+
+_1 man sisu-html
+
+_1 man sisu-odf
+
+_1 man sisu-pdf
+
+_1 man sisu-pg
+
+_1 man sisu-po
+
+_1 man sisu-sqlite
+
+_1 man sisu-txt
+
+_1 man 7 sisu_complete
+
+_1 man 7 sisu_pdf
+
+_1 man 7 sisu_postgresql
+
+_1 man 7 sisu_sqlite
+
+_1 man sisu_termsheet
+
+_1 man sisu_webrick
+
+2~ sisu generated output - links to html
+
+Note SiSU documentation is prepared in SiSU and output is available in multiple formats including amongst others html, pdf, odf and epub, which may be also be accessed via the html pages~{ named index.html or more extensively through sisu_manifest.html }~
+
+3~ www.sisudoc.org
+
+http://sisudoc.org/sisu/sisu_manual/index.html
+
+_1 http://sisudoc.org/sisu/sisu_manual/index.html
+
+2~ man2html
+
+3~ locally installed
+
+file:///usr/share/doc/sisu/html/sisu.1.html
+
+_1 file:///usr/share/doc/sisu/html/sisu.1.html
+
+_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_sqlite.7.html
+
+_1 /usr/share/doc/sisu/html/sisu_webrick.1.html
+
+3~ www.jus.uio.no/sisu
+
+http://www.jus.uio.no/sisu/man/sisu.1.html
+
+_1 http://www.jus.uio.no/sisu/man/sisu.1.html
+
+_1 http://www.jus.uio.no/sisu/man/sisu_complete.7.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_sqlite.7.html
+
+_1 http://www.jus.uio.no/sisu/man/sisu_webrick.1.html
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_homepages.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_homepages.ssi
new file mode 100644
index 00000000..3d8d95d5
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_homepages.ssi
@@ -0,0 +1,39 @@
+% SiSU insert 2.0
+
+@title: SiSU
+ :subtitle: Homepages
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2007-08-28
+ :issued: 2007-08-28
+ :available: 2007-08-28
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? @title @creator
+
+:B~? Setting up of homepages
+
+1~home Homepages
+
+SiSU is about the ability to auto-generate documents. Home pages are regarded as custom built items, and are not created by SiSU. More accurately, SiSU has a default home page, which will not be appropriate for use with other sites, and the means to provide your own home page instead in one of two ways as part of a site's configuration, these being:
+
+# through placing your home page and other custom built documents in the subdirectory _sisu/home/ (this probably being the easier and more convenient option)
+
+# through providing what you want as the home page in a skin,
+
+Document sets are contained in directories, usually organised by site or subject. Each directory can/should have its own homepage. See the section on directory structure and organisation of content.
+
+2~ Home page and other custom built pages in a sub-directory
+
+Custom built pages, including the home page index.html may be placed within the configuration directory _sisu/home/ in any of the locations that is searched for the configuration directory, namely ./_sisu ; ~/_sisu ; /etc/sisu
+From there they are copied to the root of the output directory with the command:
+
+_1 sisu -CC
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_how.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_how.ssi
new file mode 100644
index 00000000..3372bcd4
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_how.ssi
@@ -0,0 +1,26 @@
+% SiSU 2.0
+
+@title: SiSU
+ :subtitle: How Does SiSU Work?
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? @title @creator
+
+:B~? Description
+
+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).
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_howto.sst b/data/doc/sisu/markup-samples/manual/en/sisu_howto.sst
new file mode 100644
index 00000000..4a23bdfe
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_howto.sst
@@ -0,0 +1,1326 @@
+% SiSU insert 4.0
+
+@title: SiSU
+ :subtitle: Technical, Howto
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-11-12
+ :issued: 2002-11-12
+ :available: 2002-11-12
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: SiSU:manual:howto;electronic documents:SiSU:manual:howto;SiSU:document:howto;sisu:document:howto
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? SiSU some technical information
+
+:C~ HowTo
+
+1~howto_help Getting Help
+
+An online manual of sorts should be available at:
+
+http://www.jus.uio.no/sisu_manual/
+
+The manual pages provided with SiSU are also available online, and there is an interactive help, which is being superseded by the man page, and possibly some document which contains this component.
+
+2~ SiSU "man" pages *~man
+
+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
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:
+
+_* {~^ various sisu man pages }http://www.jus.uio.no/sisu/man/
+
+_* {~^ sisu.1 }http://www.jus.uio.no/sisu/man/sisu.1.html
+
+_* {~^ sisu.8 }http://www.jus.uio.no/sisu/man/sisu.8.html
+
+_* {~^ sisu_webrick.1 }http://www.jus.uio.no/sisu/man/sisu_webrick.1.html
+
+2~ SiSU built-in help
+
+_1 sisu --help
+
+_1 sisu --help [subject]
+
+_2 sisu --help env [for feedback on the way your system is setup with regard to sisu]
+
+_2 sisu -V [same as above command]
+
+_2 sisu --help commands
+
+_2 sisu --help markup
+
+2~ Command Line with Flags - Batch Processing
+
+Running sisu (alone without any flags, filenames or wildcards) brings up the interactive help, as does any sisu command that is not recognised.
+
+In the data directory run sisu -mh filename or wildcard eg. "sisu -h cisg.sst" or "sisu -h *.{sst,ssm}" to produce html version of all documents.
+
+1~howto_setup Setup, initialisation
+
+2~ initialise output directory
+
+Images, css files for a document directory are copied to their respective locations in the output directory.
+
+while within your document markup/preparation directory, issue the following command
+
+_1 sisu -CC
+
+3~ Use of search functionality, an example using sqlite
+
+SiSU can populate PostgreSQL and Sqlite databases and provides a sample search form for querying these databases.
+
+This note provides an example to get you started and will use sqlite
+
+It is necessary to:
+
+(1) make sure the required dependencies have been installed
+
+(2) have a directory with sisu markup samples that is writable
+
+(3) use sisu to create a database
+
+(4) use sisu tp populate a database
+
+(5) use sisu to start the webrick (httpd) server
+
+(6) use sisu to create a search form
+
+(7) copy the search form to the cgi directory
+
+(8) open up the form in your browser
+
+(9) query the database using the search form
+
+!_ (1) make sure the required dependencies have been installed
+
+if you use Debian, the following command will install the required dependencies
+
+aptitude install sisu-sqlite
+
+!_ (2) have a directory with sisu markup samples that is writable
+
+ideally copy the sisu-examples directory to your home directory (because the directory in which you run this example should be writable)
+
+cp -rv /usr/share/doc/sisu/markup-samples/samples .
+
+you are better off installing the package sisu-markup-samples which will make the following available
+
+cp -rv /usr/share/doc/sisu/markup-samples-non-free/samples .
+
+!_ (3) use sisu to create an sqlite database
+
+within the sisu-examples directory
+
+sisu -dv createall
+
+!_ (4) use sisu tp populate a database with some text
+
+within the sisu-examples directory
+
+sisu -div free_*.sst
+
+or
+
+sisu -dv import free_*.sst debian_constitution_v1.2.sst debian_social_contract_v1.1.sst gpl2.fsf.sst
+
+!_ (5) use sisu to start the webrick (httpd) server (if it has not already been started):
+
+sisu -W
+
+!_ (6) use sisu to create a search form (for use with the webrick server, and your sample documents)
+
+within the sisu-examples directory
+
+sisu -F webserv=webrick
+
+and follow the instructions provided
+
+#here i run into a problem, you are working from a read only
+#directory..., not my usual mode of operation, to complete the example
+#the following is necessary
+sudo touch sisu_sqlite.cgi sisu_pgsql.cgi
+sudo -P chown $USER sisu_sqlite.cgi sisu_pgsql.cgi
+
+#now this should be possible:
+sisu -F webrick
+
+!_ (7) copy the search form to the cgi directory
+
+sisu -F webserv=webrick
+
+and follow the instructions provided
+
+% sudo chmod -v 755 /usr/lib/cgi-bin/sisu_sqlite.cgi
+
+!_ (8) open up the form in your browser and query it
+
+url:
+
+http://localhost:8081/cgi-bin/sisu_sqlite.cgi
+
+or as instructed by command sisu -F webrick
+
+!_ (9) query the database using the search form
+
+if there are other options in the dropdown menu select
+
+document_samples_sisu_markup
+
+and search for some text, e.g.:
+
+aim OR project
+
+_* selecting the *index* radio button gives an index of results using the object numbers
+
+_* selecting the *text* radio button gives the content of the matched paragraphs with the match highlighted
+
+!_ (10) to start again with a new database
+
+to start from scratch you can drop the database with the command
+
+sisu -dv dropall
+
+and go to step 3
+
+to get to step 3 in one step with a single command
+
+sisu -dv recreate
+
+continue subsequent steps
+
+2~ misc
+
+3~ url for output files -u -U
+
+_1 sisu -uv[and other flags] [filename/wildcard]
+
+_1 sisu -Uv [filename/wildcard]
+
+3~ toggle screen color
+
+_1 sisu -cv[and processing flags] [filename/wildcard]
+
+3~ verbose mode
+
+_1 sisu -v[and processing flags] [filename/wildcard]
+
+_1 sisu -V[and processing flags] [filename/wildcard]
+
+3~ quiet mode
+
+_1 sisu -q[and processing flags] [filename/wildcard]
+
+3~ maintenance mode
+intermediate files kept -M
+
+_1 sisu -Mv[and other flags] [filename/wildcard]
+
+3~ start the webrick server
+
+_1 sisu -W
+
+2~ remote placement of output
+
+configuration is necessary
+
+scp
+
+_1 sisu -vr[and processing flags] [filename/wildcard]
+
+rsync
+
+_1 sisu -vR[and processing flags] [filename/wildcard]
+
+1~howto_config Configuration Files
+
+Sample provided, on untarring the source tarball:
+
+_1 conf/sisu/v4/sisurc.yml
+
+_1 conf/sisu/v5/sisurc.yml
+
+and on installation under:
+
+_1 /etc/sisu/v4/sisurc.yml
+
+_1 /etc/sisu/v5/sisurc.yml
+
+The following paths are searched:
+
+_1 ./_sisu/v4/sisurc.yml or ./_sisu/v5/sisurc.yml
+
+_1 ./_sisu/sisurc.yml
+
+_1 ~/.sisu/v4/sisurc.yml or ~/.sisu/v5/sisurc.yml
+
+_1 ~/.sisu/sisurc.yml
+
+_1 /etc/sisu/v4/sisurc.yml /etc/sisu/v5/sisurc.yml
+
+_1 /etc/sisu/sisurc.yml
+
+1~howto_markup Markup
+
+See sample markup provided on
+
+http://www.sisudoc.org/
+
+http://www.jus.uio.no/sisu
+
+http://www.jus.uio.no/sisu_markup
+
+http://www.jus.uio.no/sisu/SiSU
+
+in particular for each of the document output samples provided, the source document is provided as well
+
+http://www.jus.uio.no/sisu/SiSU/examples.html
+
+on untarring the source tarball:
+
+_1 data/doc/sisu/markup-samples
+
+or the same once source is installed (or sisu-examples) under:
+
+_1 /usr/share/doc/sisu/markup-samples/
+
+and if you have sisu-markup-samples installed, under
+
+_1 data/doc/sisu/markup-samples-non-free/
+
+_1 /usr/share/doc/sisu/markup-samples-non-free/
+
+Some notes are contained within the man page, *{man sisu}* and within sisu help via the commands *{sisu help markup}* and *{sisu help headers}*
+
+SiSU is for literary and legal text, also for some social science material. In particular it does not do formula, and is not particularly suited to technical documentation. Despite the latter caveat, some notes will be provided here and added to over time:
+
+2~ Headers
+
+Headers @headername: provide information related to the document, this may relate to
+
+# how it is to be processed, such as whether headings are to be numbered, what skin is to be used and markup instructions, such as the document structure, or words to be made bold within the document
+
+# semantic information about the document including the dublin core
+
+2~ Font Face
+
+Defaults are set. You may change the face to: bold, italics, underscore, strikethrough, ...
+
+3~ Bold
+
+\@bold: [list of words that should be made bold within document]
+
+!_ bold line
+
+\!_ bold line
+
+*{ bold word or sentence }*
+
+!\{ bold word or sentence \}!
+
+*\{ bold word or sentence \}*
+
+*boldword* or !boldword!
+
+\*boldword\* or \!boldword\!
+
+3~ Italics
+
+\@italics: [list of words that should be italicised within document]
+
+/{ italicise word or sentence }/
+
+/\{ italicise word or sentence \}/
+
+/italicisedword/
+
+\/italicisedword\/
+
+3~ Underscore
+
+_{ underscore word or sentence }_
+
+_\{ underscore word or sentence \}_
+
+_underscoreword_
+
+3~ Strikethrough
+
+-{ strikethrough word or sentence }-
+
+-\{ strikethrough word or sentence \}-
+
+-strikeword-
+
+\-strikeword\-
+
+2~ Endnotes
+
+There are two forms of markup for endnotes, they cannot be mixed within the same document
+
+here~{ this is an endnote }~
+
+# preferred endnote markup
+
+here~\{ this is an endnote \}~
+
+# alternative markup equivalent, kept because it is possible to search and replace to get markup in existing texts such as Project Gutenberg
+
+here\~^
+
+^\~ this is an endote
+
+2~ Links
+
+{ SiSU }http://www.sisudoc.org
+
+code{
+
+{ SiSU }http://www.sisudoc.org
+
+}code
+
+{sisu.png }http://www.sisudoc.org
+
+code{
+
+{sisu.png }http://www.sisudoc.org
+
+}code
+
+{tux.png 64x80 }image
+
+code{
+
+{ tux.png 64x80 }image
+
+}code
+
+{~^ SiSU }http://www.sisudoc.org
+
+code{
+
+{~^ SiSU }http://www.sisudoc.org
+
+}code
+
+is equivalent to:
+
+code{
+
+{ SiSU }http://www.sisudoc.org ~{ http://www.sisudoc.org }~
+
+}code
+
+the same can be done with an image:
+
+{~^ sisu.png "SiSU" }http://www.sisudoc.org
+
+code{
+
+{~^ sisu.png "SiSU" }http://www.sisudoc.org
+
+}code
+
+2~ Number Titles
+
+Set with the header @markup:
+
+2~ Line operations
+
+Line Operations (marker placed at start of line)
+
+\!_ bold line
+
+!_ bold line
+
+\_1 indent paragraph one level
+
+_1 indent paragraph one level
+
+\_2 indent paragraph two steps
+
+_2 indent paragraph two steps
+
+\_* bullet paragraph
+
+_* bullet paragraph
+
+\# number paragraph (see headers for numbering document headings)
+
+# number paragraph (see headers for numbering document headings)
+
+\_# number paragraph level 2 (see headers for numbering document headings)
+
+_# number paragraph level 2 (see headers for numbering document headings)
+
+2~ Tables
+
+Table markup sample
+
+code{
+
+table{~h c3; 26; 32; 32;
+
+This is a table, column1
+this would become row one of column two
+column three of row one is here
+
+column one row 2
+column two of row two
+column three of row two, and so on
+
+column one row three
+and so on
+here
+
+}table
+
+}code
+
+Alternative form of table markup
+
+code{
+
+{t~h}
+ |Mon|Tue|Wed|Thu|Fri|Sat|Sun
+0 | * | * | * | * | * | * | *
+1 | * | * | * | * | | |
+2 | - | * | * | * | * | * |
+3 | - | * | * | * | * | * | *
+4 | - | | | * | * | * |
+5 | * | * | * | * | * | * | *
+
+}code
+
+2~ Grouped Text
+
+code{
+
+ 5.times { puts 'Ruby' }
+
+}code
+
+code\{
+
+code{
+
+ 5.times { puts 'Ruby' }
+
+}code
+
+\}code
+
+poem{
+
+A Limerick
+
+There was a young lady from Clyde,
+who ate a green apple and died,
+but the apple fermented inside the lamented,
+and made cider inside her inside.
+
+}poem
+
+code{
+
+poem{
+
+There was a young lady from Clyde,
+who ate a green apple and died,
+but the apple fermented inside the lamented,
+and made cider inside her inside.
+
+}poem
+
+}code
+
+2~ Composite Document
+
+To import another document, the master document or importing document should be named filename.r3 (r for require)
+
+\<\< \{ filename.sst \}
+
+\<\< \{ filename.ssi \}
+
+1~howto_appearance Change Appearance
+
+2~ Skins
+
+"Skins" are gone in v4 replaced by @make: :header: within a document, and a common shared _sisu/sisu_document_make file (which uses identical parameters to the individual documents @make: :header:)
+
+2~ CSS
+
+The appearance of html and XML related output can be changed for an ouput collection directory by prepareing and placing a new css file in one of the sisu css directories searched in the sisu configuration path. These are located at:
+
+_./_sisu/css
+
+~/.sisu/css
+
+and
+
+/etc/sisu/css
+
+The contents of the first directory found in the search path are copied to the corresponding sisu output directory with the commnd:
+
+sisu -CC
+
+The SiSU standard css files for SiSU output are:
+
+dom.css html.css html_tables.css index.css sax.css xhtml.css
+
+A document may specify its own/bespoke css file using the css header.
+
+\@css:
+
+[expand]
+
+:C~ Extracts from the README
+
+1~howto_readme README
+
+SiSU 0.55 2007w27/6 2007-07-07
+
+Homepage: http://www.sisudoc.org
+
+old homepage: http://www.jus.uio.no/sisu
+
+!_ Description
+
+SiSU is lightweight markup based document creation and publishing framework that is controlled from the command line. Prepare documents for SiSU using your text editor of choice, then use SiSU to generate various output document formats.
+
+With minimal preparation of a plain-text (UTF-8) file using its native markup-syntax, SiSU produces: plain-text, HTML, XHTML, EPUB, XML, ODF:ODT (Opendocument), LaTeX, PDF, and populates an SQL database (PostgreSQL or SQLite) in paragraph sized chunks so that document searches are done at this "atomic" level of granularity.
+
+Outputs share a common citation numbering system, and any semantic meta-data provided about the document.
+
+SiSU also provides concordance files, document content certificates and manifests of generated output.
+
+SiSU takes advantage of well established open standard ways of representing text, and provides a bridge to take advantage of the strengths of each, while remaining simple. SiSU implements across document formats a "useful common feature set" [coming from a humanities, law, and possibly social sciences perspective, rather than technical or scientific writing] ... focus is primarily on content and data integrity rather than appearance, (though outputs in the various formats are respectable).
+
+A vim syntax highlighting file and an ftplugin with folds for sisu markup is provided. Vim 7 includes syntax highlighting for SiSU.
+
+man pages, and interactive help are provided.
+
+Dependencies for various features are taken care of in sisu related packages. The package sisu-complete installs the whole of SiSU.
+
+Additional document markup samples are provided in the package sisu-markup-samples which is found in the non-free archive the licenses for the substantive content of the marked up documents provided is that provided by the author or original publisher.
+
+Homepage: http://www.sisudoc.org
+
+old homepage: http://www.jus.uio.no/sisu
+
+SiSU - simple information structuring universe, is a publishing tool, document generation and management, (and search enabling) tool primarily for literary, academic and legal published works.
+
+SiSU can be used for Internet, Intranet, local filesystem or cd publishing.
+
+SiSU can be used directly off the filesystem, or from a database.
+
+SiSU's scalability, is dependent on your hardware, and filesystem, and/or database Postgresql.
+
+Amongst it's characteristics are:
+
+_* simple mnemonoic markup style,
+
+_* the ability to produce multiple output formats, including html, structured XML, LaTeX, pdf (via LaTeX), stream to a relational database whilst retaining document structure - Postgresql and Sqlite,
+
+_* that all share a common citation system (a simple idea from which much good), possibly most exciting, the following: if fed into a relational database (as it can be automatically), the document set is searchable, with results displayed at a paragraph level, or the possibility of an indexed display of documents in which the match is found together with a hyperlinked listing for each of each paragraph in which the match is found. In any event citations using this system (with or without the relational database) are relevant for all output formats.
+
+_* it is command line driven, and can be set up on a remote server
+
+_* Documents are marked up in SiSU syntax in your favourite editor. SiSU syntax may be regarded as a type of smart ascii - which in its basic form is simpler than the most elementary html. There is currently a syntax highlighter, and folding for Vim. Syntax highlighters for other editors are welcome.
+
+Input files should be UTF-8
+
+Once set up it is simple to use.
+
+2~ Online Information, places to look
+
+http://www.sisudoc.org
+
+http://www.jus.uio.no/sisu
+
+Download Sources:
+
+_1 http://www.jus.uio.no/sisu/SiSU/download.html#current
+
+_1 http://www.jus.uio.no/sisu/SiSU/download.html#debian
+
+2~ Installation
+
+NB. Platform is Unix / Linux.
+
+3~ Debian
+
+If you use Debian use the Debian packages, check the information at:
+
+_1 http://www.jus.uio.no/sisu/SiSU/download.html#debian
+
+(A) SiSU is available directly off the Debian archives for Sid and testing. It
+should necessary only to run as root:
+
+_1 aptitude update
+
+_1 aptitude install sisu-complete
+
+(B) If there are newer versions of SiSU upstream of the Debian archives, they
+will be available by adding the following to your /etc/apt/sources.list
+
+_1 deb http://www.jus.uio.no/sisu/archive unstable main non-free
+
+_1 deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
+
+[the non-free line is for document markup samples, for which the substantive text is provided under the author or original publisher's license and which in most cases will not be debian free software guideline compliant]
+
+Then as root run:
+
+_1 aptitude update
+
+_1 aptitude install sisu-complete
+
+3~ RPM
+
+RPMs are provided though untested, they are prepared by running alien against the source package, and against the debs.
+
+They may be downloaded from:
+
+_1 http://www.jus.uio.no/sisu/SiSU/download.html#rpm
+
+3~ Source package .tgz
+
+Otherwise to install SiSU from source, check information at:
+
+_1 http://www.jus.uio.no/sisu/SiSU/download.html#current
+
+alternative modes of installation from source are provided, setup.rb (by Minero Aoki), rake (by Jim Weirich) built install file, rant (by Stefan Lang) built install file,
+
+Ruby is the essential dependency for the basic operation of SiSU
+
+1. Download the latest source (information available) from:
+
+_1 http://www.jus.uio.no/sisu/SiSU/download.html#current
+
+2. Unpack the source
+
+Note however, that additional external package dependencies, such as texlive or postgresql should you desire to use it are not taken care of for you.
+
+3~ to use setup.rb
+
+this is a three step process, in the root directory of the unpacked SiSU as root type:
+
+_1 ruby setup.rb config
+
+_1 ruby setup.rb setup
+
+as root:
+
+_1 ruby setup.rb install
+
+further information:
+
+_1 http://i.loveruby.net/en/projects/setup/
+
+_1 http://i.loveruby.net/en/projects/setup/doc/usage.html
+
+3~ to use install (prapared with "Rake")
+
+Rake must be installed on your system:
+
+_1 http://rake.rubyforge.org/
+
+_1 http://rubyforge.org/frs/?group_id=50
+
+in the root directory of the unpacked SiSU as root type:
+
+_1 rake
+
+or
+
+_1 rake base
+
+This makes use of Rake (by Jim Weirich) and the provided Rakefile
+
+For a list of alternative actions you may type:
+
+_1 rake help
+
+_1 rake -T
+
+3~ to use install (prapared with "Rant")
+
+(you may use the instructions above for rake substituting rant if rant is
+installed on your system, or you may use an independent installer created using
+rant as follows:)
+
+in the root directory of the unpacked SiSU as root type:
+
+_1 ruby ./sisu-install
+
+or
+
+_1 ruby ./sisu-install base
+
+This makes use of Rant (by Stefan Lang) and the provided Rantfile. It has been configured to do post installation setup setup configuration and generation of first test file. Note however, that additional external package dependencies, such as tetex-extra are not taken care of for you.
+
+further information:
+
+_1 http://make.rubyforge.org/
+
+_1 http://rubyforge.org/frs/?group_id=615
+
+For a list of alternative actions you may type:
+
+_1 ruby ./sisu-install help
+
+_1 ruby ./sisu-install -T
+
+2~ Dependencies
+
+Once installed see 'man 8 sisu' for some information on additional programs that sisu makes use of, and that you may need or wish to install. (this will depend on such factors as whether you want to generate pdf, whether you will be using SiSU with or without a database, ...) 'man sisu-markup-samples' may also be of interest if the sisu-markup-samples package has also been installed.
+
+The information in man 8 may not be most up to date, and it is possible that more useful information can be gleaned from the following notes taken from the Debian control file (end edited), gives an idea of additional packages that SiSU can make use of if available, (the use/requirement of some of which are interdependent for specific actions by SiSU).
+
+The following is from the debian/control file of sisu-3.0.2, which amongst other things provides the dependencies of sisu within Debian.
+
+code{
+
+Source: sisu
+Section: text
+Priority: optional
+Maintainer: SiSU Project
+Uploaders: Ralph Amissah
+Build-Depends: debhelper (>= 8)
+Standards-Version: 3.9.1
+Homepage: http://www.sisudoc.org/
+Vcs-Browser: http://git.sisudoc.org/?p=code/sisu.git
+Vcs-Git: git://git.sisudoc.org/git/code/sisu.git
+XS-Dm-Upload-Allowed: yes
+
+}code
+
+code{
+
+Package: sisu
+Architecture: all
+Depends: ${misc:Depends}, ruby (>= 1.8.2), libwebrick-ruby, rsync, unzip, zip
+Recommends:
+ sisu-pdf, sisu-sqlite, sisu-postgresql, imagemagick, keychain, librmagick-ruby,
+ librexml-ruby, openssl, openssh-client | lsh-client, tidy, vim-addon-manager
+Suggests: lv, calibre, pinfo, texinfo, trang
+Conflicts: sisu-markup-samples (<= 1.0.11)
+Replaces: sisu-markup-samples (<= 1.0.11)
+Description: documents - structuring, publishing in multiple formats and search
+ SiSU is a lightweight markup based, command line oriented, document
+ structuring, publishing and search framework for document collections.
+ .
+ With minimal preparation of a plain-text, (UTF-8) file, using its native
+ markup syntax in your text editor of choice, SiSU can generate various
+ document formats (most of which share a common object numbering system for
+ locating content), including plain text, HTML, XHTML, XML, EPUB, OpenDocument
+ text (ODF:ODT), LaTeX, PDF files, and populate an SQL database with objects
+ (roughly paragraph-sized chunks) so searches may be performed and matches
+ returned with that degree of granularity: your search criteria is met by these
+ documents and at these locations within each document. Object numbering 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. Document outputs also share semantic meta-data
+ provided.
+ .
+ SiSU also provides concordance files, document content certificates and
+ manifests of generated output.
+ .
+ A vim syntax highlighting file and an ftplugin with folds for sisu markup is
+ provided, as are syntax highlighting files for kate, kwrite, gedit and
+ diakonos. Vim 7 includes syntax highlighting for SiSU.
+ .
+ man pages, and interactive help are provided.
+ .
+ Dependencies for various features are taken care of in sisu related packages.
+ The package sisu-complete installs the whole of SiSU.
+ .
+ Additional document markup samples are provided in the package
+ sisu-markup-samples which is found in the non-free archive the licenses for
+ the substantive content of the marked up documents provided is that provided
+ by the author or original publisher.
+
+}code
+
+code{
+
+Package: sisu-complete
+Architecture: all
+Depends:
+ ${misc:Depends}, ruby (>= 1.8.2), sisu (= ${source:Version}),
+ sisu-pdf (= ${source:Version}), sisu-postgresql (= ${source:Version}),
+ sisu-sqlite (= ${source:Version})
+Description: installs all SiSU related packages
+ SiSU is a lightweight markup based document structuring, publishing and search
+ framework for document collections.
+ .
+ This package installs SiSU and related packages that enable sisu to produce
+ pdf and to populate PostgreSQL and sqlite databases.
+ .
+ See sisu for a description of the package.
+
+}code
+
+code{
+
+Package: sisu-pdf
+Architecture: all
+Depends:
+ ${misc:Depends}, sisu, texlive-latex-base, texlive-fonts-recommended,
+ texlive-latex-recommended, texlive-latex-extra, texlive-xetex, lmodern,
+ ttf-liberation
+Suggests: evince | pdf-viewer
+Description: dependencies to convert SiSU LaTeX output to pdf
+ SiSU is a lightweight markup based document structuring, publishing and search
+ framework for document collections.
+ .
+ This package enables the conversion of SiSU LaTeX output to pdf.
+
+}code
+
+code{
+
+Package: sisu-pdf
+Architecture: all
+Depends:
+ ${misc:Depends}, sisu, texlive-latex-base, texlive-fonts-recommended,
+ texlive-latex-recommended, texlive-latex-extra, texlive-xetex, lmodern,
+ ttf-liberation
+Suggests: evince | pdf-viewer
+Description: dependencies to convert SiSU LaTeX output to pdf
+ SiSU is a lightweight markup based document structuring, publishing and search
+ framework for document collections.
+ .
+ This package enables the conversion of SiSU LaTeX output to pdf.
+
+}code
+
+code{
+
+Package: sisu-postgresql
+Architecture: all
+Depends:
+ ${misc:Depends}, sisu, libdbd-pg-ruby, libdbd-pg-ruby1.8, libdbi-ruby,
+ libdbi-ruby1.8, libdbm-ruby, postgresql, libfcgi-ruby1.8 | libfcgi-ruby1.9.1
+Suggests: postgresql-contrib
+Description: SiSU dependencies for use with PostgreSQL database
+ SiSU is a lightweight markup based document structuring, publishing and search
+ framework for document collections.
+ .
+ This package enables SiSU to populate a PostgreSQL database. This is done at
+ an object/paragraph level, making granular searches of documents possible.
+ .
+ This relational database feature of SiSU is not required but provides
+ interesting possibilities, including that of granular searches of documents
+ for matching units of text, primarily paragraphs that can be displayed or
+ identified by object citation number, from which an index of documents
+ matched and each matched paragraph within them can be displayed.
+
+}code
+
+code{
+
+Package: sisu-sqlite
+Architecture: all
+Depends:
+ ${misc:Depends}, sisu, sqlite3, libsqlite3-ruby, libdbd-sqlite3-ruby,
+ libdbd-sqlite3-ruby1.8, libdbi-ruby, libdbi-ruby1.8, libdbm-ruby,
+ libfcgi-ruby1.8 | libfcgi-ruby1.9.1
+Description: SiSU dependencies for use with SQLite database
+ SiSU is a lightweight markup based document structuring, publishing and search
+ framework for document collections.
+ .
+ This package enables SiSU to populate an SQLite database. This is done at an
+ object/paragraph level, making granular searches of documents possible.
+ .
+ This relational database feature of SiSU is not required but provides
+ interesting possibilities, including that of granular searches of documents
+ for matching units of text, primarily paragraphs that can be displayed or
+ identified by object citation number, from which an index of documents
+ matched and each matched paragraph within them can be displayed.
+
+}code
+
+2~ Quick start
+
+Most of the installation should be taken care of by the aptitude or rant
+install. (The rant install if run in full will also test run the generation of
+the first document).
+
+After installation of sisu-complete, move to the document samples directory
+
+_1 cd /usr/share/doc/sisu/markup-samples/samples
+
+and run
+
+_1 sisu -3 free_as_in_freedom.rms_and_free_software.sam_williams.sst
+
+or the same:
+
+_1 sisu -NhwpoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst
+
+look at output results, see the "sisu_manifest" page created for the document
+
+or to generate an online document move to a writable directory, as the file will be downloaded there and e.g.
+
+sisu -3 http://www.jus.uio.no/sisu/src/free_culture.lawrence_lessig.sst
+
+the database stuff is extra perhaps, the latex stuff could be considered extra perhaps but neither needs to be installed for most of sisu output to work
+
+examine source document, vim has syntax support
+
+gvim free_as_in_freedom.rms_and_free_software.sam_williams.sst
+
+additional markup samples in
+
+_1 http://www.jus.uio.no/sisu/SiSU/examples.html
+
+For help
+
+_1 man sisu
+
+or
+
+_1 sisu --help
+
+e.g.
+
+for the way sisu "sees/maps" your system
+
+_1 sisu --help env
+
+for list of commands and so on
+
+_1 sisu --help commands
+
+2~ Configuration files
+
+The default configuration/setup is contained within the program and is altered by configuration settings in /etc/[sisu version]/sisurc.yml or in ~/.sisu/sisurc.yml
+
+_* configuration file - a yaml file
+
+_1 /etc/sisu/[sisu version]/sisurc.yml
+
+_1 ~/.sisu/sisurc.yml
+
+_* directory structure - setting up of output and working directory.
+
+_* additional software - eg. Tex and LaTeX (tetex, tetex-base, tetex-extra on Debian), Postgresql, [sqlite], trang, tidy, makeinfo, ... none of which are required for basic html or XML processing.
+
+_* if you use Vim as editor there is a syntax highlighter and fold resource config file for SiSU. I hope more syntax highlighters follow.
+
+There are post installation steps (which are really part of the overall installation)
+
+sisu -C in your marked up document directory, should do some auto-configuring provided you have the right permissions for the output directories. (and provided the output directories have already been specified if you are not using the defaults).
+
+2~ Use General Overview
+
+Documents are marked up in SiSU syntax and kept in an ordinary text editable file, named with the suffix .sst, or .ssm
+
+Marked up SiSU documents are usually kept in a sub-directory of your choosing
+
+use the interactive help and man pages
+
+_1 sisu --help
+
+_1 man sisu
+
+2~ Help
+
+interactive help described below, or man page:
+
+_1 man sisu
+
+_1 man 8 sisu
+
+'man sisu_markup-samples' [if the sisu-markup-samples package is also installed]
+
+Once installed an interactive help is available typing 'sisu' (without) any flags, and select an option:
+
+_1 sisu
+
+alternatively, you could type e.g.
+
+_1 sisu --help commands
+
+_1 sisu --help env
+
+_1 sisu --help headers
+
+_1 sisu --help markup
+
+_1 sisu --help headings
+
+etc.
+
+for questions about mappings, output paths etc.
+
+_1 sisu --help env
+
+_1 sisu --help path
+
+_1 sisu --help directory
+
+2~ Directory Structure
+
+Once installed, type:
+
+_1 sisu --help env
+
+or
+
+_1 sisu -V
+
+2~ Configuration File
+
+The defaults can be changed via SiSU's configure file sisurc.yml which the program expects to find in ./_sisu ~/.sisu or /etc/sisu (searched in that order, stopping on the first one found)
+
+2~ Markup
+
+See man pages.
+
+_1 man sisu
+
+_1 man 8 sisu
+
+Once installed there is some information on SiSU Markup in its help:
+
+_1 sisu --help markup
+
+and
+
+_1 sisu --help headers
+
+Sample marked up document are provided with the download tarball in the directory:
+
+_1 ./data/doc/sisu/markup-samples/
+
+These are installed on the system usually at:
+
+_1 /usr/share/doc/sisu/markup-samples/
+
+More markup samples are available in the package sisu-markup-samples, which if installed should be available at:
+
+_1 /usr/share/doc/sisu/markup-samples-non-free/
+
+Many more are available online off:
+
+_1 http://www.jus.uio.no/sisu/SiSU/examples.html
+
+2~ Additional Things
+
+There is syntax support for some editors provided (together with a README file) in
+
+_1 ./data/sisu/v4/conf/editor-syntax-etc
+
+usually installed to:
+
+_1 /usr/share/sisu/v4/conf/editor-syntax-etc
+
+2~ License
+
+License: GPL 3 or later see the copyright file in
+
+_1 ./data/doc/sisu
+
+usually installed to:
+
+_1 /usr/share/doc/sisu
+
+2~ SiSU Standard
+
+SiSU uses:
+
+_* Standard SiSU markup syntax,
+
+_* Standard SiSU meta-markup syntax, and the
+
+_* Standard SiSU object citation numbering and system
+
+© Ralph Amissah 1997, current 2006 All Rights Reserved.
+
+_* however note the License section
+
+CHANGELOG
+
+_1 ./CHANGELOG
+
+and see
+
+_1 http://www.jus.uio.no/sisu/SiSU/changelog.html
+
+_1 http://www.jus.uio.no/sisu/SiSU/changelog_markup_samples.html
+
+:C~ Extracts from man 8 sisu
+
+1~howto_setup_post_installation Post Installation Setup
+
+2~ Post Installation Setup - Quick start
+
+After installation of sisu-complete, move to the document samples directory,
+
+_1 cd /usr/share/doc/sisu/markup-samples/samples
+
+[this is not where you would normally work but provides sample documents for
+testing, you may prefer instead to copy the contents of that directory to a local
+directory before proceeding]
+
+and in that directory, initialise the output directory with the command
+
+_1 sisu -CC
+
+then run:
+
+_1 sisu -1 free_as_in_freedom.rms_and_free_software.sam_williams.sst
+
+or the same:
+
+_1 sisu -NhwpoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst
+
+look at output results, see the "sisu_manifest" page created for the document
+
+for an overview of your current sisu setup, type:
+
+_1 sisu --help env
+
+or
+
+_1 sisu -V
+
+To generate a document from a remote url accessible location move to a writable directory, (create a work directory and cd into it) as the file will be downloaded there and e.g.
+
+_1 sisu -1 http://www.jus.uio.no/sisu/src/gpl.fsf.sst
+
+_1 sisu -3 http://www.jus.uio.no/sisu/src/free_culture.lawrence_lessig.sst
+
+examine source document, vim has syntax highlighting support
+
+gvim free_as_in_freedom.rms_and_free_software.sam_williams.sst
+
+additional markup samples in
+
+_1 http://www.jus.uio.no/sisu/SiSU/examples.html
+
+it should also be possible to run sisu against sisupods (prepared zip files, created by running the command sisu -S [filename]), whether stored locally or remotely.
+
+_1 sisu -3 http://www.jus.uio.no/sisu/pod/free_culture.lawrence_lessig.sst.zip
+
+_1 sisu -3 --trust http://www.jus.uio.no/sisu/pod/free_culture.lawrence_lessig.sst.zip
+
+For help
+
+_1 man sisu
+
+_1 sisu --help
+
+_1 sisu --help env
+for the way sisu "sees/maps" your system
+
+_1 sisu --help commands
+for list of commands and so on
+
+2~ Document markup directory
+
+% B. Generate a (local) document from a markup/work directory.
+
+Perhaps the easiest way to begin is to create a directory for sisu marked up documents within your home directory, and copy the file structure (and document samples) provided in the document sample directory:
+
+_1 mkdir ~/sisu_test
+
+_1 cd ~/sisu_test
+
+_1 cp -a /usr/share/doc/sisu/markup-samples/samples/* ~/sisu_test/.
+
+better if you have installed sisu-markup-samples
+
+_1 cp -a /usr/share/doc/sisu/markup-samples-non-free/samples/* ~/sisu_test/.
+
+% !_ Tip:
+% the markup syntax examples may be of interest
+%
+% _1 http://www.jus.uio.no/sisu/sample/
+
+!_ Tip:
+
+_1 sisu -U [sisu markup filename]
+
+should printout the different possible outputs and where sisu would place them.
+
+!_ Tip:
+if you want to toggle ansi color add
+
+_1 c
+
+to your flags.
+
+3~ Configuration files
+
+SiSU configuration file search path is:
+
+_1 ./_sisu/sisurc.yaml
+
+_1 ~/.sisu/sisurc.yaml
+
+_1 /etc/sisu/sisurc.yaml
+
+.\"%% Debian Installation Note
+
+3~ Debian INSTALLATION Note
+
+It is best you see
+
+_1 http://www.jus.uio.no/sisu/SiSU/download.html#debian
+
+for up the most up to date information.
+
+notes taken from the Debian control file (end edited), gives an idea of additional packages that SiSU can make use of if available, (the use/requirement of some of which are interdependent for specific actions by SiSU):
+
+Package: sisu
+
+SiSU is a lightweight markup based, command line oriented, document structuring, publishing and search framework for document collections.
+
+With minimal preparation of a plain-text, (UTF-8) file, using its native markup syntax in your text editor of choice, SiSU can generate various document formats (most of which share a common object numbering system for locating content), including plain text, HTML, XHTML, XML, OpenDocument text (ODF:ODT), EPUB, LaTeX, PDF files, and populate an SQL database with objects (roughly paragraph-sized chunks) so searches may be performed and matches returned with that degree of granularity: your search criteria is met by these documents and at these locations within each document. Object numbering 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. Document outputs also share semantic meta-data provided.
+
+SiSU also provides concordance files, document content certificates and manifests of generated output.
+
+A vim syntax highlighting file and an ftplugin with folds for sisu markup is provided, as are syntax highlighting files for kate, kwrite, gedit and diakonos. Vim 7 includes syntax highlighting for SiSU.
+
+man pages, and interactive help are provided.
+
+Dependencies for various features are taken care of in sisu related packages. The package sisu-complete installs the whole of SiSU.
+
+Additional document markup samples are provided in the package sisu-markup-samples which is found in the non-free archive the licenses for the substantive content of the marked up documents provided is that provided by the author or original publisher.
+
+Homepage: http://www.sisudoc.org
+
+old homepage: http://www.jus.uio.no/sisu
+
+3~ Document Resource Configuration
+
+!_ sisu
+resource configuration information is obtained from sources (where they exist):
+
+_1 ~/.sisu/sisurc.yaml
+
+_1 /etc/sisu/[sisu version]/sisurc.yaml
+
+_1 sisu program defaults
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_installation.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_installation.ssi
new file mode 100644
index 00000000..f908bb6e
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_installation.ssi
@@ -0,0 +1,368 @@
+% SiSU insert 2.0
+
+@title: SiSU
+ :subtitle: Installation
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-11-12
+ :issued: 2002-11-12
+ :available: 2002-11-12
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? SiSU Installation notes
+
+:C~ Installation
+
+1~installation Installation
+
+See the {~^ download pages }http://www.jus.uio.no/sisu/SiSU/download.html for information related to installation.
+
+2~ Debian
+
+SiSU is developed on Debian, and packages are available for Debian that take care of the dependencies encountered on installation.
+
+The package is divided into the following components:
+
+_1 *sisu*, the base code, (the main package on which the others depend), without any dependencies other than ruby (and for convenience the ruby webrick web server), this generates a number of types of output on its own, other packages provide additional functionality, and have their dependencies
+
+_1 *sisu-complete*, a dummy package that installs the whole of greater sisu as described below, apart from sisu-examples
+
+_1 *sisu-pdf*, dependencies used by sisu to produce pdf from LaTeX generated
+
+_1 *sisu-postgresql*, dependencies used by sisu to populate postgresql database (further configuration is necessary)
+
+_1 *sisu-remote*, dependencies used to place sisu output on a remote server (further configuration is necessary)
+
+_1 *sisu-sqlite*, dependencies used by sisu to populate sqlite database
+
+_1 *sisu-markup-samples*, sisu markup samples and other miscellany (under Debian Free Software Guidelines non-free)
+
+SiSU is available off { Debian Unstable and Testing }http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&subword=1&version=all&release=all&keywords=sisu&sourceid=mozilla-search ~{ http://packages.qa.debian.org/s/sisu.html }~ install it using apt-get, aptitude or alternative Debian install tools. SiSU is currently comprised of eight packages. *~apt-get
+
+Initial packaging is done here and to get the latest version of SiSU available you may add the following line(s) to your sources list: *~sources.list
+
+code{
+
+#/etc/apt/sources.list
+
+deb http://www.jus.uio.no/sisu/archive unstable main non-free
+deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
+
+}code
+
+The non-free section is for sisu markup samples provided, which contain authored works the substantive text of which cannot be changed, and which as a result do not meet the debian free software guidelines.
+
+On Debian there is little more to know beyond how to install software on Debian using apt, aptitude or synaptic.
+
+code{
+
+#Using aptitude:
+
+ aptitude update
+
+ aptitude install sisu-complete sisu-markup-samples
+
+}code
+
+code{
+
+Using apt-get
+
+ apt-get update
+
+ apt get install sisu-complete sisu-examples
+
+}code
+
+2~ Other Unix / Linux
+
+A source tarball or an rpms built using alien are available, (however dependencies have not been tested). SiSU is first packaged and tested with dependency handling for Debian.~{ Notes on dependencies are provided in the section that follows }~ Information on dependencies configured for Debian is provided as this may be of assistance.
+
+3~ source tarball
+
+!_ installation with provided install script
+
+To install SiSU, in the root directory of the unpacked SiSU _{as root type}_:~{ This makes use of rant and the provided Rantfile. Note however, that additional external package dependencies, such as tetex-extra are not taken care of for you. }~
+
+_1 ruby install
+
+Once installed see man 8 sisu for information on additional programs that sisu makes use of.
+
+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/
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/
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
+
+To install as root type:
+
+_1 ruby install
+
+For a minimal install type:
+
+_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
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
+
+!_ installation of rpm
+
+The RPM is generated from the source file using Alien.~{ http://www.kitenet.net/programs/alien/ }~ Dependencies are not handled, not even that of the essential Ruby.
+
+1~install_dependencies_and_notes SiSU Components, Dependencies and Notes
+
+The dependency lists are from the Debian control file for SiSU version 0.36, and may assist in building SiSU on other distributions.
+
+2~ sisu
+
+_* the base code, (the main package on which the others depend), without any dependencies other than ruby (and for convenience the ruby webrick web server), this generates a number of types of output on its own, other packages provide additional functionality, and have their dependencies
+
+*Depends:* on ruby (>=1.8.2), libwebrick-ruby
+
+*Recommends:* sisu-pdf, sisu-sqlite, sisu-postgresql, sisu-examples, librmagick-ruby, trang, tidy, libtidy, librexml-ruby, zip, unzip, openssl
+
+initialise directory
+
+_1 sisu -CC
+
+html
+
+_1 sisu -hv [filename/wildcard]
+
+_1 sisu -Hv [filename/wildcard]
+
+LaTeX (but sisu-pdf dependencies required to convert that to pdf)
+
+_1 sisu -pv [filename/wildcard]
+
+plain text Unix with footnotes
+
+_1 sisu -av [filename/wildcard]
+
+plain text Dos with footnotes
+
+_1 sisu -Av [filename/wildcard]
+
+plain text Unix with endnotes
+
+_1 sisu -ev [filename/wildcard]
+
+plain text Dos with endnotes
+
+_1 sisu -Ev [filename/wildcard]
+
+openoffice odt
+
+_1 sisu -ov [filename/wildcard]
+
+xhtml
+
+_1 sisu -bv [filename/wildcard]
+
+XML SAX
+
+_1 sisu -xv [filename/wildcard]
+
+XML DOM
+
+_1 sisu -Xv [filename/wildcard]
+
+wordmap (a rudimentary index of content)
+
+_1 sisu -wv [filename/wildcard]
+
+document content certificate
+
+_1 sisu -Nv [filename/wildcard]
+
+placement of sourcefile in output directory
+
+_1 sisu -sv [filename/wildcard]
+
+creation of source tarball with images, and placement of source tarball in ouput directory
+
+_1 sisu -Sv [filename/wildcard]
+
+manifest of output produced (polls output directory and provides links to existing output)
+
+_1 sisu -yv [filename/wildcard]
+
+url for output files -u -U
+
+_1 sisu -uv[and other flags] [filename/wildcard]
+
+_1 sisu -Uv [filename/wildcard]
+
+toggle screen colour
+
+_1 sisu -cv[and processing flags] [filename/wildcard]
+
+verbose mode
+
+_1 sisu -v[and processing flags] [filename/wildcard]
+
+_1 sisu -V[and processing flags] [filename/wildcard]
+
+quiet mode
+
+_1 sisu -q[and processing flags] [filename/wildcard]
+
+maintenance mode, intermediate files kept -M
+
+_1 sisu -Mv[and other flags] [filename/wildcard]
+
+[the -v is for verbose]
+
+start the webrick server
+
+_1 sisu -W
+
+2~ sisu-complete
+
+_* a dummy package that installs the whole SiSU, apart from sisu-examples
+
+*Depends:* ruby (>=1.8.2), sisu, sisu-pdf, sisu-postgresql, sisu-remote, sisu-sqlite
+
+*Recommends:* sisu-examples
+
+2~ sisu-examples
+
+_* installs sisu markup samples and other miscelleny
+
+*Depends:* sisu
+
+2~ sisu-pdf
+
+_* dependencies used by sisu to produce pdf from LaTeX generated
+
+*Depends:* sisu, tetex-bin, tetex-extra, latex-ucs
+
+*Suggests:* evince, xpdf
+
+converts sisu LaTeX produced to pdf
+
+_1 sisu -pv [filename/wildcard]
+
+[the -v is for verbose]
+
+2~ sisu-postgresql
+
+_* dependencies used by sisu to populate postgresql database (further configuration is necessary)
+
+*Depends:* sisu, postgresql-8.1, libdbi-ruby, libdbm-ruby, libdbd-pg-ruby
+
+*Suggests:* pgaccess, libdbd-pgsql, postgresql-contrib-8.1
+
+installs dependencies for sisu to work with and populate postgresql database
+
+create database
+
+_1 sisu -Dv createall
+
+drop database
+
+_1 sisu -Dv dropall
+
+import content
+
+_1 sisu -Div [filename/wildcard]
+
+_1 sisu -Dv import [filename/wildcard]
+
+update content
+
+_1 sisu -Duv [filename/wildcard]
+
+_1 sisu -Dv update [filename/wildcard]
+
+[the -v is for verbose]
+
+The following are available without installation of the sisu-postgresql component, but are of interest in this context
+
+generate a sample database query form for use with webserver on port 80
+
+_1 sisu -F
+
+or for use with webrick server
+
+_1 sisu -F webrick
+
+to start webrick server
+
+_1 sisu -W
+
+2~ sisu-remote
+
+_* dependencies used to place sisu output on a remote server (further configuration is necessary)
+
+scp
+
+_1 sisu -vr[and processing flags] [filename/wildcard]
+
+rsync
+
+_1 sisu -vR[and processing flags] [filename/wildcard]
+
+[the -v is for verbose]
+
+*Depends:* sisu, rsync, openssh-client|lsh-client, keychain
+
+2~ sisu-sqlite
+
+_* dependencies used by sisu to populate sqlite database
+
+*Depends:* sisu, sqlite, libdbi-ruby, libdbm-ruby, libdbd-sqlite-ruby
+
+*Suggests:* libdbd-sqlite
+
+installs dependencies for sisu to work with and populate sqlite database
+
+create database
+
+_1 sisu -dv createall
+
+drop database
+
+_1 sisu -dv dropall
+
+update content
+
+_1 sisu -div [filename/wildcard]
+
+_1 sisu -dv import [filename/wildcard]
+
+update content
+
+_1 sisu -duv [filename/wildcard]
+
+_1 sisu -dv update [filename/wildcard]
+
+[the -v is for verbose]
+
+The following are available without installation of the sisu-sqlite component, but are of interest in this context
+
+generate a sample database query form for use with webserver on port 80
+
+_1 sisu -F
+
+or for use with webrick server
+
+_1 sisu -F webrick
+
+to start webrick server
+
+_1 sisu -W
+
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_interesting_to_whom.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_interesting_to_whom.ssi
new file mode 100644
index 00000000..750c46ea
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_interesting_to_whom.ssi
@@ -0,0 +1,32 @@
+% SiSU 2.0
+
+@title: SiSU
+ :subtitle: Who Might Be Interested?
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :published: 2007-09-16
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? @title @creator
+
+:B~? Who might SiSU interest?
+
+1~sisu_interest Who might be interested in the SiSU feature set?
+
+SiSU is most likely to be of interest to people who are working with medium to large volumes of published texts that would like to have the presented in a uniform way that is searchable (either using sisu database integration or an appropriate indexing tool), with the possibility of multiple alternative output formats that may be added to and upgraded/updated over time. SiSU should be of interest to institutions/ organisations/ governments/ individuals with document collections and some technical knowhow that are interested in:
+
+_* long term maintenance and reducing downstream/future costs of maintaining those document sets for which SiSU is suited.
+
+_* the ability to output multiple standard format outputs for various purposes.
+
+_* the implications for search offered
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_introduction.sst b/data/doc/sisu/markup-samples/manual/en/sisu_introduction.sst
new file mode 100644
index 00000000..8978ace6
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_introduction.sst
@@ -0,0 +1,55 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: Introduction
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2011
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? What is SiSU?
+
+:C~? Description
+
+1~sisu_intro Introduction - What is SiSU?
+
+SiSU is a framework for document structuring, publishing (in multiple open standard formats) 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 (including the population of sql databases) 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 (GPLv3). Its use case for development is work with medium to large document sets and cope with evolving document formats/ representation technologies. Documents are prepared once, and generated as need be to update the technical presentation or add additional output formats. Various output formats (including search related output) share a common mechanism for cross-output-format citation.
+
+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, EPUB, ODT (Open Document Format text), LaTeX, landscape and portrait PDF, 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.
+
+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 (to take advantage of the strengths of different ways of representing documents) various standard open output formats including plain text, HTML, XHTML, XML, EPUB, ODT, 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, 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. }~ the different forms of output requested.
+
+SiSU works with an abstraction of the document based on its structure which is comprised of its headings~{ the different heading levels }~ and objects~{ units of text, primarily paragraphs and headings, also any tables, poems, code-blocks }~, 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 basis for citing material within a document across the different output format types. This is significant as page numbers are not well suited to the digital age, in web publishing, changing a browser's default font or using a different browser can mean that text will appear on a different page; and publishing in different formats, html, landscape and portrait pdf etc. again page numbers are not useful to cite text. Dealing with documents at an object level together with object numbering also has implications for search that SiSU is able to take advantage of.
+
+One of the challenges of maintaining documents is to keep them in a format that allows use of them independently of proprietary platforms. Consider issues related to 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 producing documents in multiple non-proprietary open formats including HTML, EPUB,~{ An open standard format for e-books }~ ODT,~{ Open Document Format (ODF) text }~ PDF~{ Specification submitted by Adobe to ISO to become a full open ISO specification
http://www.linux-watch.com/news/NS7542722606.html }~ ODF,~{ ISO standard 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 GPLv3 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 when it became an ISO standard for office applications and the archival of documents), EPUB was introduced in 2009; and allows the technical representations 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 thesauri, 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.sisudoc.org/
+
+http://www.jus.uio.no/sisu
+
+% SiSU is a way of preparing, publishing, managing and searching documents.
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_manual.ssm b/data/doc/sisu/markup-samples/manual/en/sisu_manual.ssm
new file mode 100644
index 00000000..90e8a323
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_manual.ssm
@@ -0,0 +1,96 @@
+% SiSU master 4.0
+
+@title: SiSU
+ :subtitle: Manual
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2008-07-21
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: SiSU:manual;electronic documents:SiSU:manual
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~ @title @creator
+
+:B~ What is SiSU?
+
+<< sisu_introduction.sst
+
+<< sisu_how.ssi
+
+<< sisu_short_feature_summary.ssi
+
+<< sisu_help.sst
+
+% :B~? SiSU Commands
+
+<< sisu_commands.sst
+
+% :B~? SiSU Markup
+
+<< sisu_markup.sst
+
+<< sisu_filetypes.sst
+
+% :B~? SiSU Configuration
+
+<< sisu_config.ssi
+
+<< sisu_css.ssi
+
+<< sisu_content_directories.ssi
+
+<< sisu_homepages.ssi
+
+% :B~? SiSU Output and Markup Examples
+
+<< sisu_examples.ssi
+
+<< sisu_output_overview.sst
+
+<< sisu_search_intro.ssi
+
+<< sisu_sql.ssi
+
+<< sisu_postgresql.sst
+
+<< sisu_sqlite.sst
+
+<< sisu_search_cgi.ssi
+
+<< sisu_webrick.sst
+
+<< sisu_remote.sst
+
+% :B~? SiSU Download and Installation
+
+<< sisu_download.ssi
+
+<< sisu_installation.ssi
+
+<< sisu_quickstart.sst
+
+% :B~? SiSU Howto and FAQ
+
+<< sisu_howto.sst
+
+<< sisu_faq.sst
+
+<< sisu_interesting_to_whom.ssi
+
+<< sisu_work_needed_and_wishlist.ssi
+
+<< sisu_syntax_highlighting.sst
+
+<< sisu_help_sources.sst
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_markup.sst b/data/doc/sisu/markup-samples/manual/en/sisu_markup.sst
new file mode 100644
index 00000000..69293637
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_markup.sst
@@ -0,0 +1,1312 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: Markup
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :published: 2008-05-22
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: electronic documents:SiSU:document:markup;SiSU:document:markup;SiSU:document:markup;SiSU:manual:markup;electronic documents:SiSU:manual:markup
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? SiSU Markup
+
+1~markup Introduction to SiSU Markup~{ 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. }~
+
+2~ Summary
+
+SiSU source documents are plaintext (UTF-8)~{ files should be prepared using UTF-8 character encoding }~ files
+
+All paragraphs are separated by an empty line.
+
+Markup is comprised of:
+
+_* at the top of a document, the document header made up of semantic meta-data about the document and if desired additional processing instructions (such an instruction to automatically number headings from a particular level down)
+
+_* followed by the prepared substantive text of which the most important single characteristic is the markup of different heading levels, which define the primary outline of the document structure. Markup of substantive text includes:
+
+_1* heading levels defines document structure
+
+_1* text basic attributes, italics, bold etc.
+
+_1* grouped text (objects), which are to be treated differently, such as code blocks or poems.
+
+_1* footnotes/endnotes
+
+_1* linked text and images
+
+_1* paragraph actions, such as indent, bulleted, numbered-lists, etc.
+
+Some interactive help on markup is available, by typing sisu and selecting markup or sisu --help markup
+
+To check the markup in a file:
+
+_1 sisu --identify [filename].sst
+
+For brief descriptive summary of markup history
+
+_1 sisu --query-history
+
+or if for a particular version:
+
+_1 sisu --query-0.38
+
+2~ Markup Examples
+
+3~ Online
+
+Online markup examples are available together with the respective outputs produced from http://www.jus.uio.no/sisu/SiSU/examples.html or from http://www.jus.uio.no/sisu/sisu_examples/
+
+There is of course this document, which provides a cursory overview of sisu markup and the respective output produced: http://www.jus.uio.no/sisu/sisu_markup/
+
+an alternative presentation of markup syntax: /usr/share/doc/sisu/on_markup.txt.gz
+
+3~ Installed
+
+With SiSU installed sample skins may be found in: /usr/share/doc/sisu/markup-samples (or equivalent directory) and if sisu-markup-samples is installed also under: /usr/share/doc/sisu/markup-samples-non-free
+
+1~headers Markup of Headers
+
+Headers contain either: semantic meta-data about a document, which can be used by any output module of the program, or; processing instructions.
+
+Note: the first line of a document may include information on the markup version used in the form of a comment. Comments are a percentage mark at the start of a paragraph (and as the first character in a line of text) followed by a space and the comment:
+
+code{
+
+% this would be a comment
+
+}code
+
+2~ Sample Header
+
+This current document is loaded by a master document that has a header similar to this one:
+
+code{
+
+% SiSU master 4.0
+
+@title: SiSU
+ :subtitle: Manual
+
+@creator:
+ :author: Amissah, Ralph
+
+@publisher: [publisher name]
+
+@rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3
+
+@classify:
+ :topic_register: SiSU:manual;electronic documents:SiSU:manual
+ :subject: ebook, epublishing, electronic book, electronic publishing,
+ electronic document, electronic citation, data structure,
+ citation systems, search
+
+% used_by: manual
+
+@date:
+ :published: 2008-05-22
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2010-03-03
+
+@make:
+ :num_top: 1
+ :breaks: new=C; break=1
+ :bold: /Gnu|Debian|Ruby|SiSU/
+ :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
+ :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
+ :manpage: name=sisu - documents: markup, structuring, publishing in multiple standard formats, and search;
+ synopsis=sisu [-abcDdeFhIiMmNnopqRrSsTtUuVvwXxYyZz0-9] [filename/wildcard ]
+ . sisu [-Ddcv] [instruction]
+ . sisu [-CcFLSVvW]
+ . sisu --v4 [operations]
+ . sisu --v3 [operations]
+
+@links:
+ { SiSU Homepage }http://www.sisudoc.org/
+ { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/
+ { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html
+ { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html
+ { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html
+ { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary
+ { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/
+ { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html
+ { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org
+ { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
+
+}code
+
+2~ Available Headers
+
+Header tags appear at the beginning of a document and provide meta information on the document (such as the Dublin Core), or information as to how the document as a whole is to be processed. All header instructions take the form @headername: or on the next line and indented by once space :subheadername: All Dublin Core meta tags are available
+
+!_ @identifier:
+information or instructions
+
+where the "identifier" is a tag recognised by the program, and the "information" or "instructions" belong to the tag/identifier specified
+
+Note: a header where used should only be used once; all headers apart from @title: are optional; the @structure: header is used to describe document structure, and can be useful to know.
+
+This is a sample header
+
+% (Dublin Core in fuschia, other information headers in cyan, markup instructions in red):
+
+code{
+
+% SiSU 2.0 [declared file-type identifier with markup version]
+
+}code
+
+code{
+
+@title: [title text] [this header is the only one that is mandatory]
+ :subtitle: [subtitle if any]
+ :language: English
+
+}code
+
+code{
+
+@creator:
+ :author: [Lastname, First names]
+ :illustrator: [Lastname, First names]
+ :translator: [Lastname, First names]
+ :prepared_by: [Lastname, First names]
+
+}code
+
+code{
+
+@date:
+ :published: [year or yyyy-mm-dd]
+ :created: [year or yyyy-mm-dd]
+ :issued: [year or yyyy-mm-dd]
+ :available: [year or yyyy-mm-dd]
+ :modified: [year or yyyy-mm-dd]
+ :valid: [year or yyyy-mm-dd]
+ :added_to_site: [year or yyyy-mm-dd]
+ :translated: [year or yyyy-mm-dd]
+
+}code
+
+code{
+
+@rights:
+ :copyright: Copyright (C) [Year and Holder]
+ :license: [Use License granted]
+ :text: [Year and Holder]
+ :translation: [Name, Year]
+ :illustrations: [Name, Year]
+
+}code
+
+code{
+
+@classify:
+ :topic_register: SiSU:markup sample:book;book:novel:fantasy
+ :type:
+ :subject:
+ :description:
+ :keywords:
+ :abstract:
+ :loc: [Library of Congress classification]
+ :dewey: [Dewey classification
+
+}code
+
+code{
+
+@identify:
+ :isbn: [ISBN]
+ :oclc:
+
+}code
+
+
+code{
+
+@links: { SiSU }http://www.sisudoc.org
+ { FSF }http://www.fsf.org
+
+}code
+
+code{
+
+@make:
+ :num_top: 1
+ :headings: [text to match for each level
+ (e.g. PART; Chapter; Section; Article; or another: none; BOOK|FIRST|SECOND; none; CHAPTER;)
+ :breaks: new=:C; break=1
+ :promo: sisu, ruby, sisu_search_libre, open_society
+ :bold: [regular expression of words/phrases to be made bold]
+ :italics: [regular expression of words/phrases to italicise]
+ :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
+ :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
+
+}code
+
+code{
+
+@original:
+ :language: [language]
+
+}code
+
+code{
+
+@notes:
+ :comment:
+ :prefix: [prefix is placed just after table of contents]
+
+}code
+
+% header ends here, NB only @title: is mandatory [this would be a comment]
+% NOTE: headings/levels below refer to 0.38 expermental markup (a conversion script provided in sisu-examples, modify.rb makes conversion between 0.37 and 0.38 markup simple)
+
+1~ Markup of Substantive Text
+
+2~heading_levels Heading Levels
+
+Heading levels are :A~ ,:B~ ,:C~ ,1~ ,2~ ,3~ ... :A - :C being part / section headings, followed by other heading levels, and 1 -6 being headings followed by substantive text or sub-headings. :A~ usually the title :A~? conditional level 1 heading (used where a stand-alone document may be imported into another)
+
+!_ :A~ [heading text]
+Top level heading [this usually has similar content to the title @title: ]
+NOTE: the heading levels described here are in 0.38 notation, see heading
+
+!_ :B~ [heading text]
+Second level heading [this is a heading level divider]
+
+!_ :C~ [heading text]
+Third level heading [this is a heading level divider]
+
+!_ 1~ [heading text]
+Top level heading preceding substantive text of document or sub-heading 2, the heading level that would normally be marked 1. or 2. or 3. etc. in a document, and the level on which sisu by default would break html output into named segments, names are provided automatically if none are given (a number), otherwise takes the form 1~my_filename_for_this_segment
+
+!_ 2~ [heading text]
+Second level heading preceding substantive text of document or sub-heading 3 , the heading level that would normally be marked 1.1 or 1.2 or 1.3 or 2.1 etc. in a document.
+
+!_ 3~ [heading text]
+Third level heading preceding substantive text of document, that would normally be marked 1.1.1 or 1.1.2 or 1.2.1 or 2.1.1 etc. in a document
+
+code{
+
+1~filename level 1 heading,
+
+% the primary division such as Chapter that is followed by substantive text, and may be further subdivided (this is the level on which by default html segments are made)
+
+}code
+
+2~ Font Attributes
+
+!_ markup example:
+
+code{
+
+normal text, *{emphasis}*, !{bold text}!, /{italics}/, _{underscore}_, "{citation}",
+^{superscript}^, ,{subscript},, +{inserted text}+, -{strikethrough}-, #{monospace}#
+
+normal text
+
+*{emphasis}* [note: can be configured to be represented by bold, italics or underscore]
+
+!{bold text}!
+
+/{italics}/
+
+_{underscore}_
+
+"{citation}"
+
+^{superscript}^
+
+,{subscript},
+
++{inserted text}+
+
+-{strikethrough}-
+
+#{monospace}#
+
+}code
+
+!_ resulting output:
+
+normal text, *{emphasis}*, !{bold text}!, /{italics}/, _{underscore}_, "{citation}",
+^{superscript}^, ,{subscript},, +{inserted text}+, -{strikethrough}-, #{monospace}#
+
+normal text
+
+*{emphasis}* [note: can be configured to be represented by bold, italics or underscore]
+
+!{bold text}!
+
+/{italics}/
+
+_{underscore}_
+
+"{citation}"
+
+^{superscript}^
+
+,{subscript},
+
++{inserted text}+
+
+-{strikethrough}-
+
+#{monospace}#
+
+2~ Indentation and bullets
+
+!_ markup example:
+
+code{
+
+ordinary paragraph
+
+_1 indent paragraph one step
+
+_2 indent paragraph two steps
+
+_9 indent paragraph nine steps
+
+}code
+
+!_ resulting output:
+
+ordinary paragraph
+
+_1 indent paragraph one step
+
+_2 indent paragraph two steps
+
+_9 indent paragraph nine steps
+
+!_ markup example:
+
+code{
+
+_* bullet text
+
+_1* bullet text, first indent
+
+_2* bullet text, two step indent
+
+}code
+
+!_ resulting output:
+
+_* bullet text
+
+_1* bullet text, first indent
+
+_2* bullet text, two step indent
+
+Numbered List (not to be confused with headings/titles, (document structure))
+
+!_ markup example:
+
+code{
+
+# numbered list numbered list 1., 2., 3, etc.
+
+_# numbered list numbered list indented a., b., c., d., etc.
+
+}code
+
+2~ Hanging Indents
+
+!_ markup example:
+
+code{
+
+_0_1 first line no indent,
+rest of paragraph indented one step
+
+_1_0 first line indented,
+rest of paragraph no indent
+
+in each case level may be 0-9
+
+}code
+
+!_ resulting output:
+
+_0_1 first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step;
+
+A regular paragraph.
+
+_1_0 first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent
+
+in each case level may be 0-9
+
+_0_1 *{live-build}* A collection of scripts used to build customized Debian Livesystems. /{live-build}/ was formerly known as live-helper, and even earlier known as live-package.
+
+_0_1 *{live-build}* \\
+A collection of scripts used to build customized Debian Livesystems. /{live-build}/ was formerly known as live-helper, and even earlier known as live-package.
+
+2~ Footnotes / Endnotes
+
+Footnotes and endnotes are marked up at the location where they would be indicated within a text. They are automatically numbered. The output type determines whether footnotes or endnotes will be produced
+
+!_ markup example:
+
+code{
+
+~{ a footnote or endnote }~
+
+}code
+
+!_ resulting output:
+
+~{ a footnote or endnote }~
+
+!_ markup example:
+
+code{
+
+normal text~{ self contained endnote marker & endnote in one }~ continues
+
+}code
+
+!_ resulting output:
+
+normal text~{ self contained endnote marker & endnote in one }~ continues
+
+!_ markup example:
+
+code{
+
+normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks if required }~ continues
+
+normal text ~{** another unnumbered asterisk footnote/endnote }~ continues
+
+}code
+
+!_ resulting output:
+
+normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks if required }~ continues
+
+normal text ~{** another unnumbered asterisk footnote/endnote }~ continues
+
+!_ markup example:
+
+code{
+
+normal text ~[* editors notes, numbered asterisk footnote/endnote series ]~ continues
+
+normal text ~[+ editors notes, numbered plus symbol footnote/endnote series ]~ continues
+
+}code
+
+!_ resulting output:
+
+normal text ~[* editors notes, numbered asterisk footnote/endnote series ]~ continues
+
+normal text ~[+ editors notes, numbered plus symbol footnote/endnote series ]~ continues
+
+!_ Alternative endnote pair notation for footnotes/endnotes:
+
+code{
+
+% note the endnote marker "~^"
+
+normal text~^ continues
+
+^~ endnote text following the paragraph in which the marker occurs
+
+}code
+
+the standard and pair notation cannot be mixed in the same document
+
+2~ Links
+
+3~ Naked URLs within text, dealing with urls
+
+urls found within text are marked up automatically. A url within text is automatically hyperlinked to itself and by default decorated with angled braces, unless they are contained within a code block (in which case they are passed as normal text), or escaped by a preceding underscore (in which case the decoration is omitted).
+
+!_ markup example:
+
+code{
+
+normal text http://www.sisudoc.org/ continues
+
+}code
+
+!_ resulting output:
+
+normal text http://www.sisudoc.org/ continues
+
+An escaped url without decoration
+
+!_ markup example:
+
+code{
+
+normal text _http://www.sisudoc.org/ continues
+
+deb _http://www.jus.uio.no/sisu/archive unstable main non-free
+
+}code
+
+!_ resulting output:
+
+normal text _http://www.sisudoc.org/ continues
+
+deb _http://www.jus.uio.no/sisu/archive unstable main non-free
+
+where a code block is used there is neither decoration nor hyperlinking, code blocks are discussed later in this document
+
+!_ resulting output:
+
+code{
+
+deb http://www.jus.uio.no/sisu/archive unstable main non-free
+deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
+
+}code
+
+3~link_text Linking Text
+
+To link text or an image to a url the markup is as follows
+
+!_ markup example:
+
+code{
+
+about { SiSU }http://url.org markup
+
+}code
+
+!_ resulting output:
+
+about { SiSU }http://www.sisudoc.org/ markup
+
+A shortcut notation is available so the url link may also be provided automatically as a footnote
+
+!_ markup example:
+
+code{
+
+about {~^ SiSU }http://url.org markup
+
+}code
+
+!_ resulting output:
+
+about {~^ SiSU }http://www.sisudoc.org/ markup
+
+Internal document links to a tagged location, including an ocn
+
+!_ markup example:
+
+code{
+
+about { text links }#link_text
+
+}code
+
+!_ resulting output:
+
+about { text links }#link_text
+
+Shared document collection link
+
+!_ markup example:
+
+code{
+
+about { SiSU book markup examples }:SiSU/examples.html
+
+}code
+
+!_ resulting output:
+
+about { SiSU book markup examples }:SiSU/examples.html
+
+3~ Linking Images
+
+!_ markup example:
+
+code{
+
+{ tux.png 64x80 }image
+
+% various url linked images
+
+{tux.png 64x80 "a better way" }http://www.sisudoc.org/
+
+{GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian and Ruby" }http://www.sisudoc.org/
+
+{~^ ruby_logo.png "Ruby" }http://www.ruby-lang.org/en/
+
+}code
+
+!_ resulting output:
+
+{ tux.png 64x80 }image
+
+{tux.png 64x80 "Gnu/Linux - a better way" }http://www.sisudoc.org/
+
+{GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian and Ruby" }http://www.sisudoc.org/
+
+{~^ ruby_logo.png "Ruby" }http://www.ruby-lang.org/en/
+
+!_ linked url footnote shortcut
+
+code{
+
+{~^ [text to link] }http://url.org
+
+% maps to: { [text to link] }http://url.org ~{ http://url.org }~
+
+% which produces hyper-linked text within a document/paragraph, with an endnote providing the url for the text location used in the hyperlink
+
+}code
+
+code{
+
+text marker *~name
+
+}code
+
+note at a heading level the same is automatically achieved by providing names to headings 1, 2 and 3 i.e. 2~[name] and 3~[name] or in the case of auto-heading numbering, without further intervention.
+
+3~ Link shortcut for multiple versions of a sisu document in the same directory tree
+
+!_ markup example:
+
+code{
+
+!_ /{"Viral Spiral"}/, David Bollier
+
+{ "Viral Spiral", David Bollier [3sS]}viral_spiral.david_bollier.sst
+
+}code
+
+
+!_ /{"Viral Spiral"}/, David Bollier
+
+{ "Viral Spiral", David Bollier [3sS]}viral_spiral.david_bollier.sst
+
+2~ Grouped Text
+
+3~ Tables
+
+Tables may be prepared in two either of two forms
+
+!_ markup example:
+
+code{
+
+table{ c3; 40; 30; 30;
+
+This is a table
+this would become column two of row one
+column three of row one is here
+
+And here begins another row
+column two of row two
+column three of row two, and so on
+
+}table
+
+}code
+
+!_ resulting output:
+
+table{ c3; 40; 30; 30;
+
+This is a table
+this would become column two of row one
+column three of row one is here
+
+And here begins another row
+column two of row two
+column three of row two, and so on
+
+}table
+
+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
http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler }~
+
+code{
+
+!_ Table 3.1: Contributors to Wikipedia, January 2001 - June 2005
+
+{table~h 24; 12; 12; 12; 12; 12; 12;}
+ |Jan. 2001|Jan. 2002|Jan. 2003|Jan. 2004|July 2004|June 2006
+Contributors* | 10| 472| 2,188| 9,653| 25,011| 48,721
+Active contributors** | 9| 212| 846| 3,228| 8,442| 16,945
+Very active contributors*** | 0| 31| 190| 692| 1,639| 3,016
+No. of English language articles| 25| 16,000| 101,000| 190,000| 320,000| 630,000
+No. of articles, all languages | 25| 19,000| 138,000| 490,000| 862,000|1,600,000
+
+* Contributed at least ten times; ** at least 5 times in last month; *** more than 100 times in last month.
+
+}code
+
+!_ resulting output:
+
+
+!_ Table 3.1: Contributors to Wikipedia, January 2001 - June 2005
+
+{table~h 24; 12; 12; 12; 12; 12; 12;}
+ |Jan. 2001|Jan. 2002|Jan. 2003|Jan. 2004|July 2004|June 2006
+Contributors* | 10| 472| 2,188| 9,653| 25,011| 48,721
+Active contributors** | 9| 212| 846| 3,228| 8,442| 16,945
+Very active contributors*** | 0| 31| 190| 692| 1,639| 3,016
+No. of English language articles| 25| 16,000| 101,000| 190,000| 320,000| 630,000
+No. of articles, all languages | 25| 19,000| 138,000| 490,000| 862,000|1,600,000
+
+* Contributed at least ten times; ** at least 5 times in last month; *** more than 100 times in last month.
+
+% code{
+
+% test
+
+% ~#
+
+% % unnumbered paragraph (place marker at end of paragraph)
+
+% -#
+
+% % unnumbered paragraph, delete when not required (place marker at end of paragraph) [used in dummy headings, eg. for segmented html]
+
+% % add a comment to text, that will be removed prior to processing (place marker at beginning of line)
+
+% }code
+
+3~ Poem
+
+!_ basic markup:
+
+code{
+
+poem{
+
+ Your poem here
+
+}poem
+
+Each verse in a poem is given an object number.
+
+}code
+
+!_ markup example:
+
+code{
+
+poem{
+
+ `Fury said to a
+ mouse, That he
+ met in the
+ house,
+ "Let us
+ both go to
+ law: I will
+ prosecute
+ YOU. --Come,
+ I'll take no
+ denial; We
+ must have a
+ trial: For
+ really this
+ morning I've
+ nothing
+ to do."
+ Said the
+ mouse to the
+ cur, "Such
+ a trial,
+ dear Sir,
+ With
+ no jury
+ or judge,
+ would be
+ wasting
+ our
+ breath."
+ "I'll be
+ judge, I'll
+ be jury,"
+ Said
+ cunning
+ old Fury:
+ "I'll
+ try the
+ whole
+ cause,
+ and
+ condemn
+ you
+ to
+ death."'
+
+}poem
+
+}code
+
+!_ resulting output:
+
+poem{
+
+ `Fury said to a
+ mouse, That he
+ met in the
+ house,
+ "Let us
+ both go to
+ law: I will
+ prosecute
+ YOU. --Come,
+ I'll take no
+ denial; We
+ must have a
+ trial: For
+ really this
+ morning I've
+ nothing
+ to do."
+ Said the
+ mouse to the
+ cur, "Such
+ a trial,
+ dear Sir,
+ With
+ no jury
+ or judge,
+ would be
+ wasting
+ our
+ breath."
+ "I'll be
+ judge, I'll
+ be jury,"
+ Said
+ cunning
+ old Fury:
+ "I'll
+ try the
+ whole
+ cause,
+ and
+ condemn
+ you
+ to
+ death."'
+
+}poem
+
+3~ Group
+
+!_ basic markup:
+
+code{
+
+group{
+
+ Your grouped text here
+
+}group
+
+A group is treated as an object and given a single object number.
+
+}code
+
+!_ markup example:
+
+code{
+
+group{
+
+ `Fury said to a
+ mouse, That he
+ met in the
+ house,
+ "Let us
+ both go to
+ law: I will
+ prosecute
+ YOU. --Come,
+ I'll take no
+ denial; We
+ must have a
+ trial: For
+ really this
+ morning I've
+ nothing
+ to do."
+ Said the
+ mouse to the
+ cur, "Such
+ a trial,
+ dear Sir,
+ With
+ no jury
+ or judge,
+ would be
+ wasting
+ our
+ breath."
+ "I'll be
+ judge, I'll
+ be jury,"
+ Said
+ cunning
+ old Fury:
+ "I'll
+ try the
+ whole
+ cause,
+ and
+ condemn
+ you
+ to
+ death."'
+
+}group
+
+}code
+
+!_ resulting output:
+
+group{
+
+ `Fury said to a
+ mouse, That he
+ met in the
+ house,
+ "Let us
+ both go to
+ law: I will
+ prosecute
+ YOU. --Come,
+ I'll take no
+ denial; We
+ must have a
+ trial: For
+ really this
+ morning I've
+ nothing
+ to do."
+ Said the
+ mouse to the
+ cur, "Such
+ a trial,
+ dear Sir,
+ With
+ no jury
+ or judge,
+ would be
+ wasting
+ our
+ breath."
+ "I'll be
+ judge, I'll
+ be jury,"
+ Said
+ cunning
+ old Fury:
+ "I'll
+ try the
+ whole
+ cause,
+ and
+ condemn
+ you
+ to
+ death."'
+
+}group
+
+3~ Code
+
+Code tags #{ code{ ... }code }# (used as with other group tags described above) are used to escape regular sisu markup, and have been used extensively within this document to provide examples of SiSU markup. You cannot however use code tags to escape code tags. They are however used in the same way as group or poem tags.
+
+A code-block is treated as an object and given a single object number. [an option to number each line of code may be considered at some later time]
+
+!_ use of code tags instead of poem compared, resulting output:
+
+code{
+
+ `Fury said to a
+ mouse, That he
+ met in the
+ house,
+ "Let us
+ both go to
+ law: I will
+ prosecute
+ YOU. --Come,
+ I'll take no
+ denial; We
+ must have a
+ trial: For
+ really this
+ morning I've
+ nothing
+ to do."
+ Said the
+ mouse to the
+ cur, "Such
+ a trial,
+ dear Sir,
+ With
+ no jury
+ or judge,
+ would be
+ wasting
+ our
+ breath."
+ "I'll be
+ judge, I'll
+ be jury,"
+ Said
+ cunning
+ old Fury:
+ "I'll
+ try the
+ whole
+ cause,
+ and
+ condemn
+ you
+ to
+ death."'
+
+}code
+
+From SiSU 2.7.7 on you can number codeblocks by placing a hash after the opening code tag #{ code{# }# as demonstrated here:
+
+code{#
+
+ `Fury said to a
+ mouse, That he
+ met in the
+ house,
+ "Let us
+ both go to
+ law: I will
+ prosecute
+ YOU. --Come,
+ I'll take no
+ denial; We
+ must have a
+ trial: For
+ really this
+ morning I've
+ nothing
+ to do."
+ Said the
+ mouse to the
+ cur, "Such
+ a trial,
+ dear Sir,
+ With
+ no jury
+ or judge,
+ would be
+ wasting
+ our
+ breath."
+ "I'll be
+ judge, I'll
+ be jury,"
+ Said
+ cunning
+ old Fury:
+ "I'll
+ try the
+ whole
+ cause,
+ and
+ condemn
+ you
+ to
+ death."'
+
+}code
+
+2~ Additional breaks - linebreaks within objects, column and page-breaks
+
+3~ line-breaks
+
+To break a line within a "paragraph object", two backslashes \\\\ \\ with a space before and a space or newline after them \\ may be used.
+
+code{
+
+To break a line within a "paragraph object",
+two backslashes \\ with a space before
+and a space or newline after them \\
+may be used.
+
+}code
+
+The html break br enclosed in angle brackets (though undocumented) is available in versions prior to 3.0.13 and 2.9.7 (it remains available for the time being, but is depreciated).
+
+To draw a dividing line dividing paragraphs, see the section on page breaks.
+
+3~ page breaks
+
+Page breaks are only relevant and honored in some output formats. A page break or a new page may be inserted manually using the following markup on a line on its own:
+
+page new =\\= or <:pn> breaks the page, starts a new page.
+
+page break -\\- or <:pb> breaks a column, starts a new column, if using columns, else breaks the page, starts a new page.
+
+page break line across page -..- draws a dividing line, dividing paragraphs
+
+page break:
+
+code{
+
+-\\-
+
+or
+
+<:pb>
+
+}code
+
+page (break) new:
+
+code{
+
+=\\=
+
+or
+
+<:pn>
+
+}code
+
+page (break) line across page (dividing paragraphs):
+
+code{
+
+-..-
+
+}code
+
+2~ Book index
+
+To make an index append to paragraph the book index term relates to it, using an equal sign and curly braces.
+
+Currently two levels are provided, a main term and if needed a sub-term. Sub-terms are separated from the main term by a colon.
+
+code{
+
+ Paragraph containing main term and sub-term.
+ ={Main term:sub-term}
+
+}code
+
+The index syntax starts on a new line, but there should not be an empty line between paragraph and index markup.
+
+The structure of the resulting index would be:
+
+code{
+
+ Main term, 1
+ sub-term, 1
+
+}code
+
+Several terms may relate to a paragraph, they are separated by a semicolon. If the term refers to more than one paragraph, indicate the number of paragraphs.
+
+code{
+
+ Paragraph containing main term, second term and sub-term.
+ ={first term; second term: sub-term}
+
+}code
+
+The structure of the resulting index would be:
+
+code{
+
+ First term, 1,
+ Second term, 1,
+ sub-term, 1
+
+}code
+
+If multiple sub-terms appear under one paragraph, they are separated under the main term heading from each other by a pipe symbol.
+
+code{
+
+ Paragraph containing main term, second term and sub-term.
+ ={Main term:
+ sub-term+2|second sub-term;
+ Another term
+ }
+
+ A paragraph that continues discussion of the first sub-term
+
+}code
+
+The plus one in the example provided indicates the first sub-term spans one additional paragraph. The logical structure of the resulting index would be:
+
+code{
+
+ Main term, 1,
+ sub-term, 1-3,
+ second sub-term, 1,
+ Another term, 1
+
+}code
+
+1~ Composite documents markup
+
+It is possible to build a document by creating a master document that requires other documents. The documents required may be complete documents that could be generated independently, or they could be markup snippets, prepared so as to be easily available to be placed within another text. If the calling document is a master document (built from other documents), it should be named with the suffix *{.ssm}* Within this document you would provide information on the other documents that should be included within the text. These may be other documents that would be processed in a regular way, or markup bits prepared only for inclusion within a master document *{.sst}* regular markup file, or *{.ssi}* (insert/information) A secondary file of the composite document is built prior to processing with the same prefix and the suffix *{._sst}*
+
+basic markup for importing a document into a master document
+
+code{
+
+<< filename1.sst
+
+<< filename2.ssi
+
+}code
+
+The form described above should be relied on. Within the Vim editor it results in the text thus linked becoming hyperlinked to the document it is calling in which is convenient for editing.
+
+1~ Substitutions
+
+!_ markup example:
+
+code{
+
+The current Debian is ${debian_stable} the next debian will be ${debian_testing}
+
+Configure substitution in _sisu/sisu_document_make
+
+@make:
+ :substitute: /${debian_stable}/,'*{Wheezy}*' /${debian_testing}/,'*{Jessie}*'
+
+}code
+
+!_ resulting output:
+
+The current Debian is ${debian_stable} the next debian will be ${debian_testing}
+
+Configure substitution in _sisu/sisu_document_make
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_markup_syntax_history.sst b/data/doc/sisu/markup-samples/manual/en/sisu_markup_syntax_history.sst
new file mode 100644
index 00000000..c6da0a14
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_markup_syntax_history.sst
@@ -0,0 +1,244 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: Markup
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :published: 2008-05-22
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: electronic documents:SiSU:document:markup;SiSU:document:markup;SiSU:document:markup;SiSU:manual:markup;electronic documents:SiSU:manual:markup
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? SiSU Markup Syntax History
+
+1~syntax_history Markup Syntax History
+
+2~ Notes related to Files-types and Markup Syntax
+
+4.0 introduced additional headers and drops the use of skins replacing them with additions to the @make: header, and having a common _sisu/sisu_document_make file that uses @make: header syntax to provide a default @make: (it will parse 2.0 but igore skins, markup is otherwise the same as version 2.0 with version 3.0's minor additions)
+
+3.0 very minor additions to markup added, substantially the same as version 2.0
+
+2.0 introduced new headers and is therefore incompatible with 1.0 though otherwise the same with the addition of a couple of tags (i.e. a superset)
+
+0.38 is substantially current for version 1.0
+
+depreciated 0.16 supported, though file names were changed at 0.37
+
+_* sisu --query=[sisu version [0.38] or 'history]
+
+provides a short history of changes to SiSU markup
+
+!_ SiSU 2.0
+(2010-03-06:09/6)
+same as 1.0, apart from the changing of headers and the addition of a monospace tag related headers now grouped, e.g.
+
+code{
+
+@title:
+ :subtitle:
+
+@creator:
+ :author:
+ :translator:
+ :illustrator:
+
+@rights:
+ :text:
+ :illustrations:
+
+}code
+
+see document markup samples, and sisu --help headers
+
+the monospace tag takes the form of a hash '#'
+
+code{
+
+#{ this enclosed text would be monospaced }#
+
+}code
+
+!_ 1.0
+(2009-12-19:50/6)
+same as 0.69
+
+!_ 0.69
+(2008-09-16:37/2)
+(same as 1.0) and as previous (0.57) with the addition of book index tags
+
+code{
+
+/^={.+?}$/
+
+}code
+
+e.g. appended to a paragraph, on a new-line (without a blank line in between) logical structure produced assuming this is the first text "object"
+
+code{
+
+ ={GNU/Linux community distribution:Debian+2|Fedora|Gentoo;Free Software Foundation+5}
+
+}code
+
+code{
+
+Free Software Foundation, 1-6
+GNU/Linux community distribution, 1
+ Debian, 1-3
+ Fedora, 1
+ Gentoo,
+
+}code
+
+!_ 0.66
+(2008-02-24:07/7)
+same as previous, adds semantic tags, [experimental and not-used]
+
+code{
+
+/[:;]{.+?}[:;][a-z+]/
+
+}code
+
+!_ 0.57
+(2007w34/4)
+SiSU 0.57 is the same as 0.42 with the introduction of some a shortcut to use the headers @title and @creator in the first heading [expanded using the contents of the headers @title: and @author:]
+
+code{
+
+:A~ @title by @author
+
+}code
+
+!_ 0.52
+(2007w14/6)
+declared document type identifier at start of text/document:
+
+_1 SiSU 0.52
+
+or, backward compatible using the comment marker:
+
+_1 % SiSU 0.38
+
+variations include 'SiSU (text|master|insert) [version]' and 'sisu-[version]'
+
+!_ 0.51
+(2007w13/6)
+skins changed (simplified), markup unchanged
+
+!_ 0.42
+(2006w27/4)
+* (asterisk) type endnotes, used e.g. in relation to author
+
+SiSU 0.42 is the same as 0.38 with the introduction of some additional endnote types,
+
+Introduces some variations on endnotes, in particular the use of the asterisk
+
+code{
+
+~{* for example for describing an author }~ and ~{** for describing a second author }~
+
+}code
+
+* for example for describing an author
+
+** for describing a second author
+
+and
+
+code{
+
+~[* my note ]~ or ~[+ another note ]~
+
+}code
+
+which numerically increments an asterisk and plus respectively
+
+*1 my note
++1 another note
+
+!_ 0.38
+(2006w15/7)
+introduced new/alternative notation for headers, e.g. @title: (instead of 0\~title), and accompanying document structure markup, :A,:B,:C,1,2,3 (maps to previous 1,2,3,4,5,6)
+
+SiSU 0.38 introduced alternative experimental header and heading/structure markers,
+
+code{
+
+@headername: and headers :A~ :B~ :C~ 1~ 2~ 3~
+
+}code
+
+as the equivalent of:
+
+code{
+
+0~headername and headers 1~ 2~ 3~ 4~ 5~ 6~
+
+}code
+
+The internal document markup of SiSU 0.16 remains valid and standard Though note that SiSU 0.37 introduced a new file naming convention
+
+SiSU has in effect two sets of levels to be considered, using 0.38 notation A-C headings/levels, pre-ordinary paragraphs /pre-substantive text, and 1-3 headings/levels, levels which are followed by ordinary text. This may be conceptualised as levels A,B,C, 1,2,3, and using such letter number notation, in effect: A must exist, optional B and C may follow in sequence (not strict) 1 must exist, optional 2 and 3 may follow in sequence i.e. there are two independent heading level sequences A,B,C and 1,2,3 (using the 0.16 standard notation 1,2,3 and 4,5,6) on the positive side: the 0.38 A,B,C,1,2,3 alternative makes explicit an aspect of structuring documents in SiSU that is not otherwise obvious to the newcomer (though it appears more complicated, is more in your face and likely to be understood fairly quickly); the substantive text follows levels 1,2,3 and it is 'nice' to do most work in those levels
+
+!_ 0.37
+(2006w09/7)
+introduced new file naming convention, .sst (text), .ssm (master), .ssi (insert), markup syntax unchanged
+
+SiSU 0.37 introduced new file naming convention, using the file extensions .sst .ssm and .ssi to replace .s1 .s2 .s3 .r1 .r2 .r3 and .si
+
+this is captured by the following file 'rename' instruction:
+
+code{
+
+rename 's/\.s[123]$/\.sst/' *.s{1,2,3}
+rename 's/\.r[123]$/\.ssm/' *.r{1,2,3}
+rename 's/\.si$/\.ssi/' *.si
+
+}code
+
+The internal document markup remains unchanged, from SiSU 0.16
+
+!_ 0.35
+(2005w52/3)
+sisupod, zipped content file introduced
+
+!_ 0.23
+(2005w36/2)
+utf-8 for markup file
+
+!_ 0.22
+(2005w35/3)
+image dimensions may be omitted if rmagick is available to be relied upon
+
+!_ 0.20.4
+(2005w33/4)
+header 0~links
+
+!_ 0.16
+(2005w25/2)
+substantial changes introduced to make markup cleaner, header 0\~title type, and headings [1-6]\~ introduced, also percentage sign (%) at start of a text line as comment marker
+
+SiSU 0.16 (0.15 development branch) introduced the use of
+
+the header 0~ and headings/structure 1~ 2~ 3~ 4~ 5~ 6~
+
+in place of the 0.1 header, heading/structure notation
+
+SiSU 0.1 headers and headings structure represented by
+header 0{~ and headings/structure 1{ 2{ 3{ 4{~ 5{ 6{
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_output_overview.sst b/data/doc/sisu/markup-samples/manual/en/sisu_output_overview.sst
new file mode 100644
index 00000000..332f4aae
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_output_overview.sst
@@ -0,0 +1,142 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: SiSU overview of status of features available in various outputs
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2005-10-31
+ :available: 2006-10-31
+ :issued: 2006-10-31
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: electronic documents:SiSU:document:markup table;SiSU:manual:output overview;electronic documents:SiSU:manual:output overview;SiSU:document:output overview;SiSU:document:output overview
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? SiSU overview of status of features available in various outputs
+
+1~ A Checklist of Output Features
+
+% 2~ features available in various output types
+
+This table gives an indication of the features that are available
+for various forms of output of SiSU.
+
+!_ sisu-2.0.0 on 2010-03-06
+
+{table~h 28}
+feature |txt|ltx/pdf|HTML|EPUB|XML/s|XML/d|ODF|SQLite|pgSQL
+headings | * | * | * | * | * | * | * | * | *
+footnotes | * | * | * | * | * | * | * | * | *
+bold, underscore, italics | . | * | * | * | * | * | * | * | *
+strikethrough | . | * | * | * | * | * | * | |
+superscript, subscript | . | * | * | * | * | * | * | |
+extended ascii set (utf-8)| * | * | * | * | * | * | * | | *
+indents | * | * | * | * | * | * | * | |
+bullets | . | * | * | * | * | * | . | |
+groups | | | | | | | | |
+* tables | | * | * | * | . | . | . | . | .
+* poem | * | * | * | * | . | . | * | . | .
+* code | * | * | * | * | . | . | * | . | .
+url | * | * | * | * | * | * | * | . | .
+links | * | * | * | * | * | * | * | . | .
+images | - | * | * | * | T | T | * | T | T
+image caption | - | * | * | * | | | | |
+table of contents | | * | * | * | * | * | . | |
+page header/footer? | - | * | * | * | * | * | t | |
+line break | * | * | * | * | * | * | * | |
+page break | | * | | | | | * | |
+segments | | | * | * | | | | |
+skins | * | * | * | * | * | * | | |
+ocn | . | * | * | * | * | * | -?| * | *
+auto-heading numbers | * | * | * | * | * | * | * | * | *
+minor list numbering | * | * | * | * | * | * | * | * | *
+special characters | . | . | . | . | | | | |
+
+!_ sisu-1.0.0 on 2009-10-28
+
+{table~h 28}
+feature |txt|ltx/pdf|HTML|XML/s|XML/d|ODF|SQLite|pgSQL
+headings | * | * | * | * | * | * | * | *
+footnotes | * | * | * | * | * | * | * | *
+bold, underscore, italics | . | * | * | * | * | * | * | *
+strikethrough | . | * | * | * | * | * | |
+superscript, subscript | . | * | * | * | * | * | |
+extended ascii set (utf-8)| * | * | * | * | * | * | | *
+indents | * | * | * | * | * | * | |
+bullets | . | * | * | * | * | . | |
+groups | | | | | | | |
+* tables | | * | * | . | . | . | . | .
+* poem | * | * | * | . | . | * | . | .
+* code | * | * | * | . | . | * | . | .
+url | * | * | * | * | * | * | . | .
+links | * | * | * | * | * | * | . | .
+images | - | * | * | T | T | * | T | T
+image caption | - | * | * | | | | |
+table of contents | | * | * | * | * | . | |
+page header/footer? | - | * | * | * | * | t | |
+line break | * | * | * | * | * | * | |
+page break | | * | | | | * | |
+segments | | | * | | | | |
+skins | * | * | * | * | * | | |
+ocn | . | * | * | * | * | -?| * | *
+auto-heading numbers | * | * | * | * | * | * | * | *
+minor list numbering | * | * | * | * | * | * | * | *
+special characters | . | . | . | | | | |
+
+!_ sisu-0.36.6 on 2006-01-23
+
+{table~h 28; 8; 8; 8; 8; 8; 8; 8; 8; 8;}
+feature |txt|ltx/pdf|HTML|XHTML|XML/s|XML/d|ODF|SQLite|pgSQL
+headings | * | * | * | * | * | * | * | * | *
+footnotes | * | * | * | * | * | * | * | * | *
+bold, underscore, italics | . | * | * | * | * | * | * | * | *
+strikethrough | . | * | * | * | * | * | * | |
+superscript, subscript | . | * | * | * | * | * | * | |
+extended ascii set (utf-8)| * | * | * | * | * | * | * | | *
+indents | * | * | * | * | * | * | * | |
+bullets | . | * | * | * | * | * | . | |
+groups | | | | | | | | |
+* tables | | * | * | . | . | . | . | . | .
+* poem | * | * | * | . | . | . | * | . | .
+* code | * | * | * | . | . | . | * | . | .
+url | * | * | * | * | * | * | * | . | .
+links | * | * | * | * | * | * | * | . | .
+images | - | * | * | T | T | T | * | T | T
+image caption | - | * | * | | | | | |
+table of contents | | * | * | * | * | * | . | |
+page header/footer? | - | * | * | * | * | * | t | |
+line break | * | * | * | * | * | * | * | |
+page break | | * | | | | | * | |
+segments | | | * | | | | | |
+skins | * | * | * | * | * | * | | |
+ocn | . | * | * | * | * | * | -?| * | *
+auto-heading numbers | * | * | * | * | * | * | * | * | *
+minor list numbering | * | * | * | * | * | * | * | * | *
+special characters | . | . | . | | | | | |
+
+group{
+
+ Done
+ * yes/done
+ . partial
+
+ - not available/appropriate
+
+ Not Done
+ T task todo
+ t lesser task/todo
+ not done
+
+}group
+
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_postgresql.sst b/data/doc/sisu/markup-samples/manual/en/sisu_postgresql.sst
new file mode 100644
index 00000000..574e307c
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_postgresql.sst
@@ -0,0 +1,82 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: Search
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: electronic documents:SiSU:document:postgresql;SiSU:manual:postgresql;electronic documents:SiSU:manual:postgresql;SiSU:document:postgresql;SiSU:document:postgresql;
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+@make:
+ :manpage: section=7; name=sisu - package to install what sisu needs to to populate a postgresql database (postgresql dependency component); synopsis=sisu -Dv [filename/wildcard ]\n sisu -Dv [instruction]
+
+:A~? @title @creator
+
+% :B~? SiSU Postgresql
+
+1~postgresql Postgresql
+
+2~ Name
+
+SiSU - Structured information, Serialized Units - a document publishing system, postgresql dependency package
+
+2~ Description
+
+Information related to using postgresql with sisu (and related to the sisu_postgresql dependency package, which is a dummy package to install dependencies needed for SiSU to populate a postgresql database, this being part of SiSU - man sisu).
+
+2~ Synopsis
+
+_1 sisu -D [instruction] [filename/wildcard if required]
+
+_1 sisu -D --pg --[instruction] [filename/wildcard if required]
+
+
+2~ Commands
+
+Mappings to two databases are provided by default, postgresql and sqlite, the same commands are used within sisu to construct and populate databases however -d (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, alternatively --sqlite or --pgsql may be used
+
+!_ -D or --pgsql
+may be used interchangeably.
+
+3~ create and destroy database
+
+!_ --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

+creates database where no database existed before
+
+!_ sisu -D --create

+creates database tables where no database tables existed before
+
+!_ 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

+destroys existing database and builds a new empty database structure
+
+3~ import and remove documents
+
+!_ 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]

+updates file contents in database
+
+!_ sisu -D --remove -v [filename/wildcard]

+removes specified document from postgresql database.
+
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_quickstart.sst b/data/doc/sisu/markup-samples/manual/en/sisu_quickstart.sst
new file mode 100644
index 00000000..ae95f528
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_quickstart.sst
@@ -0,0 +1,256 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: Quickstart, installation and use
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2006-09-06
+ :available: 2006-09-06
+ :issued: 2006-09-06
+ :published: 2007-09-16
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: electronic documents:SiSU:document:quickstart;SiSU:manual:quickstart;electronic documents:SiSU:manual:quickstart;SiSU:document:quickstart;SiSU:document:quickstart
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? Quickstart - SiSU installation and use
+
+1~ Quickstart - Getting Started Howto
+
+2~ Installation
+
+Installation is currently most straightforward and tested on the Debian platform, as there are packages for the installation of sisu and all requirements for what it does.
+
+3~ Debian Installation
+
+SiSU is available directly from the Debian Sid and testing archives (and possibly Ubuntu), assuming your /etc/apt/sources.list is set accordingly:
+
+code{
+
+ aptitude update
+ aptitude install sisu-complete
+
+}code
+
+The following /etc/apt/sources.list setting permits the download of additional markup samples:
+
+code{
+
+#/etc/apt/sources.list
+
+ deb http://ftp.fi.debian.org/debian/ unstable main non-free contrib
+ deb-src http://ftp.fi.debian.org/debian/ unstable main non-free contrib
+
+}code
+
+The aptitude commands become:
+
+code{
+
+ aptitude update
+ aptitude install sisu-complete sisu-markup-samples
+
+}code
+
+If there are newer versions of SiSU upstream of the Debian archives, they will be available by adding the following to your /etc/apt/sources.list
+
+code{
+
+#/etc/apt/sources.list
+
+ deb http://www.jus.uio.no/sisu/archive unstable main non-free
+ deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
+
+}code
+
+repeat the aptitude commands
+
+code{
+
+ aptitude update
+ aptitude install sisu-complete sisu-markup-samples
+
+}code
+
+Note however that it is not necessary to install sisu-complete if not all components of sisu are to be used. Installing just the package sisu will provide basic functionality.
+
+3~ RPM Installation
+
+RPMs are provided though untested, they are prepared by running alien against the source package, and against the debs.
+
+They may be downloaded from:
+
+_1 http://www.jus.uio.no/sisu/SiSU/download.html#rpm
+
+as root type:
+
+_1 rpm -i [rpm package name]
+
+3~ Installation from source
+
+To install SiSU from source check information at:
+
+_1 http://www.jus.uio.no/sisu/SiSU/download.html#current
+
+_* download the source package
+
+_* Unpack the source
+
+Two alternative modes of installation from source are provided, setup.rb (by Minero Aoki) and a rant(by Stefan Lang) built install file, in either case: the first steps are the same, download and unpack the source file:
+
+For basic use SiSU is only dependent on the programming language in which it is written Ruby, and SiSU will be able to generate html, EPUB, various XMLs, including ODF (and will also produce LaTeX). Dependencies required for further actions, though it relies on the installation of additional dependencies which the source tarball does not take care of, for things like using a database (postgresql or sqlite)~{ There is nothing to stop MySQL support being added in future. }~ or converting LaTeX to pdf.
+
+!_ setup.rb
+
+This is a standard ruby installer, using setup.rb is a three step process. In the root directory of the unpacked SiSU as root type:
+
+code{
+
+ ruby setup.rb config
+ ruby setup.rb setup
+ #[and as root:]
+ ruby setup.rb install
+
+}code
+
+further information on setup.rb is available from:
+
+_1 http://i.loveruby.net/en/projects/setup/
+
+_1 http://i.loveruby.net/en/projects/setup/doc/usage.html
+
+!_ "install"
+
+The "install" file provided is an installer prepared using "rant". In the root directory of the unpacked SiSU as root type:
+
+_1 ruby install base
+
+or for a more complete installation:
+
+_1 ruby install
+
+or
+
+_1 ruby install base
+
+This makes use of Rant (by Stefan Lang) and the provided Rantfile. It has been configured to do post installation setup setup configuration and generation of first test file. Note however, that additional external package dependencies, such as tetex-extra are not taken care of for you.
+
+Further information on "rant" is available from:
+
+_1 http://make.rubyforge.org/
+
+_1 http://rubyforge.org/frs/?group_id=615
+
+For a list of alternative actions you may type:
+
+_1 ruby install help
+
+_1 ruby install -T
+
+2~ Testing SiSU, generating output
+
+To check which version of sisu is installed:
+
+sisu -v
+
+Depending on your mode of installation one or a number of markup sample files may be found either in the directory:
+
+...
+
+or
+
+...
+
+change directory to the appropriate one:
+
+cd /usr/share/doc/sisu/markup-samples/samples
+
+3~ basic text, plaintext, html, XML, ODF, EPUB
+
+Having moved to the directory that contains the markup samples (see instructions above if necessary), choose a file and run sisu against it
+
+sisu -NhwoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst
+
+this will generate html including a concordance file, opendocument text format, plaintext, XHTML and various forms of XML, and OpenDocument text
+
+3~ LaTeX / pdf
+
+Assuming a LaTeX engine such as tetex or texlive is installed with the required modules (done automatically on selection of sisu-pdf in Debian)
+
+Having moved to the directory that contains the markup samples (see instructions above if necessary), choose a file and run sisu against it
+
+sisu -pv free_as_in_freedom.rms_and_free_software.sam_williams.sst
+
+sisu -3 free_as_in_freedom.rms_and_free_software.sam_williams.sst
+
+should generate most available output formats: html including a concordance file, opendocument text format, plaintext, XHTML and various forms of XML, and OpenDocument text and pdf
+
+3~ relational database - postgresql, sqlite
+
+Relational databases need some setting up - you must have permission to create the database and write to it when you run sisu.
+
+Assuming you have the database installed and the requisite permissions
+
+sisu --sqlite --recreate
+
+sisu --sqlite -v --import free_as_in_freedom.rms_and_free_software.sam_williams.sst
+
+sisu --pgsql --recreate
+
+sisu --pgsql -v --import free_as_in_freedom.rms_and_free_software.sam_williams.sst
+
+2~ Getting Help
+
+3~ The man pages
+
+Type:
+
+_1 man sisu
+
+The man pages are also available online, though not always kept as up to date as within the package itself:
+
+_* {~^ sisu.1 }http://www.jus.uio.no/sisu/man/sisu.1.html
+
+_* {~^ sisu.8 }http://www.jus.uio.no/sisu/man/sisu.8.html
+
+_* {~^ man directory }http://www.jus.uio.no/sisu/man
+
+3~ Built in help
+
+sisu --help
+
+sisu --help --env
+
+sisu --help --commands
+
+sisu --help --markup
+
+3~ The home page
+
+http://www.sisudoc.org/
+
+http://www.jus.uio.no/sisu
+
+http://www.jus.uio.no/sisu/SiSU
+
+2~ Markup Samples
+
+A number of markup samples (along with output) are available off:
+
+http://www.jus.uio.no/sisu/SiSU/examples.html
+
+Additional markup samples are packaged separately in the file:
+
+***
+
+On Debian they are available in non-free~{ the Debian Free Software guidelines require that everything distributed within Debian can be changed - and the documents are authors' works that while freely distributable are not freely changeable. }~ to include them it is necessary to include non-free in your /etc/apt/source.list or obtain them from the sisu home site.
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_remote.sst b/data/doc/sisu/markup-samples/manual/en/sisu_remote.sst
new file mode 100644
index 00000000..959fbcf6
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_remote.sst
@@ -0,0 +1,88 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: Remote Operations
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: electronic documents:SiSU:document:remote;SiSU:manual:remote;electronic documents:SiSU:manual:remote;SiSU:document:remote;SiSU:document:remote
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? SiSU Remote Operations
+
+1~remote_source Remote Source Documents
+
+SiSU processing instructions can be run against remote source documents by providing the url of the documents against which the processing instructions are to be carried out. The remote SiSU documents can either be sisu marked up files in plaintext .sst or .ssm or; zipped sisu files, sisupod.zip or filename.ssp
+
+!_ .sst / .ssm - sisu text files
+
+SiSU can be run against source text files on a remote machine, provide the processing instruction and the url. The source file and any associated parts (such as images) will be downloaded and generated locally.
+
+code{
+
+sisu -3 http://[provide url to valid .sst or .ssm file]
+
+}code
+
+Any of the source documents in the sisu examples page can be used in this way, see http://www.jus.uio.no/sisu/SiSU/examples.html and use the url to the .sst for the desired document.
+
+NOTE: to set up a remote machine to serve SiSU documents in this way, images should be in the directory relative to the document source ../_sisu/image
+
+!_ sisupod - zipped sisu files
+
+A sisupod is the zipped content of a sisu marked up text or texts and any other associated parts to the document such as images.
+
+SiSU can be run against a sisupod on a (local or) remote machine, provide the processing instruction and the url, the sisupod will be downloaded and the documents it contains generated locally.
+
+code{
+
+sisu -3 http://[provide url to valid sisupod.zip or .ssp file]
+
+}code
+
+Any of the source documents in the sisu examples page can be used in this way, see http://www.jus.uio.no/sisu/SiSU/examples.html and use the url for the desired document.
+
+:C~ Remote Document Output
+
+1~remote_output Remote Output
+
+Once properly configured SiSU output can be automatically posted once generated to a designated remote machine using either rsync, or scp.
+
+In order to do this some ssh authentication agent and keychain or similar tool will need to be configured. Once that is done the placement on a remote host can be done seamlessly with the -r (for scp) or -R (for rsync) flag, which may be used in conjunction with other processing flags, e.g.
+
+code{
+
+sisu -3R sisu_remote.sst
+
+}code
+
+2~ commands
+
+!_ -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]

+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
+
+[expand on the setting up of an ssh-agent / keychain]
+
+1~remote_servers Remote Servers
+
+As SiSU is generally operated using the command line, and works within a Unix type environment, SiSU the program and all documents can just as easily be on a remote server, to which you are logged on using a terminal, and commands and operations would be pretty much the same as they would be on your local machine.
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_search.ssm b/data/doc/sisu/markup-samples/manual/en/sisu_search.ssm
new file mode 100644
index 00000000..9c40a8bf
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_search.ssm
@@ -0,0 +1,35 @@
+% SiSU master 4.0
+
+@title: SiSU
+ :subtitle: Search
+
+@creator:
+ :author: Ralph Amissah
+
+@date:
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :published: 2007-09-16
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? SiSU Search
+
+<< sisu_search_intro.ssi
+
+<< sisu_sql.ssi
+
+<< sisu_postgresql.sst
+
+<< sisu_sqlite.sst
+
+<< sisu_search_cgi.ssi
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
new file mode 100644
index 00000000..03eef9ff
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_search_cgi.ssi
@@ -0,0 +1,75 @@
+% SiSU insert 2.0
+
+@title: SiSU
+ :subtitle: Search
+
+@creator:
+ :author: Ralph Amissah
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? @title @creator
+
+:B~? SiSU Search
+
+:C~? CGI Search Form
+
+1~search_cgi Introduction
+
+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
+A small database and sample query front-end (search from) that makes use of the citation system, _{object citation numbering}_ to demonstrates functionality.~{ (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. }~
+
+SiSU can provide information on which documents are matched and at what locations within each document the matches are found. These results are relevant across all outputs using object citation numbering, which includes html, XML, EPUB, LaTeX, PDF and indeed the SQL database. You can then refer to one of the other outputs or in the SQL database expand the text within the matched objects (paragraphs) in the 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.~{ 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 and we can tell you which documents meet your search criteria, but there is no way we can tell you without opening each document where within each your matches are found. }~
+
+% 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

+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:
+
+_1 sisu --help sql
+
+code{
+
+Postgresql
+ user: ralph
+ current db set: SiSU_sisu
+ port: 5432
+ dbi connect: DBI:Pg:database=SiSU_sisu;port=5432
+
+sqlite
+ current db set: /home/ralph/sisu_www/sisu/sisu_sqlite.db
+ dbi connect DBI:SQLite:/home/ralph/sisu_www/sisu/sisu_sqlite.db
+
+}code
+
+Note on databases built
+
+By default, [unless otherwise specified] databases are built on a directory basis, from collections of documents within that directory. The name of the directory you choose to work from is used as the database name, i.e. if you are working in a directory called /home/ralph/ebook the database SiSU_ebook is used. [otherwise a manual mapping for the collection is necessary]
+
+2~ Search Form
+
+!_ sisu -F

+generates a sample search form, which must be copied to the web-server cgi directory
+
+!_ 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

+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
new file mode 100644
index 00000000..d5da379f
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_search_intro.ssi
@@ -0,0 +1,31 @@
+% SiSU insert 2.0
+
+@title: SiSU
+ :subtitle: Search
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? @title @creator
+
+:B~? SiSU Search
+
+1~search_intro SiSU Search - Introduction
+
+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.
+
+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.
+
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_short_feature_summary.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_short_feature_summary.ssi
new file mode 100644
index 00000000..294644af
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_short_feature_summary.ssi
@@ -0,0 +1,81 @@
+% SiSU 2.0
+
+@title: SiSU
+ :subtitle: Summary of Features
+
+@creator:
+ :author: Ralph Amissah
+
+@date:
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :published: 2007-09-16
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? @title @creator
+
+:B~? What is SiSU?
+
+:C~? Description
+
+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, epub, 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:
+
+_* HTML - both as a single scrollable text and a segmented document
+
+_* XHTML
+
+_* EPUB
+
+_* XML - both in sax and dom style xml structures for further development as required
+
+_* ODT - Open Document Format text, the iso standard for document storage
+
+_* LaTeX - used to generate pdf
+
+_* PDF (via LaTeX)
+
+_* SQL - population of an sql database (PostgreSQL or SQLite), (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, EPUB, 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, epub in 2009 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, EPUB, 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/markup-samples/manual/en/sisu_sql.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_sql.ssi
new file mode 100644
index 00000000..6e54275b
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_sql.ssi
@@ -0,0 +1,50 @@
+% SiSU insert 2.0
+
+@title: SiSU
+ :subtitle: SQL and Search
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :published: 2007-09-16
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? SiSU Search
+
+:C~? Search
+
+1~search_sql SQL
+
+2~ populating SQL type databases
+
+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:
+
+_1* one containing semantic (and other) headers, including, title, author, subject, (the Dublin Core...);
+
+_1* another the substantive texts by individual "paragraph" (or object) - along with structural information, each paragraph being identifiable by its paragraph number (if it has one which almost all of them do), and the substantive text of each paragraph quite naturally being searchable (both in formatted and clean text versions for searching); and
+
+_1* a third containing endnotes cross-referenced back to the paragraph from which they are referenced (both in formatted and clean text versions for searching).
+
+_1* a fourth table with a one to one relation with the headers table contains full text versions of output, eg. pdf, html, xml, and ascii.
+
+There is of course the possibility to add further structures.
+
+At this level SiSU loads a relational database with documents chunked into objects, their smallest logical structurally constituent parts, as text objects, with their object citation number and all other structural information needed to construct the document. Text is stored (at this text object level) with and without elementary markup tagging, the stripped version being so as to facilitate ease of searching.
+
+Being able to search a relational database at an object level with the SiSU citation system is an effective way of locating content generated by SiSU. As individual text objects of a document stored (and indexed) together with object numbers, and all versions of the document have the same numbering, complex searches can be tailored to return just the locations of the search results relevant for all available output formats, with live links to the precise locations in the database or in html/xml documents; or, the structural information provided makes it possible to search the full contents of the database and have headings in which search content appears, or to search only headings etc. (as the Dublin Core is incorporated it is easy to make use of that as well).
+
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_sqlite.sst b/data/doc/sisu/markup-samples/manual/en/sisu_sqlite.sst
new file mode 100644
index 00000000..a73ae16c
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_sqlite.sst
@@ -0,0 +1,82 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: Sqlite / search
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: electronic documents:SiSU:document:sqlite;SiSU:manual:sqlite;electronic documents:SiSU:manual:sqlite;SiSU:document:sqlite;SiSU:document:sqlite
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+@make:
+ :manpage: section=7; name=sisu - package to install what sisu needs to to populate a postgresql database (postgresql dependency component); synopsis=sisu -dv [filename/wildcard ]\n sisu -dv [instruction]
+
+:A~? @title @creator
+
+% :B~? SiSU Sqlite
+
+1~sqlite Sqlite
+
+2~ Name
+
+SiSU - Structured information, Serialized Units - a document publishing system.
+
+
+2~ Description
+
+Information related to using sqlite with sisu (and related to the sisu_sqlite dependency package, which is a dummy package to install dependencies needed for SiSU to populate an sqlite database, this being part of SiSU - man sisu).
+
+2~ Synopsis
+
+_1 sisu -d [instruction] [filename/wildcard if required]
+
+_1 sisu -d --(sqlite|pg) --[instruction] [filename/wildcard if required]
+
+
+2~ Commands
+
+Mappings to two databases are provided by default, postgresql and sqlite, the same commands are used within sisu to construct and populate databases however -d (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, alternatively --sqlite or --pgsql may be used
+
+!_ -d or --sqlite
+may be used interchangeably.
+
+3~ create and destroy database
+
+!_ --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

+creates database where no database existed before
+
+!_ sisu -d --create

+creates database tables where no database tables existed before
+
+!_ 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

+destroys existing database and builds a new empty database structure
+
+3~ import and remove documents
+
+!_ 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]

+updates file contents in database
+
+!_ sisu -d --remove -v [filename/wildcard]

+removes specified document from sqlite database.
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_synopsis.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_synopsis.ssi
new file mode 100644
index 00000000..98e5d4f3
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_synopsis.ssi
@@ -0,0 +1,48 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: Commands
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :published: 2007-09-16
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? @title @creator
+
+:B~? SiSU Commands
+
+1~ Synopsis
+
+SiSU - Structured information, Serialized Units - a document publishing system
+
+sisu [ -abcDdeFhIiMmNnopqRrSsTtUuVvwXxYyZz0-9 ] [ filename/ wildcard ]
+
+sisu [ -Ddcv ] [ instruction ]
+
+sisu [ -CcFLSVvW ]
+
+Note: commands should be issued from within the directory that contains the marked up files, cd to markup directory.
+
+sisu is at version 2, version 3 is under development. To use sisu version 3
+
+sisu --v3 [and options/operations as above]
+
+or
+
+sisu3 [and options/operations as above]
+
+sisu version 1 has been discontinued.
+
+for settings see sisu --help env
+
+sisu [ filename/ wildcard] == sisu -0 [filename/wildcard]
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_syntax_highlighting.sst b/data/doc/sisu/markup-samples/manual/en/sisu_syntax_highlighting.sst
new file mode 100644
index 00000000..ef881aae
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_syntax_highlighting.sst
@@ -0,0 +1,151 @@
+% SiSU insert 4.0
+
+@title: SiSU
+ :subtitle: Syntax Highlighting
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-11-12
+ :issued: 2002-11-12
+ :available: 2002-11-12
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: electronic documents:SiSU:document:syntax highlighting;SiSU:manual:syntax highlighting;electronic documents:SiSU:manual:syntax highlighting;SiSU:document:syntax highlighting;SiSU:document:syntax highlighting
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~? @title @creator
+
+:B~? SiSU Syntax Highlighting
+
+1~ Editor Files, Syntax Highlighting
+
+The directory:
+
+_1 ./data/sisu/conf/editor-syntax-etc/
+
+_1 /usr/share/sisu/conf/editor-syntax-etc
+
+contains rudimentary sisu syntax highlighting files for:
+
+_* (g)vim http://www.vim.org
+
+_1 package: sisu-vim
+
+status: largely done
+
+_1 there is a vim syntax highlighting and folds component
+
+_* gedit http://www.gnome.org/projects/gedit
+
+_* gobby http://gobby.0x539.de/
+
+_1 file: sisu.lang
+
+place in:
+
+_1 /usr/share/gtksourceview-1.0/language-specs
+
+or
+
+_1 ~/.gnome2/gtksourceview-1.0/language-specs
+
+_1 status: very basic syntax highlighting
+
+_1 comments: this editor features display line wrap and is used by Goby!
+
+_* nano http://www.nano-editor.org
+
+_1 file: nanorc
+
+save as:
+
+_1 ~/.nanorc
+
+_1 status: basic syntax highlighting
+
+_1 comments: assumes dark background; no display line-wrap; does line breaks
+
+_* diakonos (an editor written in ruby) http://purepistos.net/diakonos
+
+file: diakonos.conf
+
+save as:
+
+_1 ~/.diakonos/diakonos.conf
+
+includes:
+
+_1 status: basic syntax highlighting
+
+comments: assumes dark background; no display line-wrap
+
+_* kate & kwrite http://kate.kde.org
+
+_1 file: sisu.xml
+
+_1 place in:
+
+_2 /usr/share/apps/katepart/syntax
+
+_1 or
+
+_2 ~/.kde/share/apps/katepart/syntax
+
+_1 [settings::configure kate::{highlighting,filetypes}]
+
+_1 [tools::highlighting::{markup,scripts}::SiSU]
+
+% kde-config --prefix
+% KDEDIR/share/apps/katepart/syntax/
+% KDEHOME/share/apps/katepart/syntax
+% [In the configure dialog in kate, go to the "Editor->highlighting" page and
+% >select a highlight to change the mimetype/pattern associations for it.]
+% /etc/mime.types
+% /usr/share/mime/text
+
+_* nedit http://www.nedit.org
+
+_1 file: sisu_nedit.pats
+
+_1 nedit -import sisu_nedit.pats
+
+_1 status: a very clumsy first attempt [not really done]
+
+_1 comments: this editor features display line wrap
+
+_* emacs http://www.gnu.org/software/emacs/emacs.html
+
+_1 files: sisu-mode.el
+
+_1 to file ~/.emacs add the following 2 lines:
+
+_2 (add-to-list 'load-path "/usr/share/sisu/conf/editor-syntax-etc/emacs")
+
+_2 (require 'sisu-mode.el)
+
+_1 [not done / not yet included]
+
+_* vim & gvim http://www.vim.org
+
+_1 files:
+
+_1 package is the most comprehensive sisu syntax highlighting and editor environment provided to date (is for vim/ gvim, and is separate from the contents of this directory)
+
+_1 status: this includes: syntax highlighting; vim folds; some error checking
+
+_1 comments: this editor features display line wrap
+
+NOTE:
+
+[SiSU parses files with long lines or line breaks, but, display linewrap (without line-breaks) is a convenient editor feature to have for sisu markup]
+
+% aeditor (an editor written in ruby)
+
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_webrick.sst b/data/doc/sisu/markup-samples/manual/en/sisu_webrick.sst
new file mode 100644
index 00000000..6e56e53a
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_webrick.sst
@@ -0,0 +1,59 @@
+% SiSU 4.0
+
+@title: SiSU
+ :subtitle: sisu_webrick
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2007-08-28
+ :published: 2007-09-16
+ :modified: 2012-10-03
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: electronic documents:SiSU:document:webrick;SiSU:manual:webrick;electronic documents:SiSU:manual:webrick;SiSU:document:webrick;SiSU:document:webrick
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+@make:
+ :manpage: section=7; name=sisu - documents: structuring, publishing in multiple formats, and search; synopsis=sisu -W
+
+:A~? @title @creator
+
+:B~? SiSU Webrick
+
+1~webrick sisu_webrick
+
+2~ Name
+
+SiSU - Structured information, Serialized Units - a document publishing system
+
+2~ Synopsis
+
+sisu_webrick [port]
+
+or
+
+sisu -W [port]
+
+2~ Description
+
+sisu_webrick is part of SiSU (man sisu) sisu_webrick starts Ruby's Webrick web-server and points it to the directories to which SiSU output is written, providing a list of these directories (assuming SiSU is in use and they exist).
+
+The default port for sisu_webrick is set to 8081, this may be modified in the yaml file: ~/.sisu/sisurc.yml a sample of which is provided as /etc/sisu/sisurc.yml (or in the equivalent directory on your system).
+
+2~ Summary of man page
+
+sisu_webrick, may be started on it's own with the command: sisu_webrick [port] or using the sisu command with the -W flag: sisu -W [port]
+
+where no port is given and settings are unchanged the default port is 8081
+
+2~ Document processing command flags
+
+sisu -W [port] starts Ruby Webrick web-server, serving SiSU output directories, on the port provided, or if no port is provided and the defaults have not been changed in ~/.sisu/sisurc.yaml then on port 8081
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_work_needed_and_wishlist.ssi b/data/doc/sisu/markup-samples/manual/en/sisu_work_needed_and_wishlist.ssi
new file mode 100644
index 00000000..20e774ac
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_work_needed_and_wishlist.ssi
@@ -0,0 +1,59 @@
+% SiSU 2.0
+
+@title: SiSU
+ :subtitle: Work Needed and Wishlist
+
+@creator:
+ :author: Ralph Amissah
+
+@date:
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :published: 2007-09-16
+ :modified: 2011-02-07
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? @title @creator
+
+:B~? Work Needed and Wishlist
+
+1~sisu_work_needed Work Needed
+
+SiSU is fairly mature and for most purposes the syntax and what it is supposed to do is clear. For the most part additions and changes are minor and backward compatible, (in particular there may be things of interest that to be able to achieve will require additions to the syntax).
+
+_* Amongst the most requested features is a way to represent and extract bibliographies from scholarly and other writings. This involves an extension of sisu markup syntax and a new module to extract the bibliography.
+
+_* Integration of postgresql tsearch2 / gin indexing, (which currently needs to be done manually, and) which has been waiting for the integration of tsearch2 / gin into Postgresql main, which is supposed to occur in Postgresql 8.3
+
+_* Internationalisation always. SiSU is utf-8 and for those parts that are utf-8 friendly will work out of the box - html and postgresql for example work out of the box (and for example comfortably represent Chinese text), LaTeX and odf do not work out of the box, they need additional work for extended language sets.
+
+_* Refinements and improvements to output representations, some are fairly mature, others (such as manpages and info files (and even ODF) remain young.
+
+_* Simple extension to contain, link and share included audio and multi-media files, (including sisupod.zip)
+
+1~sisu_wishlist Wishlist
+
+SiSU provides a lot of "plumbing" and is readily usable as a tool by those comfortable with marking up documents with an editor. The syntax is fairly easy to learn, especially the subset required to start using SiSU effectively.
+
+SiSU might also be of interest to developers interested in:
+
+_* experimenting with the search implications offered
+
+_* producing additional output formats
+
+_* producing conversion tools
+
+_* producing input interfaces, (experimenting with additional interfaces for producing sisu source documents)
+
+Several tools that are of interest would come under the heading interface and conversion. Amongst others, the following are of interest:
+
+_* Converters from various document formats, such as Open Document Text (ODF), MS Word(TM) and Word Perfect(TM), even html. The problem here is one of the most important things for SiSU is to be able to recognise the structure of a document, and many documents prepared in other formats have not been prepared strictly with a view to representing structure, but appearance - so heading levels may be "painted" to look right rather than have the correct structural representation. Even if conversion is not perfect this may serve as a first step in assisting in conversion of documents to SiSU for those with legacy document sets that they would like to have in sisu format. (once in SiSU it is easier to get out in various other formats as this is what sisu does, within the constraints of the information that sisu uses to generate output)
+
+_* The possibility to save directly from from various word processors, and possibly templates within them to assist in making sure the document structure is "understood" by SiSU.
+
+_* Web interface/front-end, a form like front end for the writing or submission of sisu documents to a server which uses SiSU to generate output. Headers could be made available as separate small entry forms with help provided to explain where they might be used. Apart from the most important headers such as title, author, date and possibly subject the remainder of the header forms could be placed after the form for substantive content. This would offer a more Web 2.0 like approach to the use of SiSU and the possibility of using it for collaborative editing of content (possibly for documents that are to be finalised/published as the citation system is most suited to published works). [Collaborative editing is currently possible through use of a collaborative editor such as Gobby which makes use of the Obby protocol].
+
diff --git a/data/doc/sisu/markup-samples/manual/translation_languages b/data/doc/sisu/markup-samples/manual/translation_languages
new file mode 100644
index 00000000..d84a94e8
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/translation_languages
@@ -0,0 +1 @@
+de fr es ja ru zh
diff --git a/data/doc/sisu/markup-samples/sisu_manual/Rakefile b/data/doc/sisu/markup-samples/sisu_manual/Rakefile
deleted file mode 100644
index 1d9b5414..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/Rakefile
+++ /dev/null
@@ -1,404 +0,0 @@
-#!/usr/bin/env ruby
-raise 'Please, use ruby1.9.3 or later.' if RUBY_VERSION < '1.9.3'
-=begin
- Common Rakefile, Rantfile to place sisu markup translation under
- po4a management softlink Rakefile and Rantfile to this file
-
- * Homepage:
-
- * Download:
-
- Copyright (C) 2013 Ralph Amissah
-
- * License: LGPL - GNU Lesser General Public License
- [same license as Rant provided within the Rant package]
-
- * Ralph Amissah
- Ralph Amissah
-
- Rake is a Ruby build program by Jim Weirich
- * Rake may be downloaded and installed from:
-
-
- Rant is a Ruby build program by Stefan Lang
- * Rant may be downloaded and installed from:
-
-
- Notes on use:
- rake -T
- [if rant is preferred and installed]
- rant -T
-=end
-require 'find'
-require 'fileutils'
-#require 'ftools'
-require 'rbconfig.rb'
-#include RbConfig
-require 'yaml'
-include FileUtils
-def project_details
- def name
- 'SiSU translations under po4a management'
- end
- def name_warning
- <<-WOK
-#{name}
-
-WARNING all sisu markup files (.ssm, .sst, .ssi) in languages other than #{language.source}
-are managed by po4a, through translations of the source language to other languages.
-
-#{language.info_on_selection}
- WOK
- end
- def rake_project
- "Rakefile for placing #{name}"
- end
- self
-end
-def query
- def answer?(ask)
- resp='redo'
- print ask + %{ ['yes', 'no' or 'quit']: }
- resp=File.new('/dev/tty').gets.strip
- if resp == 'yes'; true
- elsif resp == 'no'; false
- elsif resp =~/^quit|exit$/; exit
- else
- puts %{[please type: 'yes', 'no' or 'quit']}
- answer?(ask)
- end
- end
- self
-end
-def notice
- def warn_and_proceed?
- %{WARNING: This Software is used entirely at your own risk.
- PROCEED?}
- end
- def default(selection=nil)
- ans= if selection
- case selection
- when selection.is_a?(String)
- <<-WOK
- #{project_details.rake_project}
- Information on alternative actions is available using: "rake help" or "rake -T"
- Default action selected - "#{selection} #{project_details.name}"
- #{warn_and_proceed?}
- WOK
- when :make
- <<-WOK
- #{project_details.rake_project}
- Information on alternative actions is available using: "rake help" or "rake -T"
- #{selection.upcase} selected - #{selection} #{project_details.name}
- WARNING: this action assumes (and places) this project is under po4a
- (translation) management. It will create the sub-directories:
- #{language.translations_available_str}
- & file: #{filename.po4a_cfg}
- in the current directory:
- #{Dir.pwd}
- It will populate the sub-directories with translation files created from
- the pot and po files found under the corresponding language sub-directories,
- (under #{dir.pot}/ & #{dir.po}/). (OVERWRITING any existing translated
- .ssm .sst .ssi files in language subdirectories that are not under po4a
- management).
- #{warn_and_proceed?}
- WOK
- when :clean
- <<-WOK
- #{project_details.rake_project}
- Information on alternative actions is available using: "rake help" or "rake -T"
- #{selection.upcase} selected - #{selection} #{project_details.name}
- #{warn_and_proceed?}
- WOK
- when :distclean
- <<-WOK
- #{project_details.rake_project}
- Information on alternative actions is available using: "rake help" or "rake -T"
- #{selection.upcase} selected - #{selection} #{project_details.name}
- WARNING: this action assumes (and places) this project is under po4a
- (translation) management. It will remove the sub-directories:
- #{language.translations_available_str}
- & file: #{filename.po4a_cfg}
- in the current directory:
- #{Dir.pwd}
- Note: these sub-directories & the config file #{filename.po4a_cfg}
- should be auto-generated from pot and po files if this project translation
- is under po4a management.
- This query is to give you the chance to make sure you know what you are doing.
- #{warn_and_proceed?}
- WOK
- when :rebuild
- <<-WOK
- #{project_details.rake_project}
- Information on alternative actions is available using: "rake help" or "rake -T"
- #{selection.upcase} selected - #{selection} #{project_details.name}
- WARNING: this action assumes (and places) this project is under po4a
- (translation) management. It will destroy/clobber and then create again the
- sub-directories:
- #{language.translations_available_str}
- populating them with translation files created from the pot and po files
- found under the corresponding language sub-directories in (#{dir.pot}/
- & #{dir.po}/).
- It will also generate the file: #{filename.po4a_cfg}
- These actions will be taken in the current directory:
- #{Dir.pwd}
- This query is to give you the chance to make sure you know what you are doing.
- #{warn_and_proceed?}
- WOK
- else
- <<-WOK
- #{project_details.rake_project}
- Information on alternative actions is available using: "rake help" or "rake -T"
- Default action selected - "#{selection} #{project_details.name}"
- #{warn_and_proceed?}
- WOK
- end
- else
- <<-WOK
- #{project_details.rake_project}
- Information on alternative actions is available using: "rake help" or "rake -T"
- Default action selected - "install and to setup #{project_details.name}"
- #{warn_and_proceed?}
- WOK
- end
- resp=query.answer?(ans)
- exit unless resp
- end
- def project_help
- puts <<-WOK
-#{project_details.name}
-#{project_details.rake_project}
-
-This rake file is to assist with having sisu markup files under po4a
-translation management. It assumes that the source language files are placed
-under the sub-directory identifying the source language set, which is currently
-#{language.source}
-The files there are used to make the source translation file in the directory #{dir.pot}/
-Which is then used to create files for translation under the directory #{dir.po}/
-in sub-directories bearing the translation languages ISO code.
-
-The current language translation selection is: #{translations_selected_str}
-The languages selected are located in the file: #{filename.languages}
-
-sisu available language list: #{sisu_available_str}
-
-For a more detailed and up to date task list use:
-
- rake -T
-
- WOK
- end
- self
-end
-def tasks
- system('rake -T')
-end
-def filename
- def languages
- 'translation_languages'
- end
- def po4a_cfg
- 'po4a.cfg'
- end
- self
-end
-def dir
- def pwd
- Dir.pwd
- end
- def po4a_
- 'po4a/' # ''
- end
- def pot
- po4a_ + 'pot'
- end
- def po
- po4a_ + 'po'
- end
- self
-end
-def dir_mk(dir)
- FileUtils::mkdir_p(dir) unless FileTest.directory?(dir)
-end
-def po4a_flags
- def debug
- '-d -v'
- end
- def normal
- ''
- end
- def quiet
- '-q'
- end
- self
-end
-def language
- def source #source_language
- 'en'
- end
- def translations_selected #translation_languages
- IO.read(filename.languages, mode: 'r:utf-8').split(/\s+/)
- end
- def translations_available
- translations_selected & sisu_available
- end
- def info_on_selection
- if translations_selected != translations_available
- <<-WOK
-WARNING: language selections mismatch
-
-The current language translation selection appears to be: #{translations_selected_str}
-Of which the following are valid (available) selections: #{translations_available_str}
-
-sisu available language list: #{sisu_available_str}
-
-the following will be used: #{translations_available_str}
-The languages selected are located in the file: #{filename.languages}
- WOK
- else
- <<-WOK
-The current language translation selection is: #{translations_selected_str}
-The languages selected are located in the file: #{filename.languages}
-
-sisu available language list: #{sisu_available_str}
- WOK
- end
- end
- def sisu_available
- %w[am bg bn br ca cs cy da de el en eo es et eu fi fr ga gl he hi hr hy ia is it ja ko la lo lt lv ml mr nl nn no oc pl pt pt_BR ro ru sa se sk sl sq sr sv ta te th tk tr uk ur us vi zh]
- end
- def translations_selected_str
- language.translations_selected.join(' ')
- end
- def translations_available_str
- language.translations_available.join(' ')
- end
- def sisu_available_str
- language.sisu_available.join(' ')
- end
- self
-end
-def files_src
- def ssm
- Dir.glob("#{language.source}/*.ssm").sort
- end
- def sst
- Dir.glob("#{language.source}/*.sst").sort
- end
- def ssi
- Dir.glob("#{language.source}/*.ssi").sort
- end
- def all
- Dir.glob("#{language.source}/*{.ssm,.sst,.ssi}").sort
- end
- self
-end
-def po4a_cfg_file
- File.open("#{Dir.pwd}/#{filename.po4a_cfg}",'w')
-end
-def po4a
- def configure #po4a_cfg
- po4a_cfg_arr=[]
- po4a_cfg_arr << "[po4a_langs] #{language.translations_available_str}"
- po4a_cfg_arr << "[po4a_paths] #{dir.pot}/$master.pot $lang:#{dir.po}/$lang/$master.po"
- files_src.ssm.each do |file_src|
- file_src_fn=file_src.gsub(/#{language.source}\//,'')
- po4a_cfg_arr << "[type: text] #{file_src} $lang:$lang/#{file_src_fn}"
- end
- files_src.sst.each do |file_src|
- file_src_fn=file_src.gsub(/#{language.source}\//,'')
- po4a_cfg_arr << "[type: text] #{file_src} $lang:$lang/#{file_src_fn}"
- end
- files_src.ssi.each do |file_src|
- file_src_fn=file_src.gsub(/#{language.source}\//,'')
- po4a_cfg_arr << "[type: text] #{file_src} $lang:$lang/#{file_src_fn}"
- end
- file=po4a_cfg_file
- po4a_cfg_arr.each do |txt|
- puts txt
- file << txt << "\n"
- end
- file.close
- system("po4a --keep 0 --no-backups --package-name sisu-manual #{po4a_flags.normal} #{filename.po4a_cfg}")
- end
- self
-end
-def project
- dir_mk(dir.pot)
- language.translations_available.each do |lang_dir|
- dir_lang="#{Dir.pwd}/#{dir.po}/#{lang_dir}"
- dir_mk(dir_lang)
- end
- po4a.configure
-end
-def clean
- #rm -rf ../build
- FileUtils.rm_f Dir.glob("#{dir.po}/*/*.po~")
-end
-def distclean
- FileUtils::rm_f(filename.po4a_cfg)
- FileUtils::rm_r(language.translations_available,:force => true)
-end
-
-#% task lists
-desc "runs make (see its description below)"
-task :default => [:make]
-desc "assist with having sisu markup files managed by po4a
- create configuration files, and language directories and
- populate them with po4a pot & po files for translation and
- from those (as translated) create translated sisu markup
- .ssm .sst & .ssi files in corresponding language sub-directories"
-task :make => [:notice_make_,:build_]
-desc "help"
-task :help => [:project_help_,:tasks_]
-desc "clean temporary files"
-task :clean => [:notice_clean_,:clean_]
-desc "removes auto-generated files under po4a management
- including translated .ssm .sst & .ssi files,
- that are created from po4a pot and po files"
-task :distclean => [:notice_distclean_,:distclean_]
-desc "runs 'distclean' and 'make' (see their descriptions above)"
-task :rebuild => [:notice_rebuild_,:distclean_,:build_]
-if File.directory?(dir.pot) \
-and File.directory?(dir.po)
- #desc ""
- task :clean! => [:clean_]
- task :distclean! => [:distclean_]
- task :rebuild! => [:distclean_,:build_]
- task :make! => [:build_]
-else
- task :make! => [:build_]
-end
-
-#% task actions
-task :project_help_ do
- notice.project_help
-end
-task :tasks_ do
- tasks
-end
-task :build_ do
- project
-end
-task :clean_ do
- clean
-end
-task :distclean_ do
- distclean
-end
-task :notice_default_ do
- notice.default
-end
-task :notice_make_ do
- notice.default(:make)
-end
-task :notice_clean_ do
- notice.default(:clean)
-end
-task :notice_distclean_ do
- notice.default(:distclean)
-end
-task :notice_rebuild_ do
- notice.default(:rebuild)
-end
-__END__
diff --git a/data/doc/sisu/markup-samples/sisu_manual/_sisu/image/GnuDebianLinuxRubyBetterWay.png b/data/doc/sisu/markup-samples/sisu_manual/_sisu/image/GnuDebianLinuxRubyBetterWay.png
deleted file mode 100644
index ce5b8830..00000000
Binary files a/data/doc/sisu/markup-samples/sisu_manual/_sisu/image/GnuDebianLinuxRubyBetterWay.png and /dev/null differ
diff --git a/data/doc/sisu/markup-samples/sisu_manual/_sisu/image/ruby_logo.png b/data/doc/sisu/markup-samples/sisu_manual/_sisu/image/ruby_logo.png
deleted file mode 100644
index 829e2458..00000000
Binary files a/data/doc/sisu/markup-samples/sisu_manual/_sisu/image/ruby_logo.png and /dev/null differ
diff --git a/data/doc/sisu/markup-samples/sisu_manual/_sisu/image/sisu.png b/data/doc/sisu/markup-samples/sisu_manual/_sisu/image/sisu.png
deleted file mode 100644
index b449fa6b..00000000
Binary files a/data/doc/sisu/markup-samples/sisu_manual/_sisu/image/sisu.png and /dev/null differ
diff --git a/data/doc/sisu/markup-samples/sisu_manual/_sisu/image/tux.png b/data/doc/sisu/markup-samples/sisu_manual/_sisu/image/tux.png
deleted file mode 100644
index 15fd152b..00000000
Binary files a/data/doc/sisu/markup-samples/sisu_manual/_sisu/image/tux.png and /dev/null differ
diff --git a/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_fn.yml b/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_fn.yml
deleted file mode 100644
index f12e3144..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_fn.yml
+++ /dev/null
@@ -1,137 +0,0 @@
-# Name: SiSU - Simple information Structuring Universe
-# Author: ralph@amissah.com
-# Description: Site wide environment defaults set here
-# system environment info / resource configuration file, for sisu
-# License: GPL v3 or later
-# site environment configuration file
-# this file should be configured and live in
-# /etc/sisu #per environment settings, overridden by:
-# ~/.sisu #per user settings, overridden by:
-# ./_sisu #per local markup directory settings
-#% #image source directory, main path and subdirectories
-#image:
-# path: 'sisu_working'
-# public: '_sisu/image'
-# #all: 'image'
-#% presentation/web directory, main path and subdirectories (most subdirectories are created automatically based on markup directory name)
-#webserv:
-# url_root: 'http://www.your.url' #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
-# images: '_sisu/image'
-# man: 'man'
-# cgi: '/usr/local/lib/sisu-cgi'
-# feed: 'feed'
-# sqlite: 'sisu/sqlite'
-# webrick_url: true
-#show_output_on: 'filesystem' #for -v and -u url information, alternatives: 'filesystem','webserver','remote_webserver','local:8111','localhost','localhost:8080','webrick','path'
-#show_output_on: 'local:8111'
-#webserv_cgi:
-# host: localhost
-# base_path: ~
-# port: '8081'
-# user: ~
-# file_links: webserv
-
-show_output_on: 'filesystem_url'
-#texinfo display output
-#texinfo:
-# stub: 'texinfo'
-
-##% processing directories, main path and subdirectories (appended to $HOME), using defaults set in sysenv
-#processing:
-# path: 'sisu_processing'
-# metaverse: 'metaverse'
-# tune: 'tune'
-# latex: 'tex'
-# texinfo: 'texinfo'
-# concord_max: 400000
-
-#% flag - set (non-default) processing flag shortcuts -1, -2 etc. (here adding colour and verbosity as default)
-flag:
- color: true # making colour default -c is toggle, and will now toggle colour off
-# default: '-NQdhewpotbxXyYv' # includes verbose; -m would in any event be run by default
-# i: '-NQdhewpoty' # -m run by default
-# ii: '-NQdhewpotbxXy' # -m run by default
-# iii: '-NQdhewpotbxXyY' # -m run by default
-# iv: '-NQhewpotbxXYDy --update' # -m run by default
-# v: '-NQhewpotbxXYDyv --update' # includes verbose; -m run by default
-
-#% papersize, (LaTeX/pdf) available values: A4, US_letter, book_b5, book_a5, US_legal
-default:
- papersize: 'a4,letter'
- #language: 'en'
- #texpdf_font: 'Liberation Sans' # 'Liberation Sans' 'Liberation Serif'
- #texpdf_font_mono: 'Liberation Mono' #'Inconsolata'
- #text_wrap: 78
- #emphasis: 'bold' #make *{emphasis}* 'bold', 'italics' or 'underscore', default if not configured is 'bold'
- #digest: 'sha' #sha is sha256, default is md5
- #language: 'English'
- #emphasis: 'italics'
-
-#% settings used by ssh scp
-#remote:
-# -
-# user: '[usrname]'
-# host: '[remote.hostname]'
-# path: '.' #no trailing slash eg 'sisu/www'
-# -
-# user: '[usrname]'
-# host: '[remote.hostname]'
-# path: '.' #no trailing slash eg 'sisu/www'
-
-#% webrick information
-#webrick:
-# port: '8081'
-
-#sql database info, postgresql and sqlite
-db:
- postgresql:
- port: '5432' # '5432'
- #host: # '[if not localhost, provide host tcp/ip address or domain name]''
- #user: # '[(if different from user) provide username]'
- #password: # '[password if required]'
-# sqlite:
-# path: ~ # './sisu_sqlite.db'
-# port: "**"
-
-#% output_dir_structure_by: language (language_and_filetype); filetype; or filename (original v1 & v2)
-output_dir_structure_by: filename
-#% lingual: 'multi' | 'mono' (multi default)
-#lingual: mono
-#% language_default: lng_lst: %w[am bg bn br ca cs cy da de el en eo es et eu fi fr ga gl he hi hr hy ia is it ja ko la lo lt lv ml mr nl nn no oc pl pt pt_BR ro ru sa se sk sl sq sr sv ta te th tk tr uk ur us vi zh] ('en' default)
-#language_default: 'en'
-
-permission_set:
- zap: true
- css_modify: true
- remote_base_site: true
-
-program_set:
- rmagick: true
-# wc: true
-# editor: true
-# postgresql: true
-# sqlite: true
-# tidy: true
-# rexml: true
-# pdflatex: true
-
-#program_select:
-# editor: 'vim'
-# pdf_viewer: 'evince'
-# web_browser: 'iceweasel'
-# console_web_browser: 'links2' #'elinks' #'w3m' #'lynx' #'links'
-# odf_viewer: 'lowriter' #'oowriter' #'abiword'
-# xml_viewer: 'xml-viewer'
-# epub_viewer: 'ebook-viewer' #'calibre' #'fbreader' #'okular'
-# info_viewer: 'pinfo -f'
-# man: 'man' #'groff -man -Tascii' # 'nroff -man'
-
-#search:
-# sisu:
-# flag: true
-## action: http://localhost:8081/cgi-bin/sisu_pgsql.cgi
-# action: http://search.sisudoc.org
-# db: sisu
-# title: sample search form
-#promo: sisu_search_libre, sisu_icon, sisu, open_society, fsf, ruby
diff --git a/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_fn_monolingual.yml b/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_fn_monolingual.yml
deleted file mode 100644
index b3c49ca1..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_fn_monolingual.yml
+++ /dev/null
@@ -1,137 +0,0 @@
-# Name: SiSU - Simple information Structuring Universe
-# Author: ralph@amissah.com
-# Description: Site wide environment defaults set here
-# system environment info / resource configuration file, for sisu
-# License: GPL v3 or later
-# site environment configuration file
-# this file should be configured and live in
-# /etc/sisu #per environment settings, overridden by:
-# ~/.sisu #per user settings, overridden by:
-# ./_sisu #per local markup directory settings
-#% #image source directory, main path and subdirectories
-#image:
-# path: 'sisu_working'
-# public: '_sisu/image'
-# #all: 'image'
-#% presentation/web directory, main path and subdirectories (most subdirectories are created automatically based on markup directory name)
-#webserv:
-# url_root: 'http://www.your.url' #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
-# images: '_sisu/image'
-# man: 'man'
-# cgi: '/usr/local/lib/sisu-cgi'
-# feed: 'feed'
-# sqlite: 'sisu/sqlite'
-# webrick_url: true
-#show_output_on: 'filesystem' #for -v and -u url information, alternatives: 'filesystem','webserver','remote_webserver','local:8111','localhost','localhost:8080','webrick','path'
-#show_output_on: 'local:8111'
-#webserv_cgi:
-# host: localhost
-# base_path: ~
-# port: '8081'
-# user: ~
-# file_links: webserv
-
-show_output_on: 'filesystem_url'
-#texinfo display output
-#texinfo:
-# stub: 'texinfo'
-
-##% processing directories, main path and subdirectories (appended to $HOME), using defaults set in sysenv
-#processing:
-# path: 'sisu_processing'
-# metaverse: 'metaverse'
-# tune: 'tune'
-# latex: 'tex'
-# texinfo: 'texinfo'
-# concord_max: 400000
-
-#% flag - set (non-default) processing flag shortcuts -1, -2 etc. (here adding colour and verbosity as default)
-flag:
- color: true # making colour default -c is toggle, and will now toggle colour off
-# default: '-NQdhewpotbxXyYv' # includes verbose; -m would in any event be run by default
-# i: '-NQdhewpoty' # -m run by default
-# ii: '-NQdhewpotbxXy' # -m run by default
-# iii: '-NQdhewpotbxXyY' # -m run by default
-# iv: '-NQhewpotbxXYDy --update' # -m run by default
-# v: '-NQhewpotbxXYDyv --update' # includes verbose; -m run by default
-
-#% papersize, (LaTeX/pdf) available values: A4, US_letter, book_b5, book_a5, US_legal
-default:
- papersize: 'a4,letter'
- #language: 'en'
- #texpdf_font: 'Liberation Sans' # 'Liberation Sans' 'Liberation Serif'
- #texpdf_font_mono: 'Liberation Mono' #'Inconsolata'
- #text_wrap: 78
- #emphasis: 'bold' #make *{emphasis}* 'bold', 'italics' or 'underscore', default if not configured is 'bold'
- #digest: 'sha' #sha is sha256, default is md5
- #language: 'English'
- #emphasis: 'italics'
-
-#% settings used by ssh scp
-#remote:
-# -
-# user: '[usrname]'
-# host: '[remote.hostname]'
-# path: '.' #no trailing slash eg 'sisu/www'
-# -
-# user: '[usrname]'
-# host: '[remote.hostname]'
-# path: '.' #no trailing slash eg 'sisu/www'
-
-#% webrick information
-#webrick:
-# port: '8081'
-
-#sql database info, postgresql and sqlite
-db:
- postgresql:
- port: '5432' # '5432'
- #host: # '[if not localhost, provide host tcp/ip address or domain name]''
- #user: # '[(if different from user) provide username]'
- #password: # '[password if required]'
-# sqlite:
-# path: ~ # './sisu_sqlite.db'
-# port: "**"
-
-#% output_dir_structure_by: language (language_and_filetype); filetype; or filename (original v1 & v2)
-output_dir_structure_by: filename
-#% lingual: 'multi' | 'mono' (multi default)
-lingual: mono
-#% language_default: lng_lst: %w[am bg bn br ca cs cy da de el en eo es et eu fi fr ga gl he hi hr hy ia is it ja ko la lo lt lv ml mr nl nn no oc pl pt pt_BR ro ru sa se sk sl sq sr sv ta te th tk tr uk ur us vi zh] ('en' default)
-#language_default: 'en'
-
-permission_set:
- zap: true
- css_modify: true
- remote_base_site: true
-
-program_set:
- rmagick: true
-# wc: true
-# editor: true
-# postgresql: true
-# sqlite: true
-# tidy: true
-# rexml: true
-# pdflatex: true
-
-#program_select:
-# editor: 'vim'
-# pdf_viewer: 'evince'
-# web_browser: 'iceweasel'
-# console_web_browser: 'links2' #'elinks' #'w3m' #'lynx' #'links'
-# odf_viewer: 'lowriter' #'oowriter' #'abiword'
-# xml_viewer: 'xml-viewer'
-# epub_viewer: 'ebook-viewer' #'calibre' #'fbreader' #'okular'
-# info_viewer: 'pinfo -f'
-# man: 'man' #'groff -man -Tascii' # 'nroff -man'
-
-#search:
-# sisu:
-# flag: true
-## action: http://localhost:8081/cgi-bin/sisu_pgsql.cgi
-# action: http://search.sisudoc.org
-# db: sisu
-# title: sample search form
-#promo: sisu_search_libre, sisu_icon, sisu, open_society, fsf, ruby
diff --git a/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_ft.yml b/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_ft.yml
deleted file mode 100644
index 71faa3e0..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_ft.yml
+++ /dev/null
@@ -1,137 +0,0 @@
-# Name: SiSU - Simple information Structuring Universe
-# Author: ralph@amissah.com
-# Description: Site wide environment defaults set here
-# system environment info / resource configuration file, for sisu
-# License: GPL v3 or later
-# site environment configuration file
-# this file should be configured and live in
-# /etc/sisu #per environment settings, overridden by:
-# ~/.sisu #per user settings, overridden by:
-# ./_sisu #per local markup directory settings
-#% #image source directory, main path and subdirectories
-#image:
-# path: 'sisu_working'
-# public: '_sisu/image'
-# #all: 'image'
-#% presentation/web directory, main path and subdirectories (most subdirectories are created automatically based on markup directory name)
-#webserv:
-# url_root: 'http://www.your.url' #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
-# images: '_sisu/image'
-# man: 'man'
-# cgi: '/usr/local/lib/sisu-cgi'
-# feed: 'feed'
-# sqlite: 'sisu/sqlite'
-# webrick_url: true
-#show_output_on: 'filesystem' #for -v and -u url information, alternatives: 'filesystem','webserver','remote_webserver','local:8111','localhost','localhost:8080','webrick','path'
-#show_output_on: 'local:8111'
-#webserv_cgi:
-# host: localhost
-# base_path: ~
-# port: '8081'
-# user: ~
-# file_links: webserv
-
-show_output_on: 'filesystem_url'
-#texinfo display output
-#texinfo:
-# stub: 'texinfo'
-
-##% processing directories, main path and subdirectories (appended to $HOME), using defaults set in sysenv
-#processing:
-# path: 'sisu_processing'
-# metaverse: 'metaverse'
-# tune: 'tune'
-# latex: 'tex'
-# texinfo: 'texinfo'
-# concord_max: 400000
-
-#% flag - set (non-default) processing flag shortcuts -1, -2 etc. (here adding colour and verbosity as default)
-flag:
- color: true # making colour default -c is toggle, and will now toggle colour off
-# default: '-NQdhewpotbxXyYv' # includes verbose; -m would in any event be run by default
-# i: '-NQdhewpoty' # -m run by default
-# ii: '-NQdhewpotbxXy' # -m run by default
-# iii: '-NQdhewpotbxXyY' # -m run by default
-# iv: '-NQhewpotbxXYDy --update' # -m run by default
-# v: '-NQhewpotbxXYDyv --update' # includes verbose; -m run by default
-
-#% papersize, (LaTeX/pdf) available values: A4, US_letter, book_b5, book_a5, US_legal
-default:
- papersize: 'a4,letter'
- #language: 'en'
- #texpdf_font: 'Liberation Sans' # 'Liberation Sans' 'Liberation Serif'
- #texpdf_font_mono: 'Liberation Mono' #'Inconsolata'
- #text_wrap: 78
- #emphasis: 'bold' #make *{emphasis}* 'bold', 'italics' or 'underscore', default if not configured is 'bold'
- #digest: 'sha' #sha is sha256, default is md5
- #language: 'English'
- #emphasis: 'italics'
-
-#% settings used by ssh scp
-#remote:
-# -
-# user: '[usrname]'
-# host: '[remote.hostname]'
-# path: '.' #no trailing slash eg 'sisu/www'
-# -
-# user: '[usrname]'
-# host: '[remote.hostname]'
-# path: '.' #no trailing slash eg 'sisu/www'
-
-#% webrick information
-#webrick:
-# port: '8081'
-
-#sql database info, postgresql and sqlite
-db:
- postgresql:
- port: '5432' # '5432'
- #host: # '[if not localhost, provide host tcp/ip address or domain name]''
- #user: # '[(if different from user) provide username]'
- #password: # '[password if required]'
-# sqlite:
-# path: ~ # './sisu_sqlite.db'
-# port: "**"
-
-#% output_dir_structure_by: language (language_and_filetype); filetype; or filename (original v1 & v2)
-output_dir_structure_by: filetype
-#% lingual: 'multi' | 'mono' (multi default)
-#lingual: mono
-#% language_default: lng_lst: %w[am bg bn br ca cs cy da de el en eo es et eu fi fr ga gl he hi hr hy ia is it ja ko la lo lt lv ml mr nl nn no oc pl pt pt_BR ro ru sa se sk sl sq sr sv ta te th tk tr uk ur us vi zh] ('en' default)
-#language_default: 'en'
-
-permission_set:
- zap: true
- css_modify: true
- remote_base_site: true
-
-program_set:
- rmagick: true
-# wc: true
-# editor: true
-# postgresql: true
-# sqlite: true
-# tidy: true
-# rexml: true
-# pdflatex: true
-
-#program_select:
-# editor: 'vim'
-# pdf_viewer: 'evince'
-# web_browser: 'iceweasel'
-# console_web_browser: 'links2' #'elinks' #'w3m' #'lynx' #'links'
-# odf_viewer: 'lowriter' #'oowriter' #'abiword'
-# xml_viewer: 'xml-viewer'
-# epub_viewer: 'ebook-viewer' #'calibre' #'fbreader' #'okular'
-# info_viewer: 'pinfo -f'
-# man: 'man' #'groff -man -Tascii' # 'nroff -man'
-
-#search:
-# sisu:
-# flag: true
-## action: http://localhost:8081/cgi-bin/sisu_pgsql.cgi
-# action: http://search.sisudoc.org
-# db: sisu
-# title: sample search form
-#promo: sisu_search_libre, sisu_icon, sisu, open_society, fsf, ruby
diff --git a/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_ft_monolingual.yml b/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_ft_monolingual.yml
deleted file mode 100644
index adf144d5..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_ft_monolingual.yml
+++ /dev/null
@@ -1,137 +0,0 @@
-# Name: SiSU - Simple information Structuring Universe
-# Author: ralph@amissah.com
-# Description: Site wide environment defaults set here
-# system environment info / resource configuration file, for sisu
-# License: GPL v3 or later
-# site environment configuration file
-# this file should be configured and live in
-# /etc/sisu #per environment settings, overridden by:
-# ~/.sisu #per user settings, overridden by:
-# ./_sisu #per local markup directory settings
-#% #image source directory, main path and subdirectories
-#image:
-# path: 'sisu_working'
-# public: '_sisu/image'
-# #all: 'image'
-#% presentation/web directory, main path and subdirectories (most subdirectories are created automatically based on markup directory name)
-#webserv:
-# url_root: 'http://www.your.url' #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
-# images: '_sisu/image'
-# man: 'man'
-# cgi: '/usr/local/lib/sisu-cgi'
-# feed: 'feed'
-# sqlite: 'sisu/sqlite'
-# webrick_url: true
-#show_output_on: 'filesystem' #for -v and -u url information, alternatives: 'filesystem','webserver','remote_webserver','local:8111','localhost','localhost:8080','webrick','path'
-#show_output_on: 'local:8111'
-#webserv_cgi:
-# host: localhost
-# base_path: ~
-# port: '8081'
-# user: ~
-# file_links: webserv
-
-show_output_on: 'filesystem_url'
-#texinfo display output
-#texinfo:
-# stub: 'texinfo'
-
-##% processing directories, main path and subdirectories (appended to $HOME), using defaults set in sysenv
-#processing:
-# path: 'sisu_processing'
-# metaverse: 'metaverse'
-# tune: 'tune'
-# latex: 'tex'
-# texinfo: 'texinfo'
-# concord_max: 400000
-
-#% flag - set (non-default) processing flag shortcuts -1, -2 etc. (here adding colour and verbosity as default)
-flag:
- color: true # making colour default -c is toggle, and will now toggle colour off
-# default: '-NQdhewpotbxXyYv' # includes verbose; -m would in any event be run by default
-# i: '-NQdhewpoty' # -m run by default
-# ii: '-NQdhewpotbxXy' # -m run by default
-# iii: '-NQdhewpotbxXyY' # -m run by default
-# iv: '-NQhewpotbxXYDy --update' # -m run by default
-# v: '-NQhewpotbxXYDyv --update' # includes verbose; -m run by default
-
-#% papersize, (LaTeX/pdf) available values: A4, US_letter, book_b5, book_a5, US_legal
-default:
- papersize: 'a4,letter'
- #language: 'en'
- #texpdf_font: 'Liberation Sans' # 'Liberation Sans' 'Liberation Serif'
- #texpdf_font_mono: 'Liberation Mono' #'Inconsolata'
- #text_wrap: 78
- #emphasis: 'bold' #make *{emphasis}* 'bold', 'italics' or 'underscore', default if not configured is 'bold'
- #digest: 'sha' #sha is sha256, default is md5
- #language: 'English'
- #emphasis: 'italics'
-
-#% settings used by ssh scp
-#remote:
-# -
-# user: '[usrname]'
-# host: '[remote.hostname]'
-# path: '.' #no trailing slash eg 'sisu/www'
-# -
-# user: '[usrname]'
-# host: '[remote.hostname]'
-# path: '.' #no trailing slash eg 'sisu/www'
-
-#% webrick information
-#webrick:
-# port: '8081'
-
-#sql database info, postgresql and sqlite
-db:
- postgresql:
- port: '5432' # '5432'
- #host: # '[if not localhost, provide host tcp/ip address or domain name]''
- #user: # '[(if different from user) provide username]'
- #password: # '[password if required]'
-# sqlite:
-# path: ~ # './sisu_sqlite.db'
-# port: "**"
-
-#% output_dir_structure_by: language (language_and_filetype); filetype; or filename (original v1 & v2)
-output_dir_structure_by: filetype
-#% lingual: 'multi' | 'mono' (multi default)
-lingual: mono
-#% language_default: lng_lst: %w[am bg bn br ca cs cy da de el en eo es et eu fi fr ga gl he hi hr hy ia is it ja ko la lo lt lv ml mr nl nn no oc pl pt pt_BR ro ru sa se sk sl sq sr sv ta te th tk tr uk ur us vi zh] ('en' default)
-#language_default: 'en'
-
-permission_set:
- zap: true
- css_modify: true
- remote_base_site: true
-
-program_set:
- rmagick: true
-# wc: true
-# editor: true
-# postgresql: true
-# sqlite: true
-# tidy: true
-# rexml: true
-# pdflatex: true
-
-#program_select:
-# editor: 'vim'
-# pdf_viewer: 'evince'
-# web_browser: 'iceweasel'
-# console_web_browser: 'links2' #'elinks' #'w3m' #'lynx' #'links'
-# odf_viewer: 'lowriter' #'oowriter' #'abiword'
-# xml_viewer: 'xml-viewer'
-# epub_viewer: 'ebook-viewer' #'calibre' #'fbreader' #'okular'
-# info_viewer: 'pinfo -f'
-# man: 'man' #'groff -man -Tascii' # 'nroff -man'
-
-#search:
-# sisu:
-# flag: true
-## action: http://localhost:8081/cgi-bin/sisu_pgsql.cgi
-# action: http://search.sisudoc.org
-# db: sisu
-# title: sample search form
-#promo: sisu_search_libre, sisu_icon, sisu, open_society, fsf, ruby
diff --git a/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_lng.yml b/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_lng.yml
deleted file mode 100644
index ca1cf424..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/_sisu/rc/sisurc_by_lng.yml
+++ /dev/null
@@ -1,135 +0,0 @@
-# Name: SiSU - Simple information Structuring Universe
-# Author: ralph@amissah.com
-# Description: Site wide environment defaults set here
-# system environment info / resource configuration file, for sisu
-# License: GPL v3 or later
-# site environment configuration file
-# this file should be configured and live in
-# /etc/sisu #per environment settings, overridden by:
-# ~/.sisu #per user settings, overridden by:
-# ./_sisu #per local markup directory settings
-#% #image source directory, main path and subdirectories
-#image:
-# path: 'sisu_working'
-# public: '_sisu/image'
-# #all: 'image'
-#% presentation/web directory, main path and subdirectories (most subdirectories are created automatically based on markup directory name)
-#webserv:
-# url_root: 'http://www.your.url' #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
-# images: '_sisu/image'
-# man: 'man'
-# cgi: '/usr/local/lib/sisu-cgi'
-# feed: 'feed'
-# sqlite: 'sisu/sqlite'
-# webrick_url: true
-#show_output_on: 'filesystem' #for -v and -u url information, alternatives: 'filesystem','webserver','remote_webserver','local:8111','localhost','localhost:8080','webrick','path'
-#show_output_on: 'local:8111'
-#webserv_cgi:
-# host: localhost
-# base_path: ~
-# port: '8081'
-# user: ~
-# file_links: webserv
-
-show_output_on: 'filesystem_url'
-#texinfo display output
-#texinfo:
-# stub: 'texinfo'
-
-##% processing directories, main path and subdirectories (appended to $HOME), using defaults set in sysenv
-#processing:
-# path: 'sisu_processing'
-# metaverse: 'metaverse'
-# tune: 'tune'
-# latex: 'tex'
-# texinfo: 'texinfo'
-# concord_max: 400000
-
-#% flag - set (non-default) processing flag shortcuts -1, -2 etc. (here adding colour and verbosity as default)
-flag:
- color: true # making colour default -c is toggle, and will now toggle colour off
-# default: '-NQdhewpotbxXyYv' # includes verbose; -m would in any event be run by default
-# i: '-NQdhewpoty' # -m run by default
-# ii: '-NQdhewpotbxXy' # -m run by default
-# iii: '-NQdhewpotbxXyY' # -m run by default
-# iv: '-NQhewpotbxXYDy --update' # -m run by default
-# v: '-NQhewpotbxXYDyv --update' # includes verbose; -m run by default
-
-#% papersize, (LaTeX/pdf) available values: A4, US_letter, book_b5, book_a5, US_legal
-default:
- papersize: 'a4,letter'
- #language: 'en'
- #texpdf_font: 'Liberation Sans' # 'Liberation Sans' 'Liberation Serif'
- #texpdf_font_mono: 'Liberation Mono' #'Inconsolata'
- #text_wrap: 78
- #emphasis: 'bold' #make *{emphasis}* 'bold', 'italics' or 'underscore', default if not configured is 'bold'
- #digest: 'sha' #sha is sha256, default is md5
- #language: 'English'
- #emphasis: 'italics'
-
-#% settings used by ssh scp
-#remote:
-# -
-# user: '[usrname]'
-# host: '[remote.hostname]'
-# path: '.' #no trailing slash eg 'sisu/www'
-# -
-# user: '[usrname]'
-# host: '[remote.hostname]'
-# path: '.' #no trailing slash eg 'sisu/www'
-
-#% webrick information
-#webrick:
-# port: '8081'
-
-#sql database info, postgresql and sqlite
-db:
- postgresql:
- port: '5432' # '5432'
- #host: # '[if not localhost, provide host tcp/ip address or domain name]''
- #user: # '[(if different from user) provide username]'
- #password: # '[password if required]'
-# sqlite:
-# path: ~ # './sisu_sqlite.db'
-# port: "**"
-
-#% output_dir_structure_by: language (language_and_filetype); filetype; or filename (original v1 & v2)
-output_dir_structure_by: language
-#% language_default: lng_lst: %w[am bg bn br ca cs cy da de el en eo es et eu fi fr ga gl he hi hr hy ia is it ja ko la lo lt lv ml mr nl nn no oc pl pt pt_BR ro ru sa se sk sl sq sr sv ta te th tk tr uk ur us vi zh] ('en' default)
-#language_default: 'en'
-
-permission_set:
- zap: true
- css_modify: true
- remote_base_site: true
-
-program_set:
- rmagick: true
-# wc: true
-# editor: true
-# postgresql: true
-# sqlite: true
-# tidy: true
-# rexml: true
-# pdflatex: true
-
-#program_select:
-# editor: 'vim'
-# pdf_viewer: 'evince'
-# web_browser: 'iceweasel'
-# console_web_browser: 'links2' #'elinks' #'w3m' #'lynx' #'links'
-# odf_viewer: 'lowriter' #'oowriter' #'abiword'
-# xml_viewer: 'xml-viewer'
-# epub_viewer: 'ebook-viewer' #'calibre' #'fbreader' #'okular'
-# info_viewer: 'pinfo -f'
-# man: 'man' #'groff -man -Tascii' # 'nroff -man'
-
-#search:
-# sisu:
-# flag: true
-## action: http://localhost:8081/cgi-bin/sisu_pgsql.cgi
-# action: http://search.sisudoc.org
-# db: sisu
-# title: sample search form
-#promo: sisu_search_libre, sisu_icon, sisu, open_society, fsf, ruby
diff --git a/data/doc/sisu/markup-samples/sisu_manual/_sisu/sisu_document_make b/data/doc/sisu/markup-samples/sisu_manual/_sisu/sisu_document_make
deleted file mode 100644
index 72706d10..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/_sisu/sisu_document_make
+++ /dev/null
@@ -1,20 +0,0 @@
-@make:
- :num_top: 1
- :breaks: new=C; break=1
- :bold: /Debian|Ruby|SiSU/
- :italics: /Linux|GPL|GPLv3|LaTeX|PostgreSQL|SQLite|SQL|Vim|ascii|plaintext|UTF-?8|HTML|XHTML|XML|EPUB|OpenDocument|ODF|ODT|PDF|pgSQL|TeXinfo|YAML|YML|OCN|object citation system|object citation numbering|granular search|Dublin Core/
- :substitute: /${debian_stable}/,'*{Wheezy}*' /${debian_testing}/,'*{Jessie}*'
- :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
- :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
-
-@links:
- { SiSU Homepage }http://www.sisudoc.org/
- { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/
- { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html
- { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html
- { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html
- { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary
- { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/
- { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html
- { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org
- { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
diff --git a/data/doc/sisu/markup-samples/sisu_manual/_sisu/v5/sisurc.yml b/data/doc/sisu/markup-samples/sisu_manual/_sisu/v5/sisurc.yml
deleted file mode 120000
index e492f789..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/_sisu/v5/sisurc.yml
+++ /dev/null
@@ -1 +0,0 @@
-../rc/sisurc_by_lng.yml
\ No newline at end of file
diff --git a/data/doc/sisu/markup-samples/sisu_manual/_sisu/v6/sisurc.yml b/data/doc/sisu/markup-samples/sisu_manual/_sisu/v6/sisurc.yml
deleted file mode 120000
index e492f789..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/_sisu/v6/sisurc.yml
+++ /dev/null
@@ -1 +0,0 @@
-../rc/sisurc_by_lng.yml
\ No newline at end of file
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu.ssm b/data/doc/sisu/markup-samples/sisu_manual/en/sisu.ssm
deleted file mode 100644
index 79703fef..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu.ssm
+++ /dev/null
@@ -1,73 +0,0 @@
-% SiSU master 4.0
-
-@title: SiSU
- :subtitle: Manual
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2008-05-22
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2012
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: SiSU:manual;electronic documents:SiSU:manual
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-@make:
- :manpage: name=sisu - documents: markup, structuring, publishing in multiple standard formats, and search; synopsis=sisu [-short-options|--long-options] [filename/wildcard] . sisu [-abCcDdeFGghIikLMmNnoPpQqRrSsTtUuVvWwXxYyZ_0-9] [filename/wildcard] . sisu --txt --html --epub --odt --pdf --wordmap --sqlite --manpage --texinfo --sisupod --source --qrcode [filename/wildcard] . sisu [-Ddcv] [instruction] [filename/wildcard] . sisu --pg (--createdb|update [filename/wildcard]|--dropall) . sisu [operations] . sisu [-CcFLSVvW] . sisu (--configure|--webrick|--sample-search-form)
-
-:A~ @title @creator
-
-:B~ What is SiSU?
-
-% << sisu_synopsis.ssi
-
-<< sisu_introduction.sst
-
-% :B~? SiSU Commands
-
-<< sisu_commands.sst
-
-<< sisu_help.sst
-
-% :B~? SiSU Markup
-
-<< sisu_markup.sst
-
-<< sisu_filetypes.sst
-
-% :B~? SiSU Configuration
-
-<< sisu_config.ssi
-
-<< sisu_css.ssi
-
-<< sisu_content_directories.ssi
-
-<< sisu_homepages.ssi
-
-% :B~? SiSU Output and Markup Examples
-
-<< sisu_examples.ssi
-
-<< sisu_search_intro.ssi
-
-<< sisu_sql.ssi
-
-<< sisu_postgresql.sst
-
-<< sisu_sqlite.sst
-
-<< sisu_search_cgi.ssi
-
-<< sisu_webrick.sst
-
-<< sisu_short_feature_summary.ssi
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_commands.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_commands.sst
deleted file mode 100644
index 2ca43a43..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_commands.sst
+++ /dev/null
@@ -1,497 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: Commands
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :published: 2007-09-16
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2012
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: electronic documents:SiSU:document:commands;SiSU:manual:commands;electronic documents:SiSU:manual:commands;SiSU:document:commands;SiSU:document:commands
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? SiSU Commands
-
-1~commands Commands Summary
-
-2~ Description
-
-SiSU is a document publishing system, that from a simple single marked-up document, produces multiple output formats including: plaintext, HTML, XHTML, XML, EPUB, ODT (OpenDocument (ODF) text), LaTeX, PDF, info, and SQL (PostgreSQL and SQLite), which share text object numbers ("object citation numbering") and the same document structure information. For more see: http://sisudoc.org or http://www.jus.uio.no/sisu
-
-% 2~ Summary of man page
-
-% This man page covers a number of subjects in brief, including: document processing command flags; document markup (basic markup and headers); configuration files; directory structure; skins; document naming; interactive help and other information.
-
-2~ Document Processing Command Flags
-
-!_ -a [filename/wildcard] \\
-produces plaintext with Unix linefeeds and without markup, (object numbers are omitted), has footnotes at end of each paragraph that contains them [ -A for equivalent dos (linefeed) output file] [see -e for endnotes]. (Options include: --endnotes for endnotes --footnotes for footnotes at the end of each paragraph --unix for unix linefeed (default) --msdos for msdos linefeed)
-
-!_ --ao [filename/wildcard/url] \\
-assumed for most other flags, creates new intermediate files for processing (abstract objects, document abstraction) that is used in all subsequent processing of other output. This step is assumed for most processing flags. To skip it see -n. Alias -m. (sisu v5)
-
-!_ -b [filename/wildcard] \\
-see --xhtml
-
-!_ --by-* \\
-see --output-by-*
-
-!_ -C \\
-configure/initialise shared output directory files initialize shared output directory (config files such as css and dtd files are not updated if they already exist unless modifier is used). -C --init-site configure/initialise site more extensive than -C on its own, shared output directory files/force update, existing shared output config files such as css and dtd files are updated if this modifier is used.
-
-!_ -CC \\
-see --configure
-
-!_ -c [filename/wildcard] \\
-see --color-toggle
-
-!_ --color \\
-see --color-on
-
-!_ --color-off \\
-turn off color in output to terminal
-
-!_ --color-on \\
-turn on color in output to terminal
-
-!_ --color-toggle [filename/wildcard] \\
-screen toggle ansi screen colour on or off depending on default set (unless -c flag is used: if sisurc colour default is set to 'true', output to screen will be with colour, if sisurc colour default is set to 'false' or is undefined screen output will be without colour). Alias -c
-
-!_ --configure \\
-configure/initialise shared output directory files initialize shared output directory (config files such as css and dtd files are not updated if they already exist unless modifier is used). The equivalent of: -C --init-site configure/initialise site, more extensive than -C on its own, shared output directory files/force update, existing shared output config files such as css and dtd files are updated if -CC is used.
-
-!_ --concordance [filename/wildcard] \\
-produces concordance (wordmap) a rudimentary index of all the words in a document. (Concordance files are not generated for documents of over 260,000 words unless this limit is increased in the file sisurc.yml). Alias -w
-
-!_ -D [instruction] [filename] \\
-see --pg
-
-!_ -d [--db-[database type (sqlite|pg)]] --[instruction] [filename] \\
-see --sqlite
-
-!_ --dal [filename/wildcard/url] \\
-assumed for most other flags, creates new intermediate files for processing (abstract objects, document abstraction) that is used in all subsequent processing of other output. This step is assumed for most processing flags. To skip it see -n. Renamed --ao (abstract objects) in sisu v5. Alias -m
-
-!_ --delete [filename/wildcard] \\
-see --zap
-
-!_ --docbook [filename/wildcard/url] \\
-docbook smart text (sisu v5)
-
-!_ --dump[=directory_path] [filename/wildcard] \\
-places output in directory specified, if none is specified in the current directory (pwd). Unlike using default settings HTML files have embedded css. Compare --redirect
-
-!_ -e [filename/wildcard] \\
-see --epub
-
-!_ --epub [filename/wildcard] \\
-produces an epub document, [sisu version >=2 ] (filename.epub). Alias -e
-
-!_ --exc-* \\
-exclude output feature, overrides configuration settings
- --exc-ocn, (exclude object citation numbering, (switches off object citation numbering), affects html (seg, scroll), epub, xhtml, xml, pdf);
- --exc-toc, (exclude table of contents, affects html (scroll), epub, pdf);
- --exc-links-to-manifest, --exc-manifest-links, (exclude links to manifest, affects html (seg, scroll));
- --exc-search-form, (exclude search form, affects html (seg, scroll), manifest);
- --exc-minitoc, (exclude mini table of contents, affects html (seg), concordance, manifest);
- --exc-manifest-minitoc, (exclude mini table of contents, affects manifest);
- --exc-html-minitoc, (exclude mini table of contents, affects html (seg), concordance);
- --exc-html-navigation, (exclude navigation, affects html (seg));
- --exc-html-navigation-bar, (exclude navigation bar, affects html (seg));
- --exc-html-search-form, (exclude search form, affects html (seg, scroll));
- --exc-html-right-pane, (exclude right pane/column, affects html (seg, scroll));
- --exc-html-top-band, (exclude top band, affects html (seg, scroll), concordance (minitoc forced on to provide seg navigation));
- --exc-segsubtoc (exclude sub table of contents, affects html (seg), epub);
-see also --inc-*
-
-!_ -F [--webserv=webrick] \\
-see --sample-search-form
-
-!_ -f [optional string part of filename] \\
-see --find
-
-!_ --fictionbook [filename/wildcard/url] \\
-fictionbook smart text (sisu v5)
-
-!_ --find [optional string part of filename] \\
-without match string, glob all .sst .ssm files in directory (including language subdirectories). With match string, find files that match given string in directory (including language subdirectories). Alias -f, --glob, -G
-
-!_ -G [optional string part of filename] \\
-see --find
-
-!_ -g [filename/wildcard] \\
-see --git
-
-!_ --git [filename/wildcard] \\
-produces or updates markup source file structure in a git repo (experimental and subject to change). Alias -g
-
-!_ --glob [optional string part of filename] \\
-see --find
-
-!_ -h [filename/wildcard] \\
-see --html
-
-!_ --harvest *.ss[tm] \\
-makes two lists of sisu output based on the sisu markup documents in a directory: list of author and authors works (year and titles), and; list by topic with titles and author. Makes use of header metadata fields (author, title, date, topic_register). Can be used with maintenance (-M) and remote placement (-R) flags.
-
-!_ --help [topic] \\
-provides help on the selected topic, where topics (keywords) include: list, (com)mands, short(cuts), (mod)ifiers, (env)ironment, markup, syntax, headers, headings, endnotes, tables, example, customise, skin, (dir)ectories, path, (lang)uage, db, install, setup, (conf)igure, convert, termsheet, search, sql, features, license.
-
-!_ --html [filename/wildcard] \\
-produces html output, in two forms (i) segmented text with table of contents (toc.html and index.html) and (ii) the document in a single file (scroll.html). Alias -h
-
-!_ --html-scroll [filename/wildcard] \\
-produces html output, the document in a single file (scroll.html) only. Compare --html-seg and --html
-
-!_ --html-seg [filename/wildcard] \\
-produces html output, segmented text with table of contents (toc.html and index.html). Compare --html-scroll and --html
-
-!_ -I [filename/wildcard] \\
-see --texinfo
-
-!_ -i [filename/wildcard] \\
-see --manpage
-
-!_ --i18n-* \\
-these flags affect output by filetype and filename):
---i18n-mono (--monolingual) output filenames without language code for default language ('en' or as set);
---i18n-multi (--multilingual) language code provided as part of the output filename, this is the default.
-Where output is in one language only the language code may not be desired.
-see also --output-by-*
-
-!_ --inc-* \\
-include output feature, overrides configuration settings, (usually the default if none set), has precedence over --exc-* (exclude output feature). Some detail provided under --exc-*,
-see --exc-*
-
-!_ -j [filename/wildcard] \\
-copies images associated with a file for use by html, xhtml & xml outputs (automatically invoked by --dump & redirect).
-
-!_ -k \\
-see --color-off
-
-!_ --keep-processing-files [filename/wildcard/url] \\
-see --maintenance
-
-!_ -M [filename/wildcard/url] \\
-see --maintenance
-
-!_ -m [filename/wildcard/url] \\
-see --dal (document abstraction level/layer)
-
-!_ --machine [filename/wildcard/url] \\
-see --dal (document abstraction level/layer)
-
-!_ --maintenance [filename/wildcard/url] \\
-maintenance mode, interim processing files are preserved and their locations indicated. (also see -V). Aliases -M and --keep-processing-files.
-
-!_ --markdown [filename/wildcard/url] \\
-markdown smart text (sisu v5)
-
-!_ --manpage [filename/wildcard] \\
-produces man page of file, not suitable for all outputs. Alias -i
-
-!_ --monolingual \\
-see --i18n-*
-
-!_ --multilingual \\
-see --i18n-*
-
-!_ -N [filename/wildcard/url] \\
-document digest or document content certificate ( DCC ) as md5 digest tree of the document: the digest for the document, and digests for each object contained within the document (together with information on software versions that produced it) (digest.txt). -NV for verbose digest output to screen.
-
-!_ -n [filename/wildcard/url] \\
-skip the creation of intermediate processing files (document abstraction) if they already exist, this skips the equivalent of -m which is otherwise assumed by most processing flags.
-
-!_ --no-* \\
-see --exc-*
-
-!_ -o [filename/wildcard/url] \\
-see --odt
-
-!_ --odf [filename/wildcard/url] \\
-see --odt
-
-!_ --odt [filename/wildcard/url] \\
-output basic document in opendocument file format (opendocument.odt). Alias -o
-
-!_ --output-by-* \\
-select output directory structure from 3 alternatives:
---output-by-language, (language directory (based on language code) with filetype (html, epub, pdf etc.) subdirectories);
---output-by-filetype, (filetype directories with language code as part of filename);
---output-by-filename, (filename directories with language code as part of filename).
-This is configurable. Alias --by-*
-
-!_ -P [language_directory/filename language_directory] \\
-see --po4a
-
-!_ -p [filename/wildcard] \\
-see --pdf
-
-!_ --papersize-(a4|a5|b5|letter|legal) \\
-in conjunction with --pdf set pdf papersize, overriding any configuration settings, to set more than one papersize repeat the option --pdf --papersize-a4 --papersize-letter. See also --papersize=*
-
-!_ --papersize=a4,a5,b5,letter,legal
-in conjunction with --pdf set pdf papersize, overriding any configuration settings, to set more than one papersize list after the equal sign with a comma separator --papersize=a4,letter. See also --papersize-*
-
-!_ --pdf [filename/wildcard] \\
-produces LaTeX pdf (portrait.pdf & landscape.pdf). Orientation and papersize may be set on the command-line. Default paper size is set in config file, or document header, or provided with additional command line parameter, e.g. --papersize-a4 preset sizes include: 'A4', U.S. 'letter' and 'legal' and book sizes 'A5' and 'B5' (system defaults to A4), and; --landscape or --portrait, so: e.g. "sisu --pdf-a4 --pdf-letter --landscape --verbose [filename/wildcard]" or "sisu --pdf --landscape --a4 --letter --verbose [filename/wildcard]". --pdf defaults to both landscape & portrait output, and a4 if no other papersizes are configured. Related options --pdf-landscape --pdf-portrait --pdf-papersize-* --pdf-papersize=[list]. Alias -p
-
-!_ --pdf-l [filename/wildcard] \\
-See --pdf-landscape
-
-!_ --pdf-landscape [filename/wildcard] \\
-sets orientation, produces LaTeX pdf landscape.pdf. Default paper size is set in config file, or document header, or provided with additional command line parameter, e.g. --papersize-a4 preset sizes include: 'A4', U.S. 'letter' and 'legal' and book sizes 'A5' and 'B5' (system defaults to A4). Related options --pdf --pdf-portrait. See also --papersize-* or --papersize=[list]. Alias --pdf-l or in conjunction with --pdf --landscape
-
-!_ --pdf-p [filename/wildcard] \\
-See --pdf-portrait
-
-!_ --pdf-portrait [filename/wildcard] \\
-sets orientation, produces LaTeX pdf portrait.pdf.pdf. Default paper size is set in config file, or document header, or provided with additional command line parameter, e.g. --papersize-a4 preset sizes include: 'A4', U.S. 'letter' and 'legal' and book sizes 'A5' and 'B5' (system defaults to A4). Related options --pdf --pdf-landscape. See also --papersize-* or --papersize=[list]. Alias --pdf-p or in conjunction with --pdf --portrait
-
-!_ --pg [instruction] [filename] \\
-database PostgreSQL ( --pgsql may be used instead) possible instructions, include: --createdb; --create; --dropall; --import [filename]; --update [filename]; --remove [filename]; see database section below. Alias -D
-
-!_ --po [language_directory/filename language_directory] \\
-see --po4a
-
-!_ --po4a [language_directory/filename language_directory] \\
-produces .pot and po files for the file in the languages specified by the language directory. SiSU markup is placed in subdirectories named with the language code, e.g. en/ fr/ es/. The sisu config file must set the output directory structure to multilingual. v3, experimental
-
-!_ -Q [filename/wildcard] \\
-see --qrcode
-
-!_ -q [filename/wildcard] \\
-see --quiet
-
-!_ --qrcode [filename/wildcard] \\
-generate QR code image of metadata (used in manifest). v3 only.
-
-!_ --quiet [filename/wildcard] \\
-quiet less output to screen.
-
-!_ -R [filename/wildcard] \\
-see --rsync
-
-!_ -r [filename/wildcard] \\
-see --scp
-
-!_ --redirect[=directory_path] [filename/wildcard] \\
-places output in subdirectory under specified directory, subdirectory uses the filename (without the suffix). If no output directory is specified places the subdirectory under the current directory (pwd). Unlike using default settings HTML files have embedded css. Compare --dump
-
-!_ --rst [filename/wildcard/url] \\
-ReST (rST restructured text) smart text (sisu v5)
-
-!_ --rsync [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 --scp. Alias -R
-
-!_ -S \\
-see --sisupod
-
-!_ -S [filename/wildcard] \\
-see --sisupod
-
-!_ -s [filename/wildcard] \\
-see --source
-
-!_ --sample-search-form [--db=(pgsql|sqlite)] [--webserv=webrick] \\
-generate examples of (naive) cgi search form for SQLite or PgSQL depends on your already having used sisu to populate an SQLite or PgSQL database, (the SQLite version scans the output directories for existing sisu_sqlite databases, so it is first necessary to create them, before generating the search form) see --sqlite & --pg and the database section below. Optional additional parameters include: url location of webserver search form and db: --webserv-search='[url]'; location of webserver output: --webserv-output='[url]'; cgi search form link name: --cgi-search-form-name='[name.cgi]'; for pgsql, database user: --db-user='[username]'. If the optional parameter --webserv=webrick is passed, the cgi examples created will be set up to use the default port set for use by the webrick server, (otherwise the port is left blank and the system setting used, usually 80). The samples are dumped in the present work directory which must be writable, (with screen instructions given that they be copied to the cgi-bin directory). Alias -F
-
-!_ --scp [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 --rsync. Alias -r
-
-!_ --sqlite --[instruction] [filename] \\
-database type set to SQLite, this produces one of two possible databases, without additional database related instructions it produces a discreet SQLite file for the document processed; with additional instructions it produces a common SQLite database of all processed documents that (come from the same document preparation directory and as a result) share the same output directory base path (possible instructions include: --createdb; --create; --dropall; --import [filename]; --update [filename]; --remove [filename]); see database section below. Alias -d
-
-!_ --sisupod \\
-produces a sisupod a zipped sisu directory of markup files including sisu markup source files and the directories local configuration file, images and skins. Note: this only includes the configuration files or skins contained in ./_sisu not those in ~/.sisu -S [filename/wildcard] option. Note: (this option is tested only with zsh). Alias -S
-
-!_ --sisupod [filename/wildcard] \\
-produces a zipped file of the prepared document specified along with associated images, by default named sisupod.zip they may alternatively be named with the filename extension .ssp This provides a quick way of gathering the relevant parts of a sisu document which can then for example be emailed. A sisupod includes sisu markup source file, (along with associated documents if a master file, or available in multilingual versions), together with related images and skin. SiSU commands can be run directly against a sisupod contained in a local directory, or provided as a url on a remote site. As there is a security issue with skins provided by other users, they are not applied unless the flag --trust or --trusted is added to the command instruction, it is recommended that file that are not your own are treated as untrusted. The directory structure of the unzipped file is understood by sisu, and sisu commands can be run within it. Note: if you wish to send multiple files, it quickly becomes more space efficient to zip the sisu markup directory, rather than the individual files for sending). See the -S option without [filename/wildcard]. Alias -S
-
-!_ --source [filename/wildcard] \\
-copies sisu markup file to output directory. Alias -s
-
-!_ -T [filename/wildcard (*.termsheet.rb)] \\
-standard form document builder, preprocessing feature
-
-!_ -t [filename/wildcard] \\
-see --txt
-
-!_ --texinfo [filename/wildcard] \\
-produces texinfo and info file, (view with pinfo). Alias -I
-
-!_ --textile [filename/wildcard/url] \\
-textile smart text (sisu v5)
-
-!_ --txt [filename/wildcard] \\
-produces plaintext with Unix linefeeds and without markup, (object numbers are omitted), has footnotes at end of each paragraph that contains them [ -A for equivalent dos (linefeed) output file] [see -e for endnotes]. (Options include: --endnotes for endnotes --footnotes for footnotes at the end of each paragraph --unix for unix linefeed (default) --msdos for msdos linefeed). Alias -t
-
-!_ --txt-asciitext [filename/wildcard] \\
-see --asciitext
-
-!_ --txt-markdown [filename/wildcard] \\
-see --markdown
-
-!_ --txt-rst [filename/wildcard] \\
-see --rst
-
-!_ --txt-textile [filename/wildcard] \\
-see --textile
-
-!_ -U [filename/wildcard] \\
-see --urls
-
-!_ -u [filename/wildcard] \\
-provides url mapping of output files for the flags requested for processing, also see -U
-
-!_ --urls [filename/wildcard] \\
-prints url output list/map for the available processing flags options and resulting files that could be requested, (can be used to get a list of processing options in relation to a file, together with information on the output that would be produced), -u provides url output mapping for those flags requested for processing. The default assumes sisu_webrick is running and provides webrick url mappings where appropriate, but these can be switched to file system paths in sisurc.yml. Alias -U
-
-!_ -V \\
-on its own, provides SiSU version and environment information (sisu --help env)
-
-!_ -V [filename/wildcard] \\
-even more verbose than the -v flag.
-
-!_ -v \\
-on its own, provides SiSU version information
-
-!_ -v [filename/wildcard] \\
-see --verbose
-
-!_ --v3 [filename/wildcard] \\
-invokes the sisu v3 document parser/generator. You may run sisu3 instead.
-
-!_ --v4 [filename/wildcard] \\
-invokes the sisu v4 document parser/generator. This is the default and is normally omitted.
-
-!_ --verbose [filename/wildcard] \\
-provides verbose output of what is being generated, where output is placed (and error messages if any), as with -u flag provides a url mapping of files created for each of the processing flag requests. Alias -v
-
-!_ -W \\
-see --webrick
-
-!_ -w [filename/wildcard] \\
-see --concordance
-
-!_ --webrick \\
-starts ruby's webrick webserver points at sisu output directories, the default port is set to 8081 and can be changed in the resource configuration files. [tip: the webrick server requires link suffixes, so html output should be created using the -h option rather than -H ; also, note -F webrick ]. Alias -W
-
-!_ --wordmap [filename/wildcard] \\
-see --concordance
-
-!_ --xhtml [filename/wildcard] \\
-produces xhtml/XML output for browser viewing (sax parsing). Alias -b
-
-!_ --xml-dom [filename/wildcard] \\
-produces XML output with deep document structure, in the nature of dom. Alias -X
-
-!_ --xml-sax [filename/wildcard] \\
-produces XML output shallow structure (sax parsing). Alias -x
-
-!_ -X [filename/wildcard] \\
-see --xml-dom
-
-!_ -x [filename/wildcard] \\
-see --xml-sax
-
-!_ -Y [filename/wildcard] \\
-produces a short sitemap entry for the document, based on html output and the sisu_manifest. --sitemaps generates/updates the sitemap index of existing sitemaps. (Experimental, [g,y,m announcement this week])
-
-!_ -y [filename/wildcard] \\
-produces an html summary of output generated (hyperlinked to content) and document specific metadata (sisu_manifest.html). This step is assumed for most processing flags.
-
-!_ -Z [filename/wildcard] \\
-see --zap
-
-!_ --zap [filename/wildcard] \\
-Zap, if used with other processing flags deletes output files of the type about to be processed, prior to processing. If -Z is used as the lone processing related flag (or in conjunction with a combination of -[mMvVq]), will remove the related document output directory. Alias -Z
-
-1~command_modifiers command line modifiers
-
-!_ --no-ocn \\
-[with --html --pdf or --epub] switches off object citation numbering. Produce output without identifying numbers in margins of html or LaTeX/pdf output.
-
-!_ --no-annotate \\
-strips output text of editor endnotes~[* square brackets ]~ denoted by asterisk or dagger/plus sign
-
-!_ --no-asterisk \\
-strips output text of editor endnotes~[* square brackets ]~ denoted by asterisk sign
-
-!_ --no-dagger \\
-strips output text of editor endnotes~[+ square brackets ]~ denoted by dagger/plus sign
-
-1~commands_database database commands
-
-!_ dbi - database interface
-
-!_ -D or --pgsql
-set for PostgreSQL
-!_ -d or --sqlite
-default set for SQLite -d is modifiable with --db=[database type (PgSQL or SQLite)]
-
-!_ --pg -v --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) [ -dv --createall SQLite equivalent] it may be necessary to run sisu -Dv --createdb initially NOTE: at the present time for PostgreSQL it may be necessary to manually create the database. The command would be 'createdb [database name]' where database name would be SiSU_[present working directory name (without path)]. Please use only alphanumerics and underscores.
-
-!_ --pg -v --import \\
-[filename/wildcard] imports data specified to PostgreSQL db (rb.dbi) [ -dv --import SQLite equivalent]
-
-!_ --pg -v --update \\
-[filename/wildcard] updates/imports specified data to PostgreSQL db (rb.dbi) [ -dv --update SQLite equivalent]
-
-!_ --pg --remove \\
-[filename/wildcard] removes specified data to PostgreSQL db (rb.dbi) [ -d --remove SQLite equivalent]
-
-!_ --pg --dropall \\
-kills data" and drops (PostgreSQL or SQLite) db, tables & indexes [ -d --dropall SQLite equivalent]
-
-The -v is for verbose output.
-
-1~command_shorcuts Shortcuts, Shorthand for multiple flags
-
-!_ --update [filename/wildcard] \\
-Checks existing file output and runs the flags required to update this output. This means that if only html and pdf output was requested on previous runs, only the -hp files will be applied, and only these will be generated this time, together with the summary. This can be very convenient, if you offer different outputs of different files, and just want to do the same again.
-
-!_ -0 to -5 [filename or wildcard] \\
-Default shorthand mappings (for v3, note that the defaults can be changed/configured in the sisurc.yml file):
-
-!_ -0 \\
--NQhewpotbxXyYv [this is the default action run when no options are give, i.e. on 'sisu [filename]']
-
-!_ -1 \\
--Qhewpoty
-
-!_ -2 \\
--NQhewpotbxXy
-
-!_ -3 \\
--NQhewpotbxXyY
-
-!_ -4 \\
--NQhewpotbxXDyY --update
-
-!_ -5 \\
--NQhewpotbxXDyYv --update
-
-add -v for verbose mode and -c to toggle color state, e.g. sisu -2vc [filename or wildcard]
-
-consider -u for appended url info or -v for verbose output
-
-2~ Command Line with Flags - Batch Processing
-
-In the data directory run sisu -mh filename or wildcard eg. "sisu -h cisg.sst" or "sisu -h *.{sst,ssm}" to produce html version of all documents.
-
-Running sisu (alone without any flags, filenames or wildcards) brings up the interactive help, as does any sisu command that is not recognised. Enter to escape.
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_config.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_config.ssi
deleted file mode 100644
index 3c29f995..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_config.ssi
+++ /dev/null
@@ -1,75 +0,0 @@
-% SiSU insert 2.0
-
-@title: SiSU
- :subtitle: Configuration
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2011-12-12
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? Configuration
-
-:B~? Configure Environment
-
-1~config Configuration
-
-2~ Configuration files
-
-3~ config.yml
-
-SiSU configration parameters are adjusted in the configuration file, which can be used to override the defaults set. This includes such things as which directory interim processing should be done in and where the generated output should be placed.
-
-The SiSU configuration file is a yaml file, which means indentation is significant.
-
-SiSU resource configuration is determined by looking at the following files if they exist:
-
-_1 ./_sisu/v4/sisurc.yml
-
-_1 ./_sisu/sisurc.yml
-
-_1 ~/.sisu/v4/sisurc.yml
-
-_1 ~/.sisu/sisurc.yml
-
-_1 /etc/sisu/v4/sisurc.yml
-
-_1 /etc/sisu/sisurc.yml
-
-The search is in the order listed, and the first one found is used.
-
-In the absence of instructions in any of these it falls back to the internal program defaults.
-
-Configuration determines the output and processing directories and the database access details.
-
-If SiSU is installed a sample sisurc.yml may be found in /etc/sisu/sisurc.yml
-
-3~ sisu_document_make
-
-Most sisu document headers relate to metadata, the exception is the @make: header which provides processing related information. The default contents of the @make header may be set by placing them in a file sisu_document_make.
-
-The search order is as for resource configuration:
-
-_1 ./_sisu/v4/sisu_document_make
-
-_1 ./_sisu/sisu_document_make
-
-_1 ~/.sisu/v4/sisu_document_make
-
-_1 ~/.sisu/sisu_document_make
-
-_1 /etc/sisu/v4/sisu_document_make
-
-_1 /etc/sisu/sisu_document_make
-
-A sample sisu_document_make can be found in the _sisu/ directory under along with the provided sisu markup samples.
-
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_content_directories.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_content_directories.ssi
deleted file mode 100644
index 182b176d..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_content_directories.ssi
+++ /dev/null
@@ -1,264 +0,0 @@
-% SiSU insert 2.0
-
-@title: SiSU
- :subtitle: Content Directories, Organising Content
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2007-08-28
- :published: 2007-09-16
- :modified: 2011-02-07
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? Organisation of Content
-
-:B~? Content Directories
-
-1~organising_content Organising Content - Directory Structure and Mapping
-
-SiSU v3 has new options for the source directory tree, and output directory structures of which there are 3 alternatives.
-
-2~ Document Source Directory
-
-The document source directory is the directory in which sisu processing commands are given. It contains the sisu source files (.sst .ssm .ssi), or (for sisu v3 may contain) subdirectories with language codes which contain the sisu source files, so all English files would go in subdirectory en/, French in fr/, Spanish in es/ and so on. ISO 639-1 codes are used (as varied by po4a). A list of available languages (and possible sub-directory names) can be obtained with the command "sisu --help lang" The list of languages is limited to langagues supported by XeTeX polyglosia.
-
-3~ General Directories
-
-code{
-
-./subject_name/
-
-% files stored at this level e.g. sisu_manual.sst or
-% for sisu v3 may be under language sub-directories
-% e.g.
-
-./subject_name/en
-
-./subject_name/fr
-
-./subject_name/es
-
-./subject_name/_sisu
-
-./subject_name/_sisu/css
-
-./subject_name/_sisu/image
-
-}code
-
-2~ Document Output Directory Structures
-
-3~ Output Directory Root
-
-The output directory root can be set in the sisurc.yml file. Under the root, subdirectories are made for each directory in which a document set resides. If you have a directory named poems or conventions, that directory will be created under the output directory root and the output for all documents contained in the directory of a particular name will be generated to subdirectories beneath that directory (poem or conventions). A document will be placed in a subdirectory of the same name as the document with the filetype identifier stripped (.sst .ssm)
-
-The last part of a directory path, representing the sub-directory in which a document set resides, is the directory name that will be used for the output directory. This has implications for the organisation of document collections as it could make sense to place documents of a particular subject, or type within a directory identifying them. This grouping as suggested could be by subject (sales_law, english_literature); or just as conveniently by some other classification (X University). The mapping means it is also possible to place in the same output directory documents that are for organisational purposes kept separately, for example documents on a given subject of two different institutions may be kept in two different directories of the same name, under a directory named after each institution, and these would be output to the same output directory. Skins could be associated with each institution on a directory basis and resulting documents will take on the appropriate different appearance.
-
-3~ Alternative Output Structures
-
-There are 3 possibile output structures described as being, by language, by filetype or by filename, the selection is made in sisurc.yml
-
-code{
-
-#% output_dir_structure_by: language; filetype; or filename
-output_dir_structure_by: language #(language & filetype, preferred?)
-#output_dir_structure_by: filetype
-#output_dir_structure_by: filename #(default, closest to original v1 & v2)
-
-}code
-
-3~ By Language
-
-The by language directory structure places output files
-
-The by language directory structure separates output files by language code (all files of a given language), and within the language directory by filetype.
-
-Its selection is configured in sisurc.yml
-
-output_dir_structure_by: language
-
-% works for html epub odf, pdf, sortof for info NOT for man pages
-
-code{
-
- |-- en
- |-- epub
- |-- hashes
- |-- html
- | |-- viral_spiral.david_bollier
- | |-- manifest
- | |-- qrcode
- | |-- odt
- | |-- pdf
- | |-- sitemaps
- | |-- txt
- | |-- xhtml
- | `-- xml
- |-- po4a
- | `-- live-manual
- | |-- po
- | |-- fr
- | `-- pot
- `-- _sisu
- |-- css
- |-- image
- |-- image_sys -> ../../_sisu/image_sys
- `-- xml
- |-- rnc
- |-- rng
- `-- xsd
-
-}code
-
-#by: language
-subject_dir/en/manifest/filename.html
-
-3~ By Filetype
-
-The by filetype directory structure separates output files by filetype, all html files in one directory pdfs in another and so on. Filenames are given a language extension.
-
-Its selection is configured in sisurc.yml
-
-output_dir_structure_by: filetype
-
-% works for html epub odf, pdf, sortof for info NOT for man pages
-
-code{
-
- |-- epub
- |-- hashes
- |-- html
- |-- viral_spiral.david_bollier
- |-- manifest
- |-- qrcode
- |-- odt
- |-- pdf
- |-- po4a
- |-- live-manual
- | |-- po
- | |-- fr
- | `-- pot
- |-- _sisu
- | |-- css
- | |-- image
- | |-- image_sys -> ../../_sisu/image_sys
- | `-- xml
- | |-- rnc
- | |-- rng
- | `-- xsd
- |-- sitemaps
- |-- txt
- |-- xhtml
- `-- xml
-
-}code
-
-#by: filetype
-subject_dir/html/filename/manifest.en.html
-
-3~ By Filename
-
-The by filename directory structure places most output of a particular file (the different filetypes) in a common directory.
-
-Its selection is configured in sisurc.yml
-
-output_dir_structure_by: filename
-
-% works for html epub odf, pdf, sortof for info NOT for man pages
-
-code{
-
- |-- epub
- |-- po4a
- |-- live-manual
- | |-- po
- | |-- fr
- | `-- pot
- |-- _sisu
- | |-- css
- | |-- image
- | |-- image_sys -> ../../_sisu/image_sys
- | `-- xml
- | |-- rnc
- | |-- rng
- | `-- xsd
- |-- sitemaps
- |-- src
- |-- pod
- `-- viral_spiral.david_bollier
-
-}code
-
-#by: filename
-subject_dir/filename/manifest.en.html
-
-3~ Remote Directories
-
-code{
-
-./subject_name/
-
-% containing sub_directories named after the generated files from which they are made
-
-./subject_name/src
-
-% contains shared source files text and binary e.g. sisu_manual.sst and sisu_manual.sst.zip
-
-./subject_name/_sisu
-
-% configuration file e.g. sisurc.yml
-
-./subject_name/_sisu/skin
-
-% skins in various skin directories doc, dir, site, yml
-
-./subject_name/_sisu/css
-
-./subject_name/_sisu/image
-
-% images for documents contained in this directory
-
-./subject_name/_sisu/mm
-
-}code
-
-3~ Sisupod
-
-code{
-
-./sisupod/
-
-% files stored at this level e.g. sisu_manual.sst
-
-./sisupod/_sisu
-
-% configuration file e.g. sisurc.yml
-
-./sisupod/_sisu/skin
-
-% skins in various skin directories doc, dir, site, yml
-
-./sisupod/_sisu/css
-
-./sisupod/_sisu/image
-
-% images for documents contained in this directory
-
-./sisupod/_sisu/mm
-
-}code
-
-2~ Organising Content
-
-
-
-% .SH "SKINS \- document, directory and site skins"
-
-
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_css.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_css.ssi
deleted file mode 100644
index 7ffc654b..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_css.ssi
+++ /dev/null
@@ -1,42 +0,0 @@
-% SiSU insert 2.0
-
-@title: SiSU
- :subtitle: CSS - Cascading Style Sheets
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2007-08-28
- :issued: 2007-08-28
- :available: 2007-08-28
- :published: 2007-09-16
- :modified: 2011-02-07
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? CSS
-
-1~css CSS - Cascading Style Sheets (for html, XHTML and XML)
-
-CSS files to modify the appearance of SiSU html, XHTML or XML may be placed in the configuration directory: ./_sisu/css ; ~/.sisu/css or; /etc/sisu/css and these will be copied to the output directories with the command sisu -CC.
-
-The basic CSS file for html output is html.css, placing a file of that name in directory _sisu/css or equivalent will result in the default file of that name being overwritten.
-
-HTML:
-html.css
-
-XML DOM:
-dom.css
-
-XML SAX:
-sax.css
-
-XHTML:
-xhtml.css
-
-The default homepage may use homepage.css or html.css
-
-Under consideration is to permit the placement of a CSS file with a different name in directory _sisu/css directory or equivalent.~{ 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. }~
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_description.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_description.sst
deleted file mode 100644
index 9f8fdcd8..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_description.sst
+++ /dev/null
@@ -1,527 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU - SiSU information Structuring Universe / Structured information, Serialized Units
- :subtitle: Description
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-11-12
- :issued: 2002-11-12
- :available: 2002-11-12
- :published: 2007-08-30
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: electronic documents;SiSU:document:description;sisu:document:description
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? SiSU an attempt to describe
-
-1~ Description
-
-2~ Outline
-
-SiSU is a flexible document preparation, generation publishing and search system.~{ This information was first placed on the web 12 November 2002; with predating material taken from http://www.jus.uio.no/lm/lm.information/toc.html part of a site started and developed since 1993. See document metadata section http://www.jus.uio.no/sisu/SiSU/metadata.html or manifest page http://www.jus.uio.no/sisu/SiSU/sisu_manifest.html for information on this version. Dates related to the development of SiSU may be tracked in the http://www.jus.uio.no/sisu/SiSU/changelog.html or the Git repository http://git.sisudoc.org/?p=code/sisu.git;a=summary some of the more significant events may be contained within the Chronology section of this document http://www.jus.uio.no/sisu/sisu_chronology }~
-
-SiSU ("SiSU information Structuring Universe" or "Structured information, Serialized Units"),~{ also chosen for the meaning of the Finnish term "sisu". }~ is a Unix command line oriented framework for document structuring, publishing and search. Featuring minimalistic markup, multiple standard outputs, a common citation system, and granular search.
-
-Using markup applied to a document, SiSU can produce plain text, HTML, XHTML, XML, OpenDocument, EPUB, 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.
-
-SiSU is the data/information structuring and transforming tool, that has resulted from work on one of the oldest law web projects. It makes possible the one time, simple human readable markup of documents, that SiSU can then publish in various forms, suitable for paper~{ PDF via LaTeX }~, web~{ currently HTML (two forms of HTML presentation one based on css the other on tables), and /PHP/; potentially structured XML }~ and relational database~{ any SQL - currently PostgreSQL and SQLite (for portability, testing and development) }~ presentations, retaining common data-structure and meta-information across the output/presentation formats. Several requirements of legal and scholarly publication on the web have been addressed, including the age old need to be able to reliably cite/pinpoint text within a document, to easily make footnotes/endnotes, to allow for semantic document meta-tagging, and to keep required markup to a minimum. These and other features of interest are listed and described below. A few points are worth making early (and will be repeated a number of times):
-
-_1 (i) The SiSU document generator was the first to place material on the web with a system that makes possible citation across different document types, with paragraph, or rather object citation numbering~{ previously called "text object numbering" }~ a text positioning system, available for the pinpointing of text, 1997, a simple idea from which much benefit, and SiSU remains today, to the best of my knowledge, the only multiple format e-book/ electronic-document system on the web that gives you this possibility (including for relational databases).
-
-_1 (ii) Markup is done once for the multiple formats produced.
-
-_1 (iii) Markup is simple, and human readable (with a little practice), in almost all cases there is less and simpler markup required than basic HTML. In any event the markup required is very much simpler than the HTML, EPUB, LaTeX, [lout], structured XML, ODT (Open Document Format text), PostgreSQL or SQLite feed etc. that you can have SiSU generate for you.
-
-_1 (iv) SiSU is a batch processor, dealing with as many files as you need to generate at a time.
-
-_1 (v) Scalability is dependent on your file system, the database (currently PostgreSQL and/or SQLite) and your hardware.
-
-SiSU Sabaki~{ SiSU Sabaki, release version. Pre-release version SiSU Scribe, and version prior to that SiSU nicknamed Scribbler. Pre-release versions go back several years. Both Scribbler and Scribe (still maintained) made system calls to SiSU's various parts, instead of using libraries. }~ (or just SiSU) is the provisional name given to the software described here that helps structure documents for web and other publication. The name SiSU is a loose anagram for something along the lines of *{/{"SiSU is structuring unit"}/}*, or /{"SiSU, information structuring unit"}/ or the more descriptive /{"Structured information, Serialized Units"}/ or *{/{"simple - information structuring unit"}/}* or the more descriptive /{"Structured information, Serialized Units"}/ or what it may be directed towards /{"*semantic* and *{information structuring universe}*"}/,~{ A little universe it may be, but semantic you may have a hard time getting away with, given the meaning the word has taken on with markup. On a document wide basis semantic information may be provided, which can be really useful, (and meaningful, especially) if you have a large document set, and use this with rss feeds or in an sql database etc. On a markup level, I have little inclination to add semantic markup formally beyond references, title, author [Dublin Core entities? addresses?] etc. Actually this deserves a bit of thought possibly use letter tags (including letter alias/synonyms for font faces) to create a small set of default semantic tags, with the possibility for per document adjustments. Will seek to permit XML entity tagging, within SiSU markup and have that ignored/removed by the parts of the program that have no use for it. }~ tongue in cheek, only just. Guess I'll get away with *{/{"Simple - information Structuring Universe"}/}*. SiSU is also a Finnish word roughly meaning guts, inner strength and perseverance.~{ "Sisu refers not to the courage of optimism, but to a concept of life that says, 'I may not win, but I will gladly give my life for what I believe.'" Aini Rajanen, Of Finnish Ways, 1981, p. 10. \\ http://www.humanlanguages.com/finnishenglish/rlfs.htm \\ "Every Finn has his own pet definition. To me, sisu means patience without passion. But there are many varieties of sisu. Sisu can be a sudden outburst or it can be the kind that lasts. A man can have both kinds. It is outside reason. It is something in the soul. It comes from oneself. For instance, it makes a soldier do things because he himself must, not because he has been told." Paavo Nurmi \\ http://personalweb.smcvt.edu/tmatikainen/finnishtraditions.htm }~
-
-SiSU was born of the need to find a way, with minimal effort, and for as wide a range of document types as possible, to produce high quality publishing output in a variety of document formats. As such it was necessary to find a simple document representation that would work across a large number of document types, and the most convenient way(s) to produce acceptable output formats. The project leading to this program was started in 1993 (together with the trade law project now known as Lex Mercatoria) as an investigation of how to effectively/efficiently place documents on the web. The unified document handling, together with features such as paragraph numbering, endnote handling and tables... appeared in 1996/97. SiSU was originally written in Perl,~{ http://www.perl.org/ }~ and converted to Ruby,~{ http://www.ruby-lang.org/en/ }~ in 2000, one of the most impressive programming languages in existence! In its current form it has been written to run on the Gnu/Linux platform, and in particular on Debian,~{ http://www.debian.org/ }~ taking advantage of many of the wonderful projects that are available there.
-
-SiSU markup is based on requiring the minimum markup needed to determine the structure of a document. (This can be as little as saying in a header to look for the word Book at a specified level and the word Chapter at another level). SiSU then breaks a document into its smallest parts (at a heading, and paragraph level) while retaining all structural information. This break up of the document and information on its structure is taken advantage of in the transformations made in generating the very different output types that can be created, and in providing as much as can be for what each output type is best at doing, e.g. LaTeX (professional document typesetting, easy conversion to PDF or Postscript), EPUB, XML (in this case, structural representation), ODF (Open Document Format text), SQL (e.g. document search; representing constituent parts of documents based on their structure, headings, chapters, paragraphs as required; user control).~{ where explicit structure is provided through the use of tagging headings, it could be reduced (still) further, for example by reducing the number of characters used to identify heading levels; but in many cases even that information is not required as regular expressions can be used to extract the implicit structure. }~
-
-From markup that is simpler and more sparse than HTML you get:
-
-_* far greater output possibilities, including HTML, EPUB, XML, ODF (Open Document Format text), LaTeX (PDF), and SQL;
-
-_* the advantages implicit in the very different output possibilities;
-
-_* a common citation system (for all outputs - including the relational database, search results are relevant for all outputs);
-
-For more see the short summary of features provided below.
-
-SiSU processes files with minimal tagging to produce various document outputs including HTML, EPUB, ODF, LaTeX (which is converted to PDF) and if required loads the structured information into an SQL database (PostgreSQL and SQLite have been used for this). SiSU produces an intermediate processing format.~{ This proved to be the easiest way to develop syntax, changes could be made, or alternatives provided for the markup syntax whilst the intermediate markup syntax was largely held constant. There is actually an optional second intermediate markup format in YAML http://www.yaml.org/ }~
-
-SiSU was originally used in constructing Lex Mercatoria http://lexmercatoria.org/ or http://www.jus.uio.no/lm/ (one of the oldest law web sites), and considerable thought went into producing output that would be suitable for legal and academic writings (that do not have formulae) given the limitations of HTML, and publication in a wide variety of "formats", in particular in relation to the convenient and accurate citation of text. However, the construction of Lex Mercatoria uses only a fraction of the features available from SiSU today, /vis/ generation of flat file structures, rather than in addition the building of ("granular") SQL database content, (at an object level with relevant relational tables, and other outputs also available).
-
-2~ Short summary of features *~summary
-
-!_ (i)
-markup syntax: (a) simpler than html, (b) mnemonic, influenced by mail/messaging/wiki markup practices, (c) human readable, and easily writable,
-
-!_ (ii)
-(a) minimal markup requirement, (b) single file marked up for multiple outputs,
-
-notes:
-
-* 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/parsed 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.
-
-!_ (iii)
-(a) multiple outputs primarily industry established and institutionally accepted open standard formats, include amongst others: plaintext (UTF-8); html; EPUB; (structured) XML; ODF (Open Document text)l; LaTeX; PDF (via LaTeX); SQL type databases (currently PostgreSQL and SQLite). 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))
-
-!_ (iv)
-outputs share a common numbering system (dubbed "object citation numbering" (ocn)) that is meaningful (to man and machine) across various digital outputs whether paper, screen, or database oriented, (PDF, html, EPUB, XML, Opendocument, SQLite, PostgreSQL), this numbering system can be used to reference content.
-
-!_ (v)
-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 hyperesteier].
-
-!_ (vi)
-use of semantic meta-tags in headers permit the addition of semantic information on documents, (the available fields are easily extended)
-
-!_ (vii)
-creates organised directory/file structure for (file-system) output, easily mapped with its clearly defined structure, with all text objects numbered, you know in advance where in each document output type, a bit of text will be found (e.g. from an SQL search, you know where to go to find the prepared html output or PDF etc.)... there is more; easy directory management and document associations, the document preparation (sub-)directory may be used to determine output (sub-)directory, the skin used, and the SQL database used,
-
-!_ (viii)
-"Concordance file" wordmap, consisting of all the words in a document and their (text/ object) locations within the text, (and the possibility of adding vocabularies),
-
-!_ (ix)
-document content certification and comparison considerations: the document and each object within it stamped with an md5 hash making it possible to easily check or guarantee that the substantive content of a document is unchanged.
-
-!_ (x)
-SiSU's minimalist markup makes for meaningful "diffing" of the substantive content of markup-files,
-
-!_ (xi)
-easily skinnable, document appearance on a project/site wide, directory wide, or document instance level easily controlled/changed,
-
-!_ (xii)
-in many cases a regular expression may be used (once in the document header) to define all or part of a documents structure obviating or reducing the need to provide structural markup within the document,
-
-!_ (xiii)
-prepared files may be batch process, documents produced are static files so 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)
-
-!_ (xiv)
-possible to pre-process, which permits: the easy creation of standard form documents, and templates/term-sheets, or; building of composite documents (master documents) from other sisu marked up documents, or marked up parts, i.e. import documents or parts of text into a main document should this be desired
-
-there is a considerable degree of future-proofing, output representations are "upgradeable", and new document formats may be added.
-
-!_ (xv)
-there is a considerable degree of future-proofing, output representations are "upgradeable", and new document formats may be added: (a) modular, (thanks in no small part to Ruby) another output format required, write another module.... (b) easy to update output formats (eg html, XHTML, EPUB, LaTeX/PDF produced can be updated in program and run against whole document set), (c) easy to add, modify, or have alternative syntax rules for input, should you need to,
-
-!_ (xvi)
-scalability, dependent on your file-system and on the relational database used (currently PostgreSQL and SQLite), and your hardware,
-
-!_ (xvii)
-only marked up files need be backed up, to secure the larger document set produced,
-
-!_ (xviii)
-document management,
-
-!_ (xix)
-Syntax highlighting for SiSU markup is available for a number of text editors.
-
-!_ (xx)
-remote operations: (a) run SiSU on a remote server, (having prepared sisu markup documents locally or on that server, i.e. this solution where sisu is installed on the remote server, would work whatever type of machine you chose to prepare your markup documents on), (b) generated document outputs may be posted by sisu to remote sites (using rsync/scp) (c)document source (plaintext utf-8) if shared on the net may be identified by its url and processed locally to produce the different document outputs.
-
-!_ (xxi)
-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, these may be downloaded, shared as email attachments, or processed by running sisu against them, either using a url or the filename.
-
-!_ (xxii)
-for basic document generation, the only software dependency is Ruby, and a few standard Unix tools (this covers plaintext, html, EPUB, 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
-
-SiSU was developed in relation to legal documents, and is strong across a wide variety of texts (law, literature...). SiSU handles images but is not suitable for formulae/ statistics, or for technical writing at this time.
-
-SiSU has been developed and has been in use for several years. Requirements to cover a wide range of documents within its use domain have been explored.
-
-Some modules are more mature than others, the most mature being html and LaTeX / pdf. PostgreSQL and search functions are useable and together with /ocn/ unique (to the best of my knowledge). The XML output document set is "well formed" but largely proof of concept.
-
-2~ How it works
-
-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 text 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 instruction 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,~{ 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. }~ 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).
-
-2~ Simple markup
-
-SiSU markup is based on requiring the minimum markup needed to determine the structure of a document. (This can be as little as saying in a header to look for the word Book at a specified level and the word Chapter at another level). SiSU then breaks a document into its smallest parts (at a heading, and paragraph level) while retaining all structural information. This break up of the document and information on its structure is taken advantage of in the transformations made in generating the very different output types that can be created, and in providing as much as can be for what each output type is best at doing, e.g. LaTeX (professional document typesetting, easy conversion to pdf or Postscript), EPUB, XML (in this case, structural representation), ODF (OpenDocument), SQL (e.g. document search; representing constituent parts of documents based on their structure, headings, chapters, paragraphs as required; user control).~{ where explicit structure is provided through the use of tagging headings, it could be reduced (still) further, for example by reducing the number of characters used to identify heading levels; but in many cases even that information is not required as regular expressions can be used to extract the implicit structure. }~
-
-3~ Sparse markup requirement, try to get the most out of markup
-
-One of its strengths is that very small amounts of initial tagging is required for the program to generate its output.
-
-This is a basic markup example:
-
-_* { basic markup example, text file - an international convention }http://www.jus.uio.no/sisu/src/un_contracts_international_sale_of_goods_convention_1980.sst ~{ http://www.jus.uio.no/sisu/src/un_contracts_international_sale_of_goods_convention_1980.sst output provided as example in the next section }~
-
-Emphasis has been on simplicity and minimalism in markup requirements. Design philosophy is to try keep the amount of markup required low, for whatever has been determined to be acceptable output.~{ seems there are several "smart ASCIIs" available, primarily for ascii to html conversion, that make this, and reasonable looking ascii their goal \\ http://webseitz.fluxent.com/wiki/SmartAscii \\ http://daringfireball.net/projects/markdown/ \\ http://www.textism.com/tools/textile/ }~
-
-SiSU's markup is more minimalistic and simpler than (the equivalent) html and for it, you get considerably more than just html, as this preparation gives you all available output formats, upon request.
-
-3~ Single markup file provides multiple output formats
-
-For each document, there is only one (input, minimalistically marked up) file from which all the available output types are generated.~{ These include richly laid out and linked html (table or css variants), /PHP/, LaTeX (from which pdf portrait and landscape documents are produced), texinfo (for info files etc.), and PostgreSQL and/or SQLite. And the opportunity to fairly easily build additional modules, such as XML. See the examples provided in this document. }~
-
-Eg. the markup example:
-
-_* {~^ original text file - an international convention }http://www.jus.uio.no/sisu/src/un_contracts_international_sale_of_goods_convention_1980.sst
-
-Produces the following output:
-
-_* {~^ Manifest of output presentations generated }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/sisu_manifest.html
-
-_* {~^ Segmented html version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/toc.html
-
-_* {~^ Full length html document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/doc.html
-
-_* {~^ EPUB version of document }http://www.jus.uio.no/sisu/epub/un_contracts_international_sale_of_goods_convention_1980.epub
-
-_* {~^ pdf landscape version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/landscape.letter.pdf
-
-_* {~^ pdf portrait version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/portrait.letter.pdf
-
-_* {~^ odt open document format text version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/opendocument.odt
-
-_* {~^ xml sax version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/sax.xml
-
-_* {~^ xml dom version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/dom.xml
-
-_* {~^ clean tex ascii version of document }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/plain.txt
-
-_* {~^ Concordance }http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/concordance.html
-
-(and in addition to these: PostgreSQL, SQLite, texinfo and -{YAML}- ~{ discontinued for the time being }~ versions if desired)
-
-3~ Syntax relatively easy to read and remember
-
-Syntax is kept simple and mnemonic.~{ SiSU markup syntax, an incomplete summary: http://www.jus.uio.no/sisu/sisu_markup/toc.html \\ Visual check of elementary font face modifiers: *bold* *{bold}* !{emphasis}! /{italics}/ _{underscore}_ -{strikethrough}- ^{superscript}^ ,{subscript}, }~
-
-3~ Kept simple by having a limited publishing feature set, and features identified as most important, are available across several document types
-
-To keep SiSU markup sparse and simple SiSU deliberately provides a limited publishing feature set, including: indent levels; bold; italics; superscript; subscript; simple tables; images; tables of contents and; endnotes. Which in most cases are available across the different output formats.
-
-The publishing feature set may be expanded as required.
-
-2~ Designed with usability in mind
-
-Output is designed to be uniform, easy to read, navigate and cite.
-
-2~ Code separate from content
-
-Code~{ the program that generates the documents }~ is separated from content. This means that when changes are desired in the output presentation, the code that produces them, and not the marked up text data set (which could be thousands of documents) is modified. Separating code from content makes large scale changes to output appearance trivial, and permits the easy addition of new output modules.
-
-2~ Object citation numbering, a text or object positioning / citation system - "paragraph" (or text object) numbering, that remains same and usable across all output formats by people and machine *~citation *~ocn
-
-Object citation numbering is a simple object (text) positioning and cition system that is human relevant and machine useable, used by SiSU for all manner of presentations, and that is available for use in all text mappings. It is based on the automated sequential numbering of objects (roughly paragraphs, (headings, tables, verse) or other blocks of text or images etc.). The text positioning system (in which I claim copyright) is invaluable for publishing requiring the citing text across multiple output formats, and for the general mapping of text within a document:
-
-_* in html, html not being easily citeable (change font size, or use a different browser and the page on which specific text appears has changed), and
-
-_* across multiple formats being common to all output formats html/xml/pdf/sql output,
-
-_* the results of an sql search can just be "live" citation references to the documents in which the text is found, {~^ much like an index (see image examples provided). }http://www.jus.uio.no/sisu/SiSU/1.html#search
-
-I claim copyright on the system I use which is the most basic of all, numbering all text in headings and paragraphs sequentially (with tables and images being treated as a single paragraph) and only footnotes/endnotes not following this numbering, as their position in text is not strictly determined, (a change from footnotes to endnotes would change their numbering), footnotes instead "belong" to the paragraph from which they are referenced, and have sequential numbers of their own.
-
-SiSU has a paragraph numbering system, that remains the same regardless of the output format. This provides an effective means of citation, pinpointing text accurately in all output formats, using the same reference. This is particularly useful where text has to be located across different output formats - for example once html is printed the number of pages and pages on which given text is found will vary depending on the browser, its settings the font size setting etc. Similarly SiSU produces pdf in different forms, eg. on the example site Lex Mercatoria as portrait and landscape documents - here too page numbering varies, but paragraph numbering is the same, /{vis a vis}/ all versions of the text (portrait and landscape pdf and the html versions of the text, and as stored (with "paragraphs" as records) to the PostgreSQL or SQLite database).
-
-These numbers are placed in the text margins and are intended to be independent of and not to interfere with authors tagging. [The citation system (object citation numbering system, automated "paragraph numbering") which is automatically generated and is common and identical across all document formats] The paragraph numbering system is more accurately described as an (text) object numbering system, as headings are also numbered... all headings and paragraphs are numbered sequentially. Endnotes are automatically numbered independently and rather "belong" to the paragraph from which they are referenced, as an endnote does not (necessarily) form a part of a documents sequence, (they may be produced as either endnotes or footnotes (or both depending on what output you choose to look at - if you take the segmented html version document provided as an example, you will find that the endnotes are placed both at the end of each section, and in a separate section of their own called endnotes, and these are hyper-linked)). An attractive feature of providing citation numbering in this way is that it is independent of the document structure... it remains the same regardless of what is done about the document structure.
-
-The rules have been kept very simple, unique incremental object citation numbers are assigned to headings, paragraphs, verse, tables and images. It is possible to manually override this feature on a per heading or comment basis though this should be used exceptionally, it may be of use where there a substantive text, and the addition of a minor comment by the publisher that should not be mapped as part of the text.
-
-The object citation number markers contain additional numbering information with regard to the document structure, that can be used for alternative presentations, including such detail as the type of object (heading, paragraph, table, image, etc.), numbered sequentially.
-
-An advantage is that the numbering remains the same regardless of document structure.
-
-Text object ("paragraph") numbering is the same for all output versions of the same document, vis HTML, EPUB, PDF, PgSQL, etc.
-
-In the relational database, as individual text objects of a document stored (and indexed) together with object numbers, and all versions of the document have the same numbering, the results of searches may be tailored just to provide the location of the search result in all available document formats.
-
-/{ Note: there is a bug in the released behaviour of object citation numbering, (not certain when it was introduced) tables should be numbered, ie each table gets an ocn, required amongst other things for relational database. This will be corrected in a future release. Citation numbering of existing documents that contain tables will changed. }/
-
-2~ Handling of Dublin Core meta-tags making use of the Resource Description Framework
-
-SiSU is able to use meta tags based on the Dublin Core~{ http://dublincore.org/ }~ and Resource Description Framework~{ http://www.w3.org/RDF/ }~
-
-This provides the means of providing semantic information about a document, both as computer processable meta-tags, and as human readable information that may be of value for classification purposes.
-
-This information is provided both in html metatags, and (where available) under the section titled "Document Information - Metadata", near the end of a document, for example in the segmented html version of this text at: http://www.jus.uio.no/sisu/SiSU/metadata.html
-
-2~ Easy directory management
-
-#1 Directory file association, skins and special image management, made simpler.~{ The previous way was directory associations for file output were set up in the configuration file. The present system is a more natural way to work requireing less configuration. }~
-
-The last part of the name of the work directory in which markup is being done, or rather from where SiSU is run in order to generate document output, is used in determining the sub-directory name for output files, that is created in the document output directory. This provides a rather easy way to associate documents e.g. of a given subject, or by owner.
-
-code{
-
-/www/docs
- /intellectual_property
- /arbitration
- /contract_law
-
-/www/docs
- /ralph
- /sisu
-
-}code
-
-all are placed in their own directories within the directory structure created. Similar rules are used in the creation of sql type databases (though they can be overridden).
-
-There are a couple of further associations with these directories.
-
-# If the working directory has within it a sub-directory called image_local, the images within that directory are used for references to images, that are not part of the default site build.
-
-2~ Document Version Control Information
-
-The possibility of citing an exact document version.
-
-Permits the inclusion of document version control information to the document body and metatags.~{ from a version control system such as CVS }~ This provides a much more certain method of referring to the exact version of a particular document, (assuming that the document is from a trusted source, that will retain earlier versions of a document).~{ The version control system must be run, so the version number is obtained, prior to the SiSU document generation, and subsequent posting of the document. }~
-
-This information (where available) is provided under the section of the document titled "Document Information - MetaData", near the end of a document, for example in the segmented html version of this text at: http://www.jus.uio.no/sisu/SiSU/metadata.html
-
-2~ Table of contents
-
-SiSU produces a rudimentary a table of contents based on document headings.
-
-2~ Auto-numbering of headings
-
-Headings can be automatically numbered, (and automatically named for hyper-linking)
-
-2~ Numbering and cross-hyperlinking of endnotes
-
-SiSU can automatically number footnotes/endnotes. This is the default operation where no number is provided.
-
-Footnotes/endnotes may also be manually numbered. Where a number, or numbers are provided for a footnote/endnote, this does not increment the automatic footnote/endnote number counter.
-
-In the html output footnotes/endnotes are cross-hyper-linked (to their reference point and vice versa). In th pdf output footnotes are linked from their reference point only.
-
-2~ "Skinnable"
-
-SiSU is skinnable, on a site-wide, directory-wide and per document basis, so different looking versions of things may be produced with little difficulty. There is a default skin which may be modified, as the background site skin, and each working directory may have a skin associated with it, as may each individual document. The hierarchy of application is document, directory, then site... ie if a document skin exists it gets precedence.
-
-Whilst it is skinnable, the default output styles are selected to work across the widest possible range of document types.
-
-2~ Multiple Outputs
-
-From markup that is simpler and more sparse than html you get:
-
-_* far greater output possibilities, including multiple html types, XML (different structured types), LaTeX (pdf landscape, portrait), and SQL (PostgreSQL or SQLite or other);
-
-_* the advantages implicit in these very different output possibilities;~{ e.g. LaTeX (professional document typesetting, easy conversion to pdf or Postscript), XML (in this case, structural representation), SQL (e.g. document set searches; representation of the constituent parts of documents based on their structure, headings, chapters, paragraphs as desired; control of use) }~
-
-_* a common citation system
-
-As many output formats/presentations as one cares to write modules for - several types of html (e.g. structure based on css, or structure based on tables); /{LaTeX/pdf}/ and /{Lout/pdf}/; PgSQL other databases easily added; yaml...
-
-3~ html - several presentations: full length & segmented; css & table based
-
-Most documents are produced in single and segmented html versions, described below:
-
-!_ The Scroll (full length text presentations)
-
-The full length of the text in a single scrollable document.~{ CISG http://www.jus.uio.no/lm/un.contracts.international.sale.of.goods.convention.1980/doc.html \\ The Unidroit Contract Principles http://www.jus.uio.no/lm/unidroit.contract.principles.1994/doc.html or \\ The Autonomous Contract http://www.jus.uio.no/lm/autonomous.contract.2000.amissah/doc.html }~ As a rule the files they are saved in are named: /doc/ or more precisely /{doc.html}/
-
-For various reasons texts may only be provided in this form (such as this one which is short), though most are also provided as segmented texts.
-
-"Scroll" is a reference to the historical scroll, a single long document/ parchment, and also no doubt to what you will have to do to get to the bottom of the text.~{ Scrolling is not however necessarily confined to full length documents as you will have to scroll to get to the bottom of any long segment (eg. chapter) of a segmented text. }~
-
-!_ The Segmented Text
-
-The text divided into segments (such as articles or chapters depending on the text)~{ CISG http://www.jus.uio.no/lm/un.contracts.international.sale.of.goods.convention.1980/toc.html \\ The Unidroit Principles http://www.jus.uio.no/lm/unidroit.contract.principles.1994/toc.html \\ The Autonomous Contract http://www.jus.uio.no/lm/autonomous.contract.2000.amissah/toc.html or \\ WTA 1994 http://www.jus.uio.no/lm/wta.1994 }~ As a rule the files they are saved in are named: /toc/ and /index/ or more precisely /{toc.html}/ and /{index.html}/
-
-If you know exactly what you are looking for, loading a segment of text is faster (the segments being smaller). Occasionally longer documents such as the WTA 1994 http://www.jus.uio.no/lm/wta.1994/toc are only provided in segmented form.
-
-!_ Cascading Style Sheet, and Table based html
-
-SiSU outputs html, two current standard forms available are:
-
-{ css based }http://www.jus.uio.no/sisu/SiSU/toc.html
-
-and
-
-table based [largely discontinued]~{ formatting possibility still exists in code tree but maintenance has been largely discontinuted. }~
-
-!_ The html is tested across several browsers
-
-I like to remind you that there are other excellent browsers out there, many of which have long supported practical features like tabbing.
-
-The html is tested across several browsers, including:
-
-_* {~^ *Firefox* (Mozilla-Firefox) }http://www.mozilla.org/products/firefox/
-
-_* {~^ Kazehakase }http://kazehakase.sourceforge.jp/
-
-_* {~^ Konqueror }http://www.konqueror.org/
-
-_* {~^ Mozilla }http://www.mozilla.org/
-
-_* {~^ MS Internet Explorer }http://www.microsoft.com/windows/ie/default.asp
-
-_* {~^ Netscape }http://home.netscape.com/comprod/mirror/client_download.html
-
-_* {~^ Opera }http://www.opera.com/
-
-Also lighter weight graphical browsers:
-
-_* {~^ Dillo }http://www.dillo.org/
-
-_* {~^ *Epiphany* }http://www.gnome.org/projects/epiphany/
-
-_* {~^ *Galeon* }http://galeon.sourceforge.net/
-
-And for console/text browsing:
-
-_* {~^ *elinks* }http://elinks.or.cz/
-
-_* {~^ *links2* }http://links.twibright.com/
-
-_* {~^ *w3m* }http://w3m.sourceforge.net/
-
-The html tables output is rendered more accurately across a wider variety set and older versions of browsers (than the html css output).
-
-3~ EPUB
-
-SiSU generates EPUB documents.
-
-3~ XML
-
-SiSU generates well formed XML, and multiple versions. An XML SAX version with a flat/shallow structure, and XML DOM version with a deeper (embedded) structure. There is also a released working xhtml module. Examples of SAX and DOM versions are provided within this document.
-
-3~ ODT:ODF, Open Document Format - ISO/IEC 26300:2006
-
-SiSU generates Open Document Output format.
-
-3~ PDF - portrait and landscape, (through the generation of LaTeX output which is then transformed to pdf)
-
-SiSU outputs LaTeX if required which is easily transformed to PDF.~{ LaTeX and pdf features introduced 18^th^ June 2001, Landscape and portrait pdfs introduced 7^th^ October 2001., Lout is a more recent addition 22^th^ April 2003 }~ PDF documents are generated on the site from the same source files and Ruby program that produce html. Landscape oriented pdf introduced, providing easier screen viewing, they are also (paper saving, being currently) formatted to have fewer pages than their portrait equivalents.
-
-_* {~^ Adobe Reader }http://www.adobe.com/products/acrobat/readstep2.html
-
-_* {~^ *Evince* }http://www.gnome.org/projects/evince/
-
-_* {~^ xpdf }http://www.foolabs.com/xpdf/
-
-3~ Search - loading/populating of relational database while retaining document structure information, object citation numbering and other features (currently PostgreSQL and/or SQLite)
-
-SiSU (from the same markup input file) automatically feeds into 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 (could be any other of the better relational databases)~{ Relational database features retaining document structure and citation introduced 15^th^ July 2002 }~ - together with all additional information related to document structure, and the alternative ways in which it is generated on the site retained. As regards scaling of the database, it is as scalable as the database (here Postgresql or SQLite) and hardware allow. I will prune the images later.
-
-This is one of the more interesting output forms, as all the structural data for 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 PgSQL database tables:
-
-_1* one containing semantic (and other) headers, including, title, author, subject, (the Dublin Core...);
-
-_1* another the substantive texts by individual "paragraph" (or object) - along with structural information, each paragraph being identifiable by its paragraph number (if it has one which almost all of them do), and the substantive text of each paragraph quite naturally being searchable (both in formatted and clean text versions for searching); and
-
-_1* a third containing endnotes cross-referenced back to the paragraph from which they are referenced (both in formatted and clean text versions for searching).
-
-_1* a fourth table with a one to one relation with the headers table contains full text versions of output, eg. pdf, html, xml, and ascii.
-
-There is of course the possibility to add further structures.
-
-At this level SiSU loads a relational database with documents broken in to their smallest logical structurally constituent parts, as text objects, with their object citation number and all other structural information needed to construct the structured document. Text is stored (at this text object level) with and without elementary markup tagging, the stripped version being so as to facilitate ease of searching.
-
-Because the document structure of sites created is clearly defined, and the text object citation system is available 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.
-
-The combination of the SiSU citation system with a relational database is pretty powerful, giving rise to several possibilities. As individual text objects of a document stored (and indexed) together with object numbers, and all versions of the document have the same numbering, complex searches can be tailored to return just the locations of the search results relevant for all available output formats, with live links to the precise locations in the database or in html/xml documents; or, the structural information provided makes it possible to search the full contents of the database and have headings in which search content appears, or to search only headings etc. (as the Dublin Core is incorporated it is easy to make use of that as well).
-
-This is a larger scale project, (with little development on the front end largely ignored), though the "infrastructure" has been in place since 2002.
-
-3~ Search - database frontend sample, utilising database and SiSU features, including object citation numbering (backend currently PostgreSQL) *~search
-
-{~^ Sample search frontend }http://search.sisudoc.org
-A small database and sample query front-end (search from) that makes use of the citation system, _{object citation numbering}_ to demonstrates functionality.~{ (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. }~
-
-SiSU can provide information on which documents are matched and at what locations within each document the matches are found. These results are relevant across all outputs using object citation numbering, which includes html, EPUB, XML, LaTeX, PDF and indeed the SQL database. You can then refer to one of the other outputs or in the SQL database expand the text within the matched objects (paragraphs) in the documents matched.
-
-(further work needs to be done on the sample search form, which is rudimentary and only passes simple booleans correctly at present to the SQL engine)
-
-A few canned searches, showing object numbers. Search for:
-
-{ English documents matching Linux OR Debian }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=Linux%2BOR%2BDebian&db=SiSUv2c_sisu&view=index
-
-{ GPL OR Stallman }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=GPL%2BOR%2BStallman&db=SiSUv2c_sisu&view=index
-
-{ invention OR innovation }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=invention%2BOR%2Binnovation&db=SiSUv2c_sisu&view=index
-
-{ copyright in English language documents }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=copyright&db=SiSUv2c_sisu&view=index
-
-Note that the searches done in this form are case sensitive.
-
-Expand those same searches, showing the matching text in each document:
-
-{ English documents matching Linux OR Debian }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=Linux%2BOR%2BDebian&db=SiSUv2c_sisu&view=text
-
-{ GPL OR Stallman }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=GPL%2BOR%2BStallman&db=SiSUv2c_sisu&view=text
-
-{ invention OR innovation }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=invention%2BOR%2Binnovation&db=SiSUv2c_sisu&view=text
-
-{ copyright }http://search.sisudoc.org/cgi-bin/sisu_pgsql.cgi?s1=copyright&db=SiSUv2c_sisu&view=text
-
-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.~{ 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 and we can tell you which documents meet your search criteria, but there is no way we can tell you without opening each document where within each your matches are found. }~
-
-!_ OCN index mode,
-(object citation number) the numbers displayed are relevant (and may be used to reference the match) in any sisu generated rendition of the text~{ OCN are provided for HTML, XML, EPUB, pdf ... though currently omitted in plain-text and opendocument format output }~ the links provided are to the locations of matches within the html generated by SiSU.
-
-!_ Paragraph mode,
-you may alternatively display the text of each paragraph in which the match was made, again the object/paragraph numbers are relevant to any SiSU generated/published text.
-
-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].
-
-Simple search, results with files in which search found, and text object (paragraph or endnote) where found within files.
-
-3~ Other forms
-
-There are other forms as well, YAML file, Ruby Marshal dumps, document pre-processing (processing of documents prior to the steps described here, to produce input suitable for the program) snap in a new module as required/desired, well formed XML, no problem.
-
-2~ Concordance / Word Map or rudimentary index
-
-Concordance /WordMaps:~{ Concordance/ WordMaps introduced 15^th^ August 2002 }~ SiSU produces a rudimentary index based on the words within the text, making use of paragraph numbers to identify text locations. This is generated in html and hyper-linked but identifies these words locations in the other document formats. Though it is possible to search using a search engine, this is a means for browsing an alphabetical list of words which may suggest other useful content.
-
-% Concordance files may be built using a document vocabulary. The vocabulary to be used may be specified on a per document basis.
-
-2~ Managed (document) directory, database, or site structure
-
-SiSU builds the web site (or more generically provides a suitable directory structure) - placing various output texts in the hierarchy of the web-site (or db), which (for directories) is a sub-directory with the name of the text file.
-
-2~ Batch processing
-
-SiSU is a batch processing tool, handling and transforming multiple (or individual) documents (in many ways) with a single instruction.
-
-2~ Integration to superior Gnu/Linux and Unix tools
-
-As should have been noted by the above description of SiSU, it makes use of existing programs found on Gnu/Linux and Unix, amongst those already mentioned include the LaTeX to pdf converters and the database PostgreSQL or SQLite.
-
-3~ Backup and version control
-
-Unix provides many tools for version control. For documents Subversion, CVS and even the old RCS are useful for the per-document histories they provide.
-
-For writing code superior (more recent) version control system exist. These can also be used for documents though they tend to take stamps of changes across the repository as a whole, rather than for each individual file that is tracked, (as CVS and RCS do). My personal preference is for distributed systems such as Git, Mercurial or Darcs, of which I use Git for both code and documents.
-
-Several backup tools exist. At the base level I tend to use rdiff.
-
-3~ Editor support
-
-SiSU documents are prepared / marked up in utf-8 text _{you are free to use the text editor of your choice.}_
-
-Syntax highlighting for a number of editors are provided. Amongst them Vim, Kwrite, Kate, Gedit and diakonos. These may be found with configuration instructions at http://www.sisudoc.org/sisu/sisu_syntax_highlighting/doc.html {~^ Vim }http://www.vim.org/ as of version 7 has built in sytax highlighting for SiSU.
-
-2~ Modular design, need something new add a module
-
-Need a new output format that does not already exist, write a new module.
-
-Prefer a new input syntax, you could write a new syntax matching the existing design, though my personal preference is some uniformity in entry appearance. If necessary has been fairly easy to extend the design parameters. It is intended to incorporate some additional basic semantic tagging, (book, article, author etc.) However, keeping the requirements for input minimal, and relatively simple has been a design goal.
-
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_download.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_download.ssi
deleted file mode 100644
index 96c97985..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_download.ssi
+++ /dev/null
@@ -1,133 +0,0 @@
-% SiSU insert 2.0
-
-@title: SiSU - SiSU information Structuring Universe / Structured information, Serialized Units
- :subtitle: Download, Stable and Development Branches
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-11-12
- :issued: 2002-11-12
- :available: 2002-11-12
- :published: 2009-01-18
- :modified: 2011-03-11
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? @title @creator
-
-:B~? SiSU Downloads, Stable and Development Branches
-
-:C~ Download information
-
-1~download Download SiSU - Linux/Unix
-
-2~current- SiSU Current Version - Linux/Unix
-
-3~source- Source (tarball tar.gz)
-
-_* {~^ sisu_[version].orig.tar.gz }http://www.jus.uio.no/sisu/pkg/src/
-
-_* {~^ sisu-markup-samples_[version].orig.tar.gz }http://www.jus.uio.no/sisu/pkg/src/
-
-For more general use see http://sisudoc.org/sisu/sisu_manual
-
-For changelogs see http://www.jus.uio.no/sisu/SiSU/changelog.html
-
-3~git- Git (source control management)
-
-Git repository currently at:
-
-_* git clone git://git.sisudoc.org/git/code/sisu.git
-
-_* git clone _http://git.sisudoc.org/git/code/sisu.git
-
-_* http://git.sisudoc.org/?p=code/sisu.git;a=summary
-
-On using git, see
-
-!_ Git documentation:
-{~^ Git User's Manual }http://www.kernel.org/pub/software/scm/git/docs/user-manual.html, {~^ Everyday GIT With 20 Commands Or So }http://www.kernel.org/pub/software/scm/git/docs/everyday.html, {~^ A tutorial introduction to git }http://www.kernel.org/pub/software/scm/git/docs/v1.4.4.4/tutorial.html, {~^ A tutorial introduction to git: part two }http://www.kernel.org/pub/software/scm/git/docs/v1.4.4.4/tutorial-2.html
-
-!_ User contributed texts:
-{~^ The Git Community Book }http://book.git-scm.com/index.html, {~^ Git Magic }http://www-cs-students.stanford.edu/~blynn/gitmagic/, {~^ Git From the Bottom Up (pdf) }http://www.newartisans.com/blog_assets/git.from.bottom.up.pdf
-
-3~debian- Debian
-
-This section contains information on the latest SiSU release. For installation notes see http://sisudoc.org/sisu/sisu_manual/installation.html
-
-SiSU is updated fairly regularly in Debian testing and unstable, and should be available therefrom.
-
-To add this archive, should you still choose to do so, add the following lines to your /etc/apt/sources.list
-
-code{
-
-deb http://www.jus.uio.no/sisu/archive unstable main non-free
-deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
-
-}code
-
-*{Source}* available from
-
-http://www.jus.uio.no/sisu/pkg/src/
-
-http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/
-
-http://www.sisudoc.org/sisu/archive/pool/main/s/sisu/
-
-sisu_[version].orig.tar.gz
-
-sisu_[version].debian.tar.gz
-
-sisu_[version].dsc
-
-group{
-
-*{Debs}*
-
-{~^ sisu_[version]_all.deb }http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/ ~{ \\ sisu, the base code, (the main package on which the others depend), without any dependencies other than ruby (and for convenience the ruby webrick web server), this generates a number of types of output on its own, other packages provide additional functionality, and have their dependencies \\ Depends: ruby (>=1.8.7), libwebrick-ruby \\ Recommends: sisu-pdf, sisu-sqlite, sisu-postgresql, sisu-examples, vim-sisu, librmagick-ruby, trang, tidy, libtidy, librexml-ruby, zip, unzip, openssl }~
-
-{~^ sisu-complete_[version]_all.deb }http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/ ~{ \\ a package that pulls in other packages to build the whole of sisu (excluding sisu-examples) \\ Depends: ruby (>=1.8.7), sisu, sisu-pdf, sisu-postgresql, sisu-remote, sisu-sqlite, vim-sisu \\ Recommends: sisu-examples }~
-
-{~^ sisu-pdf_[version]_all.deb }http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/ ~{ \\ dependencies used by sisu to produce PDF from LaTeX generated \\ Depends: sisu, tetex-bin, tetex-extra, latex-ucs \\ Suggests: evince, xpdf }~
-
-{~^ sisu-postgresql_[version]_all.deb }http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/ ~{ \\ dependencies used by sisu to populate postgresql database (further configuration is necessary) \\ Depends: sisu, postgresql, libdbi-ruby, libdbm-ruby, libdbd-pg-ruby \\ Suggests: pgaccess, libdbd-pgsql, postgresql-contrib }~
-
-{~^ sisu-sqlite_[version]_all.deb }http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/ ~{ \\ dependencies used by sisu to populate sqlite database \\ Depends: sisu, sqlite, libdbi-ruby, libdbm-ruby, libdbd-sqlite-ruby \\ Suggests: libdbd-sqlite }~
-
-}group
-
-For changelogs see:
-
-_1 http://www.sisudoc.org/sisu/SiSU/changelog.html
-
-_1 http://www.jus.uio.no/sisu/SiSU/changelog.html
-
-!_ non-free
-
-Book markup samples have been moved to non-free as the substantive text of the documents are available under the author or original publisher's license, and usually do not comply with the Debian Free Software Guidelines.
-
-_* {~^ sisu-markup-samples_[version]_all.deb }http://www.jus.uio.no/sisu/archive/pool/non-free/s/sisu-markup-samples/ ~{ \\ marked up documents and other examples related to sisu, a larger package containing a number of texts \\ Depends: sisu }~
-
-_* {~^ sisu-markup-samples_[version].dsc }http://www.jus.uio.no/sisu/pkg/src/ ~{ \\ sisu-markup-samples_[version].dsc }~
-
-For changelogs see:
-
-_1 http://www.jus.uio.no/sisu/SiSU/changelog_markup_samples.html
-
-3~rpm- RPM
-
-The RPM is generated from the source file using Alien.~{ http://www.kitenet.net/programs/alien/ }~ Dependencies are not handled, not even that of the essential Ruby.
-
-sudo rpm -i [package name]
-
-_* {~^ sisu-[version].noarch.rpm }http://www.jus.uio.no/sisu/pkg/rpm/ ~{ \\ created using alien }~
-
-_* {~^ sisu-markup-samples_[version].noarch.rpm }http://www.jus.uio.no/sisu/pkg/rpm/ ~{ \\ http://www.jus.uio.no/sisu/archive/pool/non-free/s/sisu-markup-samples/ \\ created using: alien -r sisu_[version]_all.deb }~
-
-For changelogs see:
-
-_1 http://www.jus.uio.no/sisu/SiSU/changelog_markup_samples.html
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_examples.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_examples.ssi
deleted file mode 100644
index cf9df9d5..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_examples.ssi
+++ /dev/null
@@ -1,97 +0,0 @@
-% SiSU insert 2.0
-
-@title: SiSU
- :subtitle: Markup Samples, Output Examples
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-11-12
- :issued: 2002-11-12
- :available: 2002-11-12
- :published: 2007-09-16
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-A~? @title @creator
-
-B~? SiSU Markup and Output Examples
-
-1~examples Markup and Output Examples
-
-2~ Markup examples *~markup
-
-Current markup examples and document output samples are provided off http://sisudoc.org or http://www.jus.uio.no/sisu and in the sisu-markup-sample package available off http://sources.sisudoc.org
-
-For some documents hardly any markup at all is required at all, other than a header, and an indication that the levels to be taken into account by the program in generating its output are.
-
-2~sisu-markup-samples SiSU Markup Samples
-
-A few additional sample books prepared as sisu markup samples, output formats to be generated using SiSU are contained in a separate package sisu-markup-samples. sisu-markup-samples contains books (prepared using sisu markup), that were released by their authors various licenses mostly different Creative Commons licences that do not permit inclusion in the Debian Project as they have requirements that do not meet the Debian Free Software Guidelines for various reasons, most commonly that they require that the original substantive text remain unchanged, and sometimes that the works be used only non-commercially.
-
-/{Accelerando}/, Charles Stross (2005) \\
-accelerando.charles_stross.sst
-
-/{Alice's Adventures in Wonderland}/, Lewis Carroll (1865) \\
-alices_adventures_in_wonderland.lewis_carroll.sst
-
-/{CONTENT}/, Cory Doctorow (2008) \\
-content.cory_doctorow.sst
-
-/{Democratizing Innovation}/, Eric von Hippel (2005) \\
-democratizing_innovation.eric_von_hippel.sst
-
-/{Down and Out in the Magic Kingdom}/, Cory Doctorow (2003) \\
-down_and_out_in_the_magic_kingdom.cory_doctorow.sst
-
-/{For the Win}/, Cory Doctorow (2010) \\
-for_the_win.cory_doctorow.sst
-
-/{Free as in Freedom - Richard Stallman's Crusade for Free Software}/, Sam Williams (2002) \\
-free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst
-
-/{Free as in Freedom 2.0 - Richard Stallman and the Free Software Revolution}/, Sam Williams (2002), Richard M. Stallman (2010) \\
-free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst
-
-/{Free Culture - How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity}/, Lawrence Lessig (2004) \\
-free_culture.lawrence_lessig.sst
-
-/{Free For All - How Linux and the Free Software Movement Undercut the High Tech Titans}/, Peter Wayner (2002) \\
-free_for_all.peter_wayner.sst
-
-/{GNU GENERAL PUBLIC LICENSE v2}/, Free Software Foundation (1991) \\
-gpl2.fsf.sst
-
-/{GNU GENERAL PUBLIC LICENSE v3}/, Free Software Foundation (2007) \\
-gpl3.fsf.sst
-
-/{Gulliver's Travels}/, Jonathan Swift (1726 / 1735) \\
-gullivers_travels.jonathan_swift.sst
-
-/{Little Brother}/, Cory Doctorow (2008) \\
-little_brother.cory_doctorow.sst
-
-/{The Cathederal and the Bazaar}/, Eric Raymond (2000) \\
-the_cathedral_and_the_bazaar.eric_s_raymond.sst
-
-/{The Public Domain - Enclosing the Commons of the Mind}/, James Boyle (2008) \\
-the_public_domain.james_boyle.sst
-
-/{The Wealth of Networks - How Social Production Transforms Markets and Freedom}/, Yochai Benkler (2006) \\
-the_wealth_of_networks.yochai_benkler.sst
-
-/{Through the Looking Glass}/, Lewis Carroll (1871) \\
-through_the_looking_glass.lewis_carroll.sst
-
-/{Two Bits - The Cultural Significance of Free Software}/, Christopher Kelty (2008) \\
-two_bits.christopher_kelty.sst
-
-/{UN Contracts for International Sale of Goods}/, UN (1980) \\
-un_contracts_international_sale_of_goods_convention_1980.sst
-
-/{Viral Spiral}/, David Bollier (2008) \\
-viral_spiral.david_bollier.sst
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_faq.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_faq.sst
deleted file mode 100644
index 966cea5f..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_faq.sst
+++ /dev/null
@@ -1,200 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: FAQ - Frequently Asked/Answered Questions
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2008-03-12
- :created: 2006-09-06
- :available: 2006-09-06
- :issued: 2006-09-06
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: electronic documents;SiSU:document:FAQ;sisu:document:FAQ;SiSU:manual:FAQ;electronic documents:SiSU:manual:FAQ
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-1~faq FAQ - Frequently Asked/Answered Questions
-
-2~ Why are urls produced with the -v (and -u) flag that point to a web server on port 8081 ?
-
-Try the following rune:
-
-_* sisu -W
-
-This should start the ruby webserver. It should be done after having produced some output as it scans the output directory for what to serve.
-
-2~ I cannot find my output, where is it?
-
-The following should provide help on output paths:
-
-_* sisu --help env
-
-_* sisu -V [same as the previous command]
-
-_* sisu --help directory
-
-_* sisu --help path
-
-_* sisu -U [filename]
-
-_* man sisu
-
-2~ I do not get any pdf output, why?
-
-SiSU produces LaTeX and pdflatex is run against that to generate pdf files.
-
-If you use Debian the following will install the required dependencies
-
-_* aptitude install sisu-pdf
-
-the following packages are required: tetex-bin, tetex-extra, latex-ucs
-
-2~ Where is the latex (or some other interim) output?
-
-Try adding -M (for maintenance) to your command flags, e.g.:
-
-_* sisu -HpMv [filename]
-
-this should result in the interim processing output being retained, and information being provided on where to find it.
-
-_* sisu --help directory
-
-_* sisu --help path
-
-should also provide some relevant information as to where it is placed.
-
-2~ Why isn't SiSU markup XML
-
-I worked with text and (though I find XML immensely valuable) disliked noise
-... better to sidestep the question and say:
-
-SiSU currently "understands" three XML input representations - or more accurately, converts from three forms of XML to native SiSU markup for processing. The three types correspond to SAX (structure described), DOM (structure embedded, whole document must be read before structure is correctly discernable) and node based (a tree) forms of XML document structure representation. Problem is I use them very seldom and check that all is as it should be with them seldom, so I would not be surprised if something breaks there, but as far as I know they are working. I will check and add an XML markup help page before the next release. There already is a bit of information in the man page under the title SiSU VERSION CONVERSION
-
-_1 sisu --to-sax [filename/wildcard]
-
-_1 sisu --to-dom [filename/wildcard]
-
-_1 sisu --to-node [filename/wildcard]
-
-The XML should be well formed... must check, but lacks sensible headers. Suggestions welcome as to what to make of them. [For the present time I am satisfied that I can convert (both ways) between 3 forms of XML representation and SiSU markup].
-
-_1 sisu --from-xml2sst [filename/wildcard]
-
-2~ LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU?
-
-% what are some similarities and differences between LaTex and SiSU?
-
-SiSU is not really about type-setting.
-
-LaTeX is the ultimate computer instruction type-setting language for paper based publication.
-
-LaTeX is able to control just about everything that happens on page and pixel, position letters kerning, space variation between characters, words, paragraphs etc. formula.
-
-SiSU is not really about type-setting at all. It is about a lightweight markup instruction that provides enough information for an abstraction of the documents structure and objects, from which different forms of representation of the document can be generated.
-
-SiSU with very little markup instruction is able to produce relatively high quality pdf by virtue of being able to generate usable default LaTeX; it produces "quality" html by generating the html directly; likewise it populates an SQL database in a useful way with the document in object sized chunks and its meta-data. But SiSU works on an abstraction of the document's structure and content and custom builds suitable uniform output. The html for browser viewing and pdf for paper viewing/publishing are rather different things with different needs for layout - as indeed is what is needed to store information in a database in searchable objects.
-
-% SiSU is a lightweight document abstraction, meta-(structure and markup) syntax designed to make use of a minimal amount of preparation detail that can be used across very different ways of representing documents
-
-The pdfs or html produced for example by open office based on open document format and other office/word processor suits usually attempt to have similar looking outputs - your document rendered in html looks much the same, or in pdf... sisu is less this way, it seeks to have a starting point with as little information about appearance as possible, and to come up with the best possible appearance for each output that can be derived based on this minimal information.
-
-Where there are large document sets, it provides consistency in appearance in each output format for the documents.
-
-The excuse for going this way is, it is a waste of time to think much about appearance when working on substantive content, it is the substantive content that is relevant, not the way it looks beyond the basic informational tags - and yet you want to be able to take advantage of as many useful different ways of representing documents as are available, and for various types of output to to be/look as good as it can for each medium/format in which it is presented, (with different mediums having different focuses) and SiSU tries to achieve this from minimal markup.
-
-2~ Can the SiSU markup be used to prepare for a LaTex automatic building of an index to the work?
-
-Has not been, is of interest though the question on introducing such possibilities is how to keep them as unobtrusive as possible, and as generically relevant as possible to other output formats (which is why the focus on object numbers). Unobtrusive refers both to the markup (where there is no big problem with introducing optional extras); and, more challengingly how to minimise impact on competing ideas/interests, such allowing the addition of semantic tags which could be tied to objects, mapped against the objects that contain them, (permitting mapping and mining of content in various ways that would be largely agnostic of output format - object numbering being an attempt to move beyond output format based content locators (such as page numbers). The desire being to (be a meta markup and) maintain agnosticism as to what is being generated and in development to favor solutions of that nature. Keep bridging LaTeX, XML, SQL ... make use of objects and serialisation for mapping whether against content or meta-content (such as semantic [or additional structural] markers).
-
-2~ Can the conversion from SiSU to LaTeX be modified if we have special needs for the LaTeX, or do we need to modify the LaTeX manually?
-
-Should be possible to modify code, it is GPLv3, should be possible either to modify existing modules or write an independent module for generating bespoke latex. Generic improvements are welcome for inclusion/incorporation in the existing code base.
-
-If there are tools to generate mathematical/scientific formula from latex to images (jpg, png), the latex parser could conceivably be used to make these available to other output formats.
-
-2~ How do I create GIN or GiST index in Postgresql for use in SiSU
-
-This at present needs to be done "manually" and it is probably necessary to alter the sample search form. The following is a helpful response from one of the contributors of GiN to Postgresql Oleg Bartunov 2006-12-06:
-
-"I have tsearch2 slides which introduces tsearch2
-http://www.sai.msu.su/~megera/wiki/tsearch2slides
-
-FTS in PostgreSQL is provided by tsearch2, which should works without
-any indices (GiST or GIN) ! Indices provide performance, not functionality.
-
-In your example I'd do ( simple way, just for demo):
-
-!_ 0.
-compile, install tsearch2 and load tsearch2 into your database
-
-_1 cd contrib/tsearch2; make&&make&&install&&make installcheck; psql DB < tsearch2.sql
-
-!_ 1.
-Add column fts, which holds tsvector
-
-_1 alter table documents add column fts tsvector;
-
-!_ 2.
-Fill fts column
-
-_1 update document set fts = to_tsvector(clean);
-
-!_ 3.
-create index - just for performance !
-
-_1 create index fts_gin_idx on document using gin(fts);
-
-!_ 4.
-Run vacuum
-
-_1 vacuum analyze document;
-
-That's all.
-
-Now you can search:
-
-select lid, metadata_tid, rank_cd(fts, q,2)as rank from document, plainto_tsquery('markup syntax') q where q @@ fts order by rank desc limit 10;
-
-2~ Are there some examples of using Ferret Search with a SiSU repository?
-
-Heard good things about Ferret, but have not used it. The output directory structure and content produced by SiSU is very uniform. Have looked at a couple of other engines (hyperestraier, lucene). There it was enough to identify the files that needed to be indexed and pass them to the search indexing tool. Some Unix rune doing the job, such as:
-
-code{
-
-find /home/ralph/sisu_www -type f | \
-egrep '/sisu_www/(sisu|document_archive)/.+?.html$' | \
-egrep -v '(doc|concordance).html$' | \
-estcmd gather -sd casket -
-
-}code
-
-you would have to experiment with what gives the desired result, the file doc.html is the complete text in html (there are additional smaller html segments), and plain.txt the document as a text file. It may be possible to index the text file and return the html document.
-
-
-2~ Have you had any reports of building SiSU from tar on Mac OS 10.4?
-
-None. In the early days of its release a Mac friend built and run the ruby code part that did not rely on system calls to bits like the latex engine. That is already some years back. He was not into writing or document markup, and did it as a favour at the time. I have not followed up that thread of development.
-
-It should however be possible, much of the output relies on plain ruby, and the system commands to latex etc. could be made appropriate for the underlying OS.
-
-2~ Where is version 1?
-
-Version 1 was finally released on December 21, 2009, and largely to make a version 1 branch available as version 2 was in the pipeline with an imminent release. Most of SiSU was mature and stable long before the release of version 1.
-
-2~ What is the difference between version 1 and 2?
-
-Input and output of version 1 and 2 are largely the same with the following significant exceptions. On the input side, document headers, that is metadata and processing instructions have changed in version 2. On the output side, version 2 was introduced with EPUB documents as a possible output, and over time is likely to be developed further.
-
-Version 2 introduces a new processing layer, which relies more on the programming language Ruby's objects (and regular expressions), than version 1 does which relies on regular expressions. The thinking behind version 1 use of regular expressions was that it made it more straightforward to switch languages for processing, as many languages support regular expressions; the thinking behind version 2 was version 1 was more complicated than it need be, and since Ruby was the language used, why not make programming more straightforward, as it would be easier to develop further.
-
-Version 1 was removed with the introduction of the version 3 development branch
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_filetypes.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_filetypes.sst
deleted file mode 100644
index d36acac0..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_filetypes.sst
+++ /dev/null
@@ -1,143 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: Filetypes
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: SiSU:manual:filetypes;electronic documents:SiSU:manual:filetypes
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-1~filetypes SiSU filetypes
-
-SiSU has plaintext and binary filetypes, and can process either type of document.
-
-2~ .sst .ssm .ssi marked up plain text
-
-SiSU documents are prepared as plain-text (utf-8) files with SiSU markup. They may make reference to and contain images (for example), which are stored in the directory beneath them _sisu/image. SiSU plaintext markup files are of three types that may be distinguished by the file extension used: regular text .sst; master documents, composite documents that incorporate other text, which can be any regular text or text insert; and inserts the contents of which are like regular text except these are marked .ssi and are not processed.
-
-SiSU processing can be done directly against a sisu documents; which may be located locally or on a remote server for which a url is provided.
-
-SiSU source markup can be shared with the command:
-
-_1 sisu -s [filename]
-
-3~ sisu text - regular files (.sst)
-
-The most common form of document in SiSU, see the section on SiSU markup.
-
-3~ sisu master files (.ssm)
-
-Composite documents which incorporate other SiSU documents which may be either regular SiSU text .sst which may be generated independently, or inserts prepared solely for the purpose of being incorporated into one or more master documents.
-
-The mechanism by which master files incorporate other documents is described as one of the headings under under SiSU markup in the SiSU manual.
-
-Note: Master documents may be prepared in a similar way to regular documents, and processing will occur normally if a .sst file is renamed .ssm without requiring any other documents; the .ssm marker flags that the document may contain other documents.
-
-Note: a secondary file of the composite document is built prior to processing with the same prefix and the suffix ._sst ~{ .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 processing. It may be however that when the resulting file is shared .ssc is an appropriate suffix to use. }~
-
-3~ sisu insert files (.ssi)
-
-Inserts are documents prepared solely for the purpose of being incorporated into one or more master documents. They resemble regular SiSU text files except they are ignored by the SiSU processor. Making a file a .ssi file is a quick and convenient way of flagging that it is not intended that the file should be processed on its own.
-
-2~ sisupod, zipped binary container (sisupod.zip, .ssp)
-
-A sisupod is a zipped SiSU text file or set of SiSU text files and any associated images that they contain (this will be extended to include sound and multimedia-files)
-
-SiSU plaintext files rely on a recognised directory structure to find contents such as images associated with documents, but all images for example for all documents contained in a directory are located in the sub-directory _sisu/image. Without the ability to create a sisupod it can be inconvenient to manually identify all other files associated with a document. A sisupod automatically bundles all associated files with the document that is turned into a pod.
-
-The structure of the sisupod is such that it may for example contain a single document and its associated images; a master document and its associated documents and anything else; or the zipped contents of a whole directory of prepared SiSU documents.
-
-The command to create a sisupod is:
-
-_1 sisu -S [filename]
-
-Alternatively, make a pod of the contents of a whole directory:
-
-_1 sisu -S
-
-SiSU processing can be done directly against a sisupod; which may be located locally or on a remote server for which a url is provided.
-
-http://www.sisudoc.org/sisu/sisu_commands
-
-http://www.sisudoc.org/sisu/sisu_manual
-
-% 1~alt Experimental Alternative Input Representations
-%
-% 2~ Alternative XML
-%
-% SiSU offers alternative XML input representations of documents as a proof of concept, experimental feature. They are however not strictly maintained, and incomplete and should be handled with care.
-%
-% !_ convert from sst to simple xml representations (sax, dom and node):
-%
-% _1 sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard]
-%
-% _1 sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard]
-%
-% _1 sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard]
-%
-% !_ convert to sst from any sisu xml representation (sax, dom and node):
-%
-% _1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
-%
-% or the same:
-%
-% _1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
-%
-% 3~ XML SAX representation
-%
-% To convert from sst to simple xml (sax) representation:
-%
-% _1 sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard]
-%
-% To convert from any sisu xml representation back to sst
-%
-% _1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
-%
-% or the same:
-%
-% _1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
-%
-% 3~ XML DOM representation
-%
-% To convert from sst to simple xml (dom) representation:
-%
-% _1 sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard]
-%
-% To convert from any sisu xml representation back to sst
-%
-% _1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
-%
-% or the same:
-%
-% _1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
-%
-% 3~ XML Node representation
-%
-% To convert from sst to simple xml (node) representation:
-%
-% _1 sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard]
-%
-% To convert from any sisu xml representation back to sst
-%
-% _1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
-%
-% or the same:
-%
-% _1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]]
-
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_help.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_help.sst
deleted file mode 100644
index 69535085..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_help.sst
+++ /dev/null
@@ -1,77 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: Help
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :published: 2007-08-30
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: SiSU:manual:help;electronic documents:manual:SiSU:help
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? SiSU Help
-
-1~help Help
-
-2~ SiSU Manual
-
-The most up to date information on sisu should be contained in the sisu_manual, available at:
-
-_1 http://sisudoc.org/sisu/sisu_manual/
-
-The manual can be generated from source, found respectively, either within the SiSU tarball
-or installed locally at:
-
-_1 ./data/doc/sisu/markup-samples/sisu_manual
-
-_1 /usr/share/doc/sisu/markup-samples/sisu_manual
-
-move to the respective directory and type e.g.:
-
-_1 sisu sisu_manual.ssm
-
-% The manual pages provided with SiSU are also available online, and there is an interactive help, which is being superseded by the man page, and possibly some document which contains this component.
-
-2~ SiSU man pages *~man
-
-If SiSU is installed on your system usual man commands should be available, try:
-
-_1 man sisu
-
-Most SiSU man pages are generated directly from sisu documents that are used to prepare the sisu manual, the sources files for which are located within the SiSU tarball at:
-
-_1 ./data/doc/sisu/markup-samples/sisu_manual
-
-Once installed, directory equivalent to:
-
-_1 /usr/share/doc/sisu/markup-samples/sisu_manual
-
-Available man pages are converted back to html using man2html:
-
-_1 /usr/share/doc/sisu/html/
-
-_1 ./data/doc/sisu/html
-
-An online version of the sisu man page is available here:
-
-_* {~^ various sisu man pages }http://www.jus.uio.no/sisu/man/
-
-_* {~^ sisu.1 }http://www.jus.uio.no/sisu/man/sisu.1.html
-
-2~ SiSU built-in interactive help, [discontinued]
-
-This fell out of date and has been discontinued.
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_help_sources.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_help_sources.sst
deleted file mode 100644
index bee5ed78..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_help_sources.sst
+++ /dev/null
@@ -1,108 +0,0 @@
-% SiSU insert 4.0
-
-@title: SiSU
- :subtitle: References
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-11-12
- :issued: 2002-11-12
- :available: 2002-11-12
- :published: 2007-09-16
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: SiSU:manual:help sources;electronic documents:SiSU:manual:help sources
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? SiSU Help Sources
-
-1~help_sources Help Sources
-
-2~ man pages
-
-_1 man sisu
-
-_1 man sisu-concordance
-
-_1 man sisu-epub
-
-_1 man sisu-git
-
-_1 man sisu-harvest
-
-_1 man sisu-html
-
-_1 man sisu-odf
-
-_1 man sisu-pdf
-
-_1 man sisu-pg
-
-_1 man sisu-po
-
-_1 man sisu-sqlite
-
-_1 man sisu-txt
-
-_1 man 7 sisu_complete
-
-_1 man 7 sisu_pdf
-
-_1 man 7 sisu_postgresql
-
-_1 man 7 sisu_sqlite
-
-_1 man sisu_termsheet
-
-_1 man sisu_webrick
-
-2~ sisu generated output - links to html
-
-Note SiSU documentation is prepared in SiSU and output is available in multiple formats including amongst others html, pdf, odf and epub, which may be also be accessed via the html pages~{ named index.html or more extensively through sisu_manifest.html }~
-
-3~ www.sisudoc.org
-
-http://sisudoc.org/sisu/sisu_manual/index.html
-
-_1 http://sisudoc.org/sisu/sisu_manual/index.html
-
-2~ man2html
-
-3~ locally installed
-
-file:///usr/share/doc/sisu/html/sisu.1.html
-
-_1 file:///usr/share/doc/sisu/html/sisu.1.html
-
-_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_sqlite.7.html
-
-_1 /usr/share/doc/sisu/html/sisu_webrick.1.html
-
-3~ www.jus.uio.no/sisu
-
-http://www.jus.uio.no/sisu/man/sisu.1.html
-
-_1 http://www.jus.uio.no/sisu/man/sisu.1.html
-
-_1 http://www.jus.uio.no/sisu/man/sisu_complete.7.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_sqlite.7.html
-
-_1 http://www.jus.uio.no/sisu/man/sisu_webrick.1.html
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_homepages.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_homepages.ssi
deleted file mode 100644
index 3d8d95d5..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_homepages.ssi
+++ /dev/null
@@ -1,39 +0,0 @@
-% SiSU insert 2.0
-
-@title: SiSU
- :subtitle: Homepages
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2007-08-28
- :issued: 2007-08-28
- :available: 2007-08-28
- :modified: 2011-02-07
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? @title @creator
-
-:B~? Setting up of homepages
-
-1~home Homepages
-
-SiSU is about the ability to auto-generate documents. Home pages are regarded as custom built items, and are not created by SiSU. More accurately, SiSU has a default home page, which will not be appropriate for use with other sites, and the means to provide your own home page instead in one of two ways as part of a site's configuration, these being:
-
-# through placing your home page and other custom built documents in the subdirectory _sisu/home/ (this probably being the easier and more convenient option)
-
-# through providing what you want as the home page in a skin,
-
-Document sets are contained in directories, usually organised by site or subject. Each directory can/should have its own homepage. See the section on directory structure and organisation of content.
-
-2~ Home page and other custom built pages in a sub-directory
-
-Custom built pages, including the home page index.html may be placed within the configuration directory _sisu/home/ in any of the locations that is searched for the configuration directory, namely ./_sisu ; ~/_sisu ; /etc/sisu
-From there they are copied to the root of the output directory with the command:
-
-_1 sisu -CC
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_how.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_how.ssi
deleted file mode 100644
index 3372bcd4..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_how.ssi
+++ /dev/null
@@ -1,26 +0,0 @@
-% SiSU 2.0
-
-@title: SiSU
- :subtitle: How Does SiSU Work?
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2011-02-07
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? @title @creator
-
-:B~? Description
-
-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).
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_howto.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_howto.sst
deleted file mode 100644
index 4a23bdfe..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_howto.sst
+++ /dev/null
@@ -1,1326 +0,0 @@
-% SiSU insert 4.0
-
-@title: SiSU
- :subtitle: Technical, Howto
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2002-11-12
- :issued: 2002-11-12
- :available: 2002-11-12
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: SiSU:manual:howto;electronic documents:SiSU:manual:howto;SiSU:document:howto;sisu:document:howto
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? SiSU some technical information
-
-:C~ HowTo
-
-1~howto_help Getting Help
-
-An online manual of sorts should be available at:
-
-http://www.jus.uio.no/sisu_manual/
-
-The manual pages provided with SiSU are also available online, and there is an interactive help, which is being superseded by the man page, and possibly some document which contains this component.
-
-2~ SiSU "man" pages *~man
-
-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
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:
-
-_* {~^ various sisu man pages }http://www.jus.uio.no/sisu/man/
-
-_* {~^ sisu.1 }http://www.jus.uio.no/sisu/man/sisu.1.html
-
-_* {~^ sisu.8 }http://www.jus.uio.no/sisu/man/sisu.8.html
-
-_* {~^ sisu_webrick.1 }http://www.jus.uio.no/sisu/man/sisu_webrick.1.html
-
-2~ SiSU built-in help
-
-_1 sisu --help
-
-_1 sisu --help [subject]
-
-_2 sisu --help env [for feedback on the way your system is setup with regard to sisu]
-
-_2 sisu -V [same as above command]
-
-_2 sisu --help commands
-
-_2 sisu --help markup
-
-2~ Command Line with Flags - Batch Processing
-
-Running sisu (alone without any flags, filenames or wildcards) brings up the interactive help, as does any sisu command that is not recognised.
-
-In the data directory run sisu -mh filename or wildcard eg. "sisu -h cisg.sst" or "sisu -h *.{sst,ssm}" to produce html version of all documents.
-
-1~howto_setup Setup, initialisation
-
-2~ initialise output directory
-
-Images, css files for a document directory are copied to their respective locations in the output directory.
-
-while within your document markup/preparation directory, issue the following command
-
-_1 sisu -CC
-
-3~ Use of search functionality, an example using sqlite
-
-SiSU can populate PostgreSQL and Sqlite databases and provides a sample search form for querying these databases.
-
-This note provides an example to get you started and will use sqlite
-
-It is necessary to:
-
-(1) make sure the required dependencies have been installed
-
-(2) have a directory with sisu markup samples that is writable
-
-(3) use sisu to create a database
-
-(4) use sisu tp populate a database
-
-(5) use sisu to start the webrick (httpd) server
-
-(6) use sisu to create a search form
-
-(7) copy the search form to the cgi directory
-
-(8) open up the form in your browser
-
-(9) query the database using the search form
-
-!_ (1) make sure the required dependencies have been installed
-
-if you use Debian, the following command will install the required dependencies
-
-aptitude install sisu-sqlite
-
-!_ (2) have a directory with sisu markup samples that is writable
-
-ideally copy the sisu-examples directory to your home directory (because the directory in which you run this example should be writable)
-
-cp -rv /usr/share/doc/sisu/markup-samples/samples .
-
-you are better off installing the package sisu-markup-samples which will make the following available
-
-cp -rv /usr/share/doc/sisu/markup-samples-non-free/samples .
-
-!_ (3) use sisu to create an sqlite database
-
-within the sisu-examples directory
-
-sisu -dv createall
-
-!_ (4) use sisu tp populate a database with some text
-
-within the sisu-examples directory
-
-sisu -div free_*.sst
-
-or
-
-sisu -dv import free_*.sst debian_constitution_v1.2.sst debian_social_contract_v1.1.sst gpl2.fsf.sst
-
-!_ (5) use sisu to start the webrick (httpd) server (if it has not already been started):
-
-sisu -W
-
-!_ (6) use sisu to create a search form (for use with the webrick server, and your sample documents)
-
-within the sisu-examples directory
-
-sisu -F webserv=webrick
-
-and follow the instructions provided
-
-#here i run into a problem, you are working from a read only
-#directory..., not my usual mode of operation, to complete the example
-#the following is necessary
-sudo touch sisu_sqlite.cgi sisu_pgsql.cgi
-sudo -P chown $USER sisu_sqlite.cgi sisu_pgsql.cgi
-
-#now this should be possible:
-sisu -F webrick
-
-!_ (7) copy the search form to the cgi directory
-
-sisu -F webserv=webrick
-
-and follow the instructions provided
-
-% sudo chmod -v 755 /usr/lib/cgi-bin/sisu_sqlite.cgi
-
-!_ (8) open up the form in your browser and query it
-
-url:
-
-http://localhost:8081/cgi-bin/sisu_sqlite.cgi
-
-or as instructed by command sisu -F webrick
-
-!_ (9) query the database using the search form
-
-if there are other options in the dropdown menu select
-
-document_samples_sisu_markup
-
-and search for some text, e.g.:
-
-aim OR project
-
-_* selecting the *index* radio button gives an index of results using the object numbers
-
-_* selecting the *text* radio button gives the content of the matched paragraphs with the match highlighted
-
-!_ (10) to start again with a new database
-
-to start from scratch you can drop the database with the command
-
-sisu -dv dropall
-
-and go to step 3
-
-to get to step 3 in one step with a single command
-
-sisu -dv recreate
-
-continue subsequent steps
-
-2~ misc
-
-3~ url for output files -u -U
-
-_1 sisu -uv[and other flags] [filename/wildcard]
-
-_1 sisu -Uv [filename/wildcard]
-
-3~ toggle screen color
-
-_1 sisu -cv[and processing flags] [filename/wildcard]
-
-3~ verbose mode
-
-_1 sisu -v[and processing flags] [filename/wildcard]
-
-_1 sisu -V[and processing flags] [filename/wildcard]
-
-3~ quiet mode
-
-_1 sisu -q[and processing flags] [filename/wildcard]
-
-3~ maintenance mode
-intermediate files kept -M
-
-_1 sisu -Mv[and other flags] [filename/wildcard]
-
-3~ start the webrick server
-
-_1 sisu -W
-
-2~ remote placement of output
-
-configuration is necessary
-
-scp
-
-_1 sisu -vr[and processing flags] [filename/wildcard]
-
-rsync
-
-_1 sisu -vR[and processing flags] [filename/wildcard]
-
-1~howto_config Configuration Files
-
-Sample provided, on untarring the source tarball:
-
-_1 conf/sisu/v4/sisurc.yml
-
-_1 conf/sisu/v5/sisurc.yml
-
-and on installation under:
-
-_1 /etc/sisu/v4/sisurc.yml
-
-_1 /etc/sisu/v5/sisurc.yml
-
-The following paths are searched:
-
-_1 ./_sisu/v4/sisurc.yml or ./_sisu/v5/sisurc.yml
-
-_1 ./_sisu/sisurc.yml
-
-_1 ~/.sisu/v4/sisurc.yml or ~/.sisu/v5/sisurc.yml
-
-_1 ~/.sisu/sisurc.yml
-
-_1 /etc/sisu/v4/sisurc.yml /etc/sisu/v5/sisurc.yml
-
-_1 /etc/sisu/sisurc.yml
-
-1~howto_markup Markup
-
-See sample markup provided on
-
-http://www.sisudoc.org/
-
-http://www.jus.uio.no/sisu
-
-http://www.jus.uio.no/sisu_markup
-
-http://www.jus.uio.no/sisu/SiSU
-
-in particular for each of the document output samples provided, the source document is provided as well
-
-http://www.jus.uio.no/sisu/SiSU/examples.html
-
-on untarring the source tarball:
-
-_1 data/doc/sisu/markup-samples
-
-or the same once source is installed (or sisu-examples) under:
-
-_1 /usr/share/doc/sisu/markup-samples/
-
-and if you have sisu-markup-samples installed, under
-
-_1 data/doc/sisu/markup-samples-non-free/
-
-_1 /usr/share/doc/sisu/markup-samples-non-free/
-
-Some notes are contained within the man page, *{man sisu}* and within sisu help via the commands *{sisu help markup}* and *{sisu help headers}*
-
-SiSU is for literary and legal text, also for some social science material. In particular it does not do formula, and is not particularly suited to technical documentation. Despite the latter caveat, some notes will be provided here and added to over time:
-
-2~ Headers
-
-Headers @headername: provide information related to the document, this may relate to
-
-# how it is to be processed, such as whether headings are to be numbered, what skin is to be used and markup instructions, such as the document structure, or words to be made bold within the document
-
-# semantic information about the document including the dublin core
-
-2~ Font Face
-
-Defaults are set. You may change the face to: bold, italics, underscore, strikethrough, ...
-
-3~ Bold
-
-\@bold: [list of words that should be made bold within document]
-
-!_ bold line
-
-\!_ bold line
-
-*{ bold word or sentence }*
-
-!\{ bold word or sentence \}!
-
-*\{ bold word or sentence \}*
-
-*boldword* or !boldword!
-
-\*boldword\* or \!boldword\!
-
-3~ Italics
-
-\@italics: [list of words that should be italicised within document]
-
-/{ italicise word or sentence }/
-
-/\{ italicise word or sentence \}/
-
-/italicisedword/
-
-\/italicisedword\/
-
-3~ Underscore
-
-_{ underscore word or sentence }_
-
-_\{ underscore word or sentence \}_
-
-_underscoreword_
-
-3~ Strikethrough
-
--{ strikethrough word or sentence }-
-
--\{ strikethrough word or sentence \}-
-
--strikeword-
-
-\-strikeword\-
-
-2~ Endnotes
-
-There are two forms of markup for endnotes, they cannot be mixed within the same document
-
-here~{ this is an endnote }~
-
-# preferred endnote markup
-
-here~\{ this is an endnote \}~
-
-# alternative markup equivalent, kept because it is possible to search and replace to get markup in existing texts such as Project Gutenberg
-
-here\~^
-
-^\~ this is an endote
-
-2~ Links
-
-{ SiSU }http://www.sisudoc.org
-
-code{
-
-{ SiSU }http://www.sisudoc.org
-
-}code
-
-{sisu.png }http://www.sisudoc.org
-
-code{
-
-{sisu.png }http://www.sisudoc.org
-
-}code
-
-{tux.png 64x80 }image
-
-code{
-
-{ tux.png 64x80 }image
-
-}code
-
-{~^ SiSU }http://www.sisudoc.org
-
-code{
-
-{~^ SiSU }http://www.sisudoc.org
-
-}code
-
-is equivalent to:
-
-code{
-
-{ SiSU }http://www.sisudoc.org ~{ http://www.sisudoc.org }~
-
-}code
-
-the same can be done with an image:
-
-{~^ sisu.png "SiSU" }http://www.sisudoc.org
-
-code{
-
-{~^ sisu.png "SiSU" }http://www.sisudoc.org
-
-}code
-
-2~ Number Titles
-
-Set with the header @markup:
-
-2~ Line operations
-
-Line Operations (marker placed at start of line)
-
-\!_ bold line
-
-!_ bold line
-
-\_1 indent paragraph one level
-
-_1 indent paragraph one level
-
-\_2 indent paragraph two steps
-
-_2 indent paragraph two steps
-
-\_* bullet paragraph
-
-_* bullet paragraph
-
-\# number paragraph (see headers for numbering document headings)
-
-# number paragraph (see headers for numbering document headings)
-
-\_# number paragraph level 2 (see headers for numbering document headings)
-
-_# number paragraph level 2 (see headers for numbering document headings)
-
-2~ Tables
-
-Table markup sample
-
-code{
-
-table{~h c3; 26; 32; 32;
-
-This is a table, column1
-this would become row one of column two
-column three of row one is here
-
-column one row 2
-column two of row two
-column three of row two, and so on
-
-column one row three
-and so on
-here
-
-}table
-
-}code
-
-Alternative form of table markup
-
-code{
-
-{t~h}
- |Mon|Tue|Wed|Thu|Fri|Sat|Sun
-0 | * | * | * | * | * | * | *
-1 | * | * | * | * | | |
-2 | - | * | * | * | * | * |
-3 | - | * | * | * | * | * | *
-4 | - | | | * | * | * |
-5 | * | * | * | * | * | * | *
-
-}code
-
-2~ Grouped Text
-
-code{
-
- 5.times { puts 'Ruby' }
-
-}code
-
-code\{
-
-code{
-
- 5.times { puts 'Ruby' }
-
-}code
-
-\}code
-
-poem{
-
-A Limerick
-
-There was a young lady from Clyde,
-who ate a green apple and died,
-but the apple fermented inside the lamented,
-and made cider inside her inside.
-
-}poem
-
-code{
-
-poem{
-
-There was a young lady from Clyde,
-who ate a green apple and died,
-but the apple fermented inside the lamented,
-and made cider inside her inside.
-
-}poem
-
-}code
-
-2~ Composite Document
-
-To import another document, the master document or importing document should be named filename.r3 (r for require)
-
-\<\< \{ filename.sst \}
-
-\<\< \{ filename.ssi \}
-
-1~howto_appearance Change Appearance
-
-2~ Skins
-
-"Skins" are gone in v4 replaced by @make: :header: within a document, and a common shared _sisu/sisu_document_make file (which uses identical parameters to the individual documents @make: :header:)
-
-2~ CSS
-
-The appearance of html and XML related output can be changed for an ouput collection directory by prepareing and placing a new css file in one of the sisu css directories searched in the sisu configuration path. These are located at:
-
-_./_sisu/css
-
-~/.sisu/css
-
-and
-
-/etc/sisu/css
-
-The contents of the first directory found in the search path are copied to the corresponding sisu output directory with the commnd:
-
-sisu -CC
-
-The SiSU standard css files for SiSU output are:
-
-dom.css html.css html_tables.css index.css sax.css xhtml.css
-
-A document may specify its own/bespoke css file using the css header.
-
-\@css:
-
-[expand]
-
-:C~ Extracts from the README
-
-1~howto_readme README
-
-SiSU 0.55 2007w27/6 2007-07-07
-
-Homepage: http://www.sisudoc.org
-
-old homepage: http://www.jus.uio.no/sisu
-
-!_ Description
-
-SiSU is lightweight markup based document creation and publishing framework that is controlled from the command line. Prepare documents for SiSU using your text editor of choice, then use SiSU to generate various output document formats.
-
-With minimal preparation of a plain-text (UTF-8) file using its native markup-syntax, SiSU produces: plain-text, HTML, XHTML, EPUB, XML, ODF:ODT (Opendocument), LaTeX, PDF, and populates an SQL database (PostgreSQL or SQLite) in paragraph sized chunks so that document searches are done at this "atomic" level of granularity.
-
-Outputs share a common citation numbering system, and any semantic meta-data provided about the document.
-
-SiSU also provides concordance files, document content certificates and manifests of generated output.
-
-SiSU takes advantage of well established open standard ways of representing text, and provides a bridge to take advantage of the strengths of each, while remaining simple. SiSU implements across document formats a "useful common feature set" [coming from a humanities, law, and possibly social sciences perspective, rather than technical or scientific writing] ... focus is primarily on content and data integrity rather than appearance, (though outputs in the various formats are respectable).
-
-A vim syntax highlighting file and an ftplugin with folds for sisu markup is provided. Vim 7 includes syntax highlighting for SiSU.
-
-man pages, and interactive help are provided.
-
-Dependencies for various features are taken care of in sisu related packages. The package sisu-complete installs the whole of SiSU.
-
-Additional document markup samples are provided in the package sisu-markup-samples which is found in the non-free archive the licenses for the substantive content of the marked up documents provided is that provided by the author or original publisher.
-
-Homepage: http://www.sisudoc.org
-
-old homepage: http://www.jus.uio.no/sisu
-
-SiSU - simple information structuring universe, is a publishing tool, document generation and management, (and search enabling) tool primarily for literary, academic and legal published works.
-
-SiSU can be used for Internet, Intranet, local filesystem or cd publishing.
-
-SiSU can be used directly off the filesystem, or from a database.
-
-SiSU's scalability, is dependent on your hardware, and filesystem, and/or database Postgresql.
-
-Amongst it's characteristics are:
-
-_* simple mnemonoic markup style,
-
-_* the ability to produce multiple output formats, including html, structured XML, LaTeX, pdf (via LaTeX), stream to a relational database whilst retaining document structure - Postgresql and Sqlite,
-
-_* that all share a common citation system (a simple idea from which much good), possibly most exciting, the following: if fed into a relational database (as it can be automatically), the document set is searchable, with results displayed at a paragraph level, or the possibility of an indexed display of documents in which the match is found together with a hyperlinked listing for each of each paragraph in which the match is found. In any event citations using this system (with or without the relational database) are relevant for all output formats.
-
-_* it is command line driven, and can be set up on a remote server
-
-_* Documents are marked up in SiSU syntax in your favourite editor. SiSU syntax may be regarded as a type of smart ascii - which in its basic form is simpler than the most elementary html. There is currently a syntax highlighter, and folding for Vim. Syntax highlighters for other editors are welcome.
-
-Input files should be UTF-8
-
-Once set up it is simple to use.
-
-2~ Online Information, places to look
-
-http://www.sisudoc.org
-
-http://www.jus.uio.no/sisu
-
-Download Sources:
-
-_1 http://www.jus.uio.no/sisu/SiSU/download.html#current
-
-_1 http://www.jus.uio.no/sisu/SiSU/download.html#debian
-
-2~ Installation
-
-NB. Platform is Unix / Linux.
-
-3~ Debian
-
-If you use Debian use the Debian packages, check the information at:
-
-_1 http://www.jus.uio.no/sisu/SiSU/download.html#debian
-
-(A) SiSU is available directly off the Debian archives for Sid and testing. It
-should necessary only to run as root:
-
-_1 aptitude update
-
-_1 aptitude install sisu-complete
-
-(B) If there are newer versions of SiSU upstream of the Debian archives, they
-will be available by adding the following to your /etc/apt/sources.list
-
-_1 deb http://www.jus.uio.no/sisu/archive unstable main non-free
-
-_1 deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
-
-[the non-free line is for document markup samples, for which the substantive text is provided under the author or original publisher's license and which in most cases will not be debian free software guideline compliant]
-
-Then as root run:
-
-_1 aptitude update
-
-_1 aptitude install sisu-complete
-
-3~ RPM
-
-RPMs are provided though untested, they are prepared by running alien against the source package, and against the debs.
-
-They may be downloaded from:
-
-_1 http://www.jus.uio.no/sisu/SiSU/download.html#rpm
-
-3~ Source package .tgz
-
-Otherwise to install SiSU from source, check information at:
-
-_1 http://www.jus.uio.no/sisu/SiSU/download.html#current
-
-alternative modes of installation from source are provided, setup.rb (by Minero Aoki), rake (by Jim Weirich) built install file, rant (by Stefan Lang) built install file,
-
-Ruby is the essential dependency for the basic operation of SiSU
-
-1. Download the latest source (information available) from:
-
-_1 http://www.jus.uio.no/sisu/SiSU/download.html#current
-
-2. Unpack the source
-
-Note however, that additional external package dependencies, such as texlive or postgresql should you desire to use it are not taken care of for you.
-
-3~ to use setup.rb
-
-this is a three step process, in the root directory of the unpacked SiSU as root type:
-
-_1 ruby setup.rb config
-
-_1 ruby setup.rb setup
-
-as root:
-
-_1 ruby setup.rb install
-
-further information:
-
-_1 http://i.loveruby.net/en/projects/setup/
-
-_1 http://i.loveruby.net/en/projects/setup/doc/usage.html
-
-3~ to use install (prapared with "Rake")
-
-Rake must be installed on your system:
-
-_1 http://rake.rubyforge.org/
-
-_1 http://rubyforge.org/frs/?group_id=50
-
-in the root directory of the unpacked SiSU as root type:
-
-_1 rake
-
-or
-
-_1 rake base
-
-This makes use of Rake (by Jim Weirich) and the provided Rakefile
-
-For a list of alternative actions you may type:
-
-_1 rake help
-
-_1 rake -T
-
-3~ to use install (prapared with "Rant")
-
-(you may use the instructions above for rake substituting rant if rant is
-installed on your system, or you may use an independent installer created using
-rant as follows:)
-
-in the root directory of the unpacked SiSU as root type:
-
-_1 ruby ./sisu-install
-
-or
-
-_1 ruby ./sisu-install base
-
-This makes use of Rant (by Stefan Lang) and the provided Rantfile. It has been configured to do post installation setup setup configuration and generation of first test file. Note however, that additional external package dependencies, such as tetex-extra are not taken care of for you.
-
-further information:
-
-_1 http://make.rubyforge.org/
-
-_1 http://rubyforge.org/frs/?group_id=615
-
-For a list of alternative actions you may type:
-
-_1 ruby ./sisu-install help
-
-_1 ruby ./sisu-install -T
-
-2~ Dependencies
-
-Once installed see 'man 8 sisu' for some information on additional programs that sisu makes use of, and that you may need or wish to install. (this will depend on such factors as whether you want to generate pdf, whether you will be using SiSU with or without a database, ...) 'man sisu-markup-samples' may also be of interest if the sisu-markup-samples package has also been installed.
-
-The information in man 8 may not be most up to date, and it is possible that more useful information can be gleaned from the following notes taken from the Debian control file (end edited), gives an idea of additional packages that SiSU can make use of if available, (the use/requirement of some of which are interdependent for specific actions by SiSU).
-
-The following is from the debian/control file of sisu-3.0.2, which amongst other things provides the dependencies of sisu within Debian.
-
-code{
-
-Source: sisu
-Section: text
-Priority: optional
-Maintainer: SiSU Project
-Uploaders: Ralph Amissah
-Build-Depends: debhelper (>= 8)
-Standards-Version: 3.9.1
-Homepage: http://www.sisudoc.org/
-Vcs-Browser: http://git.sisudoc.org/?p=code/sisu.git
-Vcs-Git: git://git.sisudoc.org/git/code/sisu.git
-XS-Dm-Upload-Allowed: yes
-
-}code
-
-code{
-
-Package: sisu
-Architecture: all
-Depends: ${misc:Depends}, ruby (>= 1.8.2), libwebrick-ruby, rsync, unzip, zip
-Recommends:
- sisu-pdf, sisu-sqlite, sisu-postgresql, imagemagick, keychain, librmagick-ruby,
- librexml-ruby, openssl, openssh-client | lsh-client, tidy, vim-addon-manager
-Suggests: lv, calibre, pinfo, texinfo, trang
-Conflicts: sisu-markup-samples (<= 1.0.11)
-Replaces: sisu-markup-samples (<= 1.0.11)
-Description: documents - structuring, publishing in multiple formats and search
- SiSU is a lightweight markup based, command line oriented, document
- structuring, publishing and search framework for document collections.
- .
- With minimal preparation of a plain-text, (UTF-8) file, using its native
- markup syntax in your text editor of choice, SiSU can generate various
- document formats (most of which share a common object numbering system for
- locating content), including plain text, HTML, XHTML, XML, EPUB, OpenDocument
- text (ODF:ODT), LaTeX, PDF files, and populate an SQL database with objects
- (roughly paragraph-sized chunks) so searches may be performed and matches
- returned with that degree of granularity: your search criteria is met by these
- documents and at these locations within each document. Object numbering 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. Document outputs also share semantic meta-data
- provided.
- .
- SiSU also provides concordance files, document content certificates and
- manifests of generated output.
- .
- A vim syntax highlighting file and an ftplugin with folds for sisu markup is
- provided, as are syntax highlighting files for kate, kwrite, gedit and
- diakonos. Vim 7 includes syntax highlighting for SiSU.
- .
- man pages, and interactive help are provided.
- .
- Dependencies for various features are taken care of in sisu related packages.
- The package sisu-complete installs the whole of SiSU.
- .
- Additional document markup samples are provided in the package
- sisu-markup-samples which is found in the non-free archive the licenses for
- the substantive content of the marked up documents provided is that provided
- by the author or original publisher.
-
-}code
-
-code{
-
-Package: sisu-complete
-Architecture: all
-Depends:
- ${misc:Depends}, ruby (>= 1.8.2), sisu (= ${source:Version}),
- sisu-pdf (= ${source:Version}), sisu-postgresql (= ${source:Version}),
- sisu-sqlite (= ${source:Version})
-Description: installs all SiSU related packages
- SiSU is a lightweight markup based document structuring, publishing and search
- framework for document collections.
- .
- This package installs SiSU and related packages that enable sisu to produce
- pdf and to populate PostgreSQL and sqlite databases.
- .
- See sisu for a description of the package.
-
-}code
-
-code{
-
-Package: sisu-pdf
-Architecture: all
-Depends:
- ${misc:Depends}, sisu, texlive-latex-base, texlive-fonts-recommended,
- texlive-latex-recommended, texlive-latex-extra, texlive-xetex, lmodern,
- ttf-liberation
-Suggests: evince | pdf-viewer
-Description: dependencies to convert SiSU LaTeX output to pdf
- SiSU is a lightweight markup based document structuring, publishing and search
- framework for document collections.
- .
- This package enables the conversion of SiSU LaTeX output to pdf.
-
-}code
-
-code{
-
-Package: sisu-pdf
-Architecture: all
-Depends:
- ${misc:Depends}, sisu, texlive-latex-base, texlive-fonts-recommended,
- texlive-latex-recommended, texlive-latex-extra, texlive-xetex, lmodern,
- ttf-liberation
-Suggests: evince | pdf-viewer
-Description: dependencies to convert SiSU LaTeX output to pdf
- SiSU is a lightweight markup based document structuring, publishing and search
- framework for document collections.
- .
- This package enables the conversion of SiSU LaTeX output to pdf.
-
-}code
-
-code{
-
-Package: sisu-postgresql
-Architecture: all
-Depends:
- ${misc:Depends}, sisu, libdbd-pg-ruby, libdbd-pg-ruby1.8, libdbi-ruby,
- libdbi-ruby1.8, libdbm-ruby, postgresql, libfcgi-ruby1.8 | libfcgi-ruby1.9.1
-Suggests: postgresql-contrib
-Description: SiSU dependencies for use with PostgreSQL database
- SiSU is a lightweight markup based document structuring, publishing and search
- framework for document collections.
- .
- This package enables SiSU to populate a PostgreSQL database. This is done at
- an object/paragraph level, making granular searches of documents possible.
- .
- This relational database feature of SiSU is not required but provides
- interesting possibilities, including that of granular searches of documents
- for matching units of text, primarily paragraphs that can be displayed or
- identified by object citation number, from which an index of documents
- matched and each matched paragraph within them can be displayed.
-
-}code
-
-code{
-
-Package: sisu-sqlite
-Architecture: all
-Depends:
- ${misc:Depends}, sisu, sqlite3, libsqlite3-ruby, libdbd-sqlite3-ruby,
- libdbd-sqlite3-ruby1.8, libdbi-ruby, libdbi-ruby1.8, libdbm-ruby,
- libfcgi-ruby1.8 | libfcgi-ruby1.9.1
-Description: SiSU dependencies for use with SQLite database
- SiSU is a lightweight markup based document structuring, publishing and search
- framework for document collections.
- .
- This package enables SiSU to populate an SQLite database. This is done at an
- object/paragraph level, making granular searches of documents possible.
- .
- This relational database feature of SiSU is not required but provides
- interesting possibilities, including that of granular searches of documents
- for matching units of text, primarily paragraphs that can be displayed or
- identified by object citation number, from which an index of documents
- matched and each matched paragraph within them can be displayed.
-
-}code
-
-2~ Quick start
-
-Most of the installation should be taken care of by the aptitude or rant
-install. (The rant install if run in full will also test run the generation of
-the first document).
-
-After installation of sisu-complete, move to the document samples directory
-
-_1 cd /usr/share/doc/sisu/markup-samples/samples
-
-and run
-
-_1 sisu -3 free_as_in_freedom.rms_and_free_software.sam_williams.sst
-
-or the same:
-
-_1 sisu -NhwpoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst
-
-look at output results, see the "sisu_manifest" page created for the document
-
-or to generate an online document move to a writable directory, as the file will be downloaded there and e.g.
-
-sisu -3 http://www.jus.uio.no/sisu/src/free_culture.lawrence_lessig.sst
-
-the database stuff is extra perhaps, the latex stuff could be considered extra perhaps but neither needs to be installed for most of sisu output to work
-
-examine source document, vim has syntax support
-
-gvim free_as_in_freedom.rms_and_free_software.sam_williams.sst
-
-additional markup samples in
-
-_1 http://www.jus.uio.no/sisu/SiSU/examples.html
-
-For help
-
-_1 man sisu
-
-or
-
-_1 sisu --help
-
-e.g.
-
-for the way sisu "sees/maps" your system
-
-_1 sisu --help env
-
-for list of commands and so on
-
-_1 sisu --help commands
-
-2~ Configuration files
-
-The default configuration/setup is contained within the program and is altered by configuration settings in /etc/[sisu version]/sisurc.yml or in ~/.sisu/sisurc.yml
-
-_* configuration file - a yaml file
-
-_1 /etc/sisu/[sisu version]/sisurc.yml
-
-_1 ~/.sisu/sisurc.yml
-
-_* directory structure - setting up of output and working directory.
-
-_* additional software - eg. Tex and LaTeX (tetex, tetex-base, tetex-extra on Debian), Postgresql, [sqlite], trang, tidy, makeinfo, ... none of which are required for basic html or XML processing.
-
-_* if you use Vim as editor there is a syntax highlighter and fold resource config file for SiSU. I hope more syntax highlighters follow.
-
-There are post installation steps (which are really part of the overall installation)
-
-sisu -C in your marked up document directory, should do some auto-configuring provided you have the right permissions for the output directories. (and provided the output directories have already been specified if you are not using the defaults).
-
-2~ Use General Overview
-
-Documents are marked up in SiSU syntax and kept in an ordinary text editable file, named with the suffix .sst, or .ssm
-
-Marked up SiSU documents are usually kept in a sub-directory of your choosing
-
-use the interactive help and man pages
-
-_1 sisu --help
-
-_1 man sisu
-
-2~ Help
-
-interactive help described below, or man page:
-
-_1 man sisu
-
-_1 man 8 sisu
-
-'man sisu_markup-samples' [if the sisu-markup-samples package is also installed]
-
-Once installed an interactive help is available typing 'sisu' (without) any flags, and select an option:
-
-_1 sisu
-
-alternatively, you could type e.g.
-
-_1 sisu --help commands
-
-_1 sisu --help env
-
-_1 sisu --help headers
-
-_1 sisu --help markup
-
-_1 sisu --help headings
-
-etc.
-
-for questions about mappings, output paths etc.
-
-_1 sisu --help env
-
-_1 sisu --help path
-
-_1 sisu --help directory
-
-2~ Directory Structure
-
-Once installed, type:
-
-_1 sisu --help env
-
-or
-
-_1 sisu -V
-
-2~ Configuration File
-
-The defaults can be changed via SiSU's configure file sisurc.yml which the program expects to find in ./_sisu ~/.sisu or /etc/sisu (searched in that order, stopping on the first one found)
-
-2~ Markup
-
-See man pages.
-
-_1 man sisu
-
-_1 man 8 sisu
-
-Once installed there is some information on SiSU Markup in its help:
-
-_1 sisu --help markup
-
-and
-
-_1 sisu --help headers
-
-Sample marked up document are provided with the download tarball in the directory:
-
-_1 ./data/doc/sisu/markup-samples/
-
-These are installed on the system usually at:
-
-_1 /usr/share/doc/sisu/markup-samples/
-
-More markup samples are available in the package sisu-markup-samples, which if installed should be available at:
-
-_1 /usr/share/doc/sisu/markup-samples-non-free/
-
-Many more are available online off:
-
-_1 http://www.jus.uio.no/sisu/SiSU/examples.html
-
-2~ Additional Things
-
-There is syntax support for some editors provided (together with a README file) in
-
-_1 ./data/sisu/v4/conf/editor-syntax-etc
-
-usually installed to:
-
-_1 /usr/share/sisu/v4/conf/editor-syntax-etc
-
-2~ License
-
-License: GPL 3 or later see the copyright file in
-
-_1 ./data/doc/sisu
-
-usually installed to:
-
-_1 /usr/share/doc/sisu
-
-2~ SiSU Standard
-
-SiSU uses:
-
-_* Standard SiSU markup syntax,
-
-_* Standard SiSU meta-markup syntax, and the
-
-_* Standard SiSU object citation numbering and system
-
-© Ralph Amissah 1997, current 2006 All Rights Reserved.
-
-_* however note the License section
-
-CHANGELOG
-
-_1 ./CHANGELOG
-
-and see
-
-_1 http://www.jus.uio.no/sisu/SiSU/changelog.html
-
-_1 http://www.jus.uio.no/sisu/SiSU/changelog_markup_samples.html
-
-:C~ Extracts from man 8 sisu
-
-1~howto_setup_post_installation Post Installation Setup
-
-2~ Post Installation Setup - Quick start
-
-After installation of sisu-complete, move to the document samples directory,
-
-_1 cd /usr/share/doc/sisu/markup-samples/samples
-
-[this is not where you would normally work but provides sample documents for
-testing, you may prefer instead to copy the contents of that directory to a local
-directory before proceeding]
-
-and in that directory, initialise the output directory with the command
-
-_1 sisu -CC
-
-then run:
-
-_1 sisu -1 free_as_in_freedom.rms_and_free_software.sam_williams.sst
-
-or the same:
-
-_1 sisu -NhwpoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst
-
-look at output results, see the "sisu_manifest" page created for the document
-
-for an overview of your current sisu setup, type:
-
-_1 sisu --help env
-
-or
-
-_1 sisu -V
-
-To generate a document from a remote url accessible location move to a writable directory, (create a work directory and cd into it) as the file will be downloaded there and e.g.
-
-_1 sisu -1 http://www.jus.uio.no/sisu/src/gpl.fsf.sst
-
-_1 sisu -3 http://www.jus.uio.no/sisu/src/free_culture.lawrence_lessig.sst
-
-examine source document, vim has syntax highlighting support
-
-gvim free_as_in_freedom.rms_and_free_software.sam_williams.sst
-
-additional markup samples in
-
-_1 http://www.jus.uio.no/sisu/SiSU/examples.html
-
-it should also be possible to run sisu against sisupods (prepared zip files, created by running the command sisu -S [filename]), whether stored locally or remotely.
-
-_1 sisu -3 http://www.jus.uio.no/sisu/pod/free_culture.lawrence_lessig.sst.zip
-
-_1 sisu -3 --trust http://www.jus.uio.no/sisu/pod/free_culture.lawrence_lessig.sst.zip
-
-For help
-
-_1 man sisu
-
-_1 sisu --help
-
-_1 sisu --help env
-for the way sisu "sees/maps" your system
-
-_1 sisu --help commands
-for list of commands and so on
-
-2~ Document markup directory
-
-% B. Generate a (local) document from a markup/work directory.
-
-Perhaps the easiest way to begin is to create a directory for sisu marked up documents within your home directory, and copy the file structure (and document samples) provided in the document sample directory:
-
-_1 mkdir ~/sisu_test
-
-_1 cd ~/sisu_test
-
-_1 cp -a /usr/share/doc/sisu/markup-samples/samples/* ~/sisu_test/.
-
-better if you have installed sisu-markup-samples
-
-_1 cp -a /usr/share/doc/sisu/markup-samples-non-free/samples/* ~/sisu_test/.
-
-% !_ Tip:
-% the markup syntax examples may be of interest
-%
-% _1 http://www.jus.uio.no/sisu/sample/
-
-!_ Tip:
-
-_1 sisu -U [sisu markup filename]
-
-should printout the different possible outputs and where sisu would place them.
-
-!_ Tip:
-if you want to toggle ansi color add
-
-_1 c
-
-to your flags.
-
-3~ Configuration files
-
-SiSU configuration file search path is:
-
-_1 ./_sisu/sisurc.yaml
-
-_1 ~/.sisu/sisurc.yaml
-
-_1 /etc/sisu/sisurc.yaml
-
-.\"%% Debian Installation Note
-
-3~ Debian INSTALLATION Note
-
-It is best you see
-
-_1 http://www.jus.uio.no/sisu/SiSU/download.html#debian
-
-for up the most up to date information.
-
-notes taken from the Debian control file (end edited), gives an idea of additional packages that SiSU can make use of if available, (the use/requirement of some of which are interdependent for specific actions by SiSU):
-
-Package: sisu
-
-SiSU is a lightweight markup based, command line oriented, document structuring, publishing and search framework for document collections.
-
-With minimal preparation of a plain-text, (UTF-8) file, using its native markup syntax in your text editor of choice, SiSU can generate various document formats (most of which share a common object numbering system for locating content), including plain text, HTML, XHTML, XML, OpenDocument text (ODF:ODT), EPUB, LaTeX, PDF files, and populate an SQL database with objects (roughly paragraph-sized chunks) so searches may be performed and matches returned with that degree of granularity: your search criteria is met by these documents and at these locations within each document. Object numbering 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. Document outputs also share semantic meta-data provided.
-
-SiSU also provides concordance files, document content certificates and manifests of generated output.
-
-A vim syntax highlighting file and an ftplugin with folds for sisu markup is provided, as are syntax highlighting files for kate, kwrite, gedit and diakonos. Vim 7 includes syntax highlighting for SiSU.
-
-man pages, and interactive help are provided.
-
-Dependencies for various features are taken care of in sisu related packages. The package sisu-complete installs the whole of SiSU.
-
-Additional document markup samples are provided in the package sisu-markup-samples which is found in the non-free archive the licenses for the substantive content of the marked up documents provided is that provided by the author or original publisher.
-
-Homepage: http://www.sisudoc.org
-
-old homepage: http://www.jus.uio.no/sisu
-
-3~ Document Resource Configuration
-
-!_ sisu
-resource configuration information is obtained from sources (where they exist):
-
-_1 ~/.sisu/sisurc.yaml
-
-_1 /etc/sisu/[sisu version]/sisurc.yaml
-
-_1 sisu program defaults
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_installation.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_installation.ssi
deleted file mode 100644
index f908bb6e..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_installation.ssi
+++ /dev/null
@@ -1,368 +0,0 @@
-% SiSU insert 2.0
-
-@title: SiSU
- :subtitle: Installation
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2002-11-12
- :issued: 2002-11-12
- :available: 2002-11-12
- :modified: 2011-02-07
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? SiSU Installation notes
-
-:C~ Installation
-
-1~installation Installation
-
-See the {~^ download pages }http://www.jus.uio.no/sisu/SiSU/download.html for information related to installation.
-
-2~ Debian
-
-SiSU is developed on Debian, and packages are available for Debian that take care of the dependencies encountered on installation.
-
-The package is divided into the following components:
-
-_1 *sisu*, the base code, (the main package on which the others depend), without any dependencies other than ruby (and for convenience the ruby webrick web server), this generates a number of types of output on its own, other packages provide additional functionality, and have their dependencies
-
-_1 *sisu-complete*, a dummy package that installs the whole of greater sisu as described below, apart from sisu-examples
-
-_1 *sisu-pdf*, dependencies used by sisu to produce pdf from LaTeX generated
-
-_1 *sisu-postgresql*, dependencies used by sisu to populate postgresql database (further configuration is necessary)
-
-_1 *sisu-remote*, dependencies used to place sisu output on a remote server (further configuration is necessary)
-
-_1 *sisu-sqlite*, dependencies used by sisu to populate sqlite database
-
-_1 *sisu-markup-samples*, sisu markup samples and other miscellany (under Debian Free Software Guidelines non-free)
-
-SiSU is available off { Debian Unstable and Testing }http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&subword=1&version=all&release=all&keywords=sisu&sourceid=mozilla-search ~{ http://packages.qa.debian.org/s/sisu.html }~ install it using apt-get, aptitude or alternative Debian install tools. SiSU is currently comprised of eight packages. *~apt-get
-
-Initial packaging is done here and to get the latest version of SiSU available you may add the following line(s) to your sources list: *~sources.list
-
-code{
-
-#/etc/apt/sources.list
-
-deb http://www.jus.uio.no/sisu/archive unstable main non-free
-deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
-
-}code
-
-The non-free section is for sisu markup samples provided, which contain authored works the substantive text of which cannot be changed, and which as a result do not meet the debian free software guidelines.
-
-On Debian there is little more to know beyond how to install software on Debian using apt, aptitude or synaptic.
-
-code{
-
-#Using aptitude:
-
- aptitude update
-
- aptitude install sisu-complete sisu-markup-samples
-
-}code
-
-code{
-
-Using apt-get
-
- apt-get update
-
- apt get install sisu-complete sisu-examples
-
-}code
-
-2~ Other Unix / Linux
-
-A source tarball or an rpms built using alien are available, (however dependencies have not been tested). SiSU is first packaged and tested with dependency handling for Debian.~{ Notes on dependencies are provided in the section that follows }~ Information on dependencies configured for Debian is provided as this may be of assistance.
-
-3~ source tarball
-
-!_ installation with provided install script
-
-To install SiSU, in the root directory of the unpacked SiSU _{as root type}_:~{ This makes use of rant and the provided Rantfile. Note however, that additional external package dependencies, such as tetex-extra are not taken care of for you. }~
-
-_1 ruby install
-
-Once installed see man 8 sisu for information on additional programs that sisu makes use of.
-
-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/
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/
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
-
-To install as root type:
-
-_1 ruby install
-
-For a minimal install type:
-
-_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
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
-
-!_ installation of rpm
-
-The RPM is generated from the source file using Alien.~{ http://www.kitenet.net/programs/alien/ }~ Dependencies are not handled, not even that of the essential Ruby.
-
-1~install_dependencies_and_notes SiSU Components, Dependencies and Notes
-
-The dependency lists are from the Debian control file for SiSU version 0.36, and may assist in building SiSU on other distributions.
-
-2~ sisu
-
-_* the base code, (the main package on which the others depend), without any dependencies other than ruby (and for convenience the ruby webrick web server), this generates a number of types of output on its own, other packages provide additional functionality, and have their dependencies
-
-*Depends:* on ruby (>=1.8.2), libwebrick-ruby
-
-*Recommends:* sisu-pdf, sisu-sqlite, sisu-postgresql, sisu-examples, librmagick-ruby, trang, tidy, libtidy, librexml-ruby, zip, unzip, openssl
-
-initialise directory
-
-_1 sisu -CC
-
-html
-
-_1 sisu -hv [filename/wildcard]
-
-_1 sisu -Hv [filename/wildcard]
-
-LaTeX (but sisu-pdf dependencies required to convert that to pdf)
-
-_1 sisu -pv [filename/wildcard]
-
-plain text Unix with footnotes
-
-_1 sisu -av [filename/wildcard]
-
-plain text Dos with footnotes
-
-_1 sisu -Av [filename/wildcard]
-
-plain text Unix with endnotes
-
-_1 sisu -ev [filename/wildcard]
-
-plain text Dos with endnotes
-
-_1 sisu -Ev [filename/wildcard]
-
-openoffice odt
-
-_1 sisu -ov [filename/wildcard]
-
-xhtml
-
-_1 sisu -bv [filename/wildcard]
-
-XML SAX
-
-_1 sisu -xv [filename/wildcard]
-
-XML DOM
-
-_1 sisu -Xv [filename/wildcard]
-
-wordmap (a rudimentary index of content)
-
-_1 sisu -wv [filename/wildcard]
-
-document content certificate
-
-_1 sisu -Nv [filename/wildcard]
-
-placement of sourcefile in output directory
-
-_1 sisu -sv [filename/wildcard]
-
-creation of source tarball with images, and placement of source tarball in ouput directory
-
-_1 sisu -Sv [filename/wildcard]
-
-manifest of output produced (polls output directory and provides links to existing output)
-
-_1 sisu -yv [filename/wildcard]
-
-url for output files -u -U
-
-_1 sisu -uv[and other flags] [filename/wildcard]
-
-_1 sisu -Uv [filename/wildcard]
-
-toggle screen colour
-
-_1 sisu -cv[and processing flags] [filename/wildcard]
-
-verbose mode
-
-_1 sisu -v[and processing flags] [filename/wildcard]
-
-_1 sisu -V[and processing flags] [filename/wildcard]
-
-quiet mode
-
-_1 sisu -q[and processing flags] [filename/wildcard]
-
-maintenance mode, intermediate files kept -M
-
-_1 sisu -Mv[and other flags] [filename/wildcard]
-
-[the -v is for verbose]
-
-start the webrick server
-
-_1 sisu -W
-
-2~ sisu-complete
-
-_* a dummy package that installs the whole SiSU, apart from sisu-examples
-
-*Depends:* ruby (>=1.8.2), sisu, sisu-pdf, sisu-postgresql, sisu-remote, sisu-sqlite
-
-*Recommends:* sisu-examples
-
-2~ sisu-examples
-
-_* installs sisu markup samples and other miscelleny
-
-*Depends:* sisu
-
-2~ sisu-pdf
-
-_* dependencies used by sisu to produce pdf from LaTeX generated
-
-*Depends:* sisu, tetex-bin, tetex-extra, latex-ucs
-
-*Suggests:* evince, xpdf
-
-converts sisu LaTeX produced to pdf
-
-_1 sisu -pv [filename/wildcard]
-
-[the -v is for verbose]
-
-2~ sisu-postgresql
-
-_* dependencies used by sisu to populate postgresql database (further configuration is necessary)
-
-*Depends:* sisu, postgresql-8.1, libdbi-ruby, libdbm-ruby, libdbd-pg-ruby
-
-*Suggests:* pgaccess, libdbd-pgsql, postgresql-contrib-8.1
-
-installs dependencies for sisu to work with and populate postgresql database
-
-create database
-
-_1 sisu -Dv createall
-
-drop database
-
-_1 sisu -Dv dropall
-
-import content
-
-_1 sisu -Div [filename/wildcard]
-
-_1 sisu -Dv import [filename/wildcard]
-
-update content
-
-_1 sisu -Duv [filename/wildcard]
-
-_1 sisu -Dv update [filename/wildcard]
-
-[the -v is for verbose]
-
-The following are available without installation of the sisu-postgresql component, but are of interest in this context
-
-generate a sample database query form for use with webserver on port 80
-
-_1 sisu -F
-
-or for use with webrick server
-
-_1 sisu -F webrick
-
-to start webrick server
-
-_1 sisu -W
-
-2~ sisu-remote
-
-_* dependencies used to place sisu output on a remote server (further configuration is necessary)
-
-scp
-
-_1 sisu -vr[and processing flags] [filename/wildcard]
-
-rsync
-
-_1 sisu -vR[and processing flags] [filename/wildcard]
-
-[the -v is for verbose]
-
-*Depends:* sisu, rsync, openssh-client|lsh-client, keychain
-
-2~ sisu-sqlite
-
-_* dependencies used by sisu to populate sqlite database
-
-*Depends:* sisu, sqlite, libdbi-ruby, libdbm-ruby, libdbd-sqlite-ruby
-
-*Suggests:* libdbd-sqlite
-
-installs dependencies for sisu to work with and populate sqlite database
-
-create database
-
-_1 sisu -dv createall
-
-drop database
-
-_1 sisu -dv dropall
-
-update content
-
-_1 sisu -div [filename/wildcard]
-
-_1 sisu -dv import [filename/wildcard]
-
-update content
-
-_1 sisu -duv [filename/wildcard]
-
-_1 sisu -dv update [filename/wildcard]
-
-[the -v is for verbose]
-
-The following are available without installation of the sisu-sqlite component, but are of interest in this context
-
-generate a sample database query form for use with webserver on port 80
-
-_1 sisu -F
-
-or for use with webrick server
-
-_1 sisu -F webrick
-
-to start webrick server
-
-_1 sisu -W
-
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_interesting_to_whom.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_interesting_to_whom.ssi
deleted file mode 100644
index 750c46ea..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_interesting_to_whom.ssi
+++ /dev/null
@@ -1,32 +0,0 @@
-% SiSU 2.0
-
-@title: SiSU
- :subtitle: Who Might Be Interested?
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :published: 2007-09-16
- :modified: 2011-02-07
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? @title @creator
-
-:B~? Who might SiSU interest?
-
-1~sisu_interest Who might be interested in the SiSU feature set?
-
-SiSU is most likely to be of interest to people who are working with medium to large volumes of published texts that would like to have the presented in a uniform way that is searchable (either using sisu database integration or an appropriate indexing tool), with the possibility of multiple alternative output formats that may be added to and upgraded/updated over time. SiSU should be of interest to institutions/ organisations/ governments/ individuals with document collections and some technical knowhow that are interested in:
-
-_* long term maintenance and reducing downstream/future costs of maintaining those document sets for which SiSU is suited.
-
-_* the ability to output multiple standard format outputs for various purposes.
-
-_* the implications for search offered
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_introduction.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_introduction.sst
deleted file mode 100644
index 8978ace6..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_introduction.sst
+++ /dev/null
@@ -1,55 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: Introduction
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2011
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? What is SiSU?
-
-:C~? Description
-
-1~sisu_intro Introduction - What is SiSU?
-
-SiSU is a framework for document structuring, publishing (in multiple open standard formats) 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 (including the population of sql databases) 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 (GPLv3). Its use case for development is work with medium to large document sets and cope with evolving document formats/ representation technologies. Documents are prepared once, and generated as need be to update the technical presentation or add additional output formats. Various output formats (including search related output) share a common mechanism for cross-output-format citation.
-
-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, EPUB, ODT (Open Document Format text), LaTeX, landscape and portrait PDF, 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.
-
-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 (to take advantage of the strengths of different ways of representing documents) various standard open output formats including plain text, HTML, XHTML, XML, EPUB, ODT, 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, 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. }~ the different forms of output requested.
-
-SiSU works with an abstraction of the document based on its structure which is comprised of its headings~{ the different heading levels }~ and objects~{ units of text, primarily paragraphs and headings, also any tables, poems, code-blocks }~, 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 basis for citing material within a document across the different output format types. This is significant as page numbers are not well suited to the digital age, in web publishing, changing a browser's default font or using a different browser can mean that text will appear on a different page; and publishing in different formats, html, landscape and portrait pdf etc. again page numbers are not useful to cite text. Dealing with documents at an object level together with object numbering also has implications for search that SiSU is able to take advantage of.
-
-One of the challenges of maintaining documents is to keep them in a format that allows use of them independently of proprietary platforms. Consider issues related to 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 producing documents in multiple non-proprietary open formats including HTML, EPUB,~{ An open standard format for e-books }~ ODT,~{ Open Document Format (ODF) text }~ PDF~{ Specification submitted by Adobe to ISO to become a full open ISO specification
http://www.linux-watch.com/news/NS7542722606.html }~ ODF,~{ ISO standard 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 GPLv3 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 when it became an ISO standard for office applications and the archival of documents), EPUB was introduced in 2009; and allows the technical representations 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 thesauri, 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.sisudoc.org/
-
-http://www.jus.uio.no/sisu
-
-% SiSU is a way of preparing, publishing, managing and searching documents.
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_manual.ssm b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_manual.ssm
deleted file mode 100644
index 90e8a323..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_manual.ssm
+++ /dev/null
@@ -1,96 +0,0 @@
-% SiSU master 4.0
-
-@title: SiSU
- :subtitle: Manual
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2008-07-21
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: SiSU:manual;electronic documents:SiSU:manual
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~ @title @creator
-
-:B~ What is SiSU?
-
-<< sisu_introduction.sst
-
-<< sisu_how.ssi
-
-<< sisu_short_feature_summary.ssi
-
-<< sisu_help.sst
-
-% :B~? SiSU Commands
-
-<< sisu_commands.sst
-
-% :B~? SiSU Markup
-
-<< sisu_markup.sst
-
-<< sisu_filetypes.sst
-
-% :B~? SiSU Configuration
-
-<< sisu_config.ssi
-
-<< sisu_css.ssi
-
-<< sisu_content_directories.ssi
-
-<< sisu_homepages.ssi
-
-% :B~? SiSU Output and Markup Examples
-
-<< sisu_examples.ssi
-
-<< sisu_output_overview.sst
-
-<< sisu_search_intro.ssi
-
-<< sisu_sql.ssi
-
-<< sisu_postgresql.sst
-
-<< sisu_sqlite.sst
-
-<< sisu_search_cgi.ssi
-
-<< sisu_webrick.sst
-
-<< sisu_remote.sst
-
-% :B~? SiSU Download and Installation
-
-<< sisu_download.ssi
-
-<< sisu_installation.ssi
-
-<< sisu_quickstart.sst
-
-% :B~? SiSU Howto and FAQ
-
-<< sisu_howto.sst
-
-<< sisu_faq.sst
-
-<< sisu_interesting_to_whom.ssi
-
-<< sisu_work_needed_and_wishlist.ssi
-
-<< sisu_syntax_highlighting.sst
-
-<< sisu_help_sources.sst
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_markup.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_markup.sst
deleted file mode 100644
index 69293637..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_markup.sst
+++ /dev/null
@@ -1,1312 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: Markup
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :published: 2008-05-22
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: electronic documents:SiSU:document:markup;SiSU:document:markup;SiSU:document:markup;SiSU:manual:markup;electronic documents:SiSU:manual:markup
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? SiSU Markup
-
-1~markup Introduction to SiSU Markup~{ 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. }~
-
-2~ Summary
-
-SiSU source documents are plaintext (UTF-8)~{ files should be prepared using UTF-8 character encoding }~ files
-
-All paragraphs are separated by an empty line.
-
-Markup is comprised of:
-
-_* at the top of a document, the document header made up of semantic meta-data about the document and if desired additional processing instructions (such an instruction to automatically number headings from a particular level down)
-
-_* followed by the prepared substantive text of which the most important single characteristic is the markup of different heading levels, which define the primary outline of the document structure. Markup of substantive text includes:
-
-_1* heading levels defines document structure
-
-_1* text basic attributes, italics, bold etc.
-
-_1* grouped text (objects), which are to be treated differently, such as code blocks or poems.
-
-_1* footnotes/endnotes
-
-_1* linked text and images
-
-_1* paragraph actions, such as indent, bulleted, numbered-lists, etc.
-
-Some interactive help on markup is available, by typing sisu and selecting markup or sisu --help markup
-
-To check the markup in a file:
-
-_1 sisu --identify [filename].sst
-
-For brief descriptive summary of markup history
-
-_1 sisu --query-history
-
-or if for a particular version:
-
-_1 sisu --query-0.38
-
-2~ Markup Examples
-
-3~ Online
-
-Online markup examples are available together with the respective outputs produced from http://www.jus.uio.no/sisu/SiSU/examples.html or from http://www.jus.uio.no/sisu/sisu_examples/
-
-There is of course this document, which provides a cursory overview of sisu markup and the respective output produced: http://www.jus.uio.no/sisu/sisu_markup/
-
-an alternative presentation of markup syntax: /usr/share/doc/sisu/on_markup.txt.gz
-
-3~ Installed
-
-With SiSU installed sample skins may be found in: /usr/share/doc/sisu/markup-samples (or equivalent directory) and if sisu-markup-samples is installed also under: /usr/share/doc/sisu/markup-samples-non-free
-
-1~headers Markup of Headers
-
-Headers contain either: semantic meta-data about a document, which can be used by any output module of the program, or; processing instructions.
-
-Note: the first line of a document may include information on the markup version used in the form of a comment. Comments are a percentage mark at the start of a paragraph (and as the first character in a line of text) followed by a space and the comment:
-
-code{
-
-% this would be a comment
-
-}code
-
-2~ Sample Header
-
-This current document is loaded by a master document that has a header similar to this one:
-
-code{
-
-% SiSU master 4.0
-
-@title: SiSU
- :subtitle: Manual
-
-@creator:
- :author: Amissah, Ralph
-
-@publisher: [publisher name]
-
-@rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3
-
-@classify:
- :topic_register: SiSU:manual;electronic documents:SiSU:manual
- :subject: ebook, epublishing, electronic book, electronic publishing,
- electronic document, electronic citation, data structure,
- citation systems, search
-
-% used_by: manual
-
-@date:
- :published: 2008-05-22
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2010-03-03
-
-@make:
- :num_top: 1
- :breaks: new=C; break=1
- :bold: /Gnu|Debian|Ruby|SiSU/
- :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
- :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
- :manpage: name=sisu - documents: markup, structuring, publishing in multiple standard formats, and search;
- synopsis=sisu [-abcDdeFhIiMmNnopqRrSsTtUuVvwXxYyZz0-9] [filename/wildcard ]
- . sisu [-Ddcv] [instruction]
- . sisu [-CcFLSVvW]
- . sisu --v4 [operations]
- . sisu --v3 [operations]
-
-@links:
- { SiSU Homepage }http://www.sisudoc.org/
- { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/
- { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html
- { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html
- { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html
- { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary
- { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/
- { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html
- { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org
- { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
-
-}code
-
-2~ Available Headers
-
-Header tags appear at the beginning of a document and provide meta information on the document (such as the Dublin Core), or information as to how the document as a whole is to be processed. All header instructions take the form @headername: or on the next line and indented by once space :subheadername: All Dublin Core meta tags are available
-
-!_ @identifier:
-information or instructions
-
-where the "identifier" is a tag recognised by the program, and the "information" or "instructions" belong to the tag/identifier specified
-
-Note: a header where used should only be used once; all headers apart from @title: are optional; the @structure: header is used to describe document structure, and can be useful to know.
-
-This is a sample header
-
-% (Dublin Core in fuschia, other information headers in cyan, markup instructions in red):
-
-code{
-
-% SiSU 2.0 [declared file-type identifier with markup version]
-
-}code
-
-code{
-
-@title: [title text] [this header is the only one that is mandatory]
- :subtitle: [subtitle if any]
- :language: English
-
-}code
-
-code{
-
-@creator:
- :author: [Lastname, First names]
- :illustrator: [Lastname, First names]
- :translator: [Lastname, First names]
- :prepared_by: [Lastname, First names]
-
-}code
-
-code{
-
-@date:
- :published: [year or yyyy-mm-dd]
- :created: [year or yyyy-mm-dd]
- :issued: [year or yyyy-mm-dd]
- :available: [year or yyyy-mm-dd]
- :modified: [year or yyyy-mm-dd]
- :valid: [year or yyyy-mm-dd]
- :added_to_site: [year or yyyy-mm-dd]
- :translated: [year or yyyy-mm-dd]
-
-}code
-
-code{
-
-@rights:
- :copyright: Copyright (C) [Year and Holder]
- :license: [Use License granted]
- :text: [Year and Holder]
- :translation: [Name, Year]
- :illustrations: [Name, Year]
-
-}code
-
-code{
-
-@classify:
- :topic_register: SiSU:markup sample:book;book:novel:fantasy
- :type:
- :subject:
- :description:
- :keywords:
- :abstract:
- :loc: [Library of Congress classification]
- :dewey: [Dewey classification
-
-}code
-
-code{
-
-@identify:
- :isbn: [ISBN]
- :oclc:
-
-}code
-
-
-code{
-
-@links: { SiSU }http://www.sisudoc.org
- { FSF }http://www.fsf.org
-
-}code
-
-code{
-
-@make:
- :num_top: 1
- :headings: [text to match for each level
- (e.g. PART; Chapter; Section; Article; or another: none; BOOK|FIRST|SECOND; none; CHAPTER;)
- :breaks: new=:C; break=1
- :promo: sisu, ruby, sisu_search_libre, open_society
- :bold: [regular expression of words/phrases to be made bold]
- :italics: [regular expression of words/phrases to italicise]
- :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
- :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
-
-}code
-
-code{
-
-@original:
- :language: [language]
-
-}code
-
-code{
-
-@notes:
- :comment:
- :prefix: [prefix is placed just after table of contents]
-
-}code
-
-% header ends here, NB only @title: is mandatory [this would be a comment]
-% NOTE: headings/levels below refer to 0.38 expermental markup (a conversion script provided in sisu-examples, modify.rb makes conversion between 0.37 and 0.38 markup simple)
-
-1~ Markup of Substantive Text
-
-2~heading_levels Heading Levels
-
-Heading levels are :A~ ,:B~ ,:C~ ,1~ ,2~ ,3~ ... :A - :C being part / section headings, followed by other heading levels, and 1 -6 being headings followed by substantive text or sub-headings. :A~ usually the title :A~? conditional level 1 heading (used where a stand-alone document may be imported into another)
-
-!_ :A~ [heading text]
-Top level heading [this usually has similar content to the title @title: ]
-NOTE: the heading levels described here are in 0.38 notation, see heading
-
-!_ :B~ [heading text]
-Second level heading [this is a heading level divider]
-
-!_ :C~ [heading text]
-Third level heading [this is a heading level divider]
-
-!_ 1~ [heading text]
-Top level heading preceding substantive text of document or sub-heading 2, the heading level that would normally be marked 1. or 2. or 3. etc. in a document, and the level on which sisu by default would break html output into named segments, names are provided automatically if none are given (a number), otherwise takes the form 1~my_filename_for_this_segment
-
-!_ 2~ [heading text]
-Second level heading preceding substantive text of document or sub-heading 3 , the heading level that would normally be marked 1.1 or 1.2 or 1.3 or 2.1 etc. in a document.
-
-!_ 3~ [heading text]
-Third level heading preceding substantive text of document, that would normally be marked 1.1.1 or 1.1.2 or 1.2.1 or 2.1.1 etc. in a document
-
-code{
-
-1~filename level 1 heading,
-
-% the primary division such as Chapter that is followed by substantive text, and may be further subdivided (this is the level on which by default html segments are made)
-
-}code
-
-2~ Font Attributes
-
-!_ markup example:
-
-code{
-
-normal text, *{emphasis}*, !{bold text}!, /{italics}/, _{underscore}_, "{citation}",
-^{superscript}^, ,{subscript},, +{inserted text}+, -{strikethrough}-, #{monospace}#
-
-normal text
-
-*{emphasis}* [note: can be configured to be represented by bold, italics or underscore]
-
-!{bold text}!
-
-/{italics}/
-
-_{underscore}_
-
-"{citation}"
-
-^{superscript}^
-
-,{subscript},
-
-+{inserted text}+
-
--{strikethrough}-
-
-#{monospace}#
-
-}code
-
-!_ resulting output:
-
-normal text, *{emphasis}*, !{bold text}!, /{italics}/, _{underscore}_, "{citation}",
-^{superscript}^, ,{subscript},, +{inserted text}+, -{strikethrough}-, #{monospace}#
-
-normal text
-
-*{emphasis}* [note: can be configured to be represented by bold, italics or underscore]
-
-!{bold text}!
-
-/{italics}/
-
-_{underscore}_
-
-"{citation}"
-
-^{superscript}^
-
-,{subscript},
-
-+{inserted text}+
-
--{strikethrough}-
-
-#{monospace}#
-
-2~ Indentation and bullets
-
-!_ markup example:
-
-code{
-
-ordinary paragraph
-
-_1 indent paragraph one step
-
-_2 indent paragraph two steps
-
-_9 indent paragraph nine steps
-
-}code
-
-!_ resulting output:
-
-ordinary paragraph
-
-_1 indent paragraph one step
-
-_2 indent paragraph two steps
-
-_9 indent paragraph nine steps
-
-!_ markup example:
-
-code{
-
-_* bullet text
-
-_1* bullet text, first indent
-
-_2* bullet text, two step indent
-
-}code
-
-!_ resulting output:
-
-_* bullet text
-
-_1* bullet text, first indent
-
-_2* bullet text, two step indent
-
-Numbered List (not to be confused with headings/titles, (document structure))
-
-!_ markup example:
-
-code{
-
-# numbered list numbered list 1., 2., 3, etc.
-
-_# numbered list numbered list indented a., b., c., d., etc.
-
-}code
-
-2~ Hanging Indents
-
-!_ markup example:
-
-code{
-
-_0_1 first line no indent,
-rest of paragraph indented one step
-
-_1_0 first line indented,
-rest of paragraph no indent
-
-in each case level may be 0-9
-
-}code
-
-!_ resulting output:
-
-_0_1 first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step; first line no indent, rest of paragraph indented one step;
-
-A regular paragraph.
-
-_1_0 first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent first line indented, rest of paragraph no indent
-
-in each case level may be 0-9
-
-_0_1 *{live-build}* A collection of scripts used to build customized Debian Livesystems. /{live-build}/ was formerly known as live-helper, and even earlier known as live-package.
-
-_0_1 *{live-build}* \\
-A collection of scripts used to build customized Debian Livesystems. /{live-build}/ was formerly known as live-helper, and even earlier known as live-package.
-
-2~ Footnotes / Endnotes
-
-Footnotes and endnotes are marked up at the location where they would be indicated within a text. They are automatically numbered. The output type determines whether footnotes or endnotes will be produced
-
-!_ markup example:
-
-code{
-
-~{ a footnote or endnote }~
-
-}code
-
-!_ resulting output:
-
-~{ a footnote or endnote }~
-
-!_ markup example:
-
-code{
-
-normal text~{ self contained endnote marker & endnote in one }~ continues
-
-}code
-
-!_ resulting output:
-
-normal text~{ self contained endnote marker & endnote in one }~ continues
-
-!_ markup example:
-
-code{
-
-normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks if required }~ continues
-
-normal text ~{** another unnumbered asterisk footnote/endnote }~ continues
-
-}code
-
-!_ resulting output:
-
-normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks if required }~ continues
-
-normal text ~{** another unnumbered asterisk footnote/endnote }~ continues
-
-!_ markup example:
-
-code{
-
-normal text ~[* editors notes, numbered asterisk footnote/endnote series ]~ continues
-
-normal text ~[+ editors notes, numbered plus symbol footnote/endnote series ]~ continues
-
-}code
-
-!_ resulting output:
-
-normal text ~[* editors notes, numbered asterisk footnote/endnote series ]~ continues
-
-normal text ~[+ editors notes, numbered plus symbol footnote/endnote series ]~ continues
-
-!_ Alternative endnote pair notation for footnotes/endnotes:
-
-code{
-
-% note the endnote marker "~^"
-
-normal text~^ continues
-
-^~ endnote text following the paragraph in which the marker occurs
-
-}code
-
-the standard and pair notation cannot be mixed in the same document
-
-2~ Links
-
-3~ Naked URLs within text, dealing with urls
-
-urls found within text are marked up automatically. A url within text is automatically hyperlinked to itself and by default decorated with angled braces, unless they are contained within a code block (in which case they are passed as normal text), or escaped by a preceding underscore (in which case the decoration is omitted).
-
-!_ markup example:
-
-code{
-
-normal text http://www.sisudoc.org/ continues
-
-}code
-
-!_ resulting output:
-
-normal text http://www.sisudoc.org/ continues
-
-An escaped url without decoration
-
-!_ markup example:
-
-code{
-
-normal text _http://www.sisudoc.org/ continues
-
-deb _http://www.jus.uio.no/sisu/archive unstable main non-free
-
-}code
-
-!_ resulting output:
-
-normal text _http://www.sisudoc.org/ continues
-
-deb _http://www.jus.uio.no/sisu/archive unstable main non-free
-
-where a code block is used there is neither decoration nor hyperlinking, code blocks are discussed later in this document
-
-!_ resulting output:
-
-code{
-
-deb http://www.jus.uio.no/sisu/archive unstable main non-free
-deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
-
-}code
-
-3~link_text Linking Text
-
-To link text or an image to a url the markup is as follows
-
-!_ markup example:
-
-code{
-
-about { SiSU }http://url.org markup
-
-}code
-
-!_ resulting output:
-
-about { SiSU }http://www.sisudoc.org/ markup
-
-A shortcut notation is available so the url link may also be provided automatically as a footnote
-
-!_ markup example:
-
-code{
-
-about {~^ SiSU }http://url.org markup
-
-}code
-
-!_ resulting output:
-
-about {~^ SiSU }http://www.sisudoc.org/ markup
-
-Internal document links to a tagged location, including an ocn
-
-!_ markup example:
-
-code{
-
-about { text links }#link_text
-
-}code
-
-!_ resulting output:
-
-about { text links }#link_text
-
-Shared document collection link
-
-!_ markup example:
-
-code{
-
-about { SiSU book markup examples }:SiSU/examples.html
-
-}code
-
-!_ resulting output:
-
-about { SiSU book markup examples }:SiSU/examples.html
-
-3~ Linking Images
-
-!_ markup example:
-
-code{
-
-{ tux.png 64x80 }image
-
-% various url linked images
-
-{tux.png 64x80 "a better way" }http://www.sisudoc.org/
-
-{GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian and Ruby" }http://www.sisudoc.org/
-
-{~^ ruby_logo.png "Ruby" }http://www.ruby-lang.org/en/
-
-}code
-
-!_ resulting output:
-
-{ tux.png 64x80 }image
-
-{tux.png 64x80 "Gnu/Linux - a better way" }http://www.sisudoc.org/
-
-{GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian and Ruby" }http://www.sisudoc.org/
-
-{~^ ruby_logo.png "Ruby" }http://www.ruby-lang.org/en/
-
-!_ linked url footnote shortcut
-
-code{
-
-{~^ [text to link] }http://url.org
-
-% maps to: { [text to link] }http://url.org ~{ http://url.org }~
-
-% which produces hyper-linked text within a document/paragraph, with an endnote providing the url for the text location used in the hyperlink
-
-}code
-
-code{
-
-text marker *~name
-
-}code
-
-note at a heading level the same is automatically achieved by providing names to headings 1, 2 and 3 i.e. 2~[name] and 3~[name] or in the case of auto-heading numbering, without further intervention.
-
-3~ Link shortcut for multiple versions of a sisu document in the same directory tree
-
-!_ markup example:
-
-code{
-
-!_ /{"Viral Spiral"}/, David Bollier
-
-{ "Viral Spiral", David Bollier [3sS]}viral_spiral.david_bollier.sst
-
-}code
-
-
-!_ /{"Viral Spiral"}/, David Bollier
-
-{ "Viral Spiral", David Bollier [3sS]}viral_spiral.david_bollier.sst
-
-2~ Grouped Text
-
-3~ Tables
-
-Tables may be prepared in two either of two forms
-
-!_ markup example:
-
-code{
-
-table{ c3; 40; 30; 30;
-
-This is a table
-this would become column two of row one
-column three of row one is here
-
-And here begins another row
-column two of row two
-column three of row two, and so on
-
-}table
-
-}code
-
-!_ resulting output:
-
-table{ c3; 40; 30; 30;
-
-This is a table
-this would become column two of row one
-column three of row one is here
-
-And here begins another row
-column two of row two
-column three of row two, and so on
-
-}table
-
-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
http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler }~
-
-code{
-
-!_ Table 3.1: Contributors to Wikipedia, January 2001 - June 2005
-
-{table~h 24; 12; 12; 12; 12; 12; 12;}
- |Jan. 2001|Jan. 2002|Jan. 2003|Jan. 2004|July 2004|June 2006
-Contributors* | 10| 472| 2,188| 9,653| 25,011| 48,721
-Active contributors** | 9| 212| 846| 3,228| 8,442| 16,945
-Very active contributors*** | 0| 31| 190| 692| 1,639| 3,016
-No. of English language articles| 25| 16,000| 101,000| 190,000| 320,000| 630,000
-No. of articles, all languages | 25| 19,000| 138,000| 490,000| 862,000|1,600,000
-
-* Contributed at least ten times; ** at least 5 times in last month; *** more than 100 times in last month.
-
-}code
-
-!_ resulting output:
-
-
-!_ Table 3.1: Contributors to Wikipedia, January 2001 - June 2005
-
-{table~h 24; 12; 12; 12; 12; 12; 12;}
- |Jan. 2001|Jan. 2002|Jan. 2003|Jan. 2004|July 2004|June 2006
-Contributors* | 10| 472| 2,188| 9,653| 25,011| 48,721
-Active contributors** | 9| 212| 846| 3,228| 8,442| 16,945
-Very active contributors*** | 0| 31| 190| 692| 1,639| 3,016
-No. of English language articles| 25| 16,000| 101,000| 190,000| 320,000| 630,000
-No. of articles, all languages | 25| 19,000| 138,000| 490,000| 862,000|1,600,000
-
-* Contributed at least ten times; ** at least 5 times in last month; *** more than 100 times in last month.
-
-% code{
-
-% test
-
-% ~#
-
-% % unnumbered paragraph (place marker at end of paragraph)
-
-% -#
-
-% % unnumbered paragraph, delete when not required (place marker at end of paragraph) [used in dummy headings, eg. for segmented html]
-
-% % add a comment to text, that will be removed prior to processing (place marker at beginning of line)
-
-% }code
-
-3~ Poem
-
-!_ basic markup:
-
-code{
-
-poem{
-
- Your poem here
-
-}poem
-
-Each verse in a poem is given an object number.
-
-}code
-
-!_ markup example:
-
-code{
-
-poem{
-
- `Fury said to a
- mouse, That he
- met in the
- house,
- "Let us
- both go to
- law: I will
- prosecute
- YOU. --Come,
- I'll take no
- denial; We
- must have a
- trial: For
- really this
- morning I've
- nothing
- to do."
- Said the
- mouse to the
- cur, "Such
- a trial,
- dear Sir,
- With
- no jury
- or judge,
- would be
- wasting
- our
- breath."
- "I'll be
- judge, I'll
- be jury,"
- Said
- cunning
- old Fury:
- "I'll
- try the
- whole
- cause,
- and
- condemn
- you
- to
- death."'
-
-}poem
-
-}code
-
-!_ resulting output:
-
-poem{
-
- `Fury said to a
- mouse, That he
- met in the
- house,
- "Let us
- both go to
- law: I will
- prosecute
- YOU. --Come,
- I'll take no
- denial; We
- must have a
- trial: For
- really this
- morning I've
- nothing
- to do."
- Said the
- mouse to the
- cur, "Such
- a trial,
- dear Sir,
- With
- no jury
- or judge,
- would be
- wasting
- our
- breath."
- "I'll be
- judge, I'll
- be jury,"
- Said
- cunning
- old Fury:
- "I'll
- try the
- whole
- cause,
- and
- condemn
- you
- to
- death."'
-
-}poem
-
-3~ Group
-
-!_ basic markup:
-
-code{
-
-group{
-
- Your grouped text here
-
-}group
-
-A group is treated as an object and given a single object number.
-
-}code
-
-!_ markup example:
-
-code{
-
-group{
-
- `Fury said to a
- mouse, That he
- met in the
- house,
- "Let us
- both go to
- law: I will
- prosecute
- YOU. --Come,
- I'll take no
- denial; We
- must have a
- trial: For
- really this
- morning I've
- nothing
- to do."
- Said the
- mouse to the
- cur, "Such
- a trial,
- dear Sir,
- With
- no jury
- or judge,
- would be
- wasting
- our
- breath."
- "I'll be
- judge, I'll
- be jury,"
- Said
- cunning
- old Fury:
- "I'll
- try the
- whole
- cause,
- and
- condemn
- you
- to
- death."'
-
-}group
-
-}code
-
-!_ resulting output:
-
-group{
-
- `Fury said to a
- mouse, That he
- met in the
- house,
- "Let us
- both go to
- law: I will
- prosecute
- YOU. --Come,
- I'll take no
- denial; We
- must have a
- trial: For
- really this
- morning I've
- nothing
- to do."
- Said the
- mouse to the
- cur, "Such
- a trial,
- dear Sir,
- With
- no jury
- or judge,
- would be
- wasting
- our
- breath."
- "I'll be
- judge, I'll
- be jury,"
- Said
- cunning
- old Fury:
- "I'll
- try the
- whole
- cause,
- and
- condemn
- you
- to
- death."'
-
-}group
-
-3~ Code
-
-Code tags #{ code{ ... }code }# (used as with other group tags described above) are used to escape regular sisu markup, and have been used extensively within this document to provide examples of SiSU markup. You cannot however use code tags to escape code tags. They are however used in the same way as group or poem tags.
-
-A code-block is treated as an object and given a single object number. [an option to number each line of code may be considered at some later time]
-
-!_ use of code tags instead of poem compared, resulting output:
-
-code{
-
- `Fury said to a
- mouse, That he
- met in the
- house,
- "Let us
- both go to
- law: I will
- prosecute
- YOU. --Come,
- I'll take no
- denial; We
- must have a
- trial: For
- really this
- morning I've
- nothing
- to do."
- Said the
- mouse to the
- cur, "Such
- a trial,
- dear Sir,
- With
- no jury
- or judge,
- would be
- wasting
- our
- breath."
- "I'll be
- judge, I'll
- be jury,"
- Said
- cunning
- old Fury:
- "I'll
- try the
- whole
- cause,
- and
- condemn
- you
- to
- death."'
-
-}code
-
-From SiSU 2.7.7 on you can number codeblocks by placing a hash after the opening code tag #{ code{# }# as demonstrated here:
-
-code{#
-
- `Fury said to a
- mouse, That he
- met in the
- house,
- "Let us
- both go to
- law: I will
- prosecute
- YOU. --Come,
- I'll take no
- denial; We
- must have a
- trial: For
- really this
- morning I've
- nothing
- to do."
- Said the
- mouse to the
- cur, "Such
- a trial,
- dear Sir,
- With
- no jury
- or judge,
- would be
- wasting
- our
- breath."
- "I'll be
- judge, I'll
- be jury,"
- Said
- cunning
- old Fury:
- "I'll
- try the
- whole
- cause,
- and
- condemn
- you
- to
- death."'
-
-}code
-
-2~ Additional breaks - linebreaks within objects, column and page-breaks
-
-3~ line-breaks
-
-To break a line within a "paragraph object", two backslashes \\\\ \\ with a space before and a space or newline after them \\ may be used.
-
-code{
-
-To break a line within a "paragraph object",
-two backslashes \\ with a space before
-and a space or newline after them \\
-may be used.
-
-}code
-
-The html break br enclosed in angle brackets (though undocumented) is available in versions prior to 3.0.13 and 2.9.7 (it remains available for the time being, but is depreciated).
-
-To draw a dividing line dividing paragraphs, see the section on page breaks.
-
-3~ page breaks
-
-Page breaks are only relevant and honored in some output formats. A page break or a new page may be inserted manually using the following markup on a line on its own:
-
-page new =\\= or <:pn> breaks the page, starts a new page.
-
-page break -\\- or <:pb> breaks a column, starts a new column, if using columns, else breaks the page, starts a new page.
-
-page break line across page -..- draws a dividing line, dividing paragraphs
-
-page break:
-
-code{
-
--\\-
-
-or
-
-<:pb>
-
-}code
-
-page (break) new:
-
-code{
-
-=\\=
-
-or
-
-<:pn>
-
-}code
-
-page (break) line across page (dividing paragraphs):
-
-code{
-
--..-
-
-}code
-
-2~ Book index
-
-To make an index append to paragraph the book index term relates to it, using an equal sign and curly braces.
-
-Currently two levels are provided, a main term and if needed a sub-term. Sub-terms are separated from the main term by a colon.
-
-code{
-
- Paragraph containing main term and sub-term.
- ={Main term:sub-term}
-
-}code
-
-The index syntax starts on a new line, but there should not be an empty line between paragraph and index markup.
-
-The structure of the resulting index would be:
-
-code{
-
- Main term, 1
- sub-term, 1
-
-}code
-
-Several terms may relate to a paragraph, they are separated by a semicolon. If the term refers to more than one paragraph, indicate the number of paragraphs.
-
-code{
-
- Paragraph containing main term, second term and sub-term.
- ={first term; second term: sub-term}
-
-}code
-
-The structure of the resulting index would be:
-
-code{
-
- First term, 1,
- Second term, 1,
- sub-term, 1
-
-}code
-
-If multiple sub-terms appear under one paragraph, they are separated under the main term heading from each other by a pipe symbol.
-
-code{
-
- Paragraph containing main term, second term and sub-term.
- ={Main term:
- sub-term+2|second sub-term;
- Another term
- }
-
- A paragraph that continues discussion of the first sub-term
-
-}code
-
-The plus one in the example provided indicates the first sub-term spans one additional paragraph. The logical structure of the resulting index would be:
-
-code{
-
- Main term, 1,
- sub-term, 1-3,
- second sub-term, 1,
- Another term, 1
-
-}code
-
-1~ Composite documents markup
-
-It is possible to build a document by creating a master document that requires other documents. The documents required may be complete documents that could be generated independently, or they could be markup snippets, prepared so as to be easily available to be placed within another text. If the calling document is a master document (built from other documents), it should be named with the suffix *{.ssm}* Within this document you would provide information on the other documents that should be included within the text. These may be other documents that would be processed in a regular way, or markup bits prepared only for inclusion within a master document *{.sst}* regular markup file, or *{.ssi}* (insert/information) A secondary file of the composite document is built prior to processing with the same prefix and the suffix *{._sst}*
-
-basic markup for importing a document into a master document
-
-code{
-
-<< filename1.sst
-
-<< filename2.ssi
-
-}code
-
-The form described above should be relied on. Within the Vim editor it results in the text thus linked becoming hyperlinked to the document it is calling in which is convenient for editing.
-
-1~ Substitutions
-
-!_ markup example:
-
-code{
-
-The current Debian is ${debian_stable} the next debian will be ${debian_testing}
-
-Configure substitution in _sisu/sisu_document_make
-
-@make:
- :substitute: /${debian_stable}/,'*{Wheezy}*' /${debian_testing}/,'*{Jessie}*'
-
-}code
-
-!_ resulting output:
-
-The current Debian is ${debian_stable} the next debian will be ${debian_testing}
-
-Configure substitution in _sisu/sisu_document_make
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_markup_syntax_history.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_markup_syntax_history.sst
deleted file mode 100644
index c6da0a14..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_markup_syntax_history.sst
+++ /dev/null
@@ -1,244 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: Markup
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :published: 2008-05-22
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: electronic documents:SiSU:document:markup;SiSU:document:markup;SiSU:document:markup;SiSU:manual:markup;electronic documents:SiSU:manual:markup
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? SiSU Markup Syntax History
-
-1~syntax_history Markup Syntax History
-
-2~ Notes related to Files-types and Markup Syntax
-
-4.0 introduced additional headers and drops the use of skins replacing them with additions to the @make: header, and having a common _sisu/sisu_document_make file that uses @make: header syntax to provide a default @make: (it will parse 2.0 but igore skins, markup is otherwise the same as version 2.0 with version 3.0's minor additions)
-
-3.0 very minor additions to markup added, substantially the same as version 2.0
-
-2.0 introduced new headers and is therefore incompatible with 1.0 though otherwise the same with the addition of a couple of tags (i.e. a superset)
-
-0.38 is substantially current for version 1.0
-
-depreciated 0.16 supported, though file names were changed at 0.37
-
-_* sisu --query=[sisu version [0.38] or 'history]
-
-provides a short history of changes to SiSU markup
-
-!_ SiSU 2.0
-(2010-03-06:09/6)
-same as 1.0, apart from the changing of headers and the addition of a monospace tag related headers now grouped, e.g.
-
-code{
-
-@title:
- :subtitle:
-
-@creator:
- :author:
- :translator:
- :illustrator:
-
-@rights:
- :text:
- :illustrations:
-
-}code
-
-see document markup samples, and sisu --help headers
-
-the monospace tag takes the form of a hash '#'
-
-code{
-
-#{ this enclosed text would be monospaced }#
-
-}code
-
-!_ 1.0
-(2009-12-19:50/6)
-same as 0.69
-
-!_ 0.69
-(2008-09-16:37/2)
-(same as 1.0) and as previous (0.57) with the addition of book index tags
-
-code{
-
-/^={.+?}$/
-
-}code
-
-e.g. appended to a paragraph, on a new-line (without a blank line in between) logical structure produced assuming this is the first text "object"
-
-code{
-
- ={GNU/Linux community distribution:Debian+2|Fedora|Gentoo;Free Software Foundation+5}
-
-}code
-
-code{
-
-Free Software Foundation, 1-6
-GNU/Linux community distribution, 1
- Debian, 1-3
- Fedora, 1
- Gentoo,
-
-}code
-
-!_ 0.66
-(2008-02-24:07/7)
-same as previous, adds semantic tags, [experimental and not-used]
-
-code{
-
-/[:;]{.+?}[:;][a-z+]/
-
-}code
-
-!_ 0.57
-(2007w34/4)
-SiSU 0.57 is the same as 0.42 with the introduction of some a shortcut to use the headers @title and @creator in the first heading [expanded using the contents of the headers @title: and @author:]
-
-code{
-
-:A~ @title by @author
-
-}code
-
-!_ 0.52
-(2007w14/6)
-declared document type identifier at start of text/document:
-
-_1 SiSU 0.52
-
-or, backward compatible using the comment marker:
-
-_1 % SiSU 0.38
-
-variations include 'SiSU (text|master|insert) [version]' and 'sisu-[version]'
-
-!_ 0.51
-(2007w13/6)
-skins changed (simplified), markup unchanged
-
-!_ 0.42
-(2006w27/4)
-* (asterisk) type endnotes, used e.g. in relation to author
-
-SiSU 0.42 is the same as 0.38 with the introduction of some additional endnote types,
-
-Introduces some variations on endnotes, in particular the use of the asterisk
-
-code{
-
-~{* for example for describing an author }~ and ~{** for describing a second author }~
-
-}code
-
-* for example for describing an author
-
-** for describing a second author
-
-and
-
-code{
-
-~[* my note ]~ or ~[+ another note ]~
-
-}code
-
-which numerically increments an asterisk and plus respectively
-
-*1 my note
-+1 another note
-
-!_ 0.38
-(2006w15/7)
-introduced new/alternative notation for headers, e.g. @title: (instead of 0\~title), and accompanying document structure markup, :A,:B,:C,1,2,3 (maps to previous 1,2,3,4,5,6)
-
-SiSU 0.38 introduced alternative experimental header and heading/structure markers,
-
-code{
-
-@headername: and headers :A~ :B~ :C~ 1~ 2~ 3~
-
-}code
-
-as the equivalent of:
-
-code{
-
-0~headername and headers 1~ 2~ 3~ 4~ 5~ 6~
-
-}code
-
-The internal document markup of SiSU 0.16 remains valid and standard Though note that SiSU 0.37 introduced a new file naming convention
-
-SiSU has in effect two sets of levels to be considered, using 0.38 notation A-C headings/levels, pre-ordinary paragraphs /pre-substantive text, and 1-3 headings/levels, levels which are followed by ordinary text. This may be conceptualised as levels A,B,C, 1,2,3, and using such letter number notation, in effect: A must exist, optional B and C may follow in sequence (not strict) 1 must exist, optional 2 and 3 may follow in sequence i.e. there are two independent heading level sequences A,B,C and 1,2,3 (using the 0.16 standard notation 1,2,3 and 4,5,6) on the positive side: the 0.38 A,B,C,1,2,3 alternative makes explicit an aspect of structuring documents in SiSU that is not otherwise obvious to the newcomer (though it appears more complicated, is more in your face and likely to be understood fairly quickly); the substantive text follows levels 1,2,3 and it is 'nice' to do most work in those levels
-
-!_ 0.37
-(2006w09/7)
-introduced new file naming convention, .sst (text), .ssm (master), .ssi (insert), markup syntax unchanged
-
-SiSU 0.37 introduced new file naming convention, using the file extensions .sst .ssm and .ssi to replace .s1 .s2 .s3 .r1 .r2 .r3 and .si
-
-this is captured by the following file 'rename' instruction:
-
-code{
-
-rename 's/\.s[123]$/\.sst/' *.s{1,2,3}
-rename 's/\.r[123]$/\.ssm/' *.r{1,2,3}
-rename 's/\.si$/\.ssi/' *.si
-
-}code
-
-The internal document markup remains unchanged, from SiSU 0.16
-
-!_ 0.35
-(2005w52/3)
-sisupod, zipped content file introduced
-
-!_ 0.23
-(2005w36/2)
-utf-8 for markup file
-
-!_ 0.22
-(2005w35/3)
-image dimensions may be omitted if rmagick is available to be relied upon
-
-!_ 0.20.4
-(2005w33/4)
-header 0~links
-
-!_ 0.16
-(2005w25/2)
-substantial changes introduced to make markup cleaner, header 0\~title type, and headings [1-6]\~ introduced, also percentage sign (%) at start of a text line as comment marker
-
-SiSU 0.16 (0.15 development branch) introduced the use of
-
-the header 0~ and headings/structure 1~ 2~ 3~ 4~ 5~ 6~
-
-in place of the 0.1 header, heading/structure notation
-
-SiSU 0.1 headers and headings structure represented by
-header 0{~ and headings/structure 1{ 2{ 3{ 4{~ 5{ 6{
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_output_overview.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_output_overview.sst
deleted file mode 100644
index 332f4aae..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_output_overview.sst
+++ /dev/null
@@ -1,142 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: SiSU overview of status of features available in various outputs
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2005-10-31
- :available: 2006-10-31
- :issued: 2006-10-31
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: electronic documents:SiSU:document:markup table;SiSU:manual:output overview;electronic documents:SiSU:manual:output overview;SiSU:document:output overview;SiSU:document:output overview
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? SiSU overview of status of features available in various outputs
-
-1~ A Checklist of Output Features
-
-% 2~ features available in various output types
-
-This table gives an indication of the features that are available
-for various forms of output of SiSU.
-
-!_ sisu-2.0.0 on 2010-03-06
-
-{table~h 28}
-feature |txt|ltx/pdf|HTML|EPUB|XML/s|XML/d|ODF|SQLite|pgSQL
-headings | * | * | * | * | * | * | * | * | *
-footnotes | * | * | * | * | * | * | * | * | *
-bold, underscore, italics | . | * | * | * | * | * | * | * | *
-strikethrough | . | * | * | * | * | * | * | |
-superscript, subscript | . | * | * | * | * | * | * | |
-extended ascii set (utf-8)| * | * | * | * | * | * | * | | *
-indents | * | * | * | * | * | * | * | |
-bullets | . | * | * | * | * | * | . | |
-groups | | | | | | | | |
-* tables | | * | * | * | . | . | . | . | .
-* poem | * | * | * | * | . | . | * | . | .
-* code | * | * | * | * | . | . | * | . | .
-url | * | * | * | * | * | * | * | . | .
-links | * | * | * | * | * | * | * | . | .
-images | - | * | * | * | T | T | * | T | T
-image caption | - | * | * | * | | | | |
-table of contents | | * | * | * | * | * | . | |
-page header/footer? | - | * | * | * | * | * | t | |
-line break | * | * | * | * | * | * | * | |
-page break | | * | | | | | * | |
-segments | | | * | * | | | | |
-skins | * | * | * | * | * | * | | |
-ocn | . | * | * | * | * | * | -?| * | *
-auto-heading numbers | * | * | * | * | * | * | * | * | *
-minor list numbering | * | * | * | * | * | * | * | * | *
-special characters | . | . | . | . | | | | |
-
-!_ sisu-1.0.0 on 2009-10-28
-
-{table~h 28}
-feature |txt|ltx/pdf|HTML|XML/s|XML/d|ODF|SQLite|pgSQL
-headings | * | * | * | * | * | * | * | *
-footnotes | * | * | * | * | * | * | * | *
-bold, underscore, italics | . | * | * | * | * | * | * | *
-strikethrough | . | * | * | * | * | * | |
-superscript, subscript | . | * | * | * | * | * | |
-extended ascii set (utf-8)| * | * | * | * | * | * | | *
-indents | * | * | * | * | * | * | |
-bullets | . | * | * | * | * | . | |
-groups | | | | | | | |
-* tables | | * | * | . | . | . | . | .
-* poem | * | * | * | . | . | * | . | .
-* code | * | * | * | . | . | * | . | .
-url | * | * | * | * | * | * | . | .
-links | * | * | * | * | * | * | . | .
-images | - | * | * | T | T | * | T | T
-image caption | - | * | * | | | | |
-table of contents | | * | * | * | * | . | |
-page header/footer? | - | * | * | * | * | t | |
-line break | * | * | * | * | * | * | |
-page break | | * | | | | * | |
-segments | | | * | | | | |
-skins | * | * | * | * | * | | |
-ocn | . | * | * | * | * | -?| * | *
-auto-heading numbers | * | * | * | * | * | * | * | *
-minor list numbering | * | * | * | * | * | * | * | *
-special characters | . | . | . | | | | |
-
-!_ sisu-0.36.6 on 2006-01-23
-
-{table~h 28; 8; 8; 8; 8; 8; 8; 8; 8; 8;}
-feature |txt|ltx/pdf|HTML|XHTML|XML/s|XML/d|ODF|SQLite|pgSQL
-headings | * | * | * | * | * | * | * | * | *
-footnotes | * | * | * | * | * | * | * | * | *
-bold, underscore, italics | . | * | * | * | * | * | * | * | *
-strikethrough | . | * | * | * | * | * | * | |
-superscript, subscript | . | * | * | * | * | * | * | |
-extended ascii set (utf-8)| * | * | * | * | * | * | * | | *
-indents | * | * | * | * | * | * | * | |
-bullets | . | * | * | * | * | * | . | |
-groups | | | | | | | | |
-* tables | | * | * | . | . | . | . | . | .
-* poem | * | * | * | . | . | . | * | . | .
-* code | * | * | * | . | . | . | * | . | .
-url | * | * | * | * | * | * | * | . | .
-links | * | * | * | * | * | * | * | . | .
-images | - | * | * | T | T | T | * | T | T
-image caption | - | * | * | | | | | |
-table of contents | | * | * | * | * | * | . | |
-page header/footer? | - | * | * | * | * | * | t | |
-line break | * | * | * | * | * | * | * | |
-page break | | * | | | | | * | |
-segments | | | * | | | | | |
-skins | * | * | * | * | * | * | | |
-ocn | . | * | * | * | * | * | -?| * | *
-auto-heading numbers | * | * | * | * | * | * | * | * | *
-minor list numbering | * | * | * | * | * | * | * | * | *
-special characters | . | . | . | | | | | |
-
-group{
-
- Done
- * yes/done
- . partial
-
- - not available/appropriate
-
- Not Done
- T task todo
- t lesser task/todo
- not done
-
-}group
-
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_postgresql.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_postgresql.sst
deleted file mode 100644
index 574e307c..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_postgresql.sst
+++ /dev/null
@@ -1,82 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: Search
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: electronic documents:SiSU:document:postgresql;SiSU:manual:postgresql;electronic documents:SiSU:manual:postgresql;SiSU:document:postgresql;SiSU:document:postgresql;
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-@make:
- :manpage: section=7; name=sisu - package to install what sisu needs to to populate a postgresql database (postgresql dependency component); synopsis=sisu -Dv [filename/wildcard ]\n sisu -Dv [instruction]
-
-:A~? @title @creator
-
-% :B~? SiSU Postgresql
-
-1~postgresql Postgresql
-
-2~ Name
-
-SiSU - Structured information, Serialized Units - a document publishing system, postgresql dependency package
-
-2~ Description
-
-Information related to using postgresql with sisu (and related to the sisu_postgresql dependency package, which is a dummy package to install dependencies needed for SiSU to populate a postgresql database, this being part of SiSU - man sisu).
-
-2~ Synopsis
-
-_1 sisu -D [instruction] [filename/wildcard if required]
-
-_1 sisu -D --pg --[instruction] [filename/wildcard if required]
-
-
-2~ Commands
-
-Mappings to two databases are provided by default, postgresql and sqlite, the same commands are used within sisu to construct and populate databases however -d (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, alternatively --sqlite or --pgsql may be used
-
-!_ -D or --pgsql
-may be used interchangeably.
-
-3~ create and destroy database
-
-!_ --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

-creates database where no database existed before
-
-!_ sisu -D --create

-creates database tables where no database tables existed before
-
-!_ 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

-destroys existing database and builds a new empty database structure
-
-3~ import and remove documents
-
-!_ 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]

-updates file contents in database
-
-!_ sisu -D --remove -v [filename/wildcard]

-removes specified document from postgresql database.
-
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_quickstart.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_quickstart.sst
deleted file mode 100644
index ae95f528..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_quickstart.sst
+++ /dev/null
@@ -1,256 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: Quickstart, installation and use
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2006-09-06
- :available: 2006-09-06
- :issued: 2006-09-06
- :published: 2007-09-16
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: electronic documents:SiSU:document:quickstart;SiSU:manual:quickstart;electronic documents:SiSU:manual:quickstart;SiSU:document:quickstart;SiSU:document:quickstart
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? Quickstart - SiSU installation and use
-
-1~ Quickstart - Getting Started Howto
-
-2~ Installation
-
-Installation is currently most straightforward and tested on the Debian platform, as there are packages for the installation of sisu and all requirements for what it does.
-
-3~ Debian Installation
-
-SiSU is available directly from the Debian Sid and testing archives (and possibly Ubuntu), assuming your /etc/apt/sources.list is set accordingly:
-
-code{
-
- aptitude update
- aptitude install sisu-complete
-
-}code
-
-The following /etc/apt/sources.list setting permits the download of additional markup samples:
-
-code{
-
-#/etc/apt/sources.list
-
- deb http://ftp.fi.debian.org/debian/ unstable main non-free contrib
- deb-src http://ftp.fi.debian.org/debian/ unstable main non-free contrib
-
-}code
-
-The aptitude commands become:
-
-code{
-
- aptitude update
- aptitude install sisu-complete sisu-markup-samples
-
-}code
-
-If there are newer versions of SiSU upstream of the Debian archives, they will be available by adding the following to your /etc/apt/sources.list
-
-code{
-
-#/etc/apt/sources.list
-
- deb http://www.jus.uio.no/sisu/archive unstable main non-free
- deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
-
-}code
-
-repeat the aptitude commands
-
-code{
-
- aptitude update
- aptitude install sisu-complete sisu-markup-samples
-
-}code
-
-Note however that it is not necessary to install sisu-complete if not all components of sisu are to be used. Installing just the package sisu will provide basic functionality.
-
-3~ RPM Installation
-
-RPMs are provided though untested, they are prepared by running alien against the source package, and against the debs.
-
-They may be downloaded from:
-
-_1 http://www.jus.uio.no/sisu/SiSU/download.html#rpm
-
-as root type:
-
-_1 rpm -i [rpm package name]
-
-3~ Installation from source
-
-To install SiSU from source check information at:
-
-_1 http://www.jus.uio.no/sisu/SiSU/download.html#current
-
-_* download the source package
-
-_* Unpack the source
-
-Two alternative modes of installation from source are provided, setup.rb (by Minero Aoki) and a rant(by Stefan Lang) built install file, in either case: the first steps are the same, download and unpack the source file:
-
-For basic use SiSU is only dependent on the programming language in which it is written Ruby, and SiSU will be able to generate html, EPUB, various XMLs, including ODF (and will also produce LaTeX). Dependencies required for further actions, though it relies on the installation of additional dependencies which the source tarball does not take care of, for things like using a database (postgresql or sqlite)~{ There is nothing to stop MySQL support being added in future. }~ or converting LaTeX to pdf.
-
-!_ setup.rb
-
-This is a standard ruby installer, using setup.rb is a three step process. In the root directory of the unpacked SiSU as root type:
-
-code{
-
- ruby setup.rb config
- ruby setup.rb setup
- #[and as root:]
- ruby setup.rb install
-
-}code
-
-further information on setup.rb is available from:
-
-_1 http://i.loveruby.net/en/projects/setup/
-
-_1 http://i.loveruby.net/en/projects/setup/doc/usage.html
-
-!_ "install"
-
-The "install" file provided is an installer prepared using "rant". In the root directory of the unpacked SiSU as root type:
-
-_1 ruby install base
-
-or for a more complete installation:
-
-_1 ruby install
-
-or
-
-_1 ruby install base
-
-This makes use of Rant (by Stefan Lang) and the provided Rantfile. It has been configured to do post installation setup setup configuration and generation of first test file. Note however, that additional external package dependencies, such as tetex-extra are not taken care of for you.
-
-Further information on "rant" is available from:
-
-_1 http://make.rubyforge.org/
-
-_1 http://rubyforge.org/frs/?group_id=615
-
-For a list of alternative actions you may type:
-
-_1 ruby install help
-
-_1 ruby install -T
-
-2~ Testing SiSU, generating output
-
-To check which version of sisu is installed:
-
-sisu -v
-
-Depending on your mode of installation one or a number of markup sample files may be found either in the directory:
-
-...
-
-or
-
-...
-
-change directory to the appropriate one:
-
-cd /usr/share/doc/sisu/markup-samples/samples
-
-3~ basic text, plaintext, html, XML, ODF, EPUB
-
-Having moved to the directory that contains the markup samples (see instructions above if necessary), choose a file and run sisu against it
-
-sisu -NhwoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst
-
-this will generate html including a concordance file, opendocument text format, plaintext, XHTML and various forms of XML, and OpenDocument text
-
-3~ LaTeX / pdf
-
-Assuming a LaTeX engine such as tetex or texlive is installed with the required modules (done automatically on selection of sisu-pdf in Debian)
-
-Having moved to the directory that contains the markup samples (see instructions above if necessary), choose a file and run sisu against it
-
-sisu -pv free_as_in_freedom.rms_and_free_software.sam_williams.sst
-
-sisu -3 free_as_in_freedom.rms_and_free_software.sam_williams.sst
-
-should generate most available output formats: html including a concordance file, opendocument text format, plaintext, XHTML and various forms of XML, and OpenDocument text and pdf
-
-3~ relational database - postgresql, sqlite
-
-Relational databases need some setting up - you must have permission to create the database and write to it when you run sisu.
-
-Assuming you have the database installed and the requisite permissions
-
-sisu --sqlite --recreate
-
-sisu --sqlite -v --import free_as_in_freedom.rms_and_free_software.sam_williams.sst
-
-sisu --pgsql --recreate
-
-sisu --pgsql -v --import free_as_in_freedom.rms_and_free_software.sam_williams.sst
-
-2~ Getting Help
-
-3~ The man pages
-
-Type:
-
-_1 man sisu
-
-The man pages are also available online, though not always kept as up to date as within the package itself:
-
-_* {~^ sisu.1 }http://www.jus.uio.no/sisu/man/sisu.1.html
-
-_* {~^ sisu.8 }http://www.jus.uio.no/sisu/man/sisu.8.html
-
-_* {~^ man directory }http://www.jus.uio.no/sisu/man
-
-3~ Built in help
-
-sisu --help
-
-sisu --help --env
-
-sisu --help --commands
-
-sisu --help --markup
-
-3~ The home page
-
-http://www.sisudoc.org/
-
-http://www.jus.uio.no/sisu
-
-http://www.jus.uio.no/sisu/SiSU
-
-2~ Markup Samples
-
-A number of markup samples (along with output) are available off:
-
-http://www.jus.uio.no/sisu/SiSU/examples.html
-
-Additional markup samples are packaged separately in the file:
-
-***
-
-On Debian they are available in non-free~{ the Debian Free Software guidelines require that everything distributed within Debian can be changed - and the documents are authors' works that while freely distributable are not freely changeable. }~ to include them it is necessary to include non-free in your /etc/apt/source.list or obtain them from the sisu home site.
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_remote.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_remote.sst
deleted file mode 100644
index 959fbcf6..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_remote.sst
+++ /dev/null
@@ -1,88 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: Remote Operations
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: electronic documents:SiSU:document:remote;SiSU:manual:remote;electronic documents:SiSU:manual:remote;SiSU:document:remote;SiSU:document:remote
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? SiSU Remote Operations
-
-1~remote_source Remote Source Documents
-
-SiSU processing instructions can be run against remote source documents by providing the url of the documents against which the processing instructions are to be carried out. The remote SiSU documents can either be sisu marked up files in plaintext .sst or .ssm or; zipped sisu files, sisupod.zip or filename.ssp
-
-!_ .sst / .ssm - sisu text files
-
-SiSU can be run against source text files on a remote machine, provide the processing instruction and the url. The source file and any associated parts (such as images) will be downloaded and generated locally.
-
-code{
-
-sisu -3 http://[provide url to valid .sst or .ssm file]
-
-}code
-
-Any of the source documents in the sisu examples page can be used in this way, see http://www.jus.uio.no/sisu/SiSU/examples.html and use the url to the .sst for the desired document.
-
-NOTE: to set up a remote machine to serve SiSU documents in this way, images should be in the directory relative to the document source ../_sisu/image
-
-!_ sisupod - zipped sisu files
-
-A sisupod is the zipped content of a sisu marked up text or texts and any other associated parts to the document such as images.
-
-SiSU can be run against a sisupod on a (local or) remote machine, provide the processing instruction and the url, the sisupod will be downloaded and the documents it contains generated locally.
-
-code{
-
-sisu -3 http://[provide url to valid sisupod.zip or .ssp file]
-
-}code
-
-Any of the source documents in the sisu examples page can be used in this way, see http://www.jus.uio.no/sisu/SiSU/examples.html and use the url for the desired document.
-
-:C~ Remote Document Output
-
-1~remote_output Remote Output
-
-Once properly configured SiSU output can be automatically posted once generated to a designated remote machine using either rsync, or scp.
-
-In order to do this some ssh authentication agent and keychain or similar tool will need to be configured. Once that is done the placement on a remote host can be done seamlessly with the -r (for scp) or -R (for rsync) flag, which may be used in conjunction with other processing flags, e.g.
-
-code{
-
-sisu -3R sisu_remote.sst
-
-}code
-
-2~ commands
-
-!_ -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]

-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
-
-[expand on the setting up of an ssh-agent / keychain]
-
-1~remote_servers Remote Servers
-
-As SiSU is generally operated using the command line, and works within a Unix type environment, SiSU the program and all documents can just as easily be on a remote server, to which you are logged on using a terminal, and commands and operations would be pretty much the same as they would be on your local machine.
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_search.ssm b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_search.ssm
deleted file mode 100644
index 9c40a8bf..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_search.ssm
+++ /dev/null
@@ -1,35 +0,0 @@
-% SiSU master 4.0
-
-@title: SiSU
- :subtitle: Search
-
-@creator:
- :author: Ralph Amissah
-
-@date:
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :published: 2007-09-16
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? SiSU Search
-
-<< sisu_search_intro.ssi
-
-<< sisu_sql.ssi
-
-<< sisu_postgresql.sst
-
-<< sisu_sqlite.sst
-
-<< sisu_search_cgi.ssi
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_search_cgi.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_search_cgi.ssi
deleted file mode 100644
index 03eef9ff..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_search_cgi.ssi
+++ /dev/null
@@ -1,75 +0,0 @@
-% SiSU insert 2.0
-
-@title: SiSU
- :subtitle: Search
-
-@creator:
- :author: Ralph Amissah
-
-@date:
- :published: 2007-09-16
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2011-02-07
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? @title @creator
-
-:B~? SiSU Search
-
-:C~? CGI Search Form
-
-1~search_cgi Introduction
-
-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
-A small database and sample query front-end (search from) that makes use of the citation system, _{object citation numbering}_ to demonstrates functionality.~{ (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. }~
-
-SiSU can provide information on which documents are matched and at what locations within each document the matches are found. These results are relevant across all outputs using object citation numbering, which includes html, XML, EPUB, LaTeX, PDF and indeed the SQL database. You can then refer to one of the other outputs or in the SQL database expand the text within the matched objects (paragraphs) in the 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.~{ 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 and we can tell you which documents meet your search criteria, but there is no way we can tell you without opening each document where within each your matches are found. }~
-
-% 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

-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:
-
-_1 sisu --help sql
-
-code{
-
-Postgresql
- user: ralph
- current db set: SiSU_sisu
- port: 5432
- dbi connect: DBI:Pg:database=SiSU_sisu;port=5432
-
-sqlite
- current db set: /home/ralph/sisu_www/sisu/sisu_sqlite.db
- dbi connect DBI:SQLite:/home/ralph/sisu_www/sisu/sisu_sqlite.db
-
-}code
-
-Note on databases built
-
-By default, [unless otherwise specified] databases are built on a directory basis, from collections of documents within that directory. The name of the directory you choose to work from is used as the database name, i.e. if you are working in a directory called /home/ralph/ebook the database SiSU_ebook is used. [otherwise a manual mapping for the collection is necessary]
-
-2~ Search Form
-
-!_ sisu -F

-generates a sample search form, which must be copied to the web-server cgi directory
-
-!_ 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

-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/sisu_manual/en/sisu_search_intro.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_search_intro.ssi
deleted file mode 100644
index d5da379f..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_search_intro.ssi
+++ /dev/null
@@ -1,31 +0,0 @@
-% SiSU insert 2.0
-
-@title: SiSU
- :subtitle: Search
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2011-02-07
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? @title @creator
-
-:B~? SiSU Search
-
-1~search_intro SiSU Search - Introduction
-
-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.
-
-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.
-
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_short_feature_summary.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_short_feature_summary.ssi
deleted file mode 100644
index 294644af..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_short_feature_summary.ssi
+++ /dev/null
@@ -1,81 +0,0 @@
-% SiSU 2.0
-
-@title: SiSU
- :subtitle: Summary of Features
-
-@creator:
- :author: Ralph Amissah
-
-@date:
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :published: 2007-09-16
- :modified: 2011-02-07
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? @title @creator
-
-:B~? What is SiSU?
-
-:C~? Description
-
-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, epub, 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:
-
-_* HTML - both as a single scrollable text and a segmented document
-
-_* XHTML
-
-_* EPUB
-
-_* XML - both in sax and dom style xml structures for further development as required
-
-_* ODT - Open Document Format text, the iso standard for document storage
-
-_* LaTeX - used to generate pdf
-
-_* PDF (via LaTeX)
-
-_* SQL - population of an sql database (PostgreSQL or SQLite), (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, EPUB, 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, epub in 2009 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, EPUB, 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/markup-samples/sisu_manual/en/sisu_sql.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_sql.ssi
deleted file mode 100644
index 6e54275b..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_sql.ssi
+++ /dev/null
@@ -1,50 +0,0 @@
-% SiSU insert 2.0
-
-@title: SiSU
- :subtitle: SQL and Search
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :published: 2007-09-16
- :modified: 2011-02-07
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? SiSU Search
-
-:C~? Search
-
-1~search_sql SQL
-
-2~ populating SQL type databases
-
-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:
-
-_1* one containing semantic (and other) headers, including, title, author, subject, (the Dublin Core...);
-
-_1* another the substantive texts by individual "paragraph" (or object) - along with structural information, each paragraph being identifiable by its paragraph number (if it has one which almost all of them do), and the substantive text of each paragraph quite naturally being searchable (both in formatted and clean text versions for searching); and
-
-_1* a third containing endnotes cross-referenced back to the paragraph from which they are referenced (both in formatted and clean text versions for searching).
-
-_1* a fourth table with a one to one relation with the headers table contains full text versions of output, eg. pdf, html, xml, and ascii.
-
-There is of course the possibility to add further structures.
-
-At this level SiSU loads a relational database with documents chunked into objects, their smallest logical structurally constituent parts, as text objects, with their object citation number and all other structural information needed to construct the document. Text is stored (at this text object level) with and without elementary markup tagging, the stripped version being so as to facilitate ease of searching.
-
-Being able to search a relational database at an object level with the SiSU citation system is an effective way of locating content generated by SiSU. As individual text objects of a document stored (and indexed) together with object numbers, and all versions of the document have the same numbering, complex searches can be tailored to return just the locations of the search results relevant for all available output formats, with live links to the precise locations in the database or in html/xml documents; or, the structural information provided makes it possible to search the full contents of the database and have headings in which search content appears, or to search only headings etc. (as the Dublin Core is incorporated it is easy to make use of that as well).
-
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_sqlite.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_sqlite.sst
deleted file mode 100644
index a73ae16c..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_sqlite.sst
+++ /dev/null
@@ -1,82 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: Sqlite / search
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: electronic documents:SiSU:document:sqlite;SiSU:manual:sqlite;electronic documents:SiSU:manual:sqlite;SiSU:document:sqlite;SiSU:document:sqlite
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-@make:
- :manpage: section=7; name=sisu - package to install what sisu needs to to populate a postgresql database (postgresql dependency component); synopsis=sisu -dv [filename/wildcard ]\n sisu -dv [instruction]
-
-:A~? @title @creator
-
-% :B~? SiSU Sqlite
-
-1~sqlite Sqlite
-
-2~ Name
-
-SiSU - Structured information, Serialized Units - a document publishing system.
-
-
-2~ Description
-
-Information related to using sqlite with sisu (and related to the sisu_sqlite dependency package, which is a dummy package to install dependencies needed for SiSU to populate an sqlite database, this being part of SiSU - man sisu).
-
-2~ Synopsis
-
-_1 sisu -d [instruction] [filename/wildcard if required]
-
-_1 sisu -d --(sqlite|pg) --[instruction] [filename/wildcard if required]
-
-
-2~ Commands
-
-Mappings to two databases are provided by default, postgresql and sqlite, the same commands are used within sisu to construct and populate databases however -d (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, alternatively --sqlite or --pgsql may be used
-
-!_ -d or --sqlite
-may be used interchangeably.
-
-3~ create and destroy database
-
-!_ --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

-creates database where no database existed before
-
-!_ sisu -d --create

-creates database tables where no database tables existed before
-
-!_ 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

-destroys existing database and builds a new empty database structure
-
-3~ import and remove documents
-
-!_ 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]

-updates file contents in database
-
-!_ sisu -d --remove -v [filename/wildcard]

-removes specified document from sqlite database.
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_synopsis.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_synopsis.ssi
deleted file mode 100644
index 98e5d4f3..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_synopsis.ssi
+++ /dev/null
@@ -1,48 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: Commands
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :published: 2007-09-16
- :modified: 2011-02-07
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? @title @creator
-
-:B~? SiSU Commands
-
-1~ Synopsis
-
-SiSU - Structured information, Serialized Units - a document publishing system
-
-sisu [ -abcDdeFhIiMmNnopqRrSsTtUuVvwXxYyZz0-9 ] [ filename/ wildcard ]
-
-sisu [ -Ddcv ] [ instruction ]
-
-sisu [ -CcFLSVvW ]
-
-Note: commands should be issued from within the directory that contains the marked up files, cd to markup directory.
-
-sisu is at version 2, version 3 is under development. To use sisu version 3
-
-sisu --v3 [and options/operations as above]
-
-or
-
-sisu3 [and options/operations as above]
-
-sisu version 1 has been discontinued.
-
-for settings see sisu --help env
-
-sisu [ filename/ wildcard] == sisu -0 [filename/wildcard]
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_syntax_highlighting.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_syntax_highlighting.sst
deleted file mode 100644
index ef881aae..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_syntax_highlighting.sst
+++ /dev/null
@@ -1,151 +0,0 @@
-% SiSU insert 4.0
-
-@title: SiSU
- :subtitle: Syntax Highlighting
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :published: 2007-09-16
- :created: 2002-11-12
- :issued: 2002-11-12
- :available: 2002-11-12
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: electronic documents:SiSU:document:syntax highlighting;SiSU:manual:syntax highlighting;electronic documents:SiSU:manual:syntax highlighting;SiSU:document:syntax highlighting;SiSU:document:syntax highlighting
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-:A~? @title @creator
-
-:B~? SiSU Syntax Highlighting
-
-1~ Editor Files, Syntax Highlighting
-
-The directory:
-
-_1 ./data/sisu/conf/editor-syntax-etc/
-
-_1 /usr/share/sisu/conf/editor-syntax-etc
-
-contains rudimentary sisu syntax highlighting files for:
-
-_* (g)vim http://www.vim.org
-
-_1 package: sisu-vim
-
-status: largely done
-
-_1 there is a vim syntax highlighting and folds component
-
-_* gedit http://www.gnome.org/projects/gedit
-
-_* gobby http://gobby.0x539.de/
-
-_1 file: sisu.lang
-
-place in:
-
-_1 /usr/share/gtksourceview-1.0/language-specs
-
-or
-
-_1 ~/.gnome2/gtksourceview-1.0/language-specs
-
-_1 status: very basic syntax highlighting
-
-_1 comments: this editor features display line wrap and is used by Goby!
-
-_* nano http://www.nano-editor.org
-
-_1 file: nanorc
-
-save as:
-
-_1 ~/.nanorc
-
-_1 status: basic syntax highlighting
-
-_1 comments: assumes dark background; no display line-wrap; does line breaks
-
-_* diakonos (an editor written in ruby) http://purepistos.net/diakonos
-
-file: diakonos.conf
-
-save as:
-
-_1 ~/.diakonos/diakonos.conf
-
-includes:
-
-_1 status: basic syntax highlighting
-
-comments: assumes dark background; no display line-wrap
-
-_* kate & kwrite http://kate.kde.org
-
-_1 file: sisu.xml
-
-_1 place in:
-
-_2 /usr/share/apps/katepart/syntax
-
-_1 or
-
-_2 ~/.kde/share/apps/katepart/syntax
-
-_1 [settings::configure kate::{highlighting,filetypes}]
-
-_1 [tools::highlighting::{markup,scripts}::SiSU]
-
-% kde-config --prefix
-% KDEDIR/share/apps/katepart/syntax/
-% KDEHOME/share/apps/katepart/syntax
-% [In the configure dialog in kate, go to the "Editor->highlighting" page and
-% >select a highlight to change the mimetype/pattern associations for it.]
-% /etc/mime.types
-% /usr/share/mime/text
-
-_* nedit http://www.nedit.org
-
-_1 file: sisu_nedit.pats
-
-_1 nedit -import sisu_nedit.pats
-
-_1 status: a very clumsy first attempt [not really done]
-
-_1 comments: this editor features display line wrap
-
-_* emacs http://www.gnu.org/software/emacs/emacs.html
-
-_1 files: sisu-mode.el
-
-_1 to file ~/.emacs add the following 2 lines:
-
-_2 (add-to-list 'load-path "/usr/share/sisu/conf/editor-syntax-etc/emacs")
-
-_2 (require 'sisu-mode.el)
-
-_1 [not done / not yet included]
-
-_* vim & gvim http://www.vim.org
-
-_1 files:
-
-_1 package is the most comprehensive sisu syntax highlighting and editor environment provided to date (is for vim/ gvim, and is separate from the contents of this directory)
-
-_1 status: this includes: syntax highlighting; vim folds; some error checking
-
-_1 comments: this editor features display line wrap
-
-NOTE:
-
-[SiSU parses files with long lines or line breaks, but, display linewrap (without line-breaks) is a convenient editor feature to have for sisu markup]
-
-% aeditor (an editor written in ruby)
-
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_webrick.sst b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_webrick.sst
deleted file mode 100644
index 6e56e53a..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_webrick.sst
+++ /dev/null
@@ -1,59 +0,0 @@
-% SiSU 4.0
-
-@title: SiSU
- :subtitle: sisu_webrick
-
-@creator:
- :author: Amissah, Ralph
-
-@date:
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2007-08-28
- :published: 2007-09-16
- :modified: 2012-10-03
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-@classify:
- :topic_register: electronic documents:SiSU:document:webrick;SiSU:manual:webrick;electronic documents:SiSU:manual:webrick;SiSU:document:webrick;SiSU:document:webrick
- :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
-
-@make:
- :manpage: section=7; name=sisu - documents: structuring, publishing in multiple formats, and search; synopsis=sisu -W
-
-:A~? @title @creator
-
-:B~? SiSU Webrick
-
-1~webrick sisu_webrick
-
-2~ Name
-
-SiSU - Structured information, Serialized Units - a document publishing system
-
-2~ Synopsis
-
-sisu_webrick [port]
-
-or
-
-sisu -W [port]
-
-2~ Description
-
-sisu_webrick is part of SiSU (man sisu) sisu_webrick starts Ruby's Webrick web-server and points it to the directories to which SiSU output is written, providing a list of these directories (assuming SiSU is in use and they exist).
-
-The default port for sisu_webrick is set to 8081, this may be modified in the yaml file: ~/.sisu/sisurc.yml a sample of which is provided as /etc/sisu/sisurc.yml (or in the equivalent directory on your system).
-
-2~ Summary of man page
-
-sisu_webrick, may be started on it's own with the command: sisu_webrick [port] or using the sisu command with the -W flag: sisu -W [port]
-
-where no port is given and settings are unchanged the default port is 8081
-
-2~ Document processing command flags
-
-sisu -W [port] starts Ruby Webrick web-server, serving SiSU output directories, on the port provided, or if no port is provided and the defaults have not been changed in ~/.sisu/sisurc.yaml then on port 8081
diff --git a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_work_needed_and_wishlist.ssi b/data/doc/sisu/markup-samples/sisu_manual/en/sisu_work_needed_and_wishlist.ssi
deleted file mode 100644
index 20e774ac..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/en/sisu_work_needed_and_wishlist.ssi
+++ /dev/null
@@ -1,59 +0,0 @@
-% SiSU 2.0
-
-@title: SiSU
- :subtitle: Work Needed and Wishlist
-
-@creator:
- :author: Ralph Amissah
-
-@date:
- :created: 2002-08-28
- :issued: 2002-08-28
- :available: 2002-08-28
- :published: 2007-09-16
- :modified: 2011-02-07
-
-@rights:
- :copyright: Copyright (C) Ralph Amissah 2007
- :license: GPL 3 (part of SiSU documentation)
-
-:A~? @title @creator
-
-:B~? Work Needed and Wishlist
-
-1~sisu_work_needed Work Needed
-
-SiSU is fairly mature and for most purposes the syntax and what it is supposed to do is clear. For the most part additions and changes are minor and backward compatible, (in particular there may be things of interest that to be able to achieve will require additions to the syntax).
-
-_* Amongst the most requested features is a way to represent and extract bibliographies from scholarly and other writings. This involves an extension of sisu markup syntax and a new module to extract the bibliography.
-
-_* Integration of postgresql tsearch2 / gin indexing, (which currently needs to be done manually, and) which has been waiting for the integration of tsearch2 / gin into Postgresql main, which is supposed to occur in Postgresql 8.3
-
-_* Internationalisation always. SiSU is utf-8 and for those parts that are utf-8 friendly will work out of the box - html and postgresql for example work out of the box (and for example comfortably represent Chinese text), LaTeX and odf do not work out of the box, they need additional work for extended language sets.
-
-_* Refinements and improvements to output representations, some are fairly mature, others (such as manpages and info files (and even ODF) remain young.
-
-_* Simple extension to contain, link and share included audio and multi-media files, (including sisupod.zip)
-
-1~sisu_wishlist Wishlist
-
-SiSU provides a lot of "plumbing" and is readily usable as a tool by those comfortable with marking up documents with an editor. The syntax is fairly easy to learn, especially the subset required to start using SiSU effectively.
-
-SiSU might also be of interest to developers interested in:
-
-_* experimenting with the search implications offered
-
-_* producing additional output formats
-
-_* producing conversion tools
-
-_* producing input interfaces, (experimenting with additional interfaces for producing sisu source documents)
-
-Several tools that are of interest would come under the heading interface and conversion. Amongst others, the following are of interest:
-
-_* Converters from various document formats, such as Open Document Text (ODF), MS Word(TM) and Word Perfect(TM), even html. The problem here is one of the most important things for SiSU is to be able to recognise the structure of a document, and many documents prepared in other formats have not been prepared strictly with a view to representing structure, but appearance - so heading levels may be "painted" to look right rather than have the correct structural representation. Even if conversion is not perfect this may serve as a first step in assisting in conversion of documents to SiSU for those with legacy document sets that they would like to have in sisu format. (once in SiSU it is easier to get out in various other formats as this is what sisu does, within the constraints of the information that sisu uses to generate output)
-
-_* The possibility to save directly from from various word processors, and possibly templates within them to assist in making sure the document structure is "understood" by SiSU.
-
-_* Web interface/front-end, a form like front end for the writing or submission of sisu documents to a server which uses SiSU to generate output. Headers could be made available as separate small entry forms with help provided to explain where they might be used. Apart from the most important headers such as title, author, date and possibly subject the remainder of the header forms could be placed after the form for substantive content. This would offer a more Web 2.0 like approach to the use of SiSU and the possibility of using it for collaborative editing of content (possibly for documents that are to be finalised/published as the citation system is most suited to published works). [Collaborative editing is currently possible through use of a collaborative editor such as Gobby which makes use of the Obby protocol].
-
diff --git a/data/doc/sisu/markup-samples/sisu_manual/translation_languages b/data/doc/sisu/markup-samples/sisu_manual/translation_languages
deleted file mode 100644
index d84a94e8..00000000
--- a/data/doc/sisu/markup-samples/sisu_manual/translation_languages
+++ /dev/null
@@ -1 +0,0 @@
-de fr es ja ru zh
--
cgit v1.2.3

From e13aacbf91c5794db64d77e100d1974e2c435475 Mon Sep 17 00:00:00 2001
From: Ralph Amissah
Date: Wed, 5 Feb 2014 01:22:17 -0500
Subject: sisu manual update

---
data/doc/sisu/CHANGELOG_v5 | 1 +
data/doc/sisu/CHANGELOG_v6 | 1 +
data/doc/sisu/markup-samples/manual/en/README.ssm | 39 +++++
data/doc/sisu/markup-samples/manual/en/sisu.ssm | 4 +-
.../markup-samples/manual/en/sisu_commands.sst | 13 +-
.../markup-samples/manual/en/sisu_description.sst | 24 ++-
.../markup-samples/manual/en/sisu_install_run.sst | 186 +++++++++++++++++++++
.../markup-samples/manual/en/sisu_introduction.sst | 36 ++--
.../sisu/markup-samples/manual/en/sisu_manual.ssm | 6 +-
9 files changed, 277 insertions(+), 33 deletions(-)
create mode 100644 data/doc/sisu/markup-samples/manual/en/README.ssm
create mode 100644 data/doc/sisu/markup-samples/manual/en/sisu_install_run.sst

diff --git a/data/doc/sisu/CHANGELOG_v5 b/data/doc/sisu/CHANGELOG_v5
index 890f1758..e79f97ca 100644
--- a/data/doc/sisu/CHANGELOG_v5
+++ b/data/doc/sisu/CHANGELOG_v5
@@ -64,6 +64,7 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_5.3.1.orig.tar.xz

* documentation, manpage README etc.
* sisu manual directory moved
+ * sisu manual updated
* removed html man pages (man2html)

%% 5.3.0.orig.tar.xz (2014-01-26:03/7)
diff --git a/data/doc/sisu/CHANGELOG_v6 b/data/doc/sisu/CHANGELOG_v6
index c09040a6..23925664 100644
--- a/data/doc/sisu/CHANGELOG_v6
+++ b/data/doc/sisu/CHANGELOG_v6
@@ -54,6 +54,7 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_6.0.1.orig.tar.xz

* documentation, manpage README etc.
* sisu manual directory moved
+ * sisu manual updated
* removed html man pages (man2html)

%% 6.0.0.orig.tar.xz (2014-01-26:03/7)
diff --git a/data/doc/sisu/markup-samples/manual/en/README.ssm b/data/doc/sisu/markup-samples/manual/en/README.ssm
new file mode 100644
index 00000000..fc67fdb8
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/README.ssm
@@ -0,0 +1,39 @@
+% SiSU master 5.0
+
+@title: SiSU
+ :subtitle: README
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2014-02-02
+ :created: 2014-02-02
+ :available: 2014-02-02
+ :modified: 2014-02-02
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2014
+ :license: GPL 3 (part of SiSU documentation)
+
+@classify:
+ :topic_register: SiSU:manual;electronic documents:SiSU:README
+ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
+
+:A~ @title
+
+:B~ Introduction
+
+<< sisu_introduction.sst
+
+:B~ Install or Run without Installation
+
+<< sisu_install_run.sst
+
+:B~ Commands
+
+<< sisu_commands.sst
+:B~ Markup
+
+<< sisu_markup.sst
+
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu.ssm b/data/doc/sisu/markup-samples/manual/en/sisu.ssm
index 79703fef..c8260858 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu.ssm
+++ b/data/doc/sisu/markup-samples/manual/en/sisu.ssm
@@ -1,4 +1,4 @@
-% SiSU master 4.0
+% SiSU master 5.0

@title: SiSU
:subtitle: Manual
@@ -11,7 +11,7 @@
:created: 2002-08-28
:issued: 2002-08-28
:available: 2002-08-28
- :modified: 2012-10-03
+ :modified: 2014-02-05

@rights:
:copyright: Copyright (C) Ralph Amissah 2012
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_commands.sst b/data/doc/sisu/markup-samples/manual/en/sisu_commands.sst
index 2ca43a43..be491bf8 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_commands.sst
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_commands.sst
@@ -1,4 +1,4 @@
-% SiSU 4.0
+% SiSU 5.0

@title: SiSU
:subtitle: Commands
@@ -11,7 +11,7 @@
:issued: 2002-08-28
:available: 2002-08-28
:published: 2007-09-16
- :modified: 2012-10-03
+ :modified: 2014-02-05

@rights:
:copyright: Copyright (C) Ralph Amissah 2012
@@ -159,6 +159,9 @@ produces html output, the document in a single file (scroll.html) only. Compare
!_ --html-seg [filename/wildcard] \\
produces html output, segmented text with table of contents (toc.html and index.html). Compare --html-scroll and --html

+!_ --html-strict [filename/wildcard] \\
+produces html with --strict option. see --strict
+
!_ -I [filename/wildcard] \\
see --texinfo

@@ -221,6 +224,9 @@ see --exc-*
!_ -o [filename/wildcard/url] \\
see --odt

+!_ --ocn \\
+see --inc-ocn and --exc-ocn
+
!_ --odf [filename/wildcard/url] \\
see --odt

@@ -324,6 +330,9 @@ produces a zipped file of the prepared document specified along with associated
!_ --source [filename/wildcard] \\
copies sisu markup file to output directory. Alias -s

+!_ --strict \\
+together with --html, produces more w3c compliant html, for example not having purely numeric identifiers for text, the location object url#33 becomes url#o33
+
!_ -T [filename/wildcard (*.termsheet.rb)] \\
standard form document builder, preprocessing feature

diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_description.sst b/data/doc/sisu/markup-samples/manual/en/sisu_description.sst
index 9f8fdcd8..128bfe1e 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_description.sst
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_description.sst
@@ -1,4 +1,4 @@
-% SiSU 4.0
+% SiSU 5.0

@title: SiSU - SiSU information Structuring Universe / Structured information, Serialized Units
:subtitle: Description
@@ -11,7 +11,7 @@
:issued: 2002-11-12
:available: 2002-11-12
:published: 2007-08-30
- :modified: 2012-10-03
+ :modified: 2014-02-05

@rights:
:copyright: Copyright (C) Ralph Amissah 2007
@@ -29,6 +29,26 @@

2~ Outline

+SiSU is a framework for document structuring, publishing (in multiple open standard formats) 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 (including the population of sql databases) 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 (GPLv3). Its use case for development is work with medium to large document sets and cope with evolving document formats/ representation technologies. Documents are prepared once, and generated as need be to update the technical presentation or add additional output formats. Various output formats (including search related output) share a common mechanism for cross-output-format citation.
+
+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, EPUB, ODT (Open Document Format text), LaTeX, landscape and portrait PDF, 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.
+
+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 (to take advantage of the strengths of different ways of representing documents) various standard open output formats including plain text, HTML, XHTML, XML, EPUB, ODT, 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, 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. }~ the different forms of output requested.
+
+SiSU works with an abstraction of the document based on its structure which is comprised of its headings~{ the different heading levels }~ and objects~{ units of text, primarily paragraphs and headings, also any tables, poems, code-blocks }~, 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 basis for citing material within a document across the different output format types. This is significant as page numbers are not well suited to the digital age, in web publishing, changing a browser's default font or using a different browser can mean that text will appear on a different page; and publishing in different formats, html, landscape and portrait pdf etc. again page numbers are not useful to cite text. Dealing with documents at an object level together with object numbering also has implications for search that SiSU is able to take advantage of.
+
+One of the challenges of maintaining documents is to keep them in a format that allows use of them independently of proprietary platforms. Consider issues related to 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 producing documents in multiple non-proprietary open formats including HTML, EPUB,~{ An open standard format for e-books }~ ODT,~{ Open Document Format (ODF) text }~ PDF~{ Specification submitted by Adobe to ISO to become a full open ISO specification \\ http://www.linux-watch.com/news/NS7542722606.html }~ ODF,~{ ISO standard 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 GPLv3 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 when it became an ISO standard for office applications and the archival of documents), EPUB was introduced in 2009; and allows the technical representations 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).
+
+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 thesauri, 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.
+
+% SiSU is a way of preparing, publishing, managing and searching documents.
+
SiSU is a flexible document preparation, generation publishing and search system.~{ This information was first placed on the web 12 November 2002; with predating material taken from http://www.jus.uio.no/lm/lm.information/toc.html part of a site started and developed since 1993. See document metadata section http://www.jus.uio.no/sisu/SiSU/metadata.html or manifest page http://www.jus.uio.no/sisu/SiSU/sisu_manifest.html for information on this version. Dates related to the development of SiSU may be tracked in the http://www.jus.uio.no/sisu/SiSU/changelog.html or the Git repository http://git.sisudoc.org/?p=code/sisu.git;a=summary some of the more significant events may be contained within the Chronology section of this document http://www.jus.uio.no/sisu/sisu_chronology }~

SiSU ("SiSU information Structuring Universe" or "Structured information, Serialized Units"),~{ also chosen for the meaning of the Finnish term "sisu". }~ is a Unix command line oriented framework for document structuring, publishing and search. Featuring minimalistic markup, multiple standard outputs, a common citation system, and granular search.
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
new file mode 100644
index 00000000..dfd56ec8
--- /dev/null
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_install_run.sst
@@ -0,0 +1,186 @@
+% SiSU insert 5.0
+
+@title: SiSU
+ :subtitle: Installation
+
+@creator:
+ :author: Amissah, Ralph
+
+@date:
+ :published: 2007-09-16
+ :created: 2002-11-12
+ :issued: 2002-11-12
+ :available: 2002-11-12
+ :modified: 2014-02-05
+
+@rights:
+ :copyright: Copyright (C) Ralph Amissah 2007
+ :license: GPL 3 (part of SiSU documentation)
+
+:A~? SiSU Installation notes
+
+1~source_tarball Source tarball
+
+2~ run off source package directory tree (without installing)
+
+1. Download the latest source (information available) from: http://www.jus.uio.no/sisu/SiSU/download.html#current
+
+2. Unpack the source
+
+Provided you have Ruby, SiSU can be run without installation straight from the source package directory tree. Run ruby against the full path to bin/sisu (in the unzipped source package directory tree)
+
+Note however, that additional external package dependencies, such as texlive (for pdfs), sqlite3 or postgresql (for search) should you desire to use them are not taken care of for you.
+
+2~ Gem install (with rake)
+
+Gem install, you need to:
+
+(i) create the gemspec; (ii) build the gem (from the gemspec); (iii) install the gem
+
+Provided you have ruby & rake, this can be done with the single command:
+
+_1 rake gem_create_build_install # (to build and install sisu v5 & sisu v6, alias gemcbi)
+
+separate gems are made/installed for sisu v5 & sisu v6 contained in source:
+
+_1 rake gem_create_build_install_stable # (to build and install sisu v5, alias gem5cbi)
+
+_1 rake gem_create_build_install_unstable # (to build and install sisu v6, alias gem6cbi)
+
+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
+
+_1 sisu _6.0.0_ --version
+
+to uninstall sisu installed via gem
+
+_1 sudo gem uninstall --verbose sisu
+
+For a list of alternative actions you may type:
+
+_1 rake help
+
+_1 rake -T
+
+Rake: http://rake.rubyforge.org/ http://rubyforge.org/frs/?group_id=50
+
+Rant: http://make.rubyforge.org/ http://rubyforge.org/frs/?group_id=615
+
+2~ installation with setup.rb
+
+It should also be possible to install sisu using setup.rb
+
+this is a three step process, in the root directory of the unpacked SiSU as root type:
+
+``` code
+ruby setup.rb config
+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
+
+_1 ruby setup.rb config && ruby setup.rb setup && sudo ruby setup.rb install
+
+1~distribution_install Unix/Linux Distribution
+
+A distribution install should take care of the dependencies of sisu for producing various outputs.
+
+2~ Debian
+
+SiSU is available off the Debian archives. It should necessary only to run as root, Using apt-get:
+
+code{
+
+ apt-get update
+
+ apt get install sisu-complete
+
+}code
+
+(all sisu dependencies should be taken care of)
+
+If there are newer versions of SiSU upstream, they will be available by
+adding the following to your sources list /etc/apt/sources.list *~sources.list
+
+code{
+
+#/etc/apt/sources.list
+
+deb http://www.jus.uio.no/sisu/archive unstable main non-free
+deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
+
+}code
+
+The non-free section is for sisu markup samples provided, which contain authored works the substantive text of which cannot be changed, and which as a result do not meet the debian free software guidelines.
+
+SiSU is developed on Debian, and packages are available for Debian that take care of the dependencies encountered on installation.
+
+The package is divided into the following components:
+
+_1 *sisu*, the base code, (the main package on which the others depend), without any dependencies other than ruby (and for convenience the ruby webrick web server), this generates a number of types of output on its own, other packages provide additional functionality, and have their dependencies
+
+_1 *sisu-complete*, a dummy package that installs the whole of greater sisu as described below, apart from sisu-examples
+
+_1 *sisu-pdf*, dependencies used by sisu to produce pdf from LaTeX generated
+
+_1 *sisu-postgresql*, dependencies used by sisu to populate postgresql database (further configuration is necessary)
+
+_1 *sisu-sqlite*, dependencies used by sisu to populate sqlite database
+
+_1 *sisu-markup-samples*, sisu markup samples and other miscellany (under Debian Free Software Guidelines non-free)
+
+SiSU is available off { Debian Unstable and Testing }http://packages.debian.org/cgi-bin/search_packages.pl?searchon=names&subword=1&version=all&release=all&keywords=sisu ~{ http://packages.qa.debian.org/s/sisu.html }~ install it using apt-get, aptitude or alternative Debian install tools. *~apt-get
+
+1~dependencies Dependencies
+
+Here is a list of sisu's current dependencies,~{from the Debian control file}~ which depend on such factors as whether you want to generate pdf, whether you will be using SiSU with or without a database, ...). sisu_markup-samples may also be of interest.
+
+``` code
+Package: sisu
+Depends: ruby | ruby-interpreter, openssl, rsync, unzip, zip
+Recommends: sisu-pdf, sisu-sqlite, sisu-postgresql, imagemagick |
+graphicsmagick, keychain, openssh-client | lsh-client, po4a, qrencode, rake,
+ruby-rmagick, tidy, tree, vim-addon-manager
+Suggests: lv, calibre, pinfo, poedit, texinfo, trang
+```
+
+``` code
+Package: sisu-complete
+Depends: ruby | ruby-interpreter, sisu (= ${source:Version}), sisu-pdf (=
+${source:Version}), sisu-postgresql (= ${source:Version}), sisu-sqlite (=
+${source:Version})
+Description-en: installs all SiSU related packages
+```
+
+``` code
+Package: sisu-pdf
+Depends: ruby | ruby-interpreter, sisu (= ${source:Version}),
+texlive-latex-base, texlive-fonts-recommended, texlive-generic-recommended,
+texlive-latex-recommended, texlive-latex-extra, texlive-math-extra,
+texlive-xetex, fonts-liberation, lmodern, latex-cjk-all, texlive-lang-cjk
+Suggests: evince | pdf-viewer
+```
+
+``` code
+Package: sisu-postgresql
+Depends: ruby | ruby-interpreter, sisu (= ${source:Version}), postgresql,
+ruby-dbd-pg, ruby-dbi, ruby-fcgi
+Suggests: postgresql-contrib
+```
+
+``` code
+Package: sisu-sqlite
+Depends: ruby | ruby-interpreter, sisu (= ${source:Version}), sqlite3,
+ruby-sqlite3, ruby-dbd-sqlite3, ruby-dbi, ruby-fcgi
+```
+
+``` code
+Package: sisu-markup-samples
+Depends: sisu
+```
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_introduction.sst b/data/doc/sisu/markup-samples/manual/en/sisu_introduction.sst
index 8978ace6..1fc14d9a 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_introduction.sst
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_introduction.sst
@@ -1,4 +1,4 @@
-% SiSU 4.0
+% SiSU 5.0

@title: SiSU
:subtitle: Introduction
@@ -11,7 +11,7 @@
:created: 2002-08-28
:issued: 2002-08-28
:available: 2002-08-28
- :modified: 2012-10-03
+ :modified: 2014-02-05

@rights:
:copyright: Copyright (C) Ralph Amissah 2011
@@ -24,32 +24,20 @@

:B~? What is SiSU?

-:C~? Description
-
1~sisu_intro Introduction - What is SiSU?

-SiSU is a framework for document structuring, publishing (in multiple open standard formats) 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 (including the population of sql databases) 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 (GPLv3). Its use case for development is work with medium to large document sets and cope with evolving document formats/ representation technologies. Documents are prepared once, and generated as need be to update the technical presentation or add additional output formats. Various output formats (including search related output) share a common mechanism for cross-output-format citation.
-
-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, EPUB, ODT (Open Document Format text), LaTeX, landscape and portrait PDF, 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.
-
-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 (to take advantage of the strengths of different ways of representing documents) various standard open output formats including plain text, HTML, XHTML, XML, EPUB, ODT, 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, 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. }~ the different forms of output requested.
-
-SiSU works with an abstraction of the document based on its structure which is comprised of its headings~{ the different heading levels }~ and objects~{ units of text, primarily paragraphs and headings, also any tables, poems, code-blocks }~, 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 basis for citing material within a document across the different output format types. This is significant as page numbers are not well suited to the digital age, in web publishing, changing a browser's default font or using a different browser can mean that text will appear on a different page; and publishing in different formats, html, landscape and portrait pdf etc. again page numbers are not useful to cite text. Dealing with documents at an object level together with object numbering also has implications for search that SiSU is able to take advantage of.
-
-One of the challenges of maintaining documents is to keep them in a format that allows use of them independently of proprietary platforms. Consider issues related to 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 producing documents in multiple non-proprietary open formats including HTML, EPUB,~{ An open standard format for e-books }~ ODT,~{ Open Document Format (ODF) text }~ PDF~{ Specification submitted by Adobe to ISO to become a full open ISO specification
http://www.linux-watch.com/news/NS7542722606.html }~ ODF,~{ ISO standard 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 GPLv3 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 when it became an ISO standard for office applications and the archival of documents), EPUB was introduced in 2009; and allows the technical representations 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 is a lightweight markup based document creation and publishing framework that is controlled from the command line. Prepare documents for SiSU using your text editor of choice, then use SiSU to generate various output document formats.

-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 thesauri, together with the flexibility of SiSU offers great possibilities.
+From a single lightly prepared document (plain-text UTF-8) 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. SiSU produces: plain-text, HTML, XHTML, XML, EPUB, ODF:ODT (Opendocument), LaTeX, PDF, and populates an SQL database (PostgreSQL or SQLite) with text objects, roughly, paragraph sized chunks so that document searches are done at this level of granularity.

-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.
+Outputs share a common citation numbering system, associated with text objects and any semantic meta-data provided about the document.

-http://www.sisudoc.org/
+SiSU also provides concordance files, document content certificates and manifests of generated output. Book indexes may be made.

-http://www.jus.uio.no/sisu
+Some document markup samples are provided in the package sisu-markup-samples.

-% SiSU is a way of preparing, publishing, managing and searching documents.
+``` group
+Homepages:
+* http://www.sisudoc.org/
+* http://www.jus.uio.no/sisu
+```
diff --git a/data/doc/sisu/markup-samples/manual/en/sisu_manual.ssm b/data/doc/sisu/markup-samples/manual/en/sisu_manual.ssm
index 90e8a323..46d80198 100644
--- a/data/doc/sisu/markup-samples/manual/en/sisu_manual.ssm
+++ b/data/doc/sisu/markup-samples/manual/en/sisu_manual.ssm
@@ -1,4 +1,4 @@
-% SiSU master 4.0
+% SiSU master 5.0

@title: SiSU
:subtitle: Manual
@@ -11,7 +11,7 @@
:created: 2002-08-28
:issued: 2002-08-28
:available: 2002-08-28
- :modified: 2012-10-03
+ :modified: 2014-02-05

@rights:
:copyright: Copyright (C) Ralph Amissah 2007
@@ -77,7 +77,7 @@

<< sisu_download.ssi

-<< sisu_installation.ssi
+<< sisu_install_run.sst

<< sisu_quickstart.sst

--
cgit v1.2.3

From 4e7fb32481df6e47db28888ff1e8a63d39aa92c4 Mon Sep 17 00:00:00 2001
From: Ralph Amissah
Date: Wed, 5 Feb 2014 01:27:25 -0500
Subject: README & manpage (sisu.1) update

---
README | 2469 +++++++++++++++++++++++++++++++++++++-------
data/doc/sisu/CHANGELOG_v5 | 1 +
data/doc/sisu/CHANGELOG_v6 | 1 +
man/man1/sisu.1 | 209 +---
4 files changed, 2141 insertions(+), 539 deletions(-)

diff --git a/README b/README
index 624f370c..e0550c83 100644
--- a/README
+++ b/README
@@ -1,518 +1,2235 @@
-%% SiSU versions 4 & 3, 2011
-Homepage:
-* README
-* CHANGELOGS/CHANGELOG_v4
-* CHANGELOGS/CHANGELOG_v3
-* CHANGELOGS/CHANGELOG_v2
-* CHANGELOGS/CHANGELOG_v1
-
-Herein (this package) reside SiSU versions 4 and 3.
-
-%% Description
----------------
-
- SiSU is lightweight markup based document creation and publishing framework
- that is controlled from the command line. Prepare documents for SiSU using
- your text editor of choice, then use SiSU to generate various output document
- formats.
+SISU - README
+=============

- With minimal preparation of a plain-text (UTF-8) file using its native
- markup-syntax, SiSU produces: plain-text, HTML, XHTML, XML, EPUB (v2 only)
- ODF:ODT (Opendocument), LaTeX, PDF, and populates an SQL database (PostgreSQL
- or SQLite) with text objects, roughly, paragraph sized chunks so that
- document searches are done at this level of granularity.
+INTRODUCTION
+************

- Outputs share a common citation numbering system, associated with text
- objects and any semantic meta-data provided about the document.
+INTRODUCTION - WHAT IS SISU?
+----------------------------

- SiSU also provides concordance files, document content certificates and
- manifests of generated output. Book indexes may be made.
+*SiSU* is a lightweight markup based document creation and publishing framework
+that is controlled from the command line. Prepare documents for *SiSU* using
+your text editor of choice, then use *SiSU* to generate various output document
+formats.

- SiSU takes advantage of well established open standard ways of representing
- text, and provides a bridge to take advantage of the strengths of each,
- while retaining minimal markup requirement. SiSU implements a "useful
- common feature set" across document formats [coming from a humanities, law,
- and possibly social sciences perspective, rather than technical or
- scientific writing] ... focus is primarily on content and data integrity
- rather than appearance, (though outputs in the various formats are
- respectable).
+From a single lightly prepared document (plain-text /UTF-8/) 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. *SiSU* produces: plain-text, /HTML/, /XHTML/,
+/XML/, /EPUB/, /ODF/: /ODT/ (Opendocument), /LaTeX/, /PDF/, and populates an
+/SQL/ database (/PostgreSQL/ or /SQLite/) with text objects, roughly, paragraph
+sized chunks so that document searches are done at this level of granularity.

- Syntax highlighting files for a number of editors are provided.
- A vim syntax highlighting file and an ftplugin with folds for sisu markup is
- provided. Vim 7 includes syntax highlighting for SiSU.
+Outputs share a common citation numbering system, associated with text objects
+and any semantic meta-data provided about the document.

- man pages, and interactive help are provided.
+*SiSU* also provides concordance files, document content certificates and
+manifests of generated output. Book indexes may be made.

- Dependencies for various features are taken care of in sisu related packages.
- The package sisu-complete installs the whole of SiSU.
+Some document markup samples are provided in the package sisu -markup-samples.

- Additional document markup samples are provided in the package
- sisu-markup-samples which is found in the non-free archive the licenses for
- the substantive content of the marked up documents provided is that provided
- by the author or original publisher.
+Homepages:
+*
+*

- Homepage:
+INSTALL OR RUN WITHOUT INSTALLATION
+***********************************

-%% Take 2
----------
+SOURCE TARBALL
+--------------

-The ideas behind SiSU evolved working with managing static, published documents
-that needed to be citable, ideally searchable and preferably available in
-multiple formats over a period of time with a rapidly changing World Wide Web.
-Initial experience was in 1993, one issue being that the document content
-remained the same, but presentation needed to be updated with changing formats,
-html in particular has really changed since then.
+RUN OFF SOURCE PACKAGE DIRECTORY TREE (WITHOUT INSTALLING)
+..........................................................

-So the idea was to provide a minimal markup requirement for documents that
-remained the same, and a generator to convert that markup custom producing
-various output types. This made it possible to:
+1. Download the latest source (information available) from:
+

-* have a marked-up document set and continue improving the presentation, as the
-generators code was updated, e.g. update HTML as it evolves, and improve upon
-LaTeX driven pdf output
+2. Unpack the source

-* have available new document formats/ output types as they came to be of
-interest, e.g. version 2 includes EPUB
+Provided you have *Ruby*, *SiSU* can be run without installation straight from
+the source package directory tree. Run ruby against the full path to bin/sisu
+(in the unzipped source package directory tree)

-* produce a citation system that is available across different output types,
-text based on objects (rather than page numbers), i.e. you can accurately and
-reliably cite text within a document regardless of the document format version
-that is being looked at
+Note however, that additional external package dependencies, such as texlive
+(for pdfs), sqlite3 or postgresql (for search) should you desire to use them
+are not taken care of for you.

-* take advantage of the strengths of disparate technologies representing text,
-each output type being custom generated for that format, the object citation
-system lends itself as a result is that there is little necessity that one
-output type should be based on or related to another, just that the content is
-preserved and presented in a way that is well suited to the output type in
-question
+GEM INSTALL (WITH RAKE)
+.......................

-* produce consistent quality presentation for material, suitable where
-substance/content is more important than appearance, there is some sacrifice of
-flexibility and no concept of wysiwyg, e.g. there is no attempt to make pdf
-output identical to html, rather the system attempts to take advantage of
-making the best presentation it can in each output format taking advantage of
-the strengths of that format available to it given the minimal markup (sisu
-document preparation); the citation system ensures you can pinpoint the same
-text
+Gem install, you need to:

-SiSU works best:
+(i) create the gemspec; (ii) build the gem (from the gemspec); (iii) install
+the gem

-* with published works (e.g. books, articles), static documents the content of
-which is changed rarely, and ideally when they do in the form of a new edition.
+Provided you have ruby & rake, this can be done with the single command:

-* for literature and law related content
+ rake gem_create_build_install # (to build and install sisu v5 & sisu v6,
+ alias gemcbi)

-SiSU uses Unicode, utf-8 where it is available,
------
+separate gems are made/installed for sisu v5 & sisu v6 contained in source:

-SiSU - simple information structuring universe, is a publishing tool, document
-generation and management, (and search enabling) tool primarily for literary,
-academic and legal published works.
+ rake gem_create_build_install_stable # (to build and install sisu v5, alias
+ gem5cbi)

-SiSU can be used for Internet, Intranet, local filesystem or cd publishing.
+ rake gem_create_build_install_unstable # (to build and install sisu v6, alias
+ gem6cbi)

-SiSU can be used directly off the filesystem, or from a database.
+for individual steps (create, build, install) see rake options, rake -T to
+specify sisu version for sisu installed via gem

-SiSU's scalability, is be dependent on your hardware, and filesystem and/or
-database Postgresql.
+ sisu _5.3.0_ --version

-Amongst it's characteristics are:
+ sisu _6.0.0_ --version

-* simple mnemonoic markup style,
+to uninstall sisu installed via gem

-* the ability to produce multiple output formats, including html, XML, EPUB,
-LaTeX, pdf (via LaTeX), stream to a relational database whilst retaining
-document structure - Postgresql and Sqlite,
+ sudo gem uninstall --verbose sisu

-* that all share a common citation system (a simple idea from which much good),
-possibly most exciting, the following: if fed into a relational database (as it
-can be automatically), the document set is searchable, with results displayed
-at a paragraph level, or the possibility of an indexed display of documents
-identifying the paragraph in which the match is found (using the object
-citation numbering system) together with a hyperlinked listing for each of each
-paragraph in which the match is found. In any event citations using this system
-(with or without the relational database) are relevant for all output formats.
+For a list of alternative actions you may type:

-* it is command line driven, and can be set up on a remote server
+ rake help

-* Documents are marked up in SiSU syntax in your favourite editor. SiSU syntax
-may be regarded as a type of smart ascii - which in its basic form is simpler
-than the most elementary html. There is currently a syntax highlighter, and
-folding for Vim. Syntax highlighters for other editors are welcome.
+ rake -T

-Input files should be UTF-8
+Rake:

-Once set up it is simple to use.
+Rant:

-%% Information, places to look
----------------
+INSTALLATION WITH SETUP.RB
+..........................

-Within the SiSU tarball:
+It should also be possible to install sisu using setup.rb

- ./data/doc/sisu/v2/sisu_markup_samples/sisu_manual
+this is a three step process, in the root directory of the unpacked *SiSU* as
+root type:

-Once installed, directory equivalent to:
+ruby setup.rb config
+ruby setup.rb setup
+#[as root:]
+ruby setup.rb install

-

-Available man pages are converted back to html using man2html:
+further information:
+
+

-
+ ruby setup.rb config && ruby setup.rb setup && sudo ruby setup.rb install

- ./data/doc/sisu/v2/html/
+UNIX/LINUX DISTRIBUTION
+-----------------------

-%% Online Information, places to look
----------------
+A distribution install should take care of the dependencies of sisu for
+producing various outputs.

-
+DEBIAN
+......

-Download Sources:
-
-
+*SiSU* is available off the *Debian* archives. It should necessary only to run
+as root, Using apt-get:

-%% Installation
----------------
-NB. Platform is Unix / Linux.
+ apt-get update

-%% Debian
----------------
-If you use Debian use the Debian packages,
-check the information at:
-
+ apt get install sisu-complete

-(A) SiSU is available directly off the Debian archives for Sid and testing. It
-should necessary only to run as root:

- aptitude update
- aptitude install sisu-complete
+(all sisu dependencies should be taken care of)

-(B) If there are newer versions of SiSU upstream of the Debian archives, they
-will be available by adding the following to your /etc/apt/sources.list
+If there are newer versions of *SiSU* upstream, they will be available by
+adding the following to your sources list /etc/apt/sources.list

- deb http://www.jus.uio.no/sisu/archive unstable main non-free
- deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
+#/etc/apt/sources.list

- [the non-free line is for document markup
- samples, for which the substantive text is
- provided under the author or original
- publisher's license and which in most cases will
- not be debian free software guideline compliant]
+deb http://www.jus.uio.no/sisu/archive unstable main non-free
+deb-src http://www.jus.uio.no/sisu/archive unstable main non-free

-Then as root run:
- aptitude update
- aptitude install sisu-complete

-%% RPM
----------------
-RPMs are provided though untested, they are prepared by running alien against the
-source package, and against the debs.
+The non-free section is for sisu markup samples provided, which contain
+authored works the substantive text of which cannot be changed, and which as a
+result do not meet the debian free software guidelines.

-They may be downloaded from:
-
+*SiSU* is developed on *Debian*, and packages are available for *Debian* that
+take care of the dependencies encountered on installation.

-%% Source package .tgz
----------------
-Otherwise to install SiSU from source, check information at:
-
+The package is divided into the following components:

-alternative modes of installation from source are provided,
-setup.rb (by Minero Aoki),
-rake (by Jim Weirich) built install file,
-rant (by Stefan Lang) built install file,
+ *sisu*, the base code, (the main package on which the others depend), without
+ any dependencies other than ruby (and for convenience the ruby webrick web
+ server), this generates a number of types of output on its own, other
+ packages provide additional functionality, and have their dependencies

-Ruby is the essential dependency for the basic operation of SiSU
+ *sisu-complete*, a dummy package that installs the whole of greater sisu as
+ described below, apart from sisu -examples

-1. Download the latest source (information available) from:
-
+ *sisu-pdf*, dependencies used by sisu to produce pdf from /LaTeX/ generated

-2. Unpack the source
+ *sisu-postgresql*, dependencies used by sisu to populate postgresql database
+ (further configuration is necessary)

-Note however, that additional external package dependencies,
-such as texlive or postgresql should you desire to use it
-are not taken care of for you.
+ *sisu-sqlite*, dependencies used by sisu to populate sqlite database
+
+ *sisu-markup-samples*, sisu markup samples and other miscellany (under
+ *Debian* Free Software Guidelines non-free)
+
+*SiSU* is available off Debian Unstable and Testing [link:
+]
+[^1] install it using apt-get, aptitude or alternative *Debian* install tools.
+
+DEPENDENCIES
+------------
+
+Here is a list of sisu' s current dependencies,[^2] which depend on such
+factors as whether you want to generate pdf, whether you will be using *SiSU*
+with or without a database, ...). sisu_markup-samples may also be of interest.
+
+Package: sisu
+Depends: ruby | ruby-interpreter, openssl, rsync, unzip, zip
+Recommends: sisu-pdf, sisu-sqlite, sisu-postgresql, imagemagick |
+graphicsmagick, keychain, openssh-client | lsh-client, po4a, qrencode, rake,
+ruby-rmagick, tidy, tree, vim-addon-manager
+Suggests: lv, calibre, pinfo, poedit, texinfo, trang
+
+
+Package: sisu-complete
+Depends: ruby | ruby-interpreter, sisu (= ${source:Version}), sisu-pdf (=
+${source:Version}), sisu-postgresql (= ${source:Version}), sisu-sqlite (=
+${source:Version})
+Description-en: installs all SiSU related packages
+
+
+Package: sisu-pdf
+Depends: ruby | ruby-interpreter, sisu (= ${source:Version}),
+texlive-latex-base, texlive-fonts-recommended, texlive-generic-recommended,
+texlive-latex-recommended, texlive-latex-extra, texlive-math-extra,
+texlive-xetex, fonts-liberation, lmodern, latex-cjk-all, texlive-lang-cjk
+Suggests: evince | pdf-viewer
+
+
+Package: sisu-postgresql
+Depends: ruby | ruby-interpreter, sisu (= ${source:Version}), postgresql,
+ruby-dbd-pg, ruby-dbi, ruby-fcgi
+Suggests: postgresql-contrib
+
+
+Package: sisu-sqlite
+Depends: ruby | ruby-interpreter, sisu (= ${source:Version}), sqlite3,
+ruby-sqlite3, ruby-dbd-sqlite3, ruby-dbi, ruby-fcgi
+
+
+Package: sisu-markup-samples
+Depends: sisu
+
+
+COMMANDS
+********
+
+COMMANDS SUMMARY
+----------------
+
+DESCRIPTION
+...........
+
+*SiSU* is a document publishing system, that from a simple single marked-up
+document, produces multiple output formats including: /plaintext/, /HTML/,
+/XHTML/, /XML/, /EPUB/, /ODT/ (/OpenDocument/ (/ODF/) text), /LaTeX/, /PDF/,
+info, and /SQL/ (/PostgreSQL/ and /SQLite/) , which share text object numbers
+("object citation numbering") and the same document structure information. For
+more see: or
+
+DOCUMENT PROCESSING COMMAND FLAGS
+.................................
+
+*-a [filename/wildcard]*
+produces /plaintext/ with Unix linefeeds and without markup, (object numbers
+are omitted), has footnotes at end of each paragraph that contains them [ -A
+for equivalent dos (linefeed) output file] [see -e for endnotes]. (Options
+include: --endnotes for endnotes --footnotes for footnotes at the end of each
+paragraph --unix for unix linefeed (default) --msdos for msdos linefeed)
+
+*--ao [filename/wildcard/url]*
+assumed for most other flags, creates new intermediate files for processing
+(abstract objects, document abstraction) that is used in all subsequent
+processing of other output. This step is assumed for most processing flags. To
+skip it see -n. Alias -m. (sisu v5)
+
+*-b [filename/wildcard]*
+see --xhtml
+
+*--by-**
+see --output-by-*
+
+*-C*
+configure/initialise shared output directory files initialize shared output
+directory (config files such as css and dtd files are not updated if they
+already exist unless modifier is used). -C --init-site configure/initialise
+site more extensive than -C on its own, shared output directory files/force
+update, existing shared output config files such as css and dtd files are
+updated if this modifier is used.
+
+*-CC*
+see --configure
+
+*-c [filename/wildcard]*
+see --color-toggle
+
+*--color*
+see --color-on
+
+*--color-off*
+turn off color in output to terminal
+
+*--color-on*
+turn on color in output to terminal
+
+*--color-toggle [filename/wildcard]*
+screen toggle ansi screen colour on or off depending on default set (unless -c
+flag is used: if sisurc colour default is set to 'true', output to screen will
+be with colour, if sisurc colour default is set to 'false' or is undefined
+screen output will be without colour). Alias -c
+
+*--configure*
+configure/initialise shared output directory files initialize shared output
+directory (config files such as css and dtd files are not updated if they
+already exist unless modifier is used). The equivalent of: -C --init-site
+configure/initialise site, more extensive than -C on its own, shared output
+directory files/force update, existing shared output config files such as css
+and dtd files are updated if -CC is used.
+
+*--concordance [filename/wildcard]*
+produces concordance (wordmap) a rudimentary index of all the words in a
+document. (Concordance files are not generated for documents of over 260,000
+words unless this limit is increased in the file sisurc.yml). Alias -w
+
+*-D [instruction] [filename]*
+see --pg
+
+*-d [--db-[database type (sqlite|pg)]] --[instruction] [filename]*
+see --sqlite
+
+*--dal [filename/wildcard/url]*
+assumed for most other flags, creates new intermediate files for processing
+(abstract objects, document abstraction) that is used in all subsequent
+processing of other output. This step is assumed for most processing flags. To
+skip it see -n. Renamed --ao (abstract objects) in sisu v5. Alias -m
+
+*--delete [filename/wildcard]*
+see --zap
+
+*--docbook [filename/wildcard/url]*
+docbook smart text (sisu v5)
+
+*--dump[=directory_path] [filename/wildcard]*
+places output in directory specified, if none is specified in the current
+directory (pwd). Unlike using default settings /HTML/ files have embedded css.
+Compare --redirect
+
+*-e [filename/wildcard]*
+see --epub
+
+*--epub [filename/wildcard]*
+produces an epub document, [sisu version >=2 ] (filename.epub). Alias -e
+
+*--exc-**
+exclude output feature, overrides configuration settings --exc-ocn, (exclude
+/object citation numbering/, (switches off /object citation numbering/) ,
+affects html (seg, scroll), epub, xhtml, xml, pdf) ; --exc-toc, (exclude table
+of contents, affects html (scroll), epub, pdf) ; --exc-links-to-manifest,
+--exc-manifest-links, (exclude links to manifest, affects html (seg, scroll));
+--exc-search-form, (exclude search form, affects html (seg, scroll), manifest);
+--exc-minitoc, (exclude mini table of contents, affects html (seg),
+concordance, manifest); --exc-manifest-minitoc, (exclude mini table of
+contents, affects manifest); --exc-html-minitoc, (exclude mini table of
+contents, affects html (seg), concordance); --exc-html-navigation, (exclude
+navigation, affects html (seg)); --exc-html-navigation-bar, (exclude navigation
+bar, affects html (seg)); --exc-html-search-form, (exclude search form, affects
+html (seg, scroll)); --exc-html-right-pane, (exclude right pane/column, affects
+html (seg, scroll)); --exc-html-top-band, (exclude top band, affects html (seg,
+scroll), concordance (minitoc forced on to provide seg navigation));
+--exc-segsubtoc (exclude sub table of contents, affects html (seg), epub) ; see
+also --inc-*
+
+*-F [--webserv=webrick]*
+see --sample-search-form
+
+*-f [optional string part of filename]*
+see --find
+
+*--fictionbook [filename/wildcard/url]*
+fictionbook smart text (sisu v5)
+
+*--find [optional string part of filename]*
+without match string, glob all .sst .ssm files in directory (including language
+subdirectories). With match string, find files that match given string in
+directory (including language subdirectories). Alias -f, --glob, -G
+
+*-G [optional string part of filename]*
+see --find
+
+*-g [filename/wildcard]*
+see --git
+
+*--git [filename/wildcard]*
+produces or updates markup source file structure in a git repo (experimental
+and subject to change). Alias -g
+
+*--glob [optional string part of filename]*
+see --find
+
+*-h [filename/wildcard]*
+see --html
+
+*--harvest *.ss[tm]*
+makes two lists of sisu output based on the sisu markup documents in a
+directory: list of author and authors works (year and titles), and; list by
+topic with titles and author. Makes use of header metadata fields (author,
+title, date, topic_register). Can be used with maintenance (-M) and remote
+placement (-R) flags.
+
+*--help [topic]*
+provides help on the selected topic, where topics (keywords) include: list,
+(com)mands, short(cuts), (mod)ifiers, (env)ironment, markup, syntax, headers,
+headings, endnotes, tables, example, customise, skin, (dir)ectories, path,
+(lang)uage, db, install, setup, (conf)igure, convert, termsheet, search, sql,
+features, license.
+
+*--html [filename/wildcard]*
+produces html output, in two forms (i) segmented text with table of contents
+(toc.html and index.html) and (ii) the document in a single file (scroll.html).
+Alias -h
+
+*--html-scroll [filename/wildcard]*
+produces html output, the document in a single file (scroll.html) only. Compare
+--html-seg and --html
+
+*--html-seg [filename/wildcard]*
+produces html output, segmented text with table of contents (toc.html and
+index.html). Compare --html-scroll and --html
+
+*--html-strict [filename/wildcard]*
+produces html with --strict option. see --strict
+
+*-I [filename/wildcard]*
+see --texinfo
+
+*-i [filename/wildcard]*
+see --manpage
+
+*--i18n-**
+these flags affect output by filetype and filename): --i18n-mono
+(--monolingual) output filenames without language code for default language
+('en' or as set); --i18n-multi (--multilingual) language code provided as part
+of the output filename, this is the default. Where output is in one language
+only the language code may not be desired. see also --output-by-*
+
+*--inc-**
+include output feature, overrides configuration settings, (usually the default
+if none set), has precedence over --exc-* (exclude output feature). Some detail
+provided under --exc-*, see --exc-*
+
+*-j [filename/wildcard]*
+copies images associated with a file for use by html, xhtml & xml outputs
+(automatically invoked by --dump & redirect).
+
+*-k*
+see --color-off
+
+*--keep-processing-files [filename/wildcard/url]*
+see --maintenance
+
+*-M [filename/wildcard/url]*
+see --maintenance
+
+*-m [filename/wildcard/url]*
+see --dal (document abstraction level/layer)
+
+*--machine [filename/wildcard/url]*
+see --dal (document abstraction level/layer)
+
+*--maintenance [filename/wildcard/url]*
+maintenance mode, interim processing files are preserved and their locations
+indicated. (also see -V). Aliases -M and --keep-processing-files.
+
+*--markdown [filename/wildcard/url]*
+markdown smart text (sisu v5)
+
+*--manpage [filename/wildcard]*
+produces man page of file, not suitable for all outputs. Alias -i
+
+*--monolingual*
+see --i18n-*
+
+*--multilingual*
+see --i18n-*
+
+*-N [filename/wildcard/url]*
+document digest or document content certificate ( DCC ) as md5 digest tree of
+the document: the digest for the document, and digests for each object
+contained within the document (together with information on software versions
+that produced it) (digest.txt). -NV for verbose digest output to screen.
+
+*-n [filename/wildcard/url]*
+skip the creation of intermediate processing files (document abstraction) if
+they already exist, this skips the equivalent of -m which is otherwise assumed
+by most processing flags.
+
+*--no-**
+see --exc-*
+
+*-o [filename/wildcard/url]*
+see --odt
+
+*--ocn*
+see --inc-ocn and --exc-ocn
+
+*--odf [filename/wildcard/url]*
+see --odt
+
+*--odt [filename/wildcard/url]*
+output basic document in opendocument file format (opendocument.odt). Alias -o
+
+*--output-by-**
+select output directory structure from 3 alternatives: --output-by-language,
+(language directory (based on language code) with filetype (html, epub, pdf
+etc.) subdirectories); --output-by-filetype, (filetype directories with
+language code as part of filename); --output-by-filename, (filename directories
+with language code as part of filename). This is configurable. Alias --by-*
+
+*-P [language_directory/filename language_directory]*
+see --po4a
+
+*-p [filename/wildcard]*
+see --pdf
+
+*--papersize-(a4|a5|b5|letter|legal)*
+in conjunction with --pdf set pdf papersize, overriding any configuration
+settings, to set more than one papersize repeat the option --pdf --papersize-a4
+--papersize-letter. See also --papersize=*
+
+*--papersize=a4,a5,b5,letter,legal* in conjunction with --pdf set pdf
+papersize, overriding any configuration settings, to set more than one
+papersize list after the equal sign with a comma separator
+--papersize=a4,letter. See also --papersize-*
+
+*--pdf [filename/wildcard]*
+produces /LaTeX/ pdf (portrait.pdf & landscape.pdf). Orientation and papersize
+may be set on the command-line. Default paper size is set in config file, or
+document header, or provided with additional command line parameter, e.g.
+--papersize-a4 preset sizes include: 'A4', U.S. 'letter' and 'legal' and book
+sizes 'A5' and 'B5' (system defaults to A4), and; --landscape or --portrait,
+so: e.g. "sisu --pdf-a4 --pdf-letter --landscape --verbose [filename/wildcard]"
+or "sisu --pdf --landscape --a4 --letter --verbose [filename/wildcard]". --pdf
+defaults to both landscape & portrait output, and a4 if no other papersizes are
+configured. Related options --pdf-landscape --pdf-portrait --pdf-papersize-*
+--pdf-papersize=[list]. Alias -p
+
+*--pdf-l [filename/wildcard]*
+See --pdf-landscape
+
+*--pdf-landscape [filename/wildcard]*
+sets orientation, produces /LaTeX/ pdf landscape.pdf. Default paper size is set
+in config file, or document header, or provided with additional command line
+parameter, e.g. --papersize-a4 preset sizes include: 'A4', U.S. 'letter' and
+'legal' and book sizes 'A5' and 'B5' (system defaults to A4). Related options
+--pdf --pdf-portrait. See also --papersize-* or --papersize=[list]. Alias
+--pdf-l or in conjunction with --pdf --landscape
+
+*--pdf-p [filename/wildcard]*
+See --pdf-portrait
+
+*--pdf-portrait [filename/wildcard]*
+sets orientation, produces /LaTeX/ pdf portrait.pdf.pdf. Default paper size is
+set in config file, or document header, or provided with additional command
+line parameter, e.g. --papersize-a4 preset sizes include: 'A4', U.S. 'letter'
+and 'legal' and book sizes 'A5' and 'B5' (system defaults to A4). Related
+options --pdf --pdf-landscape. See also --papersize-* or --papersize=[list].
+Alias --pdf-p or in conjunction with --pdf --portrait
+
+*--pg [instruction] [filename]*
+database /PostgreSQL/ ( --pgsql may be used instead) possible instructions,
+include: --createdb; --create; --dropall; --import [filename]; --update
+[filename]; --remove [filename]; see database section below. Alias -D
+
+*--po [language_directory/filename language_directory]*
+see --po4a
+
+*--po4a [language_directory/filename language_directory]*
+produces .pot and po files for the file in the languages specified by the
+language directory. *SiSU* markup is placed in subdirectories named with the
+language code, e.g. en/ fr/ es/. The sisu config file must set the output
+directory structure to multilingual. v3, experimental
+
+*-Q [filename/wildcard]*
+see --qrcode
+
+*-q [filename/wildcard]*
+see --quiet
+
+*--qrcode [filename/wildcard]*
+generate QR code image of metadata (used in manifest). v3 only.
+
+*--quiet [filename/wildcard]*
+quiet less output to screen.
+
+*-R [filename/wildcard]*
+see --rsync
+
+*-r [filename/wildcard]*
+see --scp
+
+*--redirect[=directory_path] [filename/wildcard]*
+places output in subdirectory under specified directory, subdirectory uses the
+filename (without the suffix). If no output directory is specified places the
+subdirectory under the current directory (pwd). Unlike using default settings
+/HTML/ files have embedded css. Compare --dump
+
+*--rst [filename/wildcard/url]*
+ReST (rST restructured text) smart text (sisu v5)
+
+*--rsync [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 --scp. Alias -R
+
+*-S*
+see --sisupod
+
+*-S [filename/wildcard]*
+see --sisupod
+
+*-s [filename/wildcard]*
+see --source
+
+*--sample-search-form [--db=(pgsql|sqlite)] [--webserv=webrick]*
+generate examples of (naive) cgi search form for /SQLite/ or PgSQL depends on
+your already having used sisu to populate an /SQLite/ or PgSQL database, (the
+/SQLite/ version scans the output directories for existing sisu_sqlite
+databases, so it is first necessary to create them, before generating the
+search form) see --sqlite & --pg and the database section below. Optional
+additional parameters include: url location of webserver search form and db:
+--webserv-search='[url]'; location of webserver output:
+--webserv-output='[url]'; cgi search form link name:
+--cgi-search-form-name='[name.cgi]'; for pgsql, database user:
+--db-user='[username]'. If the optional parameter --webserv=webrick is passed,
+the cgi examples created will be set up to use the default port set for use by
+the webrick server, (otherwise the port is left blank and the system setting
+used, usually 80). The samples are dumped in the present work directory which
+must be writable, (with screen instructions given that they be copied to the
+cgi-bin directory). Alias -F
+
+*--scp [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 --rsync. Alias -r
+
+*--sqlite --[instruction] [filename]*
+database type set to /SQLite/, this produces one of two possible databases,
+without additional database related instructions it produces a discreet
+/SQLite/ file for the document processed; with additional instructions it
+produces a common /SQLite/ database of all processed documents that (come from
+the same document preparation directory and as a result) share the same output
+directory base path (possible instructions include: --createdb; --create;
+--dropall; --import [filename]; --update [filename]; --remove [filename]); see
+database section below. Alias -d
+
+*--sisupod*
+produces a sisupod a zipped sisu directory of markup files including sisu
+markup source files and the directories local configuration file, images and
+skins. Note: this only includes the configuration files or skins contained in
+./_sisu not those in ~/.sisu -S [filename/wildcard] option. Note: (this option
+is tested only with zsh). Alias -S
+
+*--sisupod [filename/wildcard]*
+produces a zipped file of the prepared document specified along with associated
+images, by default named sisupod.zip they may alternatively be named with the
+filename extension .ssp This provides a quick way of gathering the relevant
+parts of a sisu document which can then for example be emailed. A sisupod
+includes sisu markup source file, (along with associated documents if a master
+file, or available in multilingual versions), together with related images and
+skin. *SiSU* commands can be run directly against a sisupod contained in a
+local directory, or provided as a url on a remote site. As there is a security
+issue with skins provided by other users, they are not applied unless the flag
+--trust or --trusted is added to the command instruction, it is recommended
+that file that are not your own are treated as untrusted. The directory
+structure of the unzipped file is understood by sisu, and sisu commands can be
+run within it. Note: if you wish to send multiple files, it quickly becomes
+more space efficient to zip the sisu markup directory, rather than the
+individual files for sending). See the -S option without [filename/wildcard].
+Alias -S
+
+*--source [filename/wildcard]*
+copies sisu markup file to output directory. Alias -s
+
+*--strict*
+together with --html, produces more w3c compliant html, for example not having
+purely numeric identifiers for text, the location object url#33 becomes url#o33
+
+*-T [filename/wildcard (*.termsheet.rb)]*
+standard form document builder, preprocessing feature
+
+*-t [filename/wildcard]*
+see --txt
+
+*--texinfo [filename/wildcard]*
+produces texinfo and info file, (view with pinfo). Alias -I
+
+*--textile [filename/wildcard/url]*
+textile smart text (sisu v5)
+
+*--txt [filename/wildcard]*
+produces /plaintext/ with Unix linefeeds and without markup, (object numbers
+are omitted), has footnotes at end of each paragraph that contains them [ -A
+for equivalent dos (linefeed) output file] [see -e for endnotes]. (Options
+include: --endnotes for endnotes --footnotes for footnotes at the end of each
+paragraph --unix for unix linefeed (default) --msdos for msdos linefeed). Alias
+-t
+
+*--txt-asciitext [filename/wildcard]*
+see --asciitext
+
+*--txt-markdown [filename/wildcard]*
+see --markdown
+
+*--txt-rst [filename/wildcard]*
+see --rst
+
+*--txt-textile [filename/wildcard]*
+see --textile
+
+*-U [filename/wildcard]*
+see --urls
+
+*-u [filename/wildcard]*
+provides url mapping of output files for the flags requested for processing,
+also see -U
+
+*--urls [filename/wildcard]*
+prints url output list/map for the available processing flags options and
+resulting files that could be requested, (can be used to get a list of
+processing options in relation to a file, together with information on the
+output that would be produced), -u provides url output mapping for those flags
+requested for processing. The default assumes sisu_webrick is running and
+provides webrick url mappings where appropriate, but these can be switched to
+file system paths in sisurc.yml. Alias -U
+
+*-V*
+on its own, provides *SiSU* version and environment information (sisu --help
+env)
+
+*-V [filename/wildcard]*
+even more verbose than the -v flag.
+
+*-v*
+on its own, provides *SiSU* version information
+
+*-v [filename/wildcard]*
+see --verbose
+
+*--v3 [filename/wildcard]*
+invokes the sisu v3 document parser/generator. You may run sisu3 instead.
+
+*--v4 [filename/wildcard]*
+invokes the sisu v4 document parser/generator. This is the default and is
+normally omitted.
+
+*--verbose [filename/wildcard]*
+provides verbose output of what is being generated, where output is placed (and
+error messages if any), as with -u flag provides a url mapping of files created
+for each of the processing flag requests. Alias -v
+
+*-W*
+see --webrick
+
+*-w [filename/wildcard]*
+see --concordance
+
+*--webrick*
+starts ruby' s webrick webserver points at sisu output directories, the default
+port is set to 8081 and can be changed in the resource configuration files.
+[tip: the webrick server requires link suffixes, so html output should be
+created using the -h option rather than -H ; also, note -F webrick ]. Alias -W
+
+*--wordmap [filename/wildcard]*
+see --concordance
+
+*--xhtml [filename/wildcard]*
+produces xhtml//XML/ output for browser viewing (sax parsing). Alias -b
+
+*--xml-dom [filename/wildcard]*
+produces /XML/ output with deep document structure, in the nature of dom. Alias
+-X
+
+*--xml-sax [filename/wildcard]*
+produces /XML/ output shallow structure (sax parsing). Alias -x
+
+*-X [filename/wildcard]*
+see --xml-dom
+
+*-x [filename/wildcard]*
+see --xml-sax
+
+*-Y [filename/wildcard]*
+produces a short sitemap entry for the document, based on html output and the
+sisu_manifest. --sitemaps generates/updates the sitemap index of existing
+sitemaps. (Experimental, [g,y,m announcement this week])
+
+*-y [filename/wildcard]*
+produces an html summary of output generated (hyperlinked to content) and
+document specific metadata (sisu_manifest.html). This step is assumed for most
+processing flags.
+
+*-Z [filename/wildcard]*
+see --zap
+
+*--zap [filename/wildcard]*
+Zap, if used with other processing flags deletes output files of the type about
+to be processed, prior to processing. If -Z is used as the lone processing
+related flag (or in conjunction with a combination of -[mMvVq]), will remove
+the related document output directory. Alias -Z
+
+COMMAND LINE MODIFIERS
+----------------------
+
+*--no-ocn*
+[with --html --pdf or --epub] switches off /object citation numbering/. Produce
+output without identifying numbers in margins of html or /LaTeX//pdf output.
+
+*--no-annotate*
+strips output text of editor endnotes[^*1] denoted by asterisk or dagger/plus
+sign
+
+*--no-asterisk*
+strips output text of editor endnotes[^*2] denoted by asterisk sign
+
+*--no-dagger*
+strips output text of editor endnotes[^+1] denoted by dagger/plus sign
+
+DATABASE COMMANDS
+-----------------
+
+*dbi - database interface*
+
+*-D or --pgsql* set for /PostgreSQL/ *-d or --sqlite* default set for /SQLite/
+-d is modifiable with --db=[database type (PgSQL or /SQLite/) ]
+
+*--pg -v --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) [ -dv --createall /SQLite/
+equivalent] it may be necessary to run sisu -Dv --createdb initially NOTE: at
+the present time for /PostgreSQL/ it may be necessary to manually create the
+database. The command would be 'createdb [database name]' where database name
+would be SiSU_[present working directory name (without path)]. Please use only
+alphanumerics and underscores.
+
+*--pg -v --import*
+[filename/wildcard] imports data specified to /PostgreSQL/ db (rb.dbi) [ -dv
+--import /SQLite/ equivalent]
+
+*--pg -v --update*
+[filename/wildcard] updates/imports specified data to /PostgreSQL/ db (rb.dbi)
+[ -dv --update /SQLite/ equivalent]
+
+*--pg --remove*
+[filename/wildcard] removes specified data to /PostgreSQL/ db (rb.dbi) [ -d
+--remove /SQLite/ equivalent]
+
+*--pg --dropall*
+kills data" and drops (/PostgreSQL/ or /SQLite/) db, tables & indexes [ -d
+--dropall /SQLite/ equivalent]
+
+The -v is for verbose output.
+
+SHORTCUTS, SHORTHAND FOR MULTIPLE FLAGS
+---------------------------------------
+
+*--update [filename/wildcard]*
+Checks existing file output and runs the flags required to update this output.
+This means that if only html and pdf output was requested on previous runs,
+only the -hp files will be applied, and only these will be generated this time,
+together with the summary. This can be very convenient, if you offer different
+outputs of different files, and just want to do the same again.
+
+*-0 to -5 [filename or wildcard]*
+Default shorthand mappings (for v3, note that the defaults can be
+changed/configured in the sisurc.yml file):
+
+*-0*
+-NQhewpotbxXyYv [this is the default action run when no options are give, i.e.
+on 'sisu [filename]']
+
+*-1*
+-Qhewpoty
+
+*-2*
+-NQhewpotbxXy
+
+*-3*
+-NQhewpotbxXyY
+
+*-4*
+-NQhewpotbxXDyY --update
+
+*-5*
+-NQhewpotbxXDyYv --update
+
+add -v for verbose mode and -c to toggle color state, e.g. sisu -2vc [filename
+or wildcard]
+
+consider -u for appended url info or -v for verbose output
+
+COMMAND LINE WITH FLAGS - BATCH PROCESSING
+..........................................
+
+In the data directory run sisu -mh filename or wildcard eg. "sisu -h cisg.sst"
+or "sisu -h *.{sst,ssm}" to produce html version of all documents.
+
+Running sisu (alone without any flags, filenames or wildcards) brings up the
+interactive help, as does any sisu command that is not recognised. Enter to
+escape.
+
+INTRODUCTION TO SISU MARKUP[^3]
+-------------------------------
+
+SUMMARY
+.......
+
+*SiSU* source documents are /plaintext/ (/UTF-8/)[^4] files
+
+All paragraphs are separated by an empty line.
+
+Markup is comprised of:
+
+* at the top of a document, the document header made up of semantic meta-data
+about the document and if desired additional processing instructions (such an
+instruction to automatically number headings from a particular level down)
+
+* followed by the prepared substantive text of which the most important single
+characteristic is the markup of different heading levels, which define the
+primary outline of the document structure. Markup of substantive text includes:
+
+ * heading levels defines document structure
+
+ * text basic attributes, italics, bold etc.
+
+ * grouped text (objects), which are to be treated differently, such as code
+ blocks or poems.
+
+ * footnotes/endnotes
+
+ * linked text and images
+
+ * paragraph actions, such as indent, bulleted, numbered-lists, etc.
+
+Some interactive help on markup is available, by typing sisu and selecting
+markup or sisu --help markup
+
+To check the markup in a file:
+
+ sisu --identify [filename].sst
+
+For brief descriptive summary of markup history
+
+ sisu --query-history
+
+or if for a particular version:
+
+ sisu --query-0.38
+
+MARKUP EXAMPLES
+...............
+
+
+----------------------------------------
+
+ONLINE
+......
+
+Online markup examples are available together with the respective outputs
+produced from or from
+
+
+There is of course this document, which provides a cursory overview of sisu
+markup and the respective output produced:
+
+
+an alternative presentation of markup syntax:
+/usr/share/doc/sisu/on_markup.txt.gz
+
+
+----------------------------------------
+
+INSTALLED
+.........
+
+With *SiSU* installed sample skins may be found in:
+/usr/share/doc/sisu/markup-samples (or equivalent directory) and if sisu
+-markup-samples is installed also under:
+/usr/share/doc/sisu/markup-samples-non-free
+
+MARKUP OF HEADERS
+-----------------
+
+Headers contain either: semantic meta-data about a document, which can be used
+by any output module of the program, or; processing instructions.
+
+Note: the first line of a document may include information on the markup
+version used in the form of a comment. Comments are a percentage mark at the
+start of a paragraph (and as the first character in a line of text) followed by
+a space and the comment:
+
+% this would be a comment
+
+
+SAMPLE HEADER
+.............
+
+This current document is loaded by a master document that has a header similar
+to this one:
+
+% SiSU master 4.0
+
+@title: SiSU
+ :subtitle: Manual
+
+@creator:
+ :author: Amissah, Ralph
+
+@publisher: [publisher name]
+
+@rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3
+
+@classify:
+ :topic_register: SiSU:manual;electronic documents:SiSU:manual
+ :subject: ebook, epublishing, electronic book, electronic publishing,
+ electronic document, electronic citation, data structure,
+ citation systems, search
+
+% used_by: manual
+
+@date:
+ :published: 2008-05-22
+ :created: 2002-08-28
+ :issued: 2002-08-28
+ :available: 2002-08-28
+ :modified: 2010-03-03
+
+@make:
+ :num_top: 1
+ :breaks: new=C; break=1
+ :bold: /Gnu|Debian|Ruby|SiSU/
+ :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
+ :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
+ :manpage: name=sisu - documents: markup, structuring, publishing in multiple standard formats, and search;
+ synopsis=sisu [-abcDdeFhIiMmNnopqRrSsTtUuVvwXxYyZz0-9] [filename/wildcard ]
+ . sisu [-Ddcv] [instruction]
+ . sisu [-CcFLSVvW]
+ . sisu --v4 [operations]
+ . sisu --v3 [operations]
+
+@links:
+ { SiSU Homepage }http://www.sisudoc.org/
+ { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/
+ { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html
+ { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html
+ { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html
+ { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary
+ { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/
+ { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html
+ { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org
+ { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
+
+
+AVAILABLE HEADERS
+.................
+
+Header tags appear at the beginning of a document and provide meta information
+on the document (such as the /Dublin Core/) , or information as to how the
+document as a whole is to be processed. All header instructions take the form
+@headername: or on the next line and indented by once space :subheadername: All
+/Dublin Core/ meta tags are available
+
+*@identifier:* information or instructions
+
+where the "identifier" is a tag recognised by the program, and the
+"information" or "instructions" belong to the tag/identifier specified
+
+Note: a header where used should only be used once; all headers apart from
+@title: are optional; the @structure: header is used to describe document
+structure, and can be useful to know.
+
+This is a sample header
+
+% SiSU 2.0 [declared file-type identifier with markup version]
+
+
+@title: [title text] [this header is the only one that is mandatory]
+ :subtitle: [subtitle if any]
+ :language: English
+
+
+@creator:
+ :author: [Lastname, First names]
+ :illustrator: [Lastname, First names]
+ :translator: [Lastname, First names]
+ :prepared_by: [Lastname, First names]
+
+
+@date:
+ :published: [year or yyyy-mm-dd]
+ :created: [year or yyyy-mm-dd]
+ :issued: [year or yyyy-mm-dd]
+ :available: [year or yyyy-mm-dd]
+ :modified: [year or yyyy-mm-dd]
+ :valid: [year or yyyy-mm-dd]
+ :added_to_site: [year or yyyy-mm-dd]
+ :translated: [year or yyyy-mm-dd]
+
+
+@rights:
+ :copyright: Copyright (C) [Year and Holder]
+ :license: [Use License granted]
+ :text: [Year and Holder]
+ :translation: [Name, Year]
+ :illustrations: [Name, Year]
+
+
+@classify:
+ :topic_register: SiSU:markup sample:book;book:novel:fantasy
+ :type:
+ :subject:
+ :description:
+ :keywords:
+ :abstract:
+ :loc: [Library of Congress classification]
+ :dewey: [Dewey classification
+
+
+@identify:
+ :isbn: [ISBN]
+ :oclc:
+
+
+@links: { SiSU }http://www.sisudoc.org
+ { FSF }http://www.fsf.org
+
+
+@make:
+ :num_top: 1
+ :headings: [text to match for each level
+ (e.g. PART; Chapter; Section; Article; or another: none; BOOK|FIRST|SECOND; none; CHAPTER;)
+ :breaks: new=:C; break=1
+ :promo: sisu, ruby, sisu_search_libre, open_society
+ :bold: [regular expression of words/phrases to be made bold]
+ :italics: [regular expression of words/phrases to italicise]
+ :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
+ :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org
+
+
+@original:
+ :language: [language]
+
+
+@notes:
+ :comment:
+ :prefix: [prefix is placed just after table of contents]
+
+
+MARKUP OF SUBSTANTIVE TEXT
+--------------------------
+
+HEADING LEVELS
+..............
+
+Heading levels are :A~ ,:B~ ,:C~ ,1~ ,2~ ,3~ ... :A - :C being part / section
+headings, followed by other heading levels, and 1 -6 being headings followed by
+substantive text or sub-headings. :A~ usually the title :A~? conditional level
+1 heading (used where a stand-alone document may be imported into another)
+
+*:A~ [heading text]* Top level heading [this usually has similar content to the
+title @title: ] NOTE: the heading levels described here are in 0.38 notation,
+see heading
+
+*:B~ [heading text]* Second level heading [this is a heading level divider]
+
+*:C~ [heading text]* Third level heading [this is a heading level divider]
+
+*1~ [heading text]* Top level heading preceding substantive text of document or
+sub-heading 2, the heading level that would normally be marked 1. or 2. or 3.
+etc. in a document, and the level on which sisu by default would break html
+output into named segments, names are provided automatically if none are given
+(a number), otherwise takes the form 1~my_filename_for_this_segment
+
+*2~ [heading text]* Second level heading preceding substantive text of document
+or sub-heading 3 , the heading level that would normally be marked 1.1 or 1.2
+or 1.3 or 2.1 etc. in a document.
+
+*3~ [heading text]* Third level heading preceding substantive text of document,
+that would normally be marked 1.1.1 or 1.1.2 or 1.2.1 or 2.1.1 etc. in a
+document
+
+1~filename level 1 heading,
+
+% the primary division such as Chapter that is followed by substantive text, and may be further subdivided (this is the level on which by default html segments are made)
+
+
+FONT ATTRIBUTES
+...............
+
+*markup example:*
+
+normal text, *{emphasis}*, !{bold text}!, /{italics}/, _{underscore}_, "{citation}",
+^{superscript}^, ,{subscript},, +{inserted text}+, -{strikethrough}-, #{monospace}#
+
+normal text
+
+*{emphasis}* [note: can be configured to be represented by bold, italics or underscore]
+
+!{bold text}!
+
+/{italics}/
+
+_{underscore}_
+
+"{citation}"
+
+^{superscript}^
+
+,{subscript},
+
++{inserted text}+
+
+-{strikethrough}-
+
+#{monospace}#
+
+
+*resulting output:*
+
+normal text, *emphasis*, *bold text*, /italics/, _underscore_, "citation",
+^superscript^, [subscript], +inserted text+, -strikethrough-, #monospace#
+
+normal text
+
+*emphasis* [note: can be configured to be represented by bold, italics or
+underscore]
+
+*bold text*
+
+/italics/
+
+_underscore_
+
+"citation"
+
+^superscript^
+
+[subscript]
+
++inserted text+
+
+-strikethrough-
+
+#monospace#
+
+INDENTATION AND BULLETS
+.......................
+
+*markup example:*
+
+ordinary paragraph
+
+_1 indent paragraph one step
+
+_2 indent paragraph two steps

-%% to use setup.rb
----------------
-this is a three step process,
-in the root directory of the unpacked SiSU as root type:
+_9 indent paragraph nine steps

- ruby setup.rb config
- ruby setup.rb setup
- #[as root:]
- ruby setup.rb install

- further information:
-
-
+*resulting output:*

-%% to use install (prapared with "Rake")
----------------
-Rake must be installed on your system:
-
-
+ordinary paragraph

-in the root directory of the unpacked SiSU as root type:
- rake
+ indent paragraph one step
+
+ indent paragraph two steps
+
+ indent paragraph nine steps
+
+*markup example:*
+
+_* bullet text
+
+_1* bullet text, first indent
+
+_2* bullet text, two step indent
+
+
+*resulting output:*
+
+* bullet text
+
+ * bullet text, first indent
+
+ * bullet text, two step indent
+
+Numbered List (not to be confused with headings/titles, (document structure))
+
+*markup example:*
+
+# numbered list numbered list 1., 2., 3, etc.
+
+_# numbered list numbered list indented a., b., c., d., etc.
+
+
+HANGING INDENTS
+...............
+
+*markup example:*
+
+_0_1 first line no indent,
+rest of paragraph indented one step
+
+_1_0 first line indented,
+rest of paragraph no indent
+
+in each case level may be 0-9
+
+
+*resulting output:*
+
+first line no indent, rest of paragraph indented one step; first line no
+ indent, rest of paragraph indented one step; first line no indent, rest of
+ paragraph indented one step; first line no indent, rest of paragraph indented
+ one step; first line no indent, rest of paragraph indented one step; first
+ line no indent, rest of paragraph indented one step; first line no indent,
+ rest of paragraph indented one step; first line no indent, rest of paragraph
+ indented one step; first line no indent, rest of paragraph indented one step;
+
+A regular paragraph.
+
+ first line indented, rest of paragraph no indent first line indented, rest of
+paragraph no indent first line indented, rest of paragraph no indent first line
+indented, rest of paragraph no indent first line indented, rest of paragraph no
+indent first line indented, rest of paragraph no indent first line indented,
+rest of paragraph no indent first line indented, rest of paragraph no indent
+first line indented, rest of paragraph no indent first line indented, rest of
+paragraph no indent first line indented, rest of paragraph no indent
+
+in each case level may be 0-9
+
+*live-build* A collection of scripts used to build customized *Debian*
+ Livesystems. /live-build/ was formerly known as live-helper, and even earlier
+ known as live-package.
+
+*live-build*
+ A collection of scripts used to build customized *Debian* Livesystems.
+ /live-build/ was formerly known as live-helper, and even earlier known as
+ live-package.
+
+FOOTNOTES / ENDNOTES
+....................
+
+Footnotes and endnotes are marked up at the location where they would be
+indicated within a text. They are automatically numbered. The output type
+determines whether footnotes or endnotes will be produced
+
+*markup example:*
+
+~{ a footnote or endnote }~
+
+
+*resulting output:*
+
+[^5]
+
+*markup example:*
+
+normal text~{ self contained endnote marker & endnote in one }~ continues
+
+
+*resulting output:*
+
+normal text[^6] continues
+
+*markup example:*
+
+normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks if required }~ continues
+
+normal text ~{** another unnumbered asterisk footnote/endnote }~ continues
+
+
+*resulting output:*
+
+normal text [^*] continues
+
+normal text [^**] continues
+
+*markup example:*
+
+normal text ~[* editors notes, numbered asterisk footnote/endnote series ]~ continues
+
+normal text ~[+ editors notes, numbered plus symbol footnote/endnote series ]~ continues
+
+
+*resulting output:*
+
+normal text [^*3] continues
+
+normal text [^+2] continues
+
+*Alternative endnote pair notation for footnotes/endnotes:*
+
+% note the endnote marker "~^"
+
+normal text~^ continues
+
+^~ endnote text following the paragraph in which the marker occurs
+
+
+the standard and pair notation cannot be mixed in the same document
+
+LINKS
+.....
+
+
+----------------------------------------
+
+NAKED URLS WITHIN TEXT, DEALING WITH URLS
+.........................................
+
+urls found within text are marked up automatically. A url within text is
+automatically hyperlinked to itself and by default decorated with angled
+braces, unless they are contained within a code block (in which case they are
+passed as normal text), or escaped by a preceding underscore (in which case the
+decoration is omitted).
+
+*markup example:*
+
+normal text http://www.sisudoc.org/ continues
+
+
+*resulting output:*
+
+normal text continues
+
+An escaped url without decoration
+
+*markup example:*
+
+normal text _http://www.sisudoc.org/ continues
+
+deb _http://www.jus.uio.no/sisu/archive unstable main non-free
+
+
+*resulting output:*
+
+normal text http://www.sisudoc.org/ continues
+
+deb http://www.jus.uio.no/sisu/archive unstable main non-free
+
+where a code block is used there is neither decoration nor hyperlinking, code
+blocks are discussed later in this document
+
+*resulting output:*
+
+deb http://www.jus.uio.no/sisu/archive unstable main non-free
+deb-src http://www.jus.uio.no/sisu/archive unstable main non-free
+
+
+
+----------------------------------------
+
+LINKING TEXT
+............
+
+To link text or an image to a url the markup is as follows
+
+*markup example:*
+
+about { SiSU }http://url.org markup
+
+
+*resulting output:*
+
+about SiSU [link: ] markup
+
+A shortcut notation is available so the url link may also be provided
+automatically as a footnote
+
+*markup example:*
+
+about {~^ SiSU }http://url.org markup
+
+
+*resulting output:*
+
+about SiSU [link: ] [^7] markup
+
+Internal document links to a tagged location, including an ocn
+
+*markup example:*
+
+about { text links }#link_text
+
+
+*resulting output:*
+
+about text links
+
+Shared document collection link
+
+*markup example:*
+
+about { SiSU book markup examples }:SiSU/examples.html
+
+
+*resulting output:*
+
+about *SiSU* book markup examples
+
+
+----------------------------------------
+
+LINKING IMAGES
+..............
+
+*markup example:*
+
+{ tux.png 64x80 }image
+
+% various url linked images
+[image: "a better way"]
+ [image: "Way Better - with Gnu/Linux, Debian and Ruby"]
+
+{~^ ruby_logo.png "Ruby" }http://www.ruby-lang.org/en/
+
+
+*resulting output:*
+
+tux.png 64x80 [link: local image]
+
+tux.png 64x80 "Gnu/Linux - a better way" [link: ]
+
+GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian
+and Ruby" [link: ]
+
+ruby_logo.png 70x90 "Ruby" [link: ] [^8]
+
+*linked url footnote shortcut*
+
+{~^ [text to link] }http://url.org
+
+% maps to: { [text to link] }http://url.org ~{ http://url.org }~
+
+% which produces hyper-linked text within a document/paragraph, with an endnote providing the url for the text location used in the hyperlink
+
+
+text marker *~name
+
+
+note at a heading level the same is automatically achieved by providing names
+to headings 1, 2 and 3 i.e. 2~[name] and 3~[name] or in the case of
+auto-heading numbering, without further intervention.
+
+
+----------------------------------------
+
+LINK SHORTCUT FOR MULTIPLE VERSIONS OF A SISU DOCUMENT IN THE SAME DIRECTORY
+TREE
+..............................................................................
+
+*markup example:*
+
+!_ /{"Viral Spiral"}/, David Bollier
+
+{ "Viral Spiral", David Bollier [3sS]}viral_spiral.david_bollier.sst
+
+
+*/"Viral Spiral"/, David Bollier*
+
+"Viral Spiral", David Bollier [link: ]
+ document manifest [link: ]
+ html, segmented text [link: ]
+ html, scroll, document in one [link: ]
+ epub [link: ]
+ pdf, landscape [link: ]
+ pdf, portrait [link: ]
+ odf: odt, open document text [link: ]
+ xhtml scroll [link: ]
+ xml, sax [link: ]
+ xml, dom [link: ]
+ concordance [link: ]
+ dcc, document content certificate (digests) [link: ]
+ markup source text [link: ]
+ markup source (zipped) pod [link: ]
+
+GROUPED TEXT
+............
+
+
+----------------------------------------
+
+TABLES
+......
+
+Tables may be prepared in two either of two forms
+
+*markup example:*
+
+table{ c3; 40; 30; 30;
+
+This is a table
+this would become column two of row one
+column three of row one is here
+
+And here begins another row
+column two of row two
+column three of row two, and so on
+
+}table
+
+
+*resulting output:*
+
+This is a table┆this would become column two of row one┆column three of row one is here』And here begins another row┆column two of row two┆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:*[^10]
+
+!_ Table 3.1: Contributors to Wikipedia, January 2001 - June 2005
+
+{table~h 24; 12; 12; 12; 12; 12; 12;}
+ |Jan. 2001|Jan. 2002|Jan. 2003|Jan. 2004|July 2004|June 2006
+Contributors* | 10| 472| 2,188| 9,653| 25,011| 48,721
+Active contributors** | 9| 212| 846| 3,228| 8,442| 16,945
+Very active contributors*** | 0| 31| 190| 692| 1,639| 3,016
+No. of English language articles| 25| 16,000| 101,000| 190,000| 320,000| 630,000
+No. of articles, all languages | 25| 19,000| 138,000| 490,000| 862,000|1,600,000
+
+* Contributed at least ten times; ** at least 5 times in last month; *** more than 100 times in last month.
+
+
+*resulting output:*
+
+*Table 3.1: Contributors to Wikipedia, January 2001 - June 2005*
+
+┆Jan. 2001┆Jan. 2002┆Jan. 2003┆Jan. 2004┆July 2004┆June 2006』Contributors*┆10┆472┆2,188┆9,653┆25,011┆48,721』Active contributors**┆9┆212┆846┆3,228┆8,442┆16,945』Very active contributors***┆0┆31┆190┆692┆1,639┆3,016』No. of English language articles┆25┆16,000┆101,000┆190,000┆320,000┆630,000』No. of articles, all languages┆25┆19,000┆138,000┆490,000┆862,000┆1,600,000』
+
+* Contributed at least ten times; ** at least 5 times in last month; *** more
+than 100 times in last month.
+
+
+----------------------------------------
+
+POEM
+....
+
+*basic markup:*
+
+poem{
+
+ Your poem here
+
+}poem
+
+Each verse in a poem is given an object number.
+
+
+*markup example:*
+
+poem{
+
+ `Fury said to a
+ mouse, That he
+ met in the
+ house,
+ "Let us
+ both go to
+ law: I will
+ prosecute
+ YOU. --Come,
+ I'll take no
+ denial; We
+ must have a
+ trial: For
+ really this
+ morning I've
+ nothing
+ to do."
+ Said the
+ mouse to the
+ cur, "Such
+ a trial,
+ dear Sir,
+ With
+ no jury
+ or judge,
+ would be
+ wasting
+ our
+ breath."
+ "I'll be
+ judge, I'll
+ be jury,"
+ Said
+ cunning
+ old Fury:
+ "I'll
+ try the
+ whole
+ cause,
+ and
+ condemn
+ you
+ to
+ death."'
+
+}poem
+
+
+*resulting output:*
+
+ `Fury said to a
+ mouse, That he
+ met in the
+ house,
+ "Let us
+ both go to
+ law: I will
+ prosecute
+ YOU. --Come,
+ I'll take no
+ denial; We
+ must have a
+ trial: For
+ really this
+ morning I've
+ nothing
+ to do."
+ Said the
+ mouse to the
+ cur, "Such
+ a trial,
+ dear Sir,
+ With
+ no jury
+ or judge,
+ would be
+ wasting
+ our
+ breath."
+ "I'll be
+ judge, I'll
+ be jury,"
+ Said
+ cunning
+ old Fury:
+ "I'll
+ try the
+ whole
+ cause,
+ and
+ condemn
+ you
+ to
+ death."'
+
+
+----------------------------------------
+
+GROUP
+.....
+
+*basic markup:*
+
+group{
+
+ Your grouped text here
+
+}group
+
+A group is treated as an object and given a single object number.
+
+
+*markup example:*
+
+group{
+
+ `Fury said to a
+ mouse, That he
+ met in the
+ house,
+ "Let us
+ both go to
+ law: I will
+ prosecute
+ YOU. --Come,
+ I'll take no
+ denial; We
+ must have a
+ trial: For
+ really this
+ morning I've
+ nothing
+ to do."
+ Said the
+ mouse to the
+ cur, "Such
+ a trial,
+ dear Sir,
+ With
+ no jury
+ or judge,
+ would be
+ wasting
+ our
+ breath."
+ "I'll be
+ judge, I'll
+ be jury,"
+ Said
+ cunning
+ old Fury:
+ "I'll
+ try the
+ whole
+ cause,
+ and
+ condemn
+ you
+ to
+ death."'
+
+}group
+
+
+*resulting output:*
+
+ `Fury said to a
+ mouse, That he
+ met in the
+ house,
+ "Let us
+ both go to
+ law: I will
+ prosecute
+ YOU. --Come,
+ I'll take no
+ denial; We
+ must have a
+ trial: For
+ really this
+ morning I've
+ nothing
+ to do."
+ Said the
+ mouse to the
+ cur, "Such
+ a trial,
+ dear Sir,
+ With
+ no jury
+ or judge,
+ would be
+ wasting
+ our
+ breath."
+ "I'll be
+ judge, I'll
+ be jury,"
+ Said
+ cunning
+ old Fury:
+ "I'll
+ try the
+ whole
+ cause,
+ and
+ condemn
+ you
+ to
+ death."'
+
+
+----------------------------------------
+
+CODE
+....
+
+Code tags # code{ ... }code # (used as with other group tags described above)
+are used to escape regular sisu markup, and have been used extensively within
+this document to provide examples of *SiSU* markup. You cannot however use code
+tags to escape code tags. They are however used in the same way as group or
+poem tags.
+
+A code-block is treated as an object and given a single object number. [an
+option to number each line of code may be considered at some later time]
+
+*use of code tags instead of poem compared, resulting output:*
+
+ `Fury said to a
+ mouse, That he
+ met in the
+ house,
+ "Let us
+ both go to
+ law: I will
+ prosecute
+ YOU. --Come,
+ I'll take no
+ denial; We
+ must have a
+ trial: For
+ really this
+ morning I've
+ nothing
+ to do."
+ Said the
+ mouse to the
+ cur, "Such
+ a trial,
+ dear Sir,
+ With
+ no jury
+ or judge,
+ would be
+ wasting
+ our
+ breath."
+ "I'll be
+ judge, I'll
+ be jury,"
+ Said
+ cunning
+ old Fury:
+ "I'll
+ try the
+ whole
+ cause,
+ and
+ condemn
+ you
+ to
+ death."'
+
+
+From *SiSU* 2.7.7 on you can number codeblocks by placing a hash after the
+opening code tag # code{# # as demonstrated here:
+
+1 ┆ `Fury said to a
+2 ┆ mouse, That he
+3 ┆ met in the
+4 ┆ house,
+5 ┆ "Let us
+6 ┆ both go to
+7 ┆ law: I will
+8 ┆ prosecute
+9 ┆ YOU. --Come,
+10 ┆ I'll take no
+11 ┆ denial; We
+12 ┆ must have a
+13 ┆ trial: For
+14 ┆ really this
+15 ┆ morning I've
+16 ┆ nothing
+17 ┆ to do."
+18 ┆ Said the
+19 ┆ mouse to the
+20 ┆ cur, "Such
+21 ┆ a trial,
+22 ┆ dear Sir,
+23 ┆ With
+24 ┆ no jury
+25 ┆ or judge,
+26 ┆ would be
+27 ┆ wasting
+28 ┆ our
+29 ┆ breath."
+30 ┆ "I'll be
+31 ┆ judge, I'll
+32 ┆ be jury,"
+33 ┆ Said
+34 ┆ cunning
+35 ┆ old Fury:
+36 ┆ "I'll
+37 ┆ try the
+38 ┆ whole
+39 ┆ cause,
+40 ┆ and
+41 ┆ condemn
+42 ┆ you
+43 ┆ to
+44 ┆ death."'
+
+ADDITIONAL BREAKS - LINEBREAKS WITHIN OBJECTS, COLUMN AND PAGE-BREAKS
+.....................................................................
+
+
+----------------------------------------
+
+LINE-BREAKS
+...........
+
+To break a line within a "paragraph object", two backslashes \\
+with a space before and a space or newline after them
+may be used.
+
+To break a line within a "paragraph object",
+two backslashes \\ with a space before
+and a space or newline after them \\
+may be used.
+
+
+The html break br enclosed in angle brackets (though undocumented) is available
+in versions prior to 3.0.13 and 2.9.7 (it remains available for the time being,
+but is depreciated).
+
+To draw a dividing line dividing paragraphs, see the section on page breaks.
+
+
+----------------------------------------
+
+PAGE BREAKS
+...........
+
+Page breaks are only relevant and honored in some output formats. A page break
+or a new page may be inserted manually using the following markup on a line on
+its own:
+
+page new =\= or ╋ breaks the page, starts a new page.
+
+page break -\- or ┼ breaks a column, starts a new column, if using columns,
+else breaks the page, starts a new page.
+
+page break line across page -..- draws a dividing line, dividing paragraphs
+
+page break:
+
+-\\-

or
- rake base

-This makes use of Rake (by Jim Weirich) and the provided Rakefile
+<:pb>

-For a list of alternative actions you may type:
- rake help
- rake -T

-%% to use install (prapared with "Rant")
----------------
-(you may use the instructions above for rake substituting rant if rant is
-installed on your system, or you may use an independent installer created using
-rant as follows:)
+page (break) new:

-in the root directory of the unpacked SiSU as root type:
- ruby ./sisu-install
+=\\=

or
- ruby ./sisu-install base

-This makes use of Rant (by Stefan Lang) and the provided Rantfile. It has been
-configured to do post installation setup setup configuration and generation of
-first test file. Note however, that additional external package dependencies,
-such as tetex-extra are not taken care of for you.
+<:pn>

- further information:
-
-

-Dependencies
---------------
-Once installed see 'man 8 sisu' for some information on additional programs
-that sisu makes use of, and that you may need or wish to install. (this will
-depend on such factors as whether you want to generate pdf, whether you will be
-using SiSU with or without a database, ...) 'man sisu_markup-samples' may also be of
-interest if the sisu-markup-samples package has also been installed.
-
-The information in man 8 may not be most up to date, and it is possible that
-more useful information can be gleaned from the following notes taken from the
-Debian control file (end edited), gives an idea of additional packages that
-SiSU can make use of if available, (the use/requirement of some of which are
-interdependent for specific actions by SiSU):
+page (break) line across page (dividing paragraphs):

-Package: sisu
-Architecture: all
-Depends: ruby (>= 1.8.2), libwebrick-ruby, unzip, zip
-Conflicts: vim-sisu, sisu-vim, sisu-remote
-Replaces: vim-sisu, sisu-vim
-Recommends: sisu-pdf, sisu-sqlite, sisu-postgresql, librmagick-ruby, trang,
-tidy, librexml-ruby, openssl, rsync, openssh-client | lsh-client, keychain,
-hyperestraier, kdissert, vim-addon-manager
-Suggests: rcs | cvs, lv, texinfo, pinfo
+-..-

-Package: sisu-complete
-Depends: ruby (>= 1.8.4), sisu, sisu-pdf, sisu-postgresql, sisu-sqlite
-Recommends: hyperestraier

-Package: sisu-pdf
-Architecture: all
-Depends: sisu, texlive-latex-base, texlive-fonts-recommended,
-texlive-latex-recommended, texlive-latex-extra
-Suggests: evince, xpdf
+BOOK INDEX
+..........

-Package: sisu-postgresql
-Depends: sisu, postgresql-8.1, libdbi-ruby, libdbm-ruby, libdbd-pg-ruby
-Suggests: pgaccess, libdbd-pgsql, postgresql-contrib-8.1
+To make an index append to paragraph the book index term relates to it, using
+an equal sign and curly braces.

-Package: sisu-sqlite
-Depends: sisu, sqlite, libdbi-ruby, libdbm-ruby, libdbd-sqlite-ruby
-Suggests: libdbd-sqlite
+Currently two levels are provided, a main term and if needed a sub-term.
+Sub-terms are separated from the main term by a colon.

-Package: sisu-markup-samples
-Depends: sisu
+ Paragraph containing main term and sub-term.
+ ={Main term:sub-term}

-%% Quick start
----------------
-Most of the installation should be taken care of by the aptitude or rant
-install. (The rant install if run in full will also test run the generation of
-the first document).

-After installation of sisu-complete, move to the document samples directory
+The index syntax starts on a new line, but there should not be an empty line
+between paragraph and index markup.

- cd /usr/share/doc/sisu/v2/sisu_markup_samples/dfsg
+The structure of the resulting index would be:

-and run
+ Main term, 1
+ sub-term, 1

- sisu -3 free_as_in_freedom.rms_and_free_software.sam_williams.sst

-[or the same:
- sisu -NhwpoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst
-]
+Several terms may relate to a paragraph, they are separated by a semicolon. If
+the term refers to more than one paragraph, indicate the number of paragraphs.

-look at output results, see the "sisu_manifest" page created for the document
+ Paragraph containing main term, second term and sub-term.
+ ={first term; second term: sub-term}

-or to generate an online document move to a writable directory, as the file
-will be downloaded there and e.g.

-sisu -3 http://www.jus.uio.no/sisu/free_culture.lawrence_lessig/free_culture.lawrence_lessig.sst
+The structure of the resulting index would be:

-the database stuff is extra perhaps, the latex stuff could be considered extra
-perhaps but neither needs to be installed for most of sisu output to work
+ First term, 1,
+ Second term, 1,
+ sub-term, 1

-examine source document, vim has syntax support

-gvim free_as_in_freedom.rms_and_free_software.sam_williams.sst
+If multiple sub-terms appear under one paragraph, they are separated under the
+main term heading from each other by a pipe symbol.

-additional markup samples in
-
+ Paragraph containing main term, second term and sub-term.
+ ={Main term:
+ sub-term+2|second sub-term;
+ Another term
+ }

-For help
- man sisu
+ A paragraph that continues discussion of the first sub-term

-%% Configuration files
----------------

-The default configuration/setup is contained within the program and is altered
-by configuration settings in /etc/[sisu version]/sisurc.yml
-or in ~/.sisu/sisurc.yml
+The plus one in the example provided indicates the first sub-term spans one
+additional paragraph. The logical structure of the resulting index would be:

-* configuration file - a yaml file
- /etc/sisu/[sisu version]/sisurc.yml
- ~/.sisu/sisurc.yml
+ Main term, 1,
+ sub-term, 1-3,
+ second sub-term, 1,
+ Another term, 1

-* directory structure - setting up of output and working directory.

-* skins - changing the appearance of a project, directory or individual
-documents within ~/.sisu/skin
- ~/.sisu/skin/doc contains individual skins, with symbolic links from
- ~/.sisu/skin/dir if the contents of a directory are to take a particular
- document skin.
+COMPOSITE DOCUMENTS MARKUP
+--------------------------

-* additional software - eg. Tex and LaTeX (tetex, tetex-base, tetex-extra on
-Debian), Postgresql, [sqlite], trang, tidy, makeinfo, ... none of which are
-required for basic html or XML processing.
+It is possible to build a document by creating a master document that requires
+other documents. The documents required may be complete documents that could be
+generated independently, or they could be markup snippets, prepared so as to be
+easily available to be placed within another text. If the calling document is a
+master document (built from other documents), it should be named with the
+suffix *.ssm* Within this document you would provide information on the other
+documents that should be included within the text. These may be other documents
+that would be processed in a regular way, or markup bits prepared only for
+inclusion within a master document *.sst* regular markup file, or *.ssi*
+(insert/information) A secondary file of the composite document is built prior
+to processing with the same prefix and the suffix *._sst*

-* if you use Vim as editor there is a syntax highlighter and fold resource
-config file for SiSU. I hope more syntax highlighters follow.
+basic markup for importing a document into a master document

-There are post installation steps (which are really part of the overall
-installation)
+<< filename1.sst

-sisu -C in your marked up document directory, should do some auto-configuring
-provided you have the right permissions for the output directories. (and
-provided the output directories have already been specified if you are not
-using the defaults).
+<< filename2.ssi

-%% Use General Overview
----------------
-Documents are marked up in SiSU syntax and kept in an ordinary text editable
-file, named with the suffix .sst, or .ssm

-Marked up SiSU documents are usually kept in a sub-directory of your choosing
+The form described above should be relied on. Within the /Vim/ editor it
+results in the text thus linked becoming hyperlinked to the document it is
+calling in which is convenient for editing.

-%% Help
----------------
+SUBSTITUTIONS
+-------------

-interactive help described below, or man page:
+*markup example:*

- man sisu
+The current Debian is ${debian_stable} the next debian will be ${debian_testing}

- man 8 sisu
- 'man sisu_markup-samples' [if the sisu-markup-samples package is also installed]
+Configure substitution in _sisu/sisu_document_make

-%% Directory Structure
----------------
-Once installed, type:
- sisu -V
+@make:
+:substitute: /${debian_stable}/,'*{Wheezy}*' /${debian_testing}/,'*{Jessie}*'

-%% Configuration File
----------------

-The defaults can be changed via SiSU's configure file sisurc.yml which the
-program expects to find in ./_sisu ~/.sisu or /etc/sisu (searched in that
-order, stopping on the first one found)
+*resulting output:*

-%% Markup
----------------
+The current *Debian* is *Wheezy* the next debian will be *Jessie*

-See man pages.
- man sisu
+Configure substitution in _sisu/sisu_document_make

- man 8 sisu

-Sample marked up document are provided with the download tarball in the
-directory:
- ./data/doc/sisu/v2/sisu_markup_samples/dfsg
+----------------------------------------

-These are installed on the system usually at:
- /usr/share/doc/sisu/v2/sisu_markup_samples/dfsg

-More markup samples are available in the package sisu-markup-samples
-
+----------------------------------------

-Many more are available online off:
-

-%% Additional Things
----------------
+ [1]:

-There is syntax support for some editors provided (together with a README file) in
+ [2]: from the *Debian* control file

- ./data/sisu/v2/conf/editor-syntax-etc
+ [*1]: square brackets

-usually installed to:
+ [*2]: square brackets

- /usr/share/sisu/v2/conf/editor-syntax-etc
+ [+1]: square brackets

-v1, v2 Changes
----------------
+ [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.

-See changelogs
+ [4]: files should be prepared using /UTF-8/ character encoding

-From a developer's perspective the substantive change between the two versions
-is to the middle layer, (the document abstraction, the intermediate document
-representation used in processing). Version 1 uses strings and relies on
-regular expressions to identify document objects, while Version 2 uses ruby
-objects. The version 1 approach whilst programming language neutral offers less
-control, and leads to complicated code; version 2 approach takes advantage of
-features within the ruby language suited to what the application does.
-Development is curently on version 2, version 1 is likely to remain for some
-time as a reference implementation.
+ [5]: a footnote or endnote

-%% Versions
+ [6]: self contained endnote marker & endnote in one

-* v1 sisu pretty mature in operation and syntax
-* v2 introduces new processing middle layer (document abstraction);
- markup same except for minor changes to document headers;
- epub output introduced
-* v3 introduces alternative (configurable) output structures
-* v4 retires what were referred to as sisu skins
+ [*]: unnumbered asterisk footnote/endnote, insert multiple asterisks if required

-%% License
----------------
+ [**]: another unnumbered asterisk footnote/endnote

-License: GPL 3 or later see the copyright file in
+ [*3]: editors notes, numbered asterisk footnote/endnote series

- ./data/doc/sisu
+ [+2]: editors notes, numbered plus symbol footnote/endnote series

-usually installed to:
+ [7]:

- /usr/share/doc/sisu
+ [8]:

-%% SiSU Standard
------------------
+ [10]: Table from the Wealth of Networks by Yochai Benkler
+
+
+
+==============================================================================
+
+ Title: SiSU - README
+
+ Creator: Ralph Amissah
+
+ Rights: Copyright (C) Ralph Amissah 2014;\\ License: GPL 3 (part of SiSU
+ documentation)
+
+ Subject: ebook, epublishing, electronic book, electronic publishing,
+ electronic document, electronic citation, data structure,
+ citation systems, search
+
+ Publisher: SiSU http://www.jus.uio.no/sisu (this copy)
+
+ Date created: 2014-02-02
+
+ Date available: 2014-02-02
+
+ Date modified: 2014-02-02
+
+ Date: 2014-02-02
+
+ Sourcefile: README.ssm.sst
+
+ Filetype: SiSU text insert 5.0,
+
+ Source digest: SHA256(README.ssm.sst)=
+ 5927789066d1eb9cf0321946d46e3ce2a66414557038d5c745bb009233611dd8
+
+ Generated by: Generated by: SiSU 6.0.1 of 2014w05/2 (2014-02-04)
+
+ Ruby version: ruby 2.0.0p353 (2013-11-22) [i386-linux-gnu]
+
+ Document (ao) last generated: 2014-02-04 23:45:41 -0500
+
+==============================================================================
+
+
+plaintext (plain text):
+ http://niu/manual/en/txt/README.txt
+
+Other versions of this document:

-SiSU uses:
+manifest:
+ http://niu/manual/en/manifest/README.html

-* Standard SiSU markup syntax,
-* Standard SiSU meta-markup syntax, and the
-* Standard SiSU object citation numbering and system
+at:
+ http://niu/manual

-© Ralph Amissah 1997, current 2006.
-All Rights Reserved.

-* however note the License section

-CHANGELOG
- ./CHANGELOG
-and see
-
-
+* Generated by: SiSU 6.0.1 of 2014w05/2 (2014-02-04)
+* Ruby version: ruby 2.0.0p353 (2013-11-22) [i386-linux-gnu]
+* Last Generated on: 2014-02-04 23:45:43 -0500
+* SiSU http://www.sisudoc.org/
diff --git a/data/doc/sisu/CHANGELOG_v5 b/data/doc/sisu/CHANGELOG_v5
index e79f97ca..15e4ce0d 100644
--- a/data/doc/sisu/CHANGELOG_v5
+++ b/data/doc/sisu/CHANGELOG_v5
@@ -65,6 +65,7 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_5.3.1.orig.tar.xz
* documentation, manpage README etc.
* sisu manual directory moved
* sisu manual updated
+ * README & sisu.1 (manpage) updated
* removed html man pages (man2html)

%% 5.3.0.orig.tar.xz (2014-01-26:03/7)
diff --git a/data/doc/sisu/CHANGELOG_v6 b/data/doc/sisu/CHANGELOG_v6
index 23925664..4454c3e1 100644
--- a/data/doc/sisu/CHANGELOG_v6
+++ b/data/doc/sisu/CHANGELOG_v6
@@ -55,6 +55,7 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_6.0.1.orig.tar.xz
* documentation, manpage README etc.
* sisu manual directory moved
* sisu manual updated
+ * README & sisu.1 (manpage) updated
* removed html man pages (man2html)

%% 6.0.0.orig.tar.xz (2014-01-26:03/7)
diff --git a/man/man1/sisu.1 b/man/man1/sisu.1
index a692a9f4..f6bb6b5b 100644
--- a/man/man1/sisu.1
+++ b/man/man1/sisu.1
@@ -1,4 +1,4 @@
-.TH "sisu" "1" "2013-11-27" "5.1.0" "SiSU"
+.TH "sisu" "1" "2014-02-05" "6.0.1" "SiSU"
.br
.SH NAME
.br
@@ -37,197 +37,68 @@ RALPH AMISSAH

.BR
-.B SiSU
-is a framework for document structuring, publishing (in multiple open standard
-formats) 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 (including the population of
-sql databases) that (can) share a common numbering system for the citation of
-text within a document.
-
-.BR
-.B SiSU
-is developed under an open source, software libre license (
-.I GPLv3
-). Its use case for development is work with medium to large document sets and
-cope with evolving document formats/ representation technologies. Documents are
-prepared once, and generated as need be to update the technical presentation or
-add additional output formats. Various output formats (including search related
-output) share a common mechanism for cross-output-format citation.

-.BR
.B SiSU
-both defines a markup syntax and provides an engine that produces open
-standards format outputs from documents prepared with
+is a lightweight markup based document creation and publishing framework that
+is controlled from the command line. Prepare documents for
.B 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
+using your text editor of choice, then use
.B SiSU
-markup is more sparse than html and outputs which include
-.I HTML,
-.I EPUB,
-.I ODT
-(Open Document Format text),
-.I LaTeX,
-landscape and portrait
-.I PDF,
-all of which can be added to and updated.
-.B SiSU
-is also able to populate
-.I SQL
-type databases at an object level, which means that searches can be made with
-that degree of granularity.
+to generate various output document formats.

.BR
-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
-.B SiSU
-markup applied to a document,
+From a single lightly prepared document (plain-text
+.I UTF-8
+) 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.
.B SiSU
-custom builds (to take advantage of the strengths of different ways of
-representing documents) various standard open output formats including plain
-text,
+produces: plain-text,
.I HTML,
.I XHTML,
.I XML,
.I EPUB,
-.I ODT,
-.I LaTeX
-or
-.I PDF
-files, and populate an
+.I ODF:
+.I ODT
+(Opendocument),
+.I LaTeX,
+.I PDF,
+and populates an
.I SQL
-database with objects[^1] (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.
+database (
+.I PostgreSQL
+or
+.I SQLite
+) with text objects, roughly, paragraph sized chunks so that document searches
+are done at this level of granularity.

.BR
-In preparing a
-.B 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[^2] the
-different forms of output requested.
+Outputs share a common citation numbering system, associated with text objects
+and any semantic meta-data provided about the document.

.BR
-.B SiSU
-works with an abstraction of the document based on its structure which is
-comprised of its headings[^3] and objects[^4], which enables
-.B 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 basis for citing material
-within a document across the different output format types. This is significant
-as page numbers are not well suited to the digital age, in web publishing,
-changing a browser's default font or using a different browser can mean that
-text will appear on a different page; and publishing in different formats,
-html, landscape and portrait pdf etc. again page numbers are not useful to cite
-text. Dealing with documents at an object level together with object numbering
-also has implications for search that
-.B SiSU
-is able to take advantage of.

-.BR
-One of the challenges of maintaining documents is to keep them in a format that
-allows use of them independently of proprietary platforms. Consider issues
-related to 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.
-.B SiSU
-provides the flexibility of producing documents in multiple non-proprietary
-open formats including
-.I HTML,
-.I EPUB,
-[^5]
-.I ODT,
-[^6]
-.I PDF
-[^7]
-.I ODF,
-[^8]. Whilst
.B 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
-.B SiSU
-can be migrated to other document formats. Further security is provided by the
-fact that the software itself,
-.B SiSU
-is available under
-.I GPLv3
-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.
-.B SiSU
-permits new forms of output to be added as they become important, (Open
-Document Format text was added in 2006 when it became an ISO standard for
-office applications and the archival of documents),
-.I EPUB
-was introduced in 2009; and allows the technical representations existing
-output to be updated (
-.I HTML
-has evolved and the related module has been updated repeatedly over the years,
-presumably when the World Wide Web Consortium (w3c) finalises
-.I HTML
-5 which is currently under development, the
-.I HTML
-module will again be updated allowing all existing documents to be regenerated
-as
-.I HTML
-5).
+also provides concordance files, document content certificates and manifests of
+generated output. Book indexes may be made.

.BR
-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.
+Some document markup samples are provided in the package sisu -markup-samples.
+Homepages:

-.BR
-.B 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 thesauri, together with the flexibility of
-.B SiSU
-offers great possibilities.
+*

-.BR
-.B SiSU
-is primarily for published works, which can take advantage of the citation
-system to reliably reference its documents.
-.B 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
-.B SiSU.
-
-.BR
-
+*

-.BR
-

.SH COMMANDS SUMMARY

.SH DESCRIPTION

.BR
+
.B SiSU
is a document publishing system, that from a simple single marked-up document,
produces multiple output formats including:
@@ -428,6 +299,9 @@ produces html output, the document in a single file (scroll.html) only. Compare
produces html output, segmented text with table of contents (toc.html and
index.html). Compare --html-scroll and --html
.TP
+.B --html-strict [filename/wildcard]
+produces html with --strict option. see --strict
+.TP
.B -I [filename/wildcard]
see --texinfo
.TP
@@ -498,6 +372,9 @@ see --exc-*
.B -o [filename/wildcard/url]
see --odt
.TP
+.B --ocn
+see --inc-ocn and --exc-ocn
+.TP
.B --odf [filename/wildcard/url]
see --odt
.TP
@@ -702,6 +579,10 @@ for sending). See the -S option without [filename/wildcard]. Alias -S
.B --source [filename/wildcard]
copies sisu markup file to output directory. Alias -s
.TP
+.B --strict
+together with --html, produces more w3c compliant html, for example not having
+purely numeric identifiers for text, the location object url#33 becomes url#o33
+.TP
.B -T [filename/wildcard (*.termsheet.rb)]
standard form document builder, preprocessing feature
.TP
@@ -2279,6 +2160,8 @@ The html break br enclosed in angle brackets (though undocumented) is available
in versions prior to 3.0.13 and 2.9.7 (it remains available for the time being,
but is depreciated).

+.BR
+To draw a dividing line dividing paragraphs, see the section on page breaks.
.SH PAGE BREAKS

.BR
--
cgit v1.2.3}}}}