diff options
| author | Ralph Amissah <ralph@amissah.com> | 2012-12-30 15:51:42 -0500 |
|---|---|---|
| committer | Ralph Amissah <ralph@amissah.com> | 2012-12-30 15:51:42 -0500 |
| commit | 780c5275cb88587243902e6d720c935ecbb8dd94 (patch) | |
| tree | 0b90fea99f7fe015a2deb4b60479a1f11f9c9277 | |
| parent | v4 v3: manpage, attempt to improve output (line-spacing) (diff) | |
v4: documentation, sisu.1 manpage & minor
20 files changed, 4800 insertions, 5815 deletions
diff --git a/data/doc/sisu/CHANGELOG_v4 b/data/doc/sisu/CHANGELOG_v4 index 60ed276d..471c83e9 100644 --- a/data/doc/sisu/CHANGELOG_v4 +++ b/data/doc/sisu/CHANGELOG_v4 @@ -57,6 +57,8 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_4.0.1.orig.tar.xz sisu -v -k sisu --version --color-off +* v4: documentation minor updates and regenerated manpage + %% 4.0.0.orig.tar.xz (2012-12-12:50/3) http://sources.sisudoc.org/gitweb/?p=code/sisu.git;a=shortlog;h=refs/tags/sisu_4.0.0 http://sources.sisudoc.org/gitweb/?p=code/sisu.git;a=shortlog;h=refs/tags/debian/sisu_4.0.0-1 diff --git a/data/doc/sisu/html/sisu-concordance.1.html b/data/doc/sisu/html/sisu-concordance.1.html index b4e53653..ef456d75 100644 --- a/data/doc/sisu/html/sisu-concordance.1.html +++ b/data/doc/sisu/html/sisu-concordance.1.html @@ -3,7 +3,7 @@ <html> <head> -<title>SISU\-CONCORDANCE(1) manual page</title> +<title>SISU-CONCORDANCE(1) manual page</title> </head> <body bgcolor='white'> <a href='#toc'>Table of Contents</a><p> @@ -30,8 +30,6 @@ for <b>sisu --concordance</b> (or <b>sisu -w</b>) which produces an HTML concord , <br> <a href='http:~/bin/man2html?sisu-epub:1'><i>sisu-epub</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-git:1'><i>sisu-git</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-harvest:1'><i>sisu-harvest</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-html:1'><i>sisu-html</i>(1)</a> @@ -42,8 +40,6 @@ for <b>sisu --concordance</b> (or <b>sisu -w</b>) which produces an HTML concord , <br> <a href='http:~/bin/man2html?sisu-pg:1'><i>sisu-pg</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-po:1'><i>sisu-po</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-sqlite:1'><i>sisu-sqlite</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-txt:1'><i>sisu-txt</i>(1)</a> diff --git a/data/doc/sisu/html/sisu-epub.1.html b/data/doc/sisu/html/sisu-epub.1.html index fe853f62..6a84b876 100644 --- a/data/doc/sisu/html/sisu-epub.1.html +++ b/data/doc/sisu/html/sisu-epub.1.html @@ -3,7 +3,7 @@ <html> <head> -<title>SISU\-EPUB(1) manual page</title> +<title>SISU-EPUB(1) manual page</title> </head> <body bgcolor='white'> <a href='#toc'>Table of Contents</a><p> @@ -30,8 +30,6 @@ The <b>sisu-epub</b> command is an alias for , <br> <a href='http:~/bin/man2html?sisu-concordance:1'><i>sisu-concordance</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-git:1'><i>sisu-git</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-harvest:1'><i>sisu-harvest</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-html:1'><i>sisu-html</i>(1)</a> @@ -42,8 +40,6 @@ The <b>sisu-epub</b> command is an alias for , <br> <a href='http:~/bin/man2html?sisu-pg:1'><i>sisu-pg</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-po:1'><i>sisu-po</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-sqlite:1'><i>sisu-sqlite</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-txt:1'><i>sisu-txt</i>(1)</a> diff --git a/data/doc/sisu/html/sisu-git.1.html b/data/doc/sisu/html/sisu-git.1.html index b2955f6e..a23d0118 100644 --- a/data/doc/sisu/html/sisu-git.1.html +++ b/data/doc/sisu/html/sisu-git.1.html @@ -3,7 +3,7 @@ <html> <head> -<title>SISU\-GIT(1) manual page</title> +<title>SISU-GIT(1) manual page</title> </head> <body bgcolor='white'> <a href='#toc'>Table of Contents</a><p> @@ -40,8 +40,6 @@ document and associated parts (images, ). , <br> <a href='http:~/bin/man2html?sisu-pg:1'><i>sisu-pg</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-po:1'><i>sisu-po</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-sqlite:1'><i>sisu-sqlite</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-txt:1'><i>sisu-txt</i>(1)</a> diff --git a/data/doc/sisu/html/sisu-harvest.1.html b/data/doc/sisu/html/sisu-harvest.1.html index ac5d3034..8d264278 100644 --- a/data/doc/sisu/html/sisu-harvest.1.html +++ b/data/doc/sisu/html/sisu-harvest.1.html @@ -3,7 +3,7 @@ <html> <head> -<title>SISU\-HARVEST(1) manual page</title> +<title>SISU-HARVEST(1) manual page</title> </head> <body bgcolor='white'> <a href='#toc'>Table of Contents</a><p> @@ -34,8 +34,6 @@ Also</a></h2> , <br> <a href='http:~/bin/man2html?sisu-epub:1'><i>sisu-epub</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-git:1'><i>sisu-git</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-html:1'><i>sisu-html</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-pdf:1'><i>sisu-pdf</i>(1)</a> @@ -44,8 +42,6 @@ Also</a></h2> , <br> <a href='http:~/bin/man2html?sisu-pg:1'><i>sisu-pg</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-po:1'><i>sisu-po</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-sqlite:1'><i>sisu-sqlite</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-txt:1'><i>sisu-txt</i>(1)</a> diff --git a/data/doc/sisu/html/sisu-html.1.html b/data/doc/sisu/html/sisu-html.1.html index 3114567e..a95b7796 100644 --- a/data/doc/sisu/html/sisu-html.1.html +++ b/data/doc/sisu/html/sisu-html.1.html @@ -3,7 +3,7 @@ <html> <head> -<title>SISU\-HTML(1) manual page</title> +<title>SISU-HTML(1) manual page</title> </head> <body bgcolor='white'> <a href='#toc'>Table of Contents</a><p> @@ -32,8 +32,6 @@ The <b>sisu-html</b> command is an alias for , <br> <a href='http:~/bin/man2html?sisu-epub:1'><i>sisu-epub</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-git:1'><i>sisu-git</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-harvest:1'><i>sisu-harvest</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-pdf:1'><i>sisu-pdf</i>(1)</a> @@ -42,8 +40,6 @@ The <b>sisu-html</b> command is an alias for , <br> <a href='http:~/bin/man2html?sisu-pg:1'><i>sisu-pg</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-po:1'><i>sisu-po</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-sqlite:1'><i>sisu-sqlite</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-txt:1'><i>sisu-txt</i>(1)</a> diff --git a/data/doc/sisu/html/sisu-odf.1.html b/data/doc/sisu/html/sisu-odf.1.html index f2e32f3f..fddd3148 100644 --- a/data/doc/sisu/html/sisu-odf.1.html +++ b/data/doc/sisu/html/sisu-odf.1.html @@ -3,7 +3,7 @@ <html> <head> -<title>SISU\-ODF(1) manual page</title> +<title>SISU-ODF(1) manual page</title> </head> <body bgcolor='white'> <a href='#toc'>Table of Contents</a><p> @@ -32,8 +32,6 @@ file. , <br> <a href='http:~/bin/man2html?sisu-epub:1'><i>sisu-epub</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-git:1'><i>sisu-git</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-harvest:1'><i>sisu-harvest</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-html:1'><i>sisu-html</i>(1)</a> @@ -42,8 +40,6 @@ file. , <br> <a href='http:~/bin/man2html?sisu-pg:1'><i>sisu-pg</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-po:1'><i>sisu-po</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-sqlite:1'><i>sisu-sqlite</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-txt:1'><i>sisu-txt</i>(1)</a> diff --git a/data/doc/sisu/html/sisu-pdf.1.html b/data/doc/sisu/html/sisu-pdf.1.html index 2394a227..ec9f39d2 100644 --- a/data/doc/sisu/html/sisu-pdf.1.html +++ b/data/doc/sisu/html/sisu-pdf.1.html @@ -3,7 +3,7 @@ <html> <head> -<title>SISU\-PDF(1) manual page</title> +<title>SISU-PDF(1) manual page</title> </head> <body bgcolor='white'> <a href='#toc'>Table of Contents</a><p> @@ -32,8 +32,6 @@ Also</a></h2> , <br> <a href='http:~/bin/man2html?sisu-epub:1'><i>sisu-epub</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-git:1'><i>sisu-git</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-harvest:1'><i>sisu-harvest</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-html:1'><i>sisu-html</i>(1)</a> @@ -42,8 +40,6 @@ Also</a></h2> , <br> <a href='http:~/bin/man2html?sisu-pg:1'><i>sisu-pg</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-po:1'><i>sisu-po</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-sqlite:1'><i>sisu-sqlite</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-txt:1'><i>sisu-txt</i>(1)</a> diff --git a/data/doc/sisu/html/sisu-pg.1.html b/data/doc/sisu/html/sisu-pg.1.html index 98aa2070..056598f2 100644 --- a/data/doc/sisu/html/sisu-pg.1.html +++ b/data/doc/sisu/html/sisu-pg.1.html @@ -3,7 +3,7 @@ <html> <head> -<title>SISU\-PG(1) manual page</title> +<title>SISU-PG(1) manual page</title> </head> <body bgcolor='white'> <a href='#toc'>Table of Contents</a><p> @@ -32,16 +32,12 @@ The <b>sisu-pq</b> command is an alias for <b>sisu , <br> <a href='http:~/bin/man2html?sisu-epub:1'><i>sisu-epub</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-git:1'><i>sisu-git</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-harvest:1'><i>sisu-harvest</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-html:1'><i>sisu-html</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-pdf:1'><i>sisu-pdf</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-po:1'><i>sisu-po</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-odf:1'><i>sisu-odf</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-sqlite:1'><i>sisu-sqlite</i>(1)</a> diff --git a/data/doc/sisu/html/sisu-po.1.html b/data/doc/sisu/html/sisu-po.1.html index 3c87cce1..ea1c5b43 100644 --- a/data/doc/sisu/html/sisu-po.1.html +++ b/data/doc/sisu/html/sisu-po.1.html @@ -3,7 +3,7 @@ <html> <head> -<title>SISU\-PO(1) manual page</title> +<title>SISU-PO(1) manual page</title> </head> <body bgcolor='white'> <a href='#toc'>Table of Contents</a><p> @@ -33,8 +33,6 @@ Experimental, and under development. , <br> <a href='http:~/bin/man2html?sisu-epub:1'><i>sisu-epub</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-git:1'><i>sisu-git</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-harvest:1'><i>sisu-harvest</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-html:1'><i>sisu-html</i>(1)</a> diff --git a/data/doc/sisu/html/sisu-sqlite.1.html b/data/doc/sisu/html/sisu-sqlite.1.html index 218dbc81..f40c3a8b 100644 --- a/data/doc/sisu/html/sisu-sqlite.1.html +++ b/data/doc/sisu/html/sisu-sqlite.1.html @@ -3,7 +3,7 @@ <html> <head> -<title>SISU\-SQLITE(1) manual page</title> +<title>SISU-SQLITE(1) manual page</title> </head> <body bgcolor='white'> <a href='#toc'>Table of Contents</a><p> @@ -32,8 +32,6 @@ The <b>sisu-sqlite</b> command is an alias for , <br> <a href='http:~/bin/man2html?sisu-epub:1'><i>sisu-epub</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-git:1'><i>sisu-git</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-harvest:1'><i>sisu-harvest</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-html:1'><i>sisu-html</i>(1)</a> @@ -44,8 +42,6 @@ The <b>sisu-sqlite</b> command is an alias for , <br> <a href='http:~/bin/man2html?sisu-pg:1'><i>sisu-pg</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-po:1'><i>sisu-po</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-txt:1'><i>sisu-txt</i>(1)</a> . <p> diff --git a/data/doc/sisu/html/sisu-txt.1.html b/data/doc/sisu/html/sisu-txt.1.html index fb96ed17..dbfc71f4 100644 --- a/data/doc/sisu/html/sisu-txt.1.html +++ b/data/doc/sisu/html/sisu-txt.1.html @@ -3,7 +3,7 @@ <html> <head> -<title>SISU\-TXT(1) manual page</title> +<title>SISU-TXT(1) manual page</title> </head> <body bgcolor='white'> <a href='#toc'>Table of Contents</a><p> @@ -32,8 +32,6 @@ file. , <br> <a href='http:~/bin/man2html?sisu-epub:1'><i>sisu-epub</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-git:1'><i>sisu-git</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-harvest:1'><i>sisu-harvest</i>(1)</a> , <br> <a href='http:~/bin/man2html?sisu-html:1'><i>sisu-html</i>(1)</a> @@ -44,8 +42,6 @@ file. , <br> <a href='http:~/bin/man2html?sisu-pg:1'><i>sisu-pg</i>(1)</a> , <br> -<a href='http:~/bin/man2html?sisu-po:1'><i>sisu-po</i>(1)</a> -, <br> <a href='http:~/bin/man2html?sisu-sqlite:1'><i>sisu-sqlite</i>(1)</a> . <p> diff --git a/data/doc/sisu/html/sisu.1.html b/data/doc/sisu/html/sisu.1.html index 345e574b..f7268daa 100644 --- a/data/doc/sisu/html/sisu.1.html +++ b/data/doc/sisu/html/sisu.1.html @@ -34,47 +34,44 @@ sisu [-CcFLSVvW] <p> <br> sisu (--configure|--webrick|--sample-search-form) <h2><a name='sect2' href='#toc2'>Sisu - Manual,</a></h2> -RALPH AMISSAH <br> - +RALPH AMISSAH <p> -<h2><a name='sect3' href='#toc3'>What is Sisu?</a></h2> -<br> +<h2><a name='sect3' href='#toc3'>What +is Sisu?</a></h2> <p> <h2><a name='sect4' href='#toc4'>Introduction - What is Sisu?</a></h2> -<br> -<p> <br> -<b>SiSU</b> 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. -<p> <br> -<b>SiSU</b> is developed under an open source, software libre license ( <i>GPLv3</i> -). 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. - -<p> <br> -<b>SiSU</b> both defines a markup syntax and provides an engine that produces -open standards format outputs from documents prepared with <b>SiSU</b> 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 <b>SiSU</b> markup is more sparse than html and -outputs which include <i>HTML,</i> <i>EPUB,</i> <i>ODT</i> (Open Document Format text), <i>LaTeX,</i> -landscape and portrait <i>PDF,</i> all of which can be added to and updated. <b>SiSU</b> -is also able to populate <i>SQL</i> type databases at an object level, which means -that searches can be made with that degree of granularity. -<p> <br> -Source document preparation and output generation is a two step process: +<p> +<p> <b>SiSU</b> 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. +<p> <b>SiSU</b> is developed under an open source, software +libre license ( <i>GPLv3</i> ). 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. +<p> <b>SiSU</b> both defines a markup syntax and provides +an engine that produces open standards format outputs from documents prepared +with <b>SiSU</b> 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 <b>SiSU</b> markup is more sparse +than html and outputs which include <i>HTML,</i> <i>EPUB,</i> <i>ODT</i> (Open Document Format +text), <i>LaTeX,</i> landscape and portrait <i>PDF,</i> all of which can be added to +and updated. <b>SiSU</b> is also able to populate <i>SQL</i> type databases at an object +level, which means that searches can be made with that degree of granularity. + +<p> 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 @@ -90,41 +87,40 @@ 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. -<p> <br> -In preparing a <b>SiSU</b> 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. -<p> <br> -<b>SiSU</b> 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</b> 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</b> is able -to take advantage of. -<p> <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</b> provides the flexibility of producing documents in multiple non-proprietary -open formats including <i>HTML,</i> <i>EPUB,</i> [^5] <i>ODT,</i> [^6] <i>PDF</i> [^7] <i>ODF,</i> [^8]. Whilst -<b>SiSU</b> 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</b> -can be migrated to other document formats. Further security is provided -by the fact that the software itself, <b>SiSU</b> is available under <i>GPLv3</i> a licence +<p> In preparing a <b>SiSU</b> +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. +<p> <b>SiSU</b> 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</b> 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</b> is able to take advantage of. +<p> 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</b> provides the +flexibility of producing documents in multiple non-proprietary open formats +including <i>HTML,</i> <i>EPUB,</i> [^5] <i>ODT,</i> [^6] <i>PDF</i> [^7] <i>ODF,</i> [^8]. Whilst <b>SiSU</b> 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</b> can +be migrated to other document formats. Further security is provided by the +fact that the software itself, <b>SiSU</b> is available under <i>GPLv3</i> 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 @@ -137,1150 +133,948 @@ related module has been updated repeatedly over the years, presumably when the World Wide Web Consortium (w3c) finalises <i>HTML</i> 5 which is currently under development, the <i>HTML</i> module will again be updated allowing all existing documents to be regenerated as <i>HTML</i> 5). -<p> <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. -<p> <br> -<b>SiSU</b> 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</b> -offers great possibilities. -<p> <br> -<b>SiSU</b> is primarily for published works, which can take advantage of the -citation system to reliably reference its documents. <b>SiSU</b> 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.</b> -<p> <br> -<<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> 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. +<p> <b>SiSU</b> 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</b> offers great possibilities. +<p> <b>SiSU</b> is primarily for published works, +which can take advantage of the citation system to reliably reference its +documents. <b>SiSU</b> 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.</b> +<p> <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > -<p> <br> -<<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> +<p> <<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> > -<p> + <h2><a name='sect5' href='#toc5'>Commands Summary</a></h2> -<br> <p> <h2><a name='sect6' href='#toc6'>Description</a></h2> -<p> <br> -<b>SiSU</b> is a document publishing system, that from a simple single marked-up -document, produces multiple output formats including: <i>plaintext,</i> <i>HTML,</i> -<i>XHTML,</i> <i>XML,</i> <i>EPUB,</i> <i>ODT</i> ( <i>OpenDocument</i> ( <i>ODF</i> ) text), <i>LaTeX,</i> <i>PDF,</i> info, and -<i>SQL</i> ( <i>PostgreSQL</i> and <i>SQLite</i> ) , which share text object numbers ("object -citation numbering") and the same document structure information. For more -see: <<a href='http://sisudoc.org'>http://sisudoc.org</a> +<p> <b>SiSU</b> is a document publishing system, that +from a simple single marked-up document, produces multiple output formats +including: <i>plaintext,</i> <i>HTML,</i> <i>XHTML,</i> <i>XML,</i> <i>EPUB,</i> <i>ODT</i> ( <i>OpenDocument</i> ( <i>ODF</i> +) text), <i>LaTeX,</i> <i>PDF,</i> info, and <i>SQL</i> ( <i>PostgreSQL</i> and <i>SQLite</i> ) , which share +text object numbers ("object citation numbering") and the same document +structure information. For more see: <<a href='http://sisudoc.org'>http://sisudoc.org</a> > or <<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> > -<p> -<h2><a name='sect7' href='#toc7'>Document Processing -Command Flags</a></h2> + +<h2><a name='sect7' href='#toc7'>Document Processing Command Flags</a></h2> <p> <dl> <dt><b>-a [filename/wildcard]</b> </dt> -<dd>produces <i>plaintext</i> with Unix linefeeds -and without markup, (object numbers are omitted), has footnotes at end -of each paragraph that contains them [ -A for 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) -<p> </dd> - -<dt><b>-b [filename/wildcard]</b> </dt> -<dd>see --xhtml -<p> </dd> +<dd>produces <i>plaintext</i> +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) </dd> + +<dt><b>-b [filename/wildcard]</b> +</dt> +<dd>see --xhtml </dd> <dt><b>--by-*</b> </dt> -<dd>see --output-by-* -<p> </dd> +<dd>see --output-by-* </dd> <dt><b>-C</b> </dt> -<dd>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. -<p> </dd> +<dd>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. </dd> -<dt><b>-CC</b> </dt> -<dd>see --configure -<p> </dd> +<dt><b>-CC</b> +</dt> +<dd>see --configure </dd> <dt><b>-c [filename/wildcard]</b> </dt> -<dd>see --color-toggle -<p> </dd> +<dd>see --color-toggle </dd> -<dt><b>--color-toggle -[filename/wildcard]</b> </dt> -<dd>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 +<dt><b>--color</b> </dt> +<dd>see --color-on </dd> -<p>- -<p>c -<p> </dd> +<dt><b>--color-off</b> +</dt> +<dd>turn off color in output to terminal </dd> -<dt><b>--configure</b> </dt> -<dd>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. -<p> </dd> +<dt><b>--color-on</b> </dt> +<dd>turn on color in output to +terminal </dd> -<dt><b>--concordance -[filename/wildcard]</b> </dt> -<dd>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 -<p> </dd> +<dt><b>--color-toggle [filename/wildcard]</b> </dt> +<dd>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 </dd> + +<dt><b>--configure</b> </dt> +<dd>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. </dd> + +<dt><b>--concordance [filename/wildcard]</b> </dt> +<dd>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 </dd> <dt><b>-D [instruction] [filename]</b> </dt> -<dd>see --pg -<p> </dd> +<dd>see +--pg </dd> -<dt><b>-d [--db-[database type - (sqlite|pg)]] --[instruction] [filename]</b> </dt> +<dt><b>-d [--db-[database type (sqlite|pg)]] --[instruction] [filename]</b> </dt> <dd>see --sqlite -<p> </dd> - -<dt><b>--dal [filename/wildcard/url]</b> -</dt> -<dd>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. +</dd> -<p>Alias -m -<p> </dd> +<dt><b>--dal [filename/wildcard/url]</b> </dt> +<dd>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 </dd> <dt><b>--delete [filename/wildcard]</b> </dt> -<dd>see --zap -<p> </dd> +<dd>see --zap </dd> -<dt><b>--dump[=directory_path] [filename/wildcard]</b> -</dt> -<dd>places output in directory specified, if none is specified in the current -directory (pwd). Compare --redirect -<p> </dd> +<dt><b>--dump[=directory_path] +[filename/wildcard]</b> </dt> +<dd>places output in directory specified, if none is specified +in the current directory (pwd). Compare --redirect </dd> <dt><b>-e [filename/wildcard]</b> </dt> -<dd>see --epub -<p> </dd> - -<dt><b>--epub -[filename/wildcard]</b> </dt> -<dd>produces an epub document, [sisu version >=2 ] (filename.epub). +<dd>see +--epub </dd> -<p>Alias -e -<p> </dd> +<dt><b>--epub [filename/wildcard]</b> </dt> +<dd>produces an epub document, [sisu version +>=2 ] (filename.epub). Alias -e </dd> <dt><b>--exc-*</b> </dt> -<dd>exclude output feature, overrides configuration settings ---exc- <i>ocn,</i> (exclude <i>object</i> citation numbering, (switches off <i>object</i> 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-* -<p> </dd> +<dd>exclude output feature, overrides configuration +settings --exc-ocn, (exclude <i>object</i> citation numbering, (switches off <i>object</i> +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-* </dd> <dt><b>-F [--webserv=webrick]</b> </dt> -<dd>see --sample-search-form +<dd>see --sample-search-form </dd> -<p> </dd> - -<dt><b>-f [optional string part of filename]</b> </dt> -<dd>see --find -<p> </dd> +<dt><b>-f [optional string +part of filename]</b> </dt> +<dd>see --find </dd> -<dt><b>--find [optional string part - of filename]</b> </dt> -<dd>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 -<p> </dd> +<dt><b>--find [optional string part of filename]</b> </dt> +<dd>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 </dd> -<dt><b>-G [optional string part of filename]</b> </dt> -<dd>see --find -<p> </dd> - -<dt><b>-g [filename/wildcard]</b> +<dt><b>-G [optional string part of filename]</b> </dt> -<dd> -<p>see --git -<p> </dd> +<dd>see --find </dd> -<dt><b>--git [filename/wildcard]</b> </dt> -<dd>produces or updates markup source file -structure in a git repo (experimental and subject to change). Alias -g -<p> </dd> +<dt><b>-g [filename/wildcard]</b> </dt> +<dd>see --git </dd> -<dt><b>--glob -[optional string part of filename]</b> </dt> -<dd>see --find -<p> </dd> +<dt><b>--git [filename/wildcard]</b> </dt> +<dd>produces +or updates markup source file structure in a git repo (experimental and +subject to change). Alias -g </dd> -<dt><b>-h [filename/wildcard]</b> </dt> +<dt><b>--glob [optional string part of filename]</b> </dt> <dd>see +--find </dd> -<p>- -<p>- -<p>html -<p> </dd> +<dt><b>-h [filename/wildcard]</b> </dt> +<dd>see --html </dd> <dt><b>--harvest *.ss[tm]</b> </dt> -<dd>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. -<p> </dd> +<dd>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. </dd> -<dt><b>--help [topic]</b> </dt> -<dd>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. -<p> </dd> +<dt><b>--help [topic]</b> +</dt> +<dd>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. </dd> <dt><b>--html [filename/wildcard]</b> </dt> -<dd>produces html output, segmented text -with table of contents (toc.html and index.html) and the document in a single -file (scroll.html). Alias -h -<p> </dd> +<dd>produces html output, segmented +text with table of contents (toc.html and index.html) and the document in +a single file (scroll.html). Alias -h </dd> <dt><b>-I [filename/wildcard]</b> </dt> -<dd>see --texinfo -<p> </dd> +<dd>see --texinfo </dd> -<dt><b>-i [filename/wildcard]</b> -</dt> -<dd> -<p>see --manpage -<p> </dd> +<dt><b>-i +[filename/wildcard]</b> </dt> +<dd>see --manpage </dd> <dt><b>--inc-*</b> </dt> -<dd>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-* -<p> </dd> +<dd>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-* </dd> -<dt><b>-j [filename/wildcard]</b> -</dt> -<dd>copies images associated with a file for use by html, xhtml & xml outputs -(automatically invoked by --dump & redirect). -<p> </dd> +<dt><b>-j [filename/wildcard]</b> </dt> +<dd>copies images associated with a file for use +by html, xhtml & xml outputs (automatically invoked by --dump & redirect). </dd> -<dt><b>--keep-processing-files [filename/wildcard/url]</b> +<dt><b>-k</b> </dt> -<dd> -<p>see --maintenance -<p> </dd> +<dd>see --color-off </dd> + +<dt><b>--keep-processing-files [filename/wildcard/url]</b> </dt> +<dd>see --maintenance +</dd> <dt><b>-L</b> </dt> -<dd>prints license information. -<p> </dd> +<dd>prints license information. </dd> -<dt><b>-M [filename/wildcard/url]</b> -</dt> -<dd> -<p>see --maintenance -<p> </dd> +<dt><b>-M [filename/wildcard/url]</b> </dt> +<dd>see --maintenance +</dd> <dt><b>-m [filename/wildcard/url]</b> </dt> -<dd>see --dal (document abstraction -level/layer) -<p> </dd> +<dd>see --dal (document abstraction level/layer) </dd> -<dt><b>--machine [filename/wildcard/url]</b> </dt> -<dd>see --dal (document abstraction -level/layer) -<p> </dd> +<dt><b>--machine +[filename/wildcard/url]</b> </dt> +<dd>see --dal (document abstraction level/layer) </dd> -<dt><b>--maintenance [filename/wildcard/url]</b> </dt> -<dd>maintenance mode, interim -processing files are preserved and their locations indicated. (also see --V). Aliases -M and --keep-processing-files. -<p> </dd> +<dt><b>--maintenance +[filename/wildcard/url]</b> </dt> +<dd>maintenance mode, interim processing files are +preserved and their locations indicated. (also see -V). Aliases -M and --keep-processing-files. +</dd> <dt><b>--manpage [filename/wildcard]</b> </dt> -<dd>produces -man page of file, not suitable for all outputs. Alias -i -<p> </dd> - -<dt><b>-N [filename/wildcard/url]</b> -</dt> -<dd>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. -<p> </dd> - -<dt><b>-n -[filename/wildcard/url]</b> </dt> -<dd>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. -<p> </dd> +<dd>produces man page of file, not suitable for +all outputs. Alias -i </dd> + +<dt><b>-N [filename/wildcard/url]</b> </dt> +<dd>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. </dd> + +<dt><b>-n [filename/wildcard/url]</b> </dt> +<dd>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. </dd> <dt><b>--no-*</b> </dt> -<dd>see --exc-* - -<p> </dd> +<dd>see --exc-* </dd> <dt><b>-o [filename/wildcard/url]</b> </dt> <dd>see --odt -<p> </dd> +</dd> <dt><b>--odf [filename/wildcard/url]</b> </dt> -<dd>see --odt - -<p> </dd> +<dd>see --odt </dd> <dt><b>--odt [filename/wildcard/url]</b> </dt> -<dd>output basic document in opendocument file -format (opendocument.odt). Alias -o -<p> </dd> +<dd>output +basic document in opendocument file format (opendocument.odt). Alias -o </dd> -<dt><b>--output-by-*</b> </dt> -<dd>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> </dd> - -<dt><b>-P [language_directory/filename language_directory]</b> </dt> -<dd>see --po4a - -<p> </dd> - -<dt><b>-p [filename/wildcard]</b> </dt> -<dd>see --pdf -<p> </dd> +<dt><b>--output-by-*</b> +</dt> +<dd>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-* +</dd> -<dt><b>--pdf [filename/wildcard]</b> </dt> -<dd>produces <i>LaTeX</i> -pdf (portrait.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). Alias -p -<p> </dd> +<dt><b>-P [language_directory/filename language_directory]</b> </dt> +<dd>see --po4a </dd> -<dt><b>--pg [instruction] [filename]</b> +<dt><b>-p [filename/wildcard]</b> </dt> -<dd>database <i>PostgreSQL</i> ( --pgsql may be used instead) possible instructions, -include: --createdb; --create; --dropall; --import [filename]; --update [filename]; ---remove [filename]; see database section below. Alias -D -<p> </dd> +<dd>see --pdf </dd> -<dt><b>--po [language_directory/filename - language_directory]</b> </dt> +<dt><b>--pdf [filename/wildcard]</b> </dt> +<dd>produces <i>LaTeX</i> pdf (portrait.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). +Alias -p </dd> + +<dt><b>--pg [instruction] [filename]</b> </dt> +<dd>database <i>PostgreSQL</i> ( --pgsql may be +used instead) possible instructions, include: --createdb; --create; --dropall; +--import [filename]; --update [filename]; --remove [filename]; see database section +below. Alias -D </dd> + +<dt><b>--po [language_directory/filename language_directory]</b> </dt> <dd>see --po4a -<p> </dd> - -<dt><b>--po4a [language_directory/filename language_directory]</b> -</dt> -<dd>produces .pot and po files for the file in the languages specified by the -language directory. <b>SiSU</b> 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 -<p> </dd> +</dd> -<dt><b>-Q [filename/wildcard]</b> -</dt> -<dd> -<p>see --qrcode -<p> </dd> +<dt><b>--po4a [language_directory/filename language_directory]</b> </dt> +<dd>produces .pot and +po files for the file in the languages specified by the language directory. +<b>SiSU</b> 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 </dd> -<dt><b>-q [filename/wildcard]</b> </dt> -<dd>see --quiet -<p> </dd> +<dt><b>-Q [filename/wildcard]</b> </dt> +<dd>see --qrcode </dd> -<dt><b>--qrcode [filename/wildcard]</b> +<dt><b>-q [filename/wildcard]</b> </dt> -<dd>generate QR code image of metadata (used in manifest). v3 only. -<p> </dd> +<dd>see --quiet </dd> -<dt><b>--quiet [filename/wildcard]</b> -</dt> -<dd>quiet less output to screen. -<p> </dd> +<dt><b>--qrcode [filename/wildcard]</b> </dt> +<dd>generate QR code image of metadata +(used in manifest). v3 only. </dd> + +<dt><b>--quiet [filename/wildcard]</b> </dt> +<dd>quiet less output +to screen. </dd> <dt><b>-R [filename/wildcard]</b> </dt> -<dd>see --rsync -<p> </dd> +<dd>see --rsync </dd> -<dt><b>-r [filename/wildcard]</b> -</dt> -<dd> -<p>see --scp -<p> </dd> +<dt><b>-r [filename/wildcard]</b> </dt> +<dd>see --scp +</dd> <dt><b>--redirect[=directory_path] [filename/wildcard]</b> </dt> -<dd>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). Compare --dump -<p> </dd> - -<dt><b>--rsync [filename/wildcard]</b> -</dt> -<dd>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 - -<p>- -<p>R -<p> </dd> +<dd>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). Compare --dump </dd> + +<dt><b>--rsync [filename/wildcard]</b> </dt> +<dd>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 </dd> <dt><b>-S</b> </dt> <dd>see --sisupod -<p> </dd> +</dd> <dt><b>-S [filename/wildcard]</b> </dt> -<dd>see --sisupod -<p> </dd> - -<dt><b>-s [filename/wildcard]</b> -</dt> -<dd> -<p>see --source -<p> </dd> - -<dt><b>--sample-search-form [--webserv=webrick]</b> </dt> -<dd>generate examples of (naive) -cgi search form for <i>SQLite</i> and PgSQL depends on your already having used -sisu to populate an <i>SQLite</i> and/or PgSQL database, (the <i>SQLite</i> version scans -the output directories for existing sisu_sqlite databases, so it is first -necessary to create them, before generating the search form) see -d -D and -the database section below. 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 -<p> </dd> - -<dt><b>--scp [filename/wildcard]</b> +<dd>see --sisupod </dd> + +<dt><b>-s [filename/wildcard]</b> </dt> +<dd>see --source </dd> + +<dt><b>--sample-search-form +[--webserv=webrick]</b> </dt> +<dd>generate examples of (naive) cgi search form for <i>SQLite</i> +and PgSQL depends on your already having used sisu to populate an <i>SQLite</i> +and/or PgSQL database, (the <i>SQLite</i> version scans the output directories +for existing sisu_sqlite databases, so it is first necessary to create +them, before generating the search form) see -d -D and the database section +below. 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 </dd> + +<dt><b>--scp [filename/wildcard]</b> </dt> +<dd>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 </dd> + +<dt><b>--sqlite --[instruction] [filename]</b> </dt> -<dd>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 -<p> </dd> - -<dt><b>--sqlite ---[instruction] [filename]</b> </dt> -<dd>database type set to <i>SQLite,</i> this produces one -of two possible databases, without additional database related instructions -it produces a discreet <i>SQLite</i> file for the document processed; with additional -instructions it produces a common <i>SQLite</i> 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 -<p> </dd> +<dd>database type set to <i>SQLite,</i> this produces one of two possible databases, +without additional database related instructions it produces a discreet +<i>SQLite</i> file for the document processed; with additional instructions it +produces a common <i>SQLite</i> 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 </dd> <dt><b>--sisupod</b> </dt> -<dd>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<br> - option is tested only with zsh). Alias -S -<p> </dd> +<dd>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 </dd> <dt><b>--sisupod [filename/wildcard]</b> </dt> -<dd>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. <b>SiSU</b> 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 -<p> </dd> +<dd>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. <b>SiSU</b> 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 </dd> <dt><b>--source [filename/wildcard]</b> </dt> -<dd>copies sisu markup -file to output directory. Alias -s -<p> </dd> +<dd>copies sisu markup file to output directory. +Alias -s </dd> -<dt><b>-T [filename/wildcard (*.termsheet.rb)]</b> -</dt> -<dd>standard form document builder, preprocessing feature -<p> </dd> +<dt><b>-T [filename/wildcard (*.termsheet.rb)]</b> </dt> +<dd>standard form document builder, +preprocessing feature </dd> -<dt><b>-t [filename/wildcard]</b> -</dt> -<dd> -<p>see --txt -<p> </dd> - -<dt><b>--texinfo [filename/wildcard]</b> </dt> -<dd>produces texinfo and info file, (view -with pinfo). Alias -I -<p> </dd> +<dt><b>-t [filename/wildcard]</b> </dt> +<dd>see --txt </dd> -<dt><b>--txt [filename/wildcard]</b> </dt> -<dd>produces <i>plaintext</i> with Unix -linefeeds and without markup, (object numbers are omitted), has footnotes -at end of each paragraph that contains them [ -A for 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 -<p> </dd> - -<dt><b>-U [filename/wildcard]</b> </dt> -<dd>see --urls -<p> </dd> +<dt><b>--texinfo [filename/wildcard]</b> +</dt> +<dd>produces texinfo and info file, (view with pinfo). Alias -I </dd> -<dt><b>-u [filename/wildcard]</b> +<dt><b>--txt [filename/wildcard]</b> </dt> -<dd>provides url mapping of output files for the flags requested for processing, +<dd>produces <i>plaintext</i> 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 </dd> -<p>also see -U -<p> </dd> +<dt><b>-U [filename/wildcard]</b> </dt> +<dd>see --urls </dd> -<dt><b>--urls [filename/wildcard]</b> </dt> -<dd>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. +<dt><b>-u [filename/wildcard]</b> </dt> +<dd>provides url mapping +of output files for the flags requested for processing, also see -U </dd> -<p>Alias -U -<p> </dd> +<dt><b>--urls +[filename/wildcard]</b> </dt> +<dd>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 </dd> <dt><b>-V</b> </dt> -<dd>on its own, provides <b>SiSU</b> version and environment information -(sisu --help env) -<p> </dd> +<dd>on its own, +provides <b>SiSU</b> version and environment information (sisu --help env) </dd> -<dt><b>-V [filename/wildcard]</b> </dt> -<dd>even more verbose than the -v flag. - -<p> </dd> +<dt><b>-V [filename/wildcard]</b> +</dt> +<dd>even more verbose than the -v flag. </dd> <dt><b>-v</b> </dt> <dd>on its own, provides <b>SiSU</b> version information -<p> </dd> +</dd> -<dt><b>-v [filename/wildcard]</b> -</dt> -<dd> -<p>see --verbose -<p> </dd> +<dt><b>-v [filename/wildcard]</b> </dt> +<dd>see --verbose </dd> <dt><b>--v3 [filename/wildcard]</b> </dt> -<dd>invokes the sisu v3 document parser/generator. -You may run sisu3 instead. -<p> </dd> - -<dt><b>--v4 [filename/wildcard]</b> </dt> -<dd>invokes the sisu v4 document -parser/generator. This is the default and is normally omitted. -<p> </dd> +<dd>invokes the sisu +v3 document parser/generator. You may run sisu3 instead. </dd> -<dt><b>--verbose [filename/wildcard]</b> +<dt><b>--v4 [filename/wildcard]</b> </dt> -<dd>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 -<p> </dd> +<dd>invokes the sisu v4 document parser/generator. This is the default and is +normally omitted. </dd> -<dt><b>-W</b> </dt> -<dd>see --webrick +<dt><b>--verbose [filename/wildcard]</b> </dt> +<dd>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 </dd> -<p> </dd> +<dt><b>-W</b> </dt> +<dd>see --webrick </dd> -<dt><b>-w [filename/wildcard]</b> </dt> -<dd>see --concordance -<p> </dd> +<dt><b>-w [filename/wildcard]</b> +</dt> +<dd>see --concordance </dd> <dt><b>--webrick</b> </dt> -<dd>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 also, note -F webrick ]. Alias -W -<p> </dd> +<dd>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 </dd> -<dt><b>--wordmap [filename/wildcard]</b> -</dt> -<dd> -<p>see --concordance -<p> </dd> +<dt><b>--wordmap [filename/wildcard]</b> </dt> +<dd>see --concordance +</dd> <dt><b>--xhtml [filename/wildcard]</b> </dt> -<dd>produces xhtml/ <i>XML</i> output for -browser viewing (sax parsing). Alias -b -<p> </dd> +<dd>produces xhtml/ <i>XML</i> output for browser viewing +(sax parsing). Alias -b </dd> <dt><b>--xml-dom [filename/wildcard]</b> </dt> -<dd>produces -<i>XML</i> output with deep document structure, in the nature of dom. Alias -X -<p> -</dd> - -<dt><b>--xml-sax [filename/wildcard]</b> </dt> -<dd>produces <i>XML</i> output shallow structure (sax parsing). +<dd>produces <i>XML</i> output with +deep document structure, in the nature of dom. Alias -X </dd> -<p>Alias -x -<p> </dd> +<dt><b>--xml-sax [filename/wildcard]</b> +</dt> +<dd>produces <i>XML</i> output shallow structure (sax parsing). Alias -x </dd> -<dt><b>-X [filename/wildcard]</b> </dt> -<dd>see --xml-dom -<p> </dd> +<dt><b>-X [filename/wildcard]</b> +</dt> +<dd>see --xml-dom </dd> <dt><b>-x [filename/wildcard]</b> </dt> -<dd>see --xml-sax - -<p> </dd> +<dd>see --xml-sax </dd> <dt><b>-Y [filename/wildcard]</b> </dt> -<dd>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]) -<p> </dd> +<dd>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]) </dd> <dt><b>-y [filename/wildcard]</b> </dt> -<dd>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. -<p> </dd> +<dd>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. +</dd> <dt><b>-Z [filename/wildcard]</b> </dt> -<dd>see - -<p>- -<p>- -<p>zap -<p> </dd> +<dd>see --zap </dd> <dt><b>--zap [filename/wildcard]</b> </dt> -<dd>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. - -<p>Alias -Z -<p> </dd> +<dd>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 </dd> </dl> <h2><a name='sect8' href='#toc8'>Command Line Modifiers</a></h2> -<br> <p> <dl> -<dt><b>--no-</b> </dt> -<dd><i>ocn</i> [with --html --pdf or --epub] switches off <i>object</i> citation numbering. -Produce output without identifying numbers in margins of html or <i>LaTeX</i> -/pdf output. -<p> </dd> - -<dt><b>--no-annotate</b> </dt> -<dd>strips output text of editor endnotes[^*1] denoted +<dt><b>--no-ocn</b> </dt> +<dd>[with --html +--pdf or --epub] switches off <i>object</i> citation numbering. Produce output without +identifying numbers in margins of html or <i>LaTeX</i> /pdf output. </dd> -<p>by asterisk or dagger/plus sign -<p> </dd> +<dt><b>--no-annotate</b> +</dt> +<dd>strips output text of editor endnotes[^*1] denoted by asterisk or dagger/plus +sign </dd> <dt><b>--no-asterisk</b> </dt> -<dd>strips output text of editor -endnotes[^*2] denoted by asterisk sign -<p> </dd> +<dd>strips output text of editor endnotes[^*2] denoted by asterisk +sign </dd> <dt><b>--no-dagger</b> </dt> -<dd>strips output text of editor -endnotes[^+1] denoted by dagger/plus sign -<p> </dd> +<dd>strips output text of editor endnotes[^+1] denoted by dagger/plus +sign </dd> </dl> <h2><a name='sect9' href='#toc9'>Database Commands</a></h2> -<br> -<p> <br> -<b>dbi - database interface</b> -<p> <br> -<b>-D or --pgsql</b> set for <i>PostgreSQL</i> <b>-d or --sqlite</b> default set for <i>SQLite</i> -d is modifiable -with --db=[database type (PgSQL or .I SQLite ) ] -<p> +<p> <b>dbi - database interface</b> +<p> <b>-D or --pgsql</b> set for <i>PostgreSQL</i> +<b>-d or --sqlite</b> default set for <i>SQLite</i> -d is modifiable with --db=[database type +(PgSQL or <i>SQLite</i> ) ] <dl> <dt><b>--pg -v --createall</b> </dt> -<dd>initial step, -creates required relations (tables, indexes) in existing <i>PostgreSQL</i> database -(a database should be created manually and given the same name as working -directory, as requested) (rb.dbi) [ -dv --createall .I SQLite equivalent] it -may be necessary to run sisu -Dv --createdb initially NOTE: at the present -time for <i>PostgreSQL</i> it may be necessary to manually create the database. -The command would be working directory name (without path)]. Please use -only alphanumerics and underscores. -<p> </dd> - -<dt><b>--pg -v --import</b> </dt> -<dd>[filename/wildcard] imports -data specified to <i>PostgreSQL</i> db (rb.dbi) [ -dv --import .I SQLite equivalent] - -<p> </dd> +<dd>initial step, creates required relations +(tables, indexes) in existing <i>PostgreSQL</i> database (a database should be +created manually and given the same name as working directory, as requested) +(rb.dbi) [ -dv --createall <i>SQLite</i> equivalent] it may be necessary to run sisu +-Dv --createdb initially NOTE: at the present time for <i>PostgreSQL</i> it may be +necessary to manually create the database. The command would be directory +name (without path)]. Please use only alphanumerics and underscores. </dd> + +<dt><b>--pg -v +--import</b> </dt> +<dd>[filename/wildcard] imports data specified to <i>PostgreSQL</i> db (rb.dbi) +[ -dv --import <i>SQLite</i> equivalent] </dd> <dt><b>--pg -v --update</b> </dt> -<dd>[filename/wildcard] updates/imports specified data to <i>PostgreSQL</i> -db (rb.dbi) [ -dv --update .I SQLite equivalent] -<p> </dd> +<dd>[filename/wildcard] updates/imports +specified data to <i>PostgreSQL</i> db (rb.dbi) [ -dv --update <i>SQLite</i> equivalent] +</dd> <dt><b>--pg --remove</b> </dt> -<dd>[filename/wildcard] -removes specified data to <i>PostgreSQL</i> db (rb.dbi) [ -d --remove .I SQLite equivalent] - -<p> </dd> +<dd>[filename/wildcard] removes specified data to <i>PostgreSQL</i> db (rb.dbi) +[ -d --remove <i>SQLite</i> equivalent] </dd> <dt><b>--pg --dropall</b> </dt> -<dd>kills data" and drops ( <i>PostgreSQL</i> or <i>SQLite</i> ) db, tables & -indexes [ -d --dropall .I SQLite equivalent] -<p> <br> -The -v is for verbose output. -<p> </dd> +<dd>kills data" and drops ( <i>PostgreSQL</i> +or <i>SQLite</i> ) db, tables & indexes [ -d --dropall <i>SQLite</i> equivalent] +<p> The -v +is for verbose output. </dd> </dl> <h2><a name='sect10' href='#toc10'>Shortcuts, Shorthand for Multiple Flags</a></h2> -<br> <p> <dl> -<dt><b>--update [filename/wildcard]</b> </dt> -<dd>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. -<p> </dd> - -<dt><b>-0 to -5 [filename or wildcard]</b> </dt> -<dd>Default -shorthand mappings (for v3, note that the defaults can be changed/configured -in the sisurc.yml file): -<p> </dd> +<dt><b>--update [filename/wildcard]</b> +</dt> +<dd>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. </dd> + +<dt><b>-0 to -5 [filename or wildcard]</b> </dt> +<dd>Default shorthand mappings (for v3, +note that the defaults can be changed/configured in the sisurc.yml file): +</dd> <dt><b>-0</b> </dt> -<dd>-NQhewpotbxXyYv [this is the default action run - when no options are give, i.e. on ’sisu [filename]’] -<p> </dd> +<dd>-NQhewpotbxXyYv [this is the default action run when no options are give, +i.e. on ’sisu [filename]’] </dd> <dt><b>-1</b> </dt> -<dd>-Qhewpoty -<p> </dd> +<dd>-Qhewpoty </dd> <dt><b>-2</b> </dt> -<dd>-NQhewpotbxXy - -<p> </dd> +<dd>-NQhewpotbxXy </dd> <dt><b>-3</b> </dt> -<dd>-NQhewpotbxXyY -<p> </dd> +<dd>-NQhewpotbxXyY </dd> <dt><b>-4</b> </dt> -<dd>-NQhewpotbxXDyY --update -<p> </dd> +<dd>-NQhewpotbxXDyY +--update </dd> <dt><b>-5</b> </dt> <dd>-NQhewpotbxXDyYv --update -<p> <br> -add -v for verbose mode and -c to toggle color state, e.g. sisu -2vc [filename - or wildcard] -<p> <br> +<p> add -v for verbose mode and -c to toggle +color state, e.g. sisu -2vc [filename or wildcard] +<p> consider -u for appended -<p>consider -u for appended url info or -v for verbose output +<p>url info or -v for verbose output <p> </dd> </dl> -<h2><a name='sect11' href='#toc11'>Command Line -with Flags - Batch Processing</a></h2> +<h2><a name='sect11' href='#toc11'>Command Line with Flags - Batch Processing</a></h2> -<p> <br> -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. -<p> <br> -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. <p> + 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. +<p> 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. <h2><a name='sect12' href='#toc12'>Help</a></h2> -<br> <p> + <h2><a name='sect13' href='#toc13'>Sisu Manual</a></h2> -<p> <br> -The most up to date information on sisu should be contained in the sisu_manual, -available at: -<p> <br> - <<a href='http://sisudoc.org/sisu/sisu_manual/'>http://sisudoc.org/sisu/sisu_manual/</a> -><br> +<p> The most up to date information on sisu should be contained +in the sisu_manual, available at: +<p> <<a href='http://sisudoc.org/sisu/sisu_manual/'>http://sisudoc.org/sisu/sisu_manual/</a> +> -<p> <br> -The manual can be generated from source, found respectively, either within +<p> The manual can be generated from source, found respectively, either within the <b>SiSU</b> tarball or installed locally at: -<p> <br> - ./data/doc/sisu/markup-samples/sisu_manual<br> - -<p> <br> - /usr/share/doc/sisu/markup-samples/sisu_manual<br> - -<p> <br> -move to the respective directory and type e.g.: -<p> <br> - sisu sisu_manual.ssm<br> - <p> -<h2><a name='sect14' href='#toc14'>Sisu Man Pages</a></h2> +<p> /usr/share/doc/sisu/markup-samples/sisu_manual -<p> <br> -If <b>SiSU</b> is installed on your system usual man commands should be available, -try: -<p> <br> - man sisu<br> +<p> move to the respective directory and type e.g.: +<p> sisu sisu_manual.ssm +<h2><a name='sect14' href='#toc14'>Sisu +Man Pages</a></h2> -<p> <br> -Most <b>SiSU</b> 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 <b>SiSU</b> tarball at: -<p> <br> - ./data/doc/sisu/markup-samples/sisu_manual<br> +<p> If <b>SiSU</b> is installed on your system usual man commands should +be available, try: +<p> man sisu +<p> Most <b>SiSU</b> 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 <b>SiSU</b> tarball at: +<p> ./data/doc/sisu/markup-samples/sisu_manual<br> -<p> <br> -Once installed, directory equivalent to: -<p> <br> - /usr/share/doc/sisu/markup-samples/sisu_manual<br> +<p> Once installed, directory equivalent to: +<p> /usr/share/doc/sisu/markup-samples/sisu_manual<br> -<p> <br> -Available man pages are converted back to html using man2html: -<p> <br> - /usr/share/doc/sisu/html/<br> +<p> Available man pages are converted back to html using man2html: +<p> /usr/share/doc/sisu/html/<br> -<p> <br> - ./data/doc/sisu/html<br> +<p> ./data/doc/sisu/html<br> -<p> <br> -An online version of the sisu man page is available here: -<p> <br> -* various sisu man pages <<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a> +<p> An online version of the sisu man page is available here: +<p> * various +sisu man pages <<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a> > [^9] -<p> <br> -* sisu.1 <<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a> -> [^10] -<p> -<h2><a name='sect15' href='#toc15'>Sisu Built-in Interactive -Help</a></h2> - -<p> <br> -This is particularly useful for getting the current sisu setup/environment -information: -<p> <br> - sisu --help<br> - -<p> <br> - sisu --help [subject]<br> - -<p> <br> - sisu --help commands<br> - -<p> <br> - sisu --help markup<br> - -<p> <br> - sisu --help env [for feedback on the way your system is <br> - setup with regard to sisu ]<br> - -<p> <br> - sisu -V [environment information, same as above command]<br> - -<p> <br> - sisu (on its own provides version and some help information)<br> - -<p> <br> -Apart from real-time information on your current configuration the <b>SiSU</b> -manual and man pages are likely to contain more up-to-date information than -the sisu interactive help (for example on commands and markup). -<p> <br> -NOTE: Running the command 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. -<p> -<h2><a name='sect16' href='#toc16'>Introduction to Sisu Markup[^11]</a></h2> -<br> +<p> * sisu.1 <<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a> +> +[^10] +<p> +<h2><a name='sect15' href='#toc15'>Sisu Built-in Interactive Help</a></h2> + +<p> This is particularly useful for getting +the current sisu setup/environment information: +<p> sisu --help +<p> sisu --help +[subject] +<p> sisu --help commands +<p> sisu --help markup +<p> sisu --help env [for +feedback on the way your system is setup with regard to sisu ]<br> + +<p> sisu -V [environment information, same as above command] +<p> sisu (on its +own provides version and some help information) +<p> Apart from real-time information +on your current configuration the <b>SiSU</b> manual and man pages are likely +to contain more up-to-date information than the sisu interactive help (for +example on commands and markup). +<p> NOTE: Running the command 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. +<h2><a name='sect16' href='#toc16'>Introduction +to Sisu Markup[^11]</a></h2> <p> <h2><a name='sect17' href='#toc17'>Summary</a></h2> -<p> <br> -<b>SiSU</b> source documents are <i>plaintext</i> ( <i>UTF-8</i> )[^12] files -<p> <br> -All paragraphs are separated by an empty line. -<p> <br> -Markup is comprised of: -<p> <br> -* 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) -<p> <br> -* 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: -<p> <br> - * heading levels defines document structure<br> - -<p> <br> - * text basic attributes, italics, bold etc.<br> - -<p> <br> - * grouped text (objects), which are to be treated differently, such as -code<br> +<p> <b>SiSU</b> source documents are <i>plaintext</i> ( <i>UTF-8</i> +)[^12] files +<p> All paragraphs are separated by an empty line. +<p> Markup is +comprised of: +<p> * 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) +<p> * 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: +<p> * heading levels defines document +structure<br> + +<p> * text basic attributes, italics, bold etc.<br> + +<p> * grouped text (objects), which are to be treated differently, such +as code<br> blocks or poems.<br> -<p> <br> - * footnotes/endnotes<br> - -<p> <br> - * linked text and images<br> - -<p> <br> - * paragraph actions, such as indent, bulleted, numbered-lists, etc.<br> - -<p> <br> -Some interactive help on markup is available, by typing sisu and selecting - -<p>markup or sisu --help markup -<p> <br> -To check the markup in a file: -<p> <br> - sisu --identify [filename].sst<br> - -<p> <br> +<p> * footnotes/endnotes<br> -<p>For brief descriptive summary of markup history -<p> <br> - sisu --query-history<br> +<p> * linked text and images +<p> * paragraph actions, such as indent, bulleted, +numbered-lists, etc. +<p> Some interactive help on markup is available, by typing -<p> <br> -or if for a particular version: -<p> <br> - sisu --query-0.38<br> +<p>sisu and selecting markup or sisu --help markup +<p> To check the markup in +a file: +<p> sisu --identify [filename].sst +<p> For brief descriptive summary of +<p>markup history +<p> sisu --query-history +<p> or if for a particular version: <p> +sisu --query-0.38 <h2><a name='sect18' href='#toc18'>Markup Examples</a></h2> <p> <h2><a name='sect19' href='#toc19'>Online</a></h2> -<p> <br> -Online markup examples are available together with the respective outputs -produced from <<a href='http://www.jus.uio.no/sisu/SiSU/examples.html'>http://www.jus.uio.no/sisu/SiSU/examples.html</a> -> or from <<a href='http://www.jus.uio.no/sisu/sisu_examples/'>http://www.jus.uio.no/sisu/sisu_examples/</a> +<p> Online markup examples are available +together with the respective outputs produced from <<a href='http://www.jus.uio.no/sisu/SiSU/examples.html'>http://www.jus.uio.no/sisu/SiSU/examples.html</a> > - -<p> <br> -There is of course this document, which provides a cursory overview of -sisu markup and the respective output produced: <<a href='http://www.jus.uio.no/sisu/sisu_markup/'>http://www.jus.uio.no/sisu/sisu_markup/</a> +or from <<a href='http://www.jus.uio.no/sisu/sisu_examples/'>http://www.jus.uio.no/sisu/sisu_examples/</a> > - -<p> <br> -an alternative presentation of markup syntax: /usr/share/doc/sisu/on_markup.txt.gz - +<p> There is of course this +document, which provides a cursory overview of sisu markup and the respective +output produced: <<a href='http://www.jus.uio.no/sisu/sisu_markup/'>http://www.jus.uio.no/sisu/sisu_markup/</a> +> +<p> an alternative +presentation of markup syntax: /usr/share/doc/sisu/on_markup.txt.gz <p> <h2><a name='sect20' href='#toc20'>Installed</a></h2> -<p> <br> -With <b>SiSU</b> installed sample skins may be found in: /usr/share/doc/sisu/markup-samples +<p> + With <b>SiSU</b> 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: <p>/usr/share/doc/sisu/markup-samples-non-free <p> <h2><a name='sect21' href='#toc21'>Markup of Headers</a></h2> -<br> -<p> <br> -Headers contain either: semantic meta-data about a document, which can be -used by any output module of the program, or; processing instructions. <p> -<br> -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: +<p> Headers contain +either: semantic meta-data about a document, which can be used by any output +module of the program, or; processing instructions. +<p> 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: <p> <br> <pre>% this would be a comment </pre> <p> <h2><a name='sect22' href='#toc22'>Sample Header</a></h2> +<p> This current document is loaded by a master document that +has a header similar to this one: <p> <br> -This current document is loaded by a master document that has a header -similar to this one: -<p> <br> -<pre>% SiSU master 2.0 +<pre>% SiSU master 4.0 @title: SiSU -:subtitle: Manual + :subtitle: Manual @creator: -:author: Amissah, Ralph -@publisher: [publisher name] + :author: Amissah, Ralph +@publisher: [publisher name] @rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 @classify: -:type: information -:topic_register: SiSU:manual;electronic documents:SiSU:manual -:subject: ebook, epublishing, electronic book, electronic publishing, + :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 + :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 + :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 + { 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 </pre> <p> <h2><a name='sect23' href='#toc23'>Available Headers</a></h2> -<p> <br> -Header tags appear at the beginning of a document and provide meta information -on the document (such as the <i>Dublin</i> 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: +<p> Header tags appear at the beginning of a document and +provide meta information on the document (such as the <i>Dublin</i> 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 <i>Dublin</i> Core meta tags are available +<p> + <b>@indentifier:</b> information or instructions +<p> where the "identifier" is +a tag recognised by the program, and the "information" or "instructions" -<p>All <i>Dublin</i> Core meta tags are available -<p> <br> -<b>@indentifier:</b> information or instructions -<p> <br> -where the "identifier" is a tag recognised by the program, and the "information" -or "instructions" belong to the tag/indentifier specified -<p> <br> -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. -<p> <br> +<p>belong to the tag/identifier specified +<p> 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. -<p>This is a sample header +<p> This is a sample header <p> <br> -<pre>% SiSU 2.0 [declared file-type identifier with markup version] +<pre>% SiSU 2.0 [declared file-type identifier with markup version] </pre> <p> <br> -<pre>@title: [title text] [this header is the only one that is mandatory] - :subtitle: [subtitle if any] +<pre>@title: [title text] [this header is the only one that is mandatory] + :subtitle: [subtitle if any] :language: English </pre> <p> <br> <pre>@creator: -:author: [Lastname, First names] -:illustrator: [Lastname, First names] -:translator: [Lastname, First names] -:prepared_by: [Lastname, First names] + :author: [Lastname, First names] + :illustrator: [Lastname, First names] + :translator: [Lastname, First names] + :prepared_by: [Lastname, First names] </pre> <p> <br> <pre>@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] + :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] </pre> <p> <br> <pre>@rights: -:copyright: Copyright (C) [Year and Holder] -:license: [Use License granted] -:text: [Year and Holder] -:translation: [Name, Year] -:illustrations: [Name, Year] + :copyright: Copyright (C) [Year and Holder] + :license: [Use License granted] + :text: [Year and Holder] + :translation: [Name, Year] + :illustrations: [Name, Year] </pre> <p> <br> <pre>@classify: -:topic_register: SiSU:markup sample:book;book:novel:fantasy -:type: -:subject: -:description: -:keywords: -:abstract: -:loc: [Library of Congress classification] -:dewey: Dewey classification + :topic_register: SiSU:markup sample:book;book:novel:fantasy + :type: + :subject: + :description: + :keywords: + :abstract: + :loc: [Library of Congress classification] + :dewey: [Dewey classification </pre> <p> <br> <pre>@identify: -:isbn: [ISBN] -:oclc: + :isbn: [ISBN] + :oclc: </pre> <p> <br> <pre>@links: { SiSU }http://www.sisudoc.org @@ -1288,62 +1082,58 @@ structure, and can be useful to know. </pre> <p> <br> <pre>@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 + :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 </pre> <p> <br> <pre>@original: -:language: [language] + :language: [language] </pre> <p> <br> <pre>@notes: -:comment: -:prefix: [prefix is placed just after table of contents] + :comment: + :prefix: [prefix is placed just after table of contents] </pre> <p> <h2><a name='sect24' href='#toc24'>Markup of Substantive Text</a></h2> -<br> <p> <h2><a name='sect25' href='#toc25'>Heading Levels</a></h2> -<p> <br> -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) -<p> <br> -<b>:A~ [heading text]</b> 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 -<p> <br> -<b>:B~ [heading text]</b> Second level heading [this is a heading level divider] - -<p> <br> -<b>:C~ [heading text]</b> Third level heading [this is a heading level divider] - -<p> <br> -<b>1~ [heading text]</b> 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 - -<p> <br> -<b>2~ [heading text]</b> 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. -<p> <br> -<b>3~ [heading text]</b> 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 - +<p> 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) +<p> <b>:A~ [heading +text]</b> Top level heading [this usually has similar content to the title +@title: ] NOTE: the heading levels described here are in 0.38 notation, + +<p>see heading +<p> <b>:B~ [heading text]</b> Second level heading [this is a heading +level divider] +<p> <b>:C~ [heading text]</b> Third level heading [this is a heading +level divider] +<p> <b>1~ [heading text]</b> 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 + +<p> <b>2~ [heading text]</b> 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. +<p> <b>3~ [heading text]</b> 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 <p> <br> <pre>1~filename level 1 heading, % the primary division such as Chapter that is followed by substantive @@ -1353,15 +1143,14 @@ html segments are made) <p> <h2><a name='sect26' href='#toc26'>Font Attributes</a></h2> -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>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] +*{emphasis}* [note: can be configured to be represented by bold, italics +or underscore] !{bold text}! /{italics}/ _{underscore}_ @@ -1372,86 +1161,58 @@ _{underscore}_ -{strikethrough}- #{monospace}# </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -normal text, <b>emphasis,</b> <b>bold text</b> , <i>italics,</i> <i>underscore,</i> "citation", ^superscript^, -[subscript], ++inserted text++, --strikethrough--, monospace -<p> <br> - -<p>normal text -<p> <br> -<b>emphasis</b> [note: can be configured to be represented by bold, italics italics - or underscore] or underscore] -<p> <br> +<p> <b>resulting output:</b> +<p> normal text, <b>emphasis,</b> <b>bold text</b> , <i>italics,</i> <i>underscore,</i> +"citation", ^superscript^, [subscript], ++inserted text++, --strikethrough--, -<p><b>bold text</b> -<p> <br> +<p>monospace +<p> normal text +<p> <b>emphasis</b> [note: can be configured to be represented +by bold, italics or underscore] +<p> <b>bold text</b> +<p> <i>italics</i> +<p> <i>underscore</i> +<p> "citation" -<p><i>italics</i> -<p> <br> +<p> ^superscript^ +<p> [subscript] +<p> ++inserted text++ +<p> --strikethrough-- +<p> monospace -<p><i>underscore</i> -<p> <br> -"citation" -<p> <br> -^superscript^ -<p> <br> -[subscript] -<p> <br> -++inserted text++ -<p> <br> ---strikethrough-- -<p> <br> - -<p>monospace <p> <h2><a name='sect27' href='#toc27'>Indentation and Bullets</a></h2> -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>ordinary paragraph _1 indent paragraph one step _2 indent paragraph two steps _9 indent paragraph nine steps </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> +<p> <b>resulting output:</b> +<p> ordinary paragraph +<p> indent paragraph one step<br> -<p>ordinary paragraph -<p> <br> - indent paragraph one step<br> +<p> indent paragraph two steps<br> -<p> <br> - indent paragraph two steps<br> +<p> indent paragraph nine steps<br> -<p> <br> - indent paragraph nine steps<br> - -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>_* bullet text _1* bullet text, first indent _2* bullet text, two step indent </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -* bullet text -<p> <br> - * bullet text, first indent<br> +<p> <b>resulting output:</b> +<p> * bullet text +<p> * bullet text, first indent<br> -<p> <br> - * bullet text, two step indent<br> +<p> * bullet text, two step indent<br> -<p> <br> -Numbered List (not to be confused with headings/titles, (document structure)) +<p> Numbered List (not to be confused with headings/titles, (document structure)) -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre># numbered list numbered list 1., 2., 3, etc. _# numbered list numbered list indented a., b., c., d., etc. @@ -1459,8 +1220,7 @@ _# numbered list numbered list indented a., b., c., d., etc. <p> <h2><a name='sect28' href='#toc28'>Hanging Indents</a></h2> -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>_0_1 first line no indent, rest of paragraph indented one step @@ -1468,125 +1228,127 @@ _1_0 first line indented, rest of paragraph no indent in each case level may be 0-9 </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> - first line no indent, rest of paragraph indented one step<br> - -<p> <br> +<p> <b>resulting output:</b> +<p> 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<br> + paragraph indented one step; first line no indent, rest of paragraph +indented<br> + one step; first line no indent, rest of paragraph indented one step; +first<br> + line no indent, rest of paragraph indented one step; first line no indent,<br> + rest of paragraph indented one step; first line no indent, rest of paragraph<br> + indented one step; first line no indent, rest of paragraph indented +one step;<br> + +<p> A regular paragraph. +<p> 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 -<p> <br> +<p> in each case level may + +<p>be 0-9 +<p> <b>live-build</b> A collection of scripts used to build customized Debian<br> + Livesystems.<br> + .I live-build<br> + was formerly known as live-helper, and even earlier known as live-package.<br> + +<p> <b>live-build</b> +<p> A collection of scripts used to build customized Debian<br> + Livesystems. live-build was formerly known as live-helper, and even earlier<br> + known as live-package.<br> -<p>in each case level may be 0-9 -<p> <h2><a name='sect29' href='#toc29'>Footnotes / Endnotes</a></h2> -<p> <br> -Footnotes and endnotes are marked up at the location where they would be -indicated within a text. They are automatically numbered. The output type +<p> Footnotes and endnotes are marked up at the location +where they would be indicated within a text. They are automatically numbered. -<p>determines whether footnotes or endnotes will be produced -<p> <br> -<b>markup example:</b> +<p>The output type determines whether footnotes or endnotes will be produced + +<p> <b>markup example:</b> <p> <br> <pre>~{ a footnote or endnote }~ </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -[^13] -<p> <br> -<b>markup example:</b> +<p> <b>resulting output:</b> +<p> [^13] +<p> <b>markup example:</b> <p> <br> <pre>normal text~{ self contained endnote marker & endnote in one }~ continues </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -normal text[^14] continues -<p> <br> -<b>markup example:</b> +<p> <b>resulting output:</b> +<p> normal text[^14] continues +<p> <b>markup example:</b> <p> <br> <pre>normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks if required }~ continues normal text ~{** another unnumbered asterisk footnote/endnote }~ continues </pre> +<p> <b>resulting output:</b> +<p> normal text [^*] continues +<p> normal text [^**] continues + +<p> <b>markup example:</b> <p> <br> -<b>resulting output:</b> -<p> <br> -normal text [^*] continues -<p> <br> -normal text [^**] continues -<p> <br> -<b>markup example:</b> -<p> <br> -<pre>normal text ~[* editors notes, numbered asterisk footnote/endnote series - ]~ continues -normal text ~[+ editors notes, numbered asterisk footnote/endnote series - ]~ continues +<pre>normal text ~[* editors notes, numbered asterisk footnote/endnote series +]~ continues +normal text ~[+ editors notes, numbered asterisk footnote/endnote series +]~ continues </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -normal text [^*3] continues -<p> <br> -normal text [^+2] continues -<p> <br> -<b>Alternative endnote pair notation for footnotes/endnotes:</b> +<p> <b>resulting output:</b> +<p> normal text [^*3] continues +<p> normal text [^+2] continues + +<p> <b>Alternative endnote pair notation for footnotes/endnotes:</b> <p> <br> <pre>% note the endnote marker "~^" normal text~^ continues ^~ endnote text following the paragraph in which the marker occurs </pre> -<p> <br> - -<p>the standard and pair notation cannot be mixed in the same document +<p> the standard and pair notation cannot be mixed in the same document <p> + <h2><a name='sect30' href='#toc30'>Links</a></h2> <p> - <h2><a name='sect31' href='#toc31'>Naked Urls Within Text, Dealing with Urls</a></h2> -<p> <br> -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). -<p> <br> -<b>markup example:</b> +<p> 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). +<p> <b>markup example:</b> <p> <br> <pre>normal text http://www.sisudoc.org/ continues </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -normal text <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> <b>resulting output:</b> +<p> normal text <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > continues -<p> <br> +<p> An -<p>An escaped url without decoration -<p> <br> -<b>markup example:</b> +<p>escaped url without decoration +<p> <b>markup example:</b> <p> <br> <pre>normal text _http://www.sisudoc.org/ continues deb _http://www.jus.uio.no/sisu/archive unstable main non-free </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -normal text <_<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> <b>resulting output:</b> +<p> normal text <_<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > continues -<p> <br> -deb <_<a href='http://www.jus.uio.no/sisu/archive'>http://www.jus.uio.no/sisu/archive</a> +<p> deb +<_<a href='http://www.jus.uio.no/sisu/archive'>http://www.jus.uio.no/sisu/archive</a> > unstable main non-free -<p> <br> -where a code block is used there is neither decoration nor hyperlinking, +<p> where a code block +is used there is neither decoration nor hyperlinking, code blocks are discussed -<p>code blocks are discussed later in this document -<p> <br> -<b>resulting output:</b> +<p>later in this document +<p> <b>resulting output:</b> <p> <br> <pre>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 @@ -1594,63 +1356,50 @@ deb-src http://www.jus.uio.no/sisu/archive unstable main non-free <p> <h2><a name='sect32' href='#toc32'>Linking Text</a></h2> -<p> <br> +<p> To link text or an image to a url the markup is as follows -<p>To link text or an image to a url the markup is as follows -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>about { SiSU }http://url.org markup </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -aboutSiSU <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> <b>resulting output:</b> +<p> aboutSiSU <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > markup -<p> <br> +<p> A shortcut -<p>A shortcut notation is available so the url link may also be provided automatically +<p>notation is available so the url link may also be provided automatically <p>as a footnote -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>about {~^ SiSU }http://url.org markup </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -aboutSiSU <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> <b>resulting output:</b> +<p> aboutSiSU <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > [^15] markup -<p> <br> -Internal document links to a tagged location, including an <i>ocn</i> -<p> <br> -<b>markup example:</b> +<p> Internal +document links to a tagged location, including an ocn +<p> <b>markup example:</b> + <p> <br> <pre>about { text links }#link_text </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -about ⌠text links⌡⌈link_text⌋ -<p> <br> +<p> <b>resulting output:</b> +<p> about ⌠text links⌡⌈link_text⌋ +<p> Shared document -<p>Shared document collection link -<p> <br> -<b>markup example:</b> +<p>collection link +<p> <b>markup example:</b> <p> <br> <pre>about { SiSU book markup examples }:SiSU/examples.html </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -about ⌠ <b>SiSU</b> book markup examples⌡⌈:SiSU/examples.html⌋ +<p> <b>resulting output:</b> +<p> about ⌠ <b>SiSU</b> book markup examples⌡⌈:SiSU/examples.html⌋ + <p> -<h2><a name='sect33' href='#toc33'>Linking -Images</a></h2> +<h2><a name='sect33' href='#toc33'>Linking Images</a></h2> -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>{ tux.png 64x80 }image % various url linked images @@ -1659,48 +1408,41 @@ Images</a></h2> and Ruby" }http://www.sisudoc.org/ {~^ ruby_logo.png "Ruby" }http://www.ruby-lang.org/en/ </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -[ tux.png ] -<p> <br> -tux.png 64x80 "Gnu/Linux - a better way" <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> <b>resulting output:</b> +<p> [ tux.png ] +<p> tux.png 64x80 "Gnu/Linux - a better way" +<<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > -<p> <br> -GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian -and Ruby" <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better +- with Gnu/Linux, Debian and Ruby" <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > -<p> <br> -ruby_logo.png 70x90 "Ruby" <<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a> +<p> ruby_logo.png +70x90 "Ruby" <<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a> > [^16] -<p> <br> +<p> <b>linked url footnote shortcut</b> -<p><b>linked url footnote shortcut</b> <p> <br> -<pre>{~^ [text to link] }http://url.org -% maps to: { [text to link] }http://url.org ~{ http://url.org }~ +<pre>{~^ [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 </pre> <p> <br> <pre>text marker *~name </pre> -<p> <br> -note at a heading level the same is automatically achieved by providing +<p> 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. -<p> -<h2><a name='sect34' href='#toc34'>Link Shortcut for -Multiple Versions of a Sisu Document in the Same Directory</a></h2> +<h2><a name='sect34' href='#toc34'>Link Shortcut for Multiple +Versions of a Sisu Document in the Same Directory</a></h2> TREE -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> + <p> <br> <pre>!_ /{"Viral Spiral"}/, David Bollier { "Viral Spiral", David Bollier [3sS]}viral_spiral.david_bollier.sst </pre> -<p> <br> -<b></b> <i>Viral Spiral</i>, David Bollier +<p> <b></b> <i>Viral Spiral</i>, David Bollier <p> "Viral Spiral", David Bollier <<a href='http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html'>http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html</a> > document manifest <<a href='http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html'>http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html</a> @@ -1738,11 +1480,9 @@ TREE <p> <h2><a name='sect36' href='#toc36'>Tables</a></h2> -<p> <br> +<p> Tables may be prepared in two either of two forms -<p>Tables may be prepared in two either of two forms -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>table{ c3; 40; 30; 30; This is a table @@ -1753,19 +1493,16 @@ column two of row two column three of row two, and so on }table </pre> -<p> <br> -<b>resulting output:</b> -<p> 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』 -<p> <br> +<p> <b>resulting output:</b> +<p> 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』 +<p> a second form may -<p>a second form may be easier to work with in cases where there is not much +<p>be easier to work with in cases where there is not much information in -<p>information in each column -<p> <br> -<b>markup example:</b> [^18] -<p> <br> +<p>each column +<p> <b>markup example:</b> [^17] <br> <pre>!_ 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 @@ -1782,31 +1519,26 @@ No. of articles, all languages | 25| 19,000| 138,000| 490,000| 862,0 * Contributed at least ten times; ** at least 5 times in last month; *** more than 100 times in last month. </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -<b>Table 3.1: Contributors to Wikipedia, January 2001 - June 2005</b> -<p> |Jan. 2001|Jan. -2002|Jan. 2003|Jan. 2004|July 2004|June 2006』Contributors*|10|472|2,188|9,653|25,011|48,721』Active +<p> <b>resulting output:</b> +<p> <b>Table 3.1: Contributors to Wikipedia, January 2001 +- June 2005</b> |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』 -<p> <br> -* Contributed at least ten times; ** at least 5 times in last month; *** -more than 100 times in last month. +<p> * Contributed +at least ten times; ** at least 5 times in last month; *** more than 100 +times in last month. <p> <h2><a name='sect37' href='#toc37'>Poem</a></h2> -<p> <br> -<b>basic markup:</b> +<p> <b>basic markup:</b> <p> <br> <pre>poem{ Your poem here }poem Each verse in a poem is given an object number. </pre> -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>poem{ ‘Fury said to a @@ -1855,8 +1587,7 @@ Each verse in a poem is given an object number. death."’ }poem </pre> -<p> <br> -<b>resulting output:</b> +<p> <b>resulting output:</b> <p> ‘Fury said to a<br> mouse, That he<br> met in the<br> @@ -1905,16 +1636,14 @@ Each verse in a poem is given an object number. <p> <h2><a name='sect38' href='#toc38'>Group</a></h2> -<p> <br> -<b>basic markup:</b> +<p> <b>basic markup:</b> <p> <br> <pre>group{ Your grouped text here }group A group is treated as an object and given a single object number. </pre> -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>group{ ‘Fury said to a @@ -1963,8 +1692,7 @@ A group is treated as an object and given a single object number. death."’ }group </pre> -<p> <br> -<b>resulting output:</b> +<p> <b>resulting output:</b> <p> ‘Fury said to a<br> mouse, That he<br> met in the<br> @@ -2013,18 +1741,16 @@ A group is treated as an object and given a single object number. <p> <h2><a name='sect39' href='#toc39'>Code</a></h2> -<p> <br> -Code tags code{ ... }code (used as with other group tags described above) -are used to escape regular sisu markup, and have been used extensively +<p> 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 <b>SiSU</b> markup. You cannot however use code tags to escape code tags. They are however used in the same way as group or poem tags. -<p> <br> -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] - -<p> <br> -<b>use of code tags instead of poem compared, resulting output:</b> +<p> 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] +<p> <b>use of code tags instead of poem compared, resulting +output:</b> <p> <br> <pre> ‘Fury said to a mouse, That he @@ -2071,8 +1797,7 @@ option to number each line of code may to death."’ </pre> -<p> <br> -From <b>SiSU</b> 2.7.7 on you can number codeblocks by placing a hash after the +<p> From <b>SiSU</b> 2.7.7 on you can number codeblocks by placing a hash after the opening code tag code{# as demonstrated here: <p> <br> <pre>1 | ‘Fury said to a @@ -2127,8 +1852,7 @@ opening code tag code{# as demonstrated here: <h2><a name='sect41' href='#toc41'>Line-breaks</a></h2> <p> -<br> -To break a line within a "paragraph object", two backslashes \\ with a space + To break a line within a "paragraph object", two backslashes \\ with a space before and a space or newline after them may be used. <p> <br> <pre>To break a line within a "paragraph object", @@ -2136,30 +1860,26 @@ two backslashes \\ with a space before and a space or newline after them \\ may be used. </pre> -<p> <br> -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). +<p> 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). <p> <h2><a name='sect42' href='#toc42'>Page Breaks</a></h2> -<p> <br> -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: -<p> <br> -page new =\= or breaks the page, starts a new page. -<p> <br> -page break -\- or breaks a column, starts a new column, if using columns, -else breaks the page, starts a new page. +<p> 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: +<p> page new =\= +or breaks the page, starts a new page. +<p> page break -\- or breaks a column, +starts a new column, if using columns, else breaks the page, starts a new +page. <p> <br> <pre>-\\- or <:pb> </pre> -<p> <br> - -<p>or +<p> or <p> <br> <pre>=\\= or @@ -2168,50 +1888,43 @@ or <p> <h2><a name='sect43' href='#toc43'>Book Index</a></h2> -<p> <br> -To make an index append to paragraph the book index term relates to it, -using an equal sign and curly braces. -<p> <br> -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. -<p> <br> +<p> To make an index append to paragraph the book index term relates +to it, using an equal sign and curly braces. +<p> 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. <br> <pre> Paragraph containing main term and sub-term. ={Main term:sub-term} </pre> -<p> <br> -The index syntax starts on a new line, but there should not be an empty +<p> The index syntax starts on a new line, but there should not be an empty line between paragraph and index markup. -<p> <br> -The structure of the resulting index would be: +<p> The structure of the resulting +index would be: <p> <br> <pre> Main term, 1 sub-term, 1 </pre> -<p> <br> -Several terms may relate to a paragraph, they are separated by a semicolon. +<p> 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. <p> <br> <pre> Paragraph containing main term, second term and sub-term. ={first term; second term: sub-term} </pre> -<p> <br> -The structure of the resulting index would be: +<p> The structure of the resulting index would be: <p> <br> <pre> First term, 1, Second term, 1, sub-term, 1 </pre> -<p> <br> -If multiple sub-terms appear under one paragraph, they are separated under +<p> If multiple sub-terms appear under one paragraph, they are separated under the main term heading from each other by a pipe symbol. <p> <br> <pre> 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 </pre> -<p> <br> -The plus one in the example provided indicates the first sub-term spans +<p> 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: <p> <br> @@ -2221,97 +1934,88 @@ be: </pre> <p> <h2><a name='sect44' href='#toc44'>Composite Documents Markup</a></h2> -<br> -<p> <br> -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 <b>.ssm</b> 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 <b>.sst</b> regular markup -file, or <b>.ssi</b> (insert/information) A secondary file of the composite document - -<p>is built prior to processing with the same prefix and the suffix <b>._sst</b> -<p> -<br> +<p> 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 <b>.ssm</b> 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 <b>.sst</b> regular markup file, or <b>.ssi</b> (insert/information) + +<p>A secondary file of the composite document is built prior to processing + +<p>with the same prefix and the suffix <b>._sst</b> +<p> basic markup for importing a -<p>basic markup for importing a document into a master document +<p>document into a master document <p> <br> <pre><< filename1.sst << filename2.ssi </pre> -<p> <br> -The form described above should be relied on. Within the <i>Vim</i> editor it results -in the text thus linked becoming hyperlinked to the document it is calling -in which is convenient for editing. +<p> The form described above should be relied on. Within the <i>Vim</i> editor it +results in the text thus linked becoming hyperlinked to the document it +is calling in which is convenient for editing. <p> <h2><a name='sect45' href='#toc45'>Sisu Filetypes</a></h2> -<br> -<p> <br> -<b>SiSU</b> has <i>plaintext</i> and binary filetypes, and can process either type of -document. +<p> <b>SiSU</b> has +<i>plaintext</i> and binary filetypes, and can process either type of document. + <p> <h2><a name='sect46' href='#toc46'>.sst .ssm .ssi Marked Up Plain Text</a></h2> <p> <dl> -<dt><b>SiSU¤b〕 documents are prepared -as plain-text (utf-8) files with</b> </dt> -<dd><b>SiSU</b> markup. They may make reference to and -contain images (for example), which are stored in the directory beneath -them _sisu/image. 〔b¤SiSU <i>plaintext</i> 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.<br> - -<p> <br> -<b>SiSU</b> 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. -<p> <br> -<b>SiSU</b> source markup can be shared with the command: -<p> <br> - sisu -s [filename]<br> - +<dt><b>SiSU</b> </dt> +<dd>documents are prepared as plain-text +(utf-8) files with <b>SiSU</b> markup. They may make reference to and contain images +(for example), which are stored in the directory beneath them _sisu/image. +〔b¤SiSU <i>plaintext</i> 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. +<p> <b>SiSU</b> 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. +<p> <b>SiSU</b> source markup can be shared +with the command: +<p> sisu -s [filename] <p> </dd> </dl> <h2><a name='sect47' href='#toc47'>Sisu Text - Regular Files (.sst)</a></h2> -<p> <br> +<p> The most common form of document in <b>SiSU,</b> see the section on <b>SiSU</b> markup. <p> <h2><a name='sect48' href='#toc48'>Sisu Master Files (.ssm)</a></h2> -<p> <br> -Composite documents which incorporate other <b>SiSU</b> documents which may be -either regular <b>SiSU</b> text .sst which may be generated independently, or inserts -prepared solely for the purpose of being incorporated into one or more -master documents. -<p> <br> -The mechanism by which master files incorporate other documents is described -as one of the headings under under <b>SiSU</b> markup in the <b>SiSU</b> manual. -<p> <br> -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. -<p> <br> -Note: a secondary file of the composite document is built prior to processing -with the same prefix and the suffix ._sst [^19] +<p> Composite documents which incorporate other <b>SiSU</b> +documents which may be either regular <b>SiSU</b> text .sst which may be generated +independently, or inserts prepared solely for the purpose of being incorporated +into one or more master documents. +<p> The mechanism by which master files +incorporate other documents is described as one of the headings under under +<b>SiSU</b> markup in the <b>SiSU</b> manual. +<p> 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. +<p> Note: +a secondary file of the composite document is built prior to processing +with the same prefix and the suffix ._sst [^18] <p> <h2><a name='sect49' href='#toc49'>Sisu Insert Files (.ssi)</a></h2> <p> -<br> -Inserts are documents prepared solely for the purpose of being incorporated + Inserts are documents prepared solely for the purpose of being incorporated into one or more master documents. They resemble regular <b>SiSU</b> text files except they are ignored by the <b>SiSU</b> processor. Making a file a .ssi file is a quick and convenient way of flagging that it is not intended that @@ -2320,170 +2024,134 @@ the file should be processed on its own. <h2><a name='sect50' href='#toc50'>Sisupod, Zipped Binary Container (sisupod.zip, .ssp)</a></h2> -<p> <br> -A sisupod is a zipped <b>SiSU</b> text file or set of <b>SiSU</b> text files and any -associated images that they contain (this will be extended to include sound -and multimedia-files) +<p> A sisupod is a zipped <b>SiSU</b> text file or set of <b>SiSU</b> +text files and any associated images that they contain (this will be extended +to include sound and multimedia-files) <p> <dl> <dt><b>SiSU</b> </dt> -<dd><i>plaintext</i> 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 +<dd><i>plaintext</i> 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. -<p> <br> -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 <b>SiSU</b> documents. -<p> <br> -The command to create a sisupod is: -<p> <br> - sisu -S [filename]<br> - -<p> <br> -Alternatively, make a pod of the contents of a whole directory: -<p> <br> - sisu -S<br> - -<p> <br> -<b>SiSU</b> processing can be done directly against a sisupod; which may be located -locally or on a remote server for which a url is provided. -<p> <br> -<<a href='http://www.sisudoc.org/sisu/sisu_commands'>http://www.sisudoc.org/sisu/sisu_commands</a> +<p> 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 <b>SiSU</b> documents. + +<p> The command to create a sisupod is: +<p> sisu -S [filename] +<p> Alternatively, +make a pod of the contents of a whole directory: +<p> sisu -S +<p> <b>SiSU</b> processing +can be done directly against a sisupod; which may be located locally or +on a remote server for which a url is provided. +<p> <<a href='http://www.sisudoc.org/sisu/sisu_commands'>http://www.sisudoc.org/sisu/sisu_commands</a> > -<p> <br> -<<a href='http://www.sisudoc.org/sisu/sisu_manual'>http://www.sisudoc.org/sisu/sisu_manual</a> + +<p> <<a href='http://www.sisudoc.org/sisu/sisu_manual'>http://www.sisudoc.org/sisu/sisu_manual</a> > <p> </dd> </dl> <h2><a name='sect51' href='#toc51'>Configuration</a></h2> -<br> <p> <h2><a name='sect52' href='#toc52'>Configuration Files</a></h2> <p> + <h2><a name='sect53' href='#toc53'>Config.yml</a></h2> -<p> <br> -<b>SiSU</b> 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. -<p> <br> -The <b>SiSU</b> configuration file is a yaml file, which means indentation is -significant. -<p> <br> -<b>SiSU</b> resource configuration is determined by looking at the following files -if they exist: -<p> <br> - ./_sisu/v4/sisurc.yml<br> +<p> <b>SiSU</b> 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. +<p> The <b>SiSU</b> configuration file is +a yaml file, which means indentation is significant. +<p> <b>SiSU</b> resource configuration +is determined by looking at the following files if they exist: +<p> ./_sisu/v4/sisurc.yml<br> -<p> <br> - ./_sisu/sisurc.yml<br> +<p> ./_sisu/sisurc.yml<br> -<p> <br> - ~/.sisu/v4/sisurc.yml<br> +<p> ~/.sisu/v4/sisurc.yml<br> -<p> <br> - ~/.sisu/sisurc.yml<br> +<p> ~/.sisu/sisurc.yml<br> -<p> <br> - /etc/sisu/v4/sisurc.yml<br> +<p> /etc/sisu/v4/sisurc.yml<br> -<p> <br> - /etc/sisu/sisurc.yml<br> +<p> /etc/sisu/sisurc.yml<br> -<p> <br> -The search is in the order listed, and the first one found is used. -<p> <br> -In the absence of instructions in any of these it falls back to the internal +<p> The search is in the order listed, and the first one found is used. +<p> + In the absence of instructions in any of these it falls back to the internal program defaults. -<p> <br> -Configuration determines the output and processing directories and the -database access details. -<p> <br> - -<p>If <b>SiSU</b> is installed a sample sisurc.yml may be found in /etc/sisu/sisurc.yml +<p> Configuration determines the output and processing directories +and the database access details. +<p> If <b>SiSU</b> is installed a sample sisurc.yml +<p>may be found in /etc/sisu/sisurc.yml <p> <h2><a name='sect54' href='#toc54'>Sisu_document_make</a></h2> -<p> <br> -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. +<p> 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. +<p> The search order +is as for resource configuration: +<p> ./_sisu/v4/sisu_document_make<br> -<p> <br> -The search order is as for resource configuration: -<p> <br> - ./_sisu/v4/sisu_document_make<br> +<p> ./_sisu/sisu_document_make<br> -<p> <br> - ./_sisu/sisu_document_make<br> +<p> ~/.sisu/v4/sisu_document_make<br> -<p> <br> - ~/.sisu/v4/sisu_document_make<br> +<p> ~/.sisu/sisu_document_make<br> -<p> <br> - ~/.sisu/sisu_document_make<br> +<p> /etc/sisu/v4/sisu_document_make<br> -<p> <br> - /etc/sisu/v4/sisu_document_make<br> +<p> /etc/sisu/sisu_document_make<br> -<p> <br> - /etc/sisu/sisu_document_make<br> - -<p> <br> -A sample sisu_document_make can be found in the _sisu/ directory under +<p> A sample sisu_document_make can be found in the _sisu/ directory under along with the provided sisu markup samples. <p> <h2><a name='sect55' href='#toc55'>Css - Cascading Style Sheets (for Html, Xhtml and Xml)</a></h2> -<br> - -<p> <br> -CSS files to modify the appearance of <b>SiSU</b> html, <i>XHTML</i> or <i>XML</i> 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. -<p> <br> -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. -<p> <br> -<i>HTML:</i> html. css -<p> <br> -<i>XML</i> DOM: dom.css -<p> <br> -<i>XML</i> SAX: sax.css -<p> <br> -<i>XHTML:</i> xhtml. css -<p> <br> -The default homepage may use homepage.css or html. css -<p> <br> -Under consideration is to permit the placement of a CSS file with a different -name in directory _sisu/css directory or equivalent.[^20] -<p> -<h2><a name='sect56' href='#toc56'>Organising Content -- Directory Structure and Mapping</a></h2> -<br> -<p> <br> -<b>SiSU</b> v3 has new options for the source directory tree, and output directory +<p> CSS files to modify the appearance of <b>SiSU</b> html, +<i>XHTML</i> or <i>XML</i> 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. +<p> 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. +<p> <i>HTML:</i> html. css +<p> <i>XML</i> +DOM: dom.css +<p> <i>XML</i> SAX: sax.css +<p> <i>XHTML:</i> xhtml. css +<p> The default homepage +may use homepage.css or html. css +<p> Under consideration is to permit the +placement of a CSS file with a different name in directory _sisu/css directory +or equivalent.[^19] +<p> +<h2><a name='sect56' href='#toc56'>Organising Content - Directory Structure and Mapping</a></h2> + +<p> + <b>SiSU</b> v3 has new options for the source directory tree, and output directory structures of which there are 3 alternatives. <p> <h2><a name='sect57' href='#toc57'>Document Source Directory</a></h2> <p> -<br> -The document source directory is the directory in which sisu processing + 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/, @@ -2512,35 +2180,34 @@ is limited to langagues supported by XeTeX polyglosia. <p> <h2><a name='sect60' href='#toc60'>Output Directory Root</a></h2> -<p> <br> -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 +<p> 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) -<p> <br> -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. +<p> 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. <p> <h2><a name='sect61' href='#toc61'>Alternative Output Structures</a></h2> -<p> <br> -There are 3 possibile output structures described as being, by language, +<p> + There are 3 possibile output structures described as being, by language, by filetype or by filename, the selection is made in sisurc.yml <p> <br> <pre>#% output_dir_structure_by: language; filetype; or filename @@ -2552,18 +2219,15 @@ v2) <p> <h2><a name='sect62' href='#toc62'>by Language</a></h2> -<p> <br> - -<p>The by language directory structure places output files -<p> <br> -The by language directory structure separates output files by language +<p> The by language directory structure places output files +<p> + The by language directory structure separates output files by language code (all files of a given language), and within the language directory by filetype. -<p> <br> +<p> Its selection is configured in sisurc.yml +<p> output_dir_structure_by: -<p>Its selection is configured in sisurc.yml -<p> <br> -output_dir_structure_by: language +<p>language <p> <br> <pre> |-- en |-- epub @@ -2592,20 +2256,18 @@ output_dir_structure_by: language |-- rng ‘-- xsd </pre> -<p> <br> -#by: language subject_dir/en/manifest/filename.html +<p> #by: language subject_dir/en/manifest/filename.html <p> <h2><a name='sect63' href='#toc63'>by Filetype</a></h2> -<p> <br> -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. -<p> <br> +<p> 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. +<p> Its selection is configured in sisurc.yml +<p> output_dir_structure_by: -<p>Its selection is configured in sisurc.yml -<p> <br> -output_dir_structure_by: filetype +<p>filetype <p> <br> <pre> |-- epub |-- hashes @@ -2633,19 +2295,17 @@ output_dir_structure_by: filetype |-- xhtml ‘-- xml </pre> -<p> <br> -#by: filetype subject_dir/html/filename/manifest.en.html +<p> #by: filetype subject_dir/html/filename/manifest.en.html <p> <h2><a name='sect64' href='#toc64'>by Filename</a></h2> -<p> <br> +<p> The by filename directory structure places most output of a particular file (the different filetypes) in a common directory. -<p> <br> +<p> Its selection is -<p>Its selection is configured in sisurc.yml -<p> <br> -output_dir_structure_by: filename +<p>configured in sisurc.yml +<p> output_dir_structure_by: filename <p> <br> <pre> |-- epub |-- po4a @@ -2666,13 +2326,14 @@ output_dir_structure_by: filename |-- pod ‘-- viral_spiral.david_bollier </pre> -<p> <br> -#by: filename subject_dir/filename/manifest.en.html +<p> #by: filename subject_dir/filename/manifest.en.html <p> <h2><a name='sect65' href='#toc65'>Remote Directories</a></h2> -<p> <br> -<pre>% containing sub_directories named after the generated files from which +<p> +<br> +<pre> ./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 @@ -2689,7 +2350,8 @@ they are made <h2><a name='sect66' href='#toc66'>Sisupod</a></h2> <p> <br> -<pre>% files stored at this level e.g. sisu_manual.sst +<pre> ./sisupod/ +% files stored at this level e.g. sisu_manual.sst ./sisupod/_sisu % configuration file e.g. sisurc.yml ./sisupod/_sisu/skin @@ -2704,60 +2366,52 @@ they are made <p> <h2><a name='sect68' href='#toc68'>Homepages</a></h2> -<br> -<p> <br> -<b>SiSU</b> is about the ability to auto-generate documents. Home pages are regarded -as custom built items, and are not created by <b>SiSU.</b> More accurately, <b>SiSU</b> -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: -<p> <br> -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) -<p> <br> -2. through providing what you want as the home page in a skin, -<p> <br> -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. -<p> -<h2><a name='sect69' href='#toc69'>Home Page and Other -Custom Built Pages in a Sub-directory</a></h2> - -<p> <br> -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: -<p> <br> - sisu -CC<br> - -<p> +<p> <b>SiSU</b> is about the ability to auto-generate +documents. Home pages are regarded as custom built items, and are not created +by <b>SiSU.</b> More accurately, <b>SiSU</b> 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: +<p> 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) +<p> 2. through providing what you want as the +home page in a skin, +<p> 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. +<p> +<h2><a name='sect69' href='#toc69'>Home +Page and Other Custom Built Pages in a Sub-directory</a></h2> + +<p> 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: +<p> + sisu -CC <h2><a name='sect70' href='#toc70'>Markup and Output Examples</a></h2> -<br> <p> <h2><a name='sect71' href='#toc71'>Markup Examples</a></h2> -<p> <br> -Current markup examples and document output samples are provided off <<a href='http://sisudoc.org'>http://sisudoc.org</a> +<p> Current markup examples +and document output samples are provided off <<a href='http://sisudoc.org'>http://sisudoc.org</a> +> or <<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> > -or <<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> -> and in the sisu -markup-sample package available -off <<a href='http://sources.sisudoc.org'>http://sources.sisudoc.org</a> +and in the sisu -markup-sample package available off <<a href='http://sources.sisudoc.org'>http://sources.sisudoc.org</a> > -<p> <br> -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. + +<p> 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. <p> <h2><a name='sect72' href='#toc72'>Sisu Markup Samples</a></h2> -<p> <br> -A few additional sample books prepared as sisu markup samples, output formats +<p> A few +additional sample books prepared as sisu markup samples, output formats to be generated using <b>SiSU</b> 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 @@ -2766,320 +2420,284 @@ requirements that do not meet the <b>Debian</b> Free Software Guidelines for var reasons, most commonly that they require that the original substantive text remain unchanged, and sometimes that the works be used only non-commercially. -<p> <br> -<i>Accelerando,</i> Charles Stross (2005) accelerando.charles_stross.sst -<p> <br> -<i>Alice’s</i> Adventures in Wonderland, Lewis Carroll (1865) alices_adventures_in_wonderland.lewis_carroll.sst +<p> <i>Accelerando,</i> Charles Stross (2005) accelerando.charles_stross.sst +<p> <i>Alice’s</i> +Adventures in Wonderland, Lewis Carroll (1865) alices_adventures_in_wonderland.lewis_carroll.sst -<p> <br> -<i>CONTENT,</i> Cory Doctorow (2008) content.cory_doctorow.sst -<p> <br> -<i>Democratizing</i> Innovation, Eric von Hippel (2005) democratizing_innovation.eric_von_hippel.sst +<p> <i>CONTENT,</i> Cory Doctorow (2008) content.cory_doctorow.sst +<p> <i>Democratizing</i> +Innovation, Eric von Hippel (2005) democratizing_innovation.eric_von_hippel.sst -<p> <br> -<i>Down</i> and Out in the Magic Kingdom, Cory Doctorow (2003) down_and_out_in_the_magic_kingdom.cory_doctorow.sst +<p> <i>Down</i> and Out in the Magic Kingdom, Cory Doctorow (2003) down_and_out_in_the_magic_kingdom.cory_doctorow.sst -<p> <br> -<i>For</i> the Win, Cory Doctorow (2010) for_the_win.cory_doctorow.sst -<p> <br> -<i>Free</i> as in Freedom - Richard Stallman’s Crusade for Free Software, Sam Williams +<p> <i>For</i> the Win, Cory Doctorow (2010) for_the_win.cory_doctorow.sst +<p> <i>Free</i> +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 -<p> <br> -<i>Free</i> as in Freedom 2.0 - Richard Stallman and the Free Software Revolution, +<p> <i>Free</i> 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 -<p> <br> -<i>Free</i> Culture - How Big Media Uses Technology and the Law to Lock Down Culture -and Control Creativity, Lawrence Lessig (2004) free_culture.lawrence_lessig.sst +<p> <i>Free</i> Culture - How Big Media Uses Technology and the Law to Lock Down +Culture and Control Creativity, Lawrence Lessig (2004) free_culture.lawrence_lessig.sst -<p> <br> -<i>Free</i> For All - How Linux and the Free Software Movement Undercut the High +<p> <i>Free</i> For All - How Linux and the Free Software Movement Undercut the High Tech Titans, Peter Wayner (2002) free_for_all.peter_wayner.sst -<p> <br> -<i>GNU</i> GENERAL PUBLIC LICENSE v2, Free Software Foundation (1991) gpl2.fsf.sst +<p> <i>GNU</i> GENERAL +PUBLIC LICENSE v2, Free Software Foundation (1991) gpl2.fsf.sst +<p> <i>GNU</i> GENERAL +PUBLIC LICENSE v3, Free Software Foundation (2007) gpl3.fsf.sst +<p> <i>Gulliver’s</i> +Travels, Jonathan Swift (1726 / 1735) gullivers_travels.jonathan_swift.sst -<p> <br> -<i>GNU</i> GENERAL PUBLIC LICENSE v3, Free Software Foundation (2007) gpl3.fsf.sst +<p> <i>Little</i> Brother, Cory Doctorow (2008) little_brother.cory_doctorow.sst +<p> + <i>The</i> Cathederal and the Bazaar, Eric Raymond (2000) the_cathedral_and_the_bazaar.eric_s_raymond.sst -<p> <br> -<i>Gulliver’s</i> Travels, Jonathan Swift (1726 / 1735) gullivers_travels.jonathan_swift.sst - -<p> <br> -<i>Little</i> Brother, Cory Doctorow (2008) little_brother.cory_doctorow.sst -<p> <br> -<i>The</i> Cathederal and the Bazaar, Eric Raymond (2000) the_cathedral_and_the_bazaar.eric_s_raymond.sst - -<p> <br> -<i>The</i> Public Domain - Enclosing the Commons of the Mind, James Boyle (2008) +<p> <i>The</i> Public Domain - Enclosing the Commons of the Mind, James Boyle (2008) <p>the_public_domain.james_boyle.sst -<p> <br> -<i>The</i> Wealth of Networks - How Social Production Transforms Markets and Freedom, -Yochai Benkler (2006) the_wealth_of_networks.yochai_benkler.sst -<p> <br> -<i>Through</i> the Looking Glass, Lewis Carroll (1871) through_the_looking_glass.lewis_carroll.sst +<p> <i>The</i> Wealth of Networks - How Social Production +Transforms Markets and Freedom, Yochai Benkler (2006) the_wealth_of_networks.yochai_benkler.sst -<p> <br> -<i>Two</i> Bits - The Cultural Significance of Free Software, Christopher Kelty +<p> <i>Through</i> the Looking Glass, Lewis Carroll (1871) through_the_looking_glass.lewis_carroll.sst + +<p> <i>Two</i> Bits - The Cultural Significance of Free Software, Christopher Kelty (2008) two_bits.christopher_kelty.sst -<p> <br> -<i>UN</i> Contracts for International Sale of Goods, UN (1980) un_contracts_international_sale_of_goods_convention_1980.sst +<p> <i>UN</i> Contracts for International Sale +of Goods, UN (1980) un_contracts_international_sale_of_goods_convention_1980.sst -<p> <br> -<i>Viral</i> Spiral, David Bollier (2008) viral_spiral.david_bollier.sst +<p> <i>Viral</i> Spiral, David Bollier (2008) viral_spiral.david_bollier.sst <p> -<h2><a name='sect73' href='#toc73'>Sisu Search -- Introduction</a></h2> -<br> +<h2><a name='sect73' href='#toc73'>Sisu +Search - Introduction</a></h2> -<p> <br> -<b>SiSU</b> output can easily and conveniently be indexed by a number of standalone -indexing tools, such as Lucene, Hyperestraier. -<p> <br> -Because the document structure of sites created is clearly defined, and +<p> <b>SiSU</b> output can easily and conveniently be indexed +by a number of standalone indexing tools, such as Lucene, Hyperestraier. + +<p> Because the document structure of sites created is clearly defined, and the text <i>object</i> 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. -<p> <br> -In addition to this <b>SiSU</b> 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. +<p> In addition to this <b>SiSU</b> 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. <p> <h2><a name='sect74' href='#toc74'>Sql</a></h2> -<br> <p> <h2><a name='sect75' href='#toc75'>Populating Sql Type Databases</a></h2> -<p> <br> -<b>SiSU</b> feeds sisu markupd documents into sql type databases <i>PostgreSQL</i> [^21] -and/or <i>SQLite</i> [^22] database together with information related to document -structure. -<p> <br> -This is one of the more interesting output forms, as all the structural +<p> <b>SiSU</b> feeds +sisu markupd documents into sql type databases <i>PostgreSQL</i> [^20] and/or <i>SQLite</i> +[^21] database together with information related to document structure. +<p> + 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: -<p> <br> - * one containing semantic (and other) headers, including, title, author,<br> - subject, (the<br> +<p> * one containing semantic (and other) headers, +including, title, author, subject, (the<br> .I Dublin Core.<br> ..);<br> -<p> <br> - * another the substantive texts by individual "paragraph" (or object) --<br> - along with structural information, each paragraph being identifiable +<p> * another the substantive texts by individual "paragraph" (or object) +- along with structural information, each paragraph being identifiable by its<br> paragraph number (if it has one which almost all of them do), and the<br> substantive text of each paragraph quite naturally being searchable (both in<br> formatted and clean text versions for searching); and<br> -<p> <br> - * a third containing endnotes cross-referenced back to the paragraph from<br> - which they are referenced (both in formatted and clean text versions +<p> * a third containing endnotes cross-referenced back to the paragraph +from which they are referenced (both in formatted and clean text versions for<br> searching).<br> -<p> <br> - * a fourth table with a one to one relation with the headers table contains<br> - full text versions of output, eg. pdf, html, xml, and<br> +<p> * a fourth table with a one to one relation with the headers table contains + full text versions of output, eg. pdf, html, xml, and<br> .I ascii.<br> -<p> <br> -There is of course the possibility to add further structures. -<p> <br> -At this level <b>SiSU</b> 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 +<p> There is of course the possibility to add further structures. +<p> At this +level <b>SiSU</b> 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. -<p> <br> -Being able to search a relational database at an object level with the -<b>SiSU</b> citation system is an effective way of locating content generated -by <b>SiSU.</b> 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 <i>Dublin</i> Core is incorporated it is easy to make -use of that as well). +<p> Being able to search a relational +database at an object level with the <b>SiSU</b> citation system is an effective +way of locating content generated by <b>SiSU.</b> 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 +<i>Dublin</i> Core is incorporated it is easy to make use of that as well). <p> <h2><a name='sect76' href='#toc76'>Postgresql</a></h2> -<br> <p> -<h2><a name='sect77' href='#toc77'>Name</a></h2> -<p> <br> -<b>SiSU</b> - Structured information, Serialized Units - a document publishing system, +<h2><a name='sect77' href='#toc77'>Name</a></h2> -<p>postgresql dependency package +<p> <b>SiSU</b> - Structured information, Serialized Units - a document publishing +system, postgresql dependency package <p> <h2><a name='sect78' href='#toc78'>Description</a></h2> -<p> <br> -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 <b>SiSU</b> to populate a postgresql database, this being part of <b>SiSU</b> - man -sisu) . +<p> 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 <b>SiSU</b> +to populate a postgresql database, this being part of <b>SiSU</b> - man sisu) . + <p> <h2><a name='sect79' href='#toc79'>Synopsis</a></h2> -<p> <br> - sisu -D [instruction] [filename/wildcard if required]<br> - -<p> <br> - sisu -D --pg --[instruction] [filename/wildcard if required]<br> - +<p> sisu -D [instruction] [filename/wildcard if required] +<p> sisu +-D --pg --[instruction] [filename/wildcard if required] <p> <h2><a name='sect80' href='#toc80'>Commands</a></h2> -<p> <br> -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, +<p> 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 -<p>alternatively --sqlite or --pgsql may be used -<p> <br> -<b>-D or --pgsql</b> may be used interchangeably. +<p>- +<p>- +<p>sqlite or --pgsql may be used +<p> <b>-D or --pgsql</b> may be used interchangeably. <p> -<h2><a name='sect81' href='#toc81'>Create and Destroy Database</a></h2> +<h2><a name='sect81' href='#toc81'>Create +and Destroy Database</a></h2> <p> <dl> -<dt><b>--pgsql ---createall</b> </dt> -<dd>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) +<dt><b>--pgsql --createall</b> </dt> +<dd>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) <p> </dd> -<dt><b>sisu -D ---createdb</b> </dt> +<dt><b>sisu -D --createdb</b> </dt> <dd>creates database where no database existed before + <p> </dd> -<dt><b>sisu -D --create</b> -</dt> -<dd> -<p>creates database tables where no database tables existed before +<dt><b>sisu -D --create</b> </dt> +<dd>creates database tables where no database tables existed + +<p>before <p> </dd> -<dt><b>sisu -D ---Dropall</b> </dt> -<dd>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). +<dt><b>sisu -D --Dropall</b> </dt> +<dd>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). <p> </dd> <dt><b>sisu -D --recreate</b> </dt> -<dd>destroys existing database and builds +<dd>destroys existing database -<p>a new empty database structure +<p>and builds a new empty database structure <p> </dd> </dl> <h2><a name='sect82' href='#toc82'>Import and Remove Documents</a></h2> <p> -<dl> -<dt><b>sisu -D --import --v [filename/wildcard]</b> </dt> -<dd>populates database with the contents of the file. -Imports documents(s) specified to a postgresql database (at an object level). +<dl> +<dt><b>sisu -D --import -v [filename/wildcard]</b> </dt> +<dd>populates database with the contents +of the file. Imports documents(s) specified to a postgresql database (at +an object level). <p> </dd> <dt><b>sisu -D --update -v [filename/wildcard]</b> </dt> -<dd>updates file contents in database +<dd>updates file contents +<p>in database <p> </dd> <dt><b>sisu -D --remove -v [filename/wildcard]</b> </dt> -<dd>removes specified document from postgresql -database. +<dd>removes specified document +from postgresql database. <p> </dd> </dl> <h2><a name='sect83' href='#toc83'>Sqlite</a></h2> -<br> <p> <h2><a name='sect84' href='#toc84'>Name</a></h2> -<p> <br> -<b>SiSU</b> - Structured information, Serialized Units - a document publishing system. - +<p> <b>SiSU</b> - Structured information, Serialized +Units - a document publishing system. <p> <h2><a name='sect85' href='#toc85'>Description</a></h2> -<p> <br> -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 <b>SiSU</b> to populate an sqlite database, this being part of <b>SiSU</b> - man sisu) -. +<p> 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 <b>SiSU</b> to populate +an sqlite database, this being part of <b>SiSU</b> - man sisu) . <p> <h2><a name='sect86' href='#toc86'>Synopsis</a></h2> -<p> <br> - sisu -d [instruction] [filename/wildcard if required]<br> - -<p> <br> - sisu -d --(sqlite|pg) --[instruction] [filename/wildcard if <br> - required]<br> - +<p> sisu +-d [instruction] [filename/wildcard if required] +<p> sisu -d --(sqlite|pg) --[instruction] +[filename/wildcard if required] <p> <h2><a name='sect87' href='#toc87'>Commands</a></h2> -<p> <br> -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, +<p> 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 -<p>alternatively --sqlite or --pgsql may be used -<p> <br> -<b>-d or --sqlite</b> may be used interchangeably. +<p>may be used +<p> <b>-d or --sqlite</b> may be used interchangeably. <p> -<h2><a name='sect88' href='#toc88'>Create and Destroy Database</a></h2> +<h2><a name='sect88' href='#toc88'>Create and Destroy +Database</a></h2> <p> <dl> -<dt><b>--sqlite ---createall</b> </dt> -<dd>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) +<dt><b>--sqlite --createall</b> </dt> +<dd>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) <p> </dd> -<dt><b>sisu -d --createdb</b> -</dt> -<dd> -<p>creates database where no database existed before +<dt><b>sisu +-d --createdb</b> </dt> +<dd>creates database where no database existed before <p> </dd> -<dt><b>sisu -d --create</b> </dt> -<dd>creates - -<p>database tables where no database tables existed before +<dt><b>sisu -d --create</b> +</dt> +<dd> +<p>creates database tables where no database tables existed before <p> </dd> -<dt><b>sisu -d --dropall</b> -</dt> -<dd>destroys database (including all its content)! kills data and drops tables, -indexes and database associated with a given directory (and directories +<dt><b>sisu -d +--dropall</b> </dt> +<dd>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). <p> </dd> @@ -3114,43 +2732,38 @@ database. </dl> <h2><a name='sect90' href='#toc90'>Introduction</a></h2> -<br> <p> -<h2><a name='sect91' href='#toc91'>Search - Database Frontend Sample, Utilising Database and Sisu Features,</a></h2> -INCLUDING -OBJECT CITATION NUMBERING (BACKEND CURRENTLY POSTGRESQL) -<p> <br> -Sample search frontend <<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a> -> [^23] A small database and -sample query front-end (search from) that makes use of the citation system, -<i>object</i> citation numbering to demonstrates functionality.[^24] -<p> <br> -<b>SiSU</b> can provide information on which documents are matched and at what +<h2><a name='sect91' href='#toc91'>Search - Database Frontend Sample, Utilising Database +and Sisu Features,</a></h2> +INCLUDING OBJECT CITATION NUMBERING (BACKEND CURRENTLY +POSTGRESQL) +<p> Sample search frontend <<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a> +> [^22] A small +database and sample query front-end (search from) that makes use of the +citation system, .I object citation numbering to demonstrates functionality.[^23] + +<p> <b>SiSU</b> 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 <i>object</i> citation numbering, which includes html, <i>XML,</i> <i>EPUB,</i> <i>LaTeX,</i> <i>PDF</i> and indeed the <i>SQL</i> database. You can then refer to one of the other outputs or in the <i>SQL</i> database expand the text within the matched objects (paragraphs) in the documents matched. -<p> <br> -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] +<p> 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.[^24] <p> <dl> <dt><b>sisu -F --webserv-webrick</b> </dt> -<dd>builds a cgi web - -<p>search frontend for the database created -<p> <br> -The following is feedback on the setup on a machine provided by the help -command: -<p> <br> - sisu --help sql<br> +<dd>builds a cgi web search -<p> <br> +<p>frontend for the database created +<p> The following is feedback on the setup +on a machine provided by the help command: +<p> sisu --help sql <br> <pre>Postgresql user: ralph current db set: SiSU_sisu @@ -3160,156 +2773,138 @@ sqlite current db set: /home/ralph/sisu_www/sisu/sisu_sqlite.db dbi connect DBI:SQLite:/home/ralph/sisu_www/sisu/sisu_sqlite.db </pre> -<p> <br> - -<p>Note on databases built -<p> <br> -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 -<p> </dd> +<p> Note on databases built +<p> 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] </dd> </dl> -<h2><a name='sect92' href='#toc92'>Search -Form</a></h2> +<h2><a name='sect92' href='#toc92'>Search Form</a></h2> <p> <dl> <dt><b>sisu -F</b> </dt> -<dd>generates a sample search form, which must be copied to the +<dd>generates a sample search form, which -<p>web-server cgi directory +<p>must be copied to the web-server cgi directory <p> </dd> <dt><b>sisu -F --webserv-webrick</b> </dt> -<dd>generates a sample search -form for use with the webrick server, which must be copied to the web-server +<dd>generates +a sample search form for use with the webrick server, which must be copied -<p>cgi directory +<p>to the web-server cgi directory <p> </dd> <dt><b>sisu -W</b> </dt> -<dd>starts the webrick server which should be available +<dd>starts the webrick server which -<p>wherever sisu is properly installed -<p> <br> +<p>should be available wherever sisu is properly installed +<p> The generated -<p>The generated search form must be copied manually to the webserver directory +<p>search form must be copied manually to the webserver directory as instructed -<p>as instructed <p> </dd> </dl> <h2><a name='sect93' href='#toc93'>Sisu_webrick</a></h2> -<br> <p> <h2><a name='sect94' href='#toc94'>Name</a></h2> -<p> <br> -<b>SiSU</b> - Structured information, Serialized Units - a document publishing system +<p> <b>SiSU</b> - Structured information, Serialized Units - a document +<p>publishing system <p> <h2><a name='sect95' href='#toc95'>Synopsis</a></h2> -<p> <br> -sisu_webrick [port] -<p> <br> - -<p>or -<p> <br> -sisu -W [port] +<p> sisu_webrick [port] +<p> or +<p> sisu -W [port] <p> + <h2><a name='sect96' href='#toc96'>Description</a></h2> -<p> <br> -sisu_webrick is part of <b>SiSU</b> (man sisu) sisu_webrick starts <b>Ruby</b> <b>SiSU</b> -output is written, providing a list of these directories (assuming <b>SiSU</b> -is in use and they exist). -<p> <br> -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). +<p> sisu_webrick is part of <b>SiSU</b> (man sisu) sisu_webrick starts +<b>Ruby</b> <b>SiSU</b> output is written, providing a list of these directories (assuming +<b>SiSU</b> is in use and they exist). +<p> 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). <p> <h2><a name='sect97' href='#toc97'>Summary of Man Page</a></h2> -<p> <br> -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] -<p> <br> - -<p>where no port is given and settings are unchanged the default port is 8081 +<p> 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] +<p> where no port is given and settings are unchanged +<p>the default port is 8081 <p> <h2><a name='sect98' href='#toc98'>Document Processing Command Flags</a></h2> -<p> <br> -sisu -W [port] starts <b>Ruby</b> Webrick web-server, serving <b>SiSU</b> output directories, -on the port provided, or if no port is provided and the defaults have not +<p> sisu -W [port] +starts <b>Ruby</b> Webrick web-server, serving <b>SiSU</b> output directories, on the +port provided, or if no port is provided and the defaults have not been -<p>been changed in ~/.sisu/sisurc.yaml then on port 8081 +<p>changed in ~/.sisu/sisurc.yaml then on port 8081 <p> <h2><a name='sect99' href='#toc99'>Summary of Features</a></h2> -<br> -<p> <br> -* sparse/minimal markup (clean utf-8 source texts). Documents are prepared +<p> * +sparse/minimal markup (clean utf-8 source texts). Documents are prepared in a single <i>UTF-8</i> file using a minimalistic mnemonic syntax. Typical literature, documents like "War and Peace" require almost no markup, and most of the headers are optional. -<p> <br> -* markup is easily readable/parsable by the human eye, (basic markup is -simpler and more sparse than the most basic <i>HTML</i> ) , [this may also be - converted to .I XML representations of the same input/source document]. -<p> -<br> -* 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. <b>SiSU</b> 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) -<p> <br> -* 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: -<p> <br> -* <i>HTML</i> - both as a single scrollable text and a segmented document -<p> <br> -* <i>XHTML</i> -<p> <br> -* <i>EPUB</i> -<p> <br> -* <i>XML</i> - both in sax and dom style xml structures for further development - -<p>as required -<p> <br> -* <i>ODT</i> - Open Document Format text, the iso standard for document storage - -<p> <br> -* <i>LaTeX</i> - used to generate pdf -<p> <br> -* <i>PDF</i> (via <i>LaTeX</i> ) -<p> <br> -* <i>SQL</i> - population of an sql database ( <i>PostgreSQL</i> or <i>SQLite</i> ) , (at the -same object level that is used to cite text within a document) -<p> <br> -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 <i>LaTeX,</i> databases populated with documents at an individual object/paragraph -level, making possible <i>granular</i> search (and related possibilities)) -<p> <br> -* ensuring content can be cited in a meaningful way regardless of selected +<p> * markup is easily readable/parsable by the human +eye, (basic markup is simpler and more sparse than the most basic <i>HTML</i> +) , [this may also be converted to <i>XML</i> representations of the same input/source +document]. +<p> * 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. <b>SiSU</b> 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) +<p> * 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: +<p> * <i>HTML</i> - both as a single scrollable + +<p>text and a segmented document +<p> * <i>XHTML</i> +<p> * <i>EPUB</i> +<p> * <i>XML</i> - both in sax and + +<p>dom style xml structures for further development as required +<p> * <i>ODT</i> - Open +Document Format text, the iso standard for document storage +<p> * <i>LaTeX</i> - + +<p>used to generate pdf +<p> * <i>PDF</i> (via <i>LaTeX</i> ) +<p> * <i>SQL</i> - population of an sql +database ( <i>PostgreSQL</i> or <i>SQLite</i> ) , (at the same object level that is used +to cite text within a document) +<p> 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 <i>LaTeX,</i> databases populated with documents at an individual +object/paragraph level, making possible <i>granular</i> search (and related possibilities)) + +<p> * 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 @@ -3319,229 +2914,178 @@ 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, <i>HTML,</i> <i>EPUB,</i> xml, sqlite, postgresql) , this numbering system can be used to reference content. -<p> <br> -* Granular search within documents. <i>SQL</i> 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 -<p> <br> -* 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 -<p> <br> -* <i>SQL</i> search aside, documents are generated as required and static once -generated. -<p> <br> -* 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) -<p> <br> -* document source ( <i>plaintext</i> utf-8) if shared on the net may be used as - -<p>input and processed locally to produce the different document outputs -<p> -<br> -* document source may be bundled together (automatically) with associated +<p> * Granular search within +documents. <i>SQL</i> 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]. +<p> * 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, + +<p>without modification of existing prepared texts +<p> * <i>SQL</i> search aside, documents +are generated as required and static once generated. +<p> * 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) + +<p> * document source ( <i>plaintext</i> utf-8) if shared on the net may be used + +<p>as input and processed locally to produce the different document outputs + +<p> * 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 <p>these too may be processed locally to produce the desired document outputs -<p> <br> -* generated document outputs may automatically be posted to remote sites. +<p> * generated document outputs may automatically be posted to remote sites. -<p> <br> -* for basic document generation, the only software dependency is <b>Ruby,</b> +<p> * for basic document generation, the only software dependency is <b>Ruby,</b> and a few standard Unix tools (this covers <i>plaintext,</i> <i>HTML,</i> <i>EPUB,</i> <i>XML,</i> <i>ODF,</i> <i>LaTeX</i> ) . To use a database you of course need that, and to convert the <i>LaTeX</i> generated to pdf, a latex processor like tetex or texlive. -<p> <br> -* as a developers tool it is flexible and extensible -<p> <br> -Syntax highlighting for <b>SiSU</b> markup is available for a number of text editors. - -<p> <br> -<b>SiSU</b> 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 -<p> <br> -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) ... -<p> <br> -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. +<p> * + +<p>as a developers tool it is flexible and extensible +<p> Syntax highlighting +for <b>SiSU</b> markup is available for a number of text editors. +<p> <b>SiSU</b> 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 +<p> 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) ... +<p> 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. <p> <ol> -<b>.</b><li>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. -<p> <br> -</li><b>.</b><li>i.e. the -<p> <br> -<i>HTML,</i> -<p> <br> -<i>PDF,</i> -<p> <br> -<i>EPUB,</i> -<p> <br> - -<p><i>ODT</i> -<p> <br> -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. -<p> <br> -</li><b>.</b><li> -<p>the different heading levels -<p> <br> -</li><b>.</b><li>units of text, primarily paragraphs and headings, also any tables, poems, - -<p>code-blocks -<p> <br> -</li><b>.</b><li> -<p>An open standard format for e-books -<p> <br> -</li><b>.</b><li>Open Document Format ( -<p> <br> - -<p><i>ODF</i> -<p> <br> -) text -<p> <br> -</li><b>.</b><li> -<p>Specification submitted by Adobe to ISO to become a full open ISO specification - -<p> <br> -<<a href='http://www.linux-watch.com/news/NS7542722606.html'>http://www.linux-watch.com/news/NS7542722606.html</a> +<b>.</b><li>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. +<p> </li><b>.</b><li>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. +<p> </li><b>.</b><li>the different + +<p>heading levels +<p> </li><b>.</b><li>units of text, primarily paragraphs and headings, also +any tables, poems, code-blocks +<p> </li><b>.</b><li>An open standard format for e-books +<p> </li><b>.</b><li>Open +Document Format ( ODF ) text +<p> </li><b>.</b><li>Specification submitted by Adobe to ISO +to become a full open ISO specification <<a href='http://www.linux-watch.com/news/NS7542722606.html'>http://www.linux-watch.com/news/NS7542722606.html</a> > -<p> <br> -</li><b>.</b><li> -<p>ISO standard ISO/IEC 26300:2006 -<p> <br> -</dd> + +<p> </li><b>.</b><li>ISO standard ISO/IEC 26300:2006 +<p> </dd> <dt><b>*1.</b> </dt> <dd>square brackets -<p> <br> -</dd> +<p> </dd> <dt><b>*2.</b> </dt> <dd>square brackets -<p> <br> -</dd> + +<p> </dd> <dt><b>+1.</b> </dt> <dd>square brackets -<p> <br> -</li><b>.</b><li><<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a> +<p> </li><b>.</b><li><<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a> > -<p> <br> -</li><b>.</b><li><<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a> +<p> </li><b>.</b><li><<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a> > -<p> <br> -</li><b>.</b><li>From sometime after SiSU 0.58 it should be possible to describe SiSU markup + +<p> </li><b>.</b><li>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. -<p> <br> -</li><b>.</b><li> -<p>files should be prepared using -<p> <br> +<p> </li><b>.</b><li>files -<p><i>UTF-8</i> -<p> <br> +<p>should be prepared using UTF-8 character encoding +<p> </li><b>.</b><li>a footnote or endnote -<p>character encoding -<p> <br> -</li><b>.</b><li> -<p>a footnote or endnote -<p> <br> -</li><b>.</b><li>self contained endnote marker & endnote in one -<p> <br> -</dd> +<p> </li><b>.</b><li>self contained endnote marker & endnote in one +<p> </dd> <dt><b>*.</b> </dt> -<dd>unnumbered asterisk footnote/endnote, insert multiple asterisks if required - -<p> <br> -</dd> +<dd>unnumbered asterisk +footnote/endnote, insert multiple asterisks if required +<p> </dd> <dt><b>**.</b> </dt> -<dd>another unnumbered asterisk footnote/endnote -<p> <br> -</dd> +<dd>another unnumbered + +<p>asterisk footnote/endnote +<p> </dd> <dt><b>*3.</b> </dt> -<dd>editors notes, numbered asterisk footnote/endnote series -<p> <br> -</dd> +<dd>editors notes, numbered asterisk footnote/endnote + +<p>series +<p> </dd> <dt><b>+2.</b> </dt> <dd>editors notes, numbered asterisk footnote/endnote series -<p> <br> +<p> </li><b>.</b><li><<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > -<p> <br> -</li><b>.</b><li><<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a> +<p> </li><b>.</b><li><<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a> > -<p> <br> -</li><b>.</b><li> -<p>Table from the Wealth of Networks by Yochai Benkler -<p> <br> -<<a href='http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler'>http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler</a> +<p> </li><b>.</b><li>Table from the Wealth +of Networks by Yochai Benkler <<a href='http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler'>http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler</a> > -<p> <br> -</li><b>.</b><li>.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 + +<p> </li><b>.</b><li>.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. -<p> <br> -</li><b>.</b><li><<a href='http://www.postgresql.org/'>http://www.postgresql.org/</a> -> -<p> <br> -<<a href='http://advocacy.postgresql.org/'>http://advocacy.postgresql.org/</a> +<p> </li><b>.</b><li>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. +<p> </li><b>.</b><li><<a href='http://www.postgresql.org/'>http://www.postgresql.org/</a> +> <<a href='http://advocacy.postgresql.org/'>http://advocacy.postgresql.org/</a> > -<p> <br> <<a href='http://en.wikipedia.org/wiki/Postgresql'>http://en.wikipedia.org/wiki/Postgresql</a> > -<p> <br> -</li><b>.</b><li><<a href='http://www.hwaci.com/sw/sqlite/'>http://www.hwaci.com/sw/sqlite/</a> -> -<p> <br> -<<a href='http://en.wikipedia.org/wiki/Sqlite'>http://en.wikipedia.org/wiki/Sqlite</a> +<p> </li><b>.</b><li><<a href='http://www.hwaci.com/sw/sqlite/'>http://www.hwaci.com/sw/sqlite/</a> +> <<a href='http://en.wikipedia.org/wiki/Sqlite'>http://en.wikipedia.org/wiki/Sqlite</a> > -<p> <br> -</li><b>.</b><li><<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a> + +<p> </li><b>.</b><li><<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a> > -<p> <br> -</li><b>.</b><li>(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. -<p> <br> -</li><b>.</b><li>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. -<p> <br> +<p> </li><b>.</b><li>(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. +<p> </li><b>.</b><li>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. +<p> <p> </li> </ol> diff --git a/data/doc/sisu/html/sisu4.1.html b/data/doc/sisu/html/sisu4.1.html index 345e574b..f7268daa 100644 --- a/data/doc/sisu/html/sisu4.1.html +++ b/data/doc/sisu/html/sisu4.1.html @@ -34,47 +34,44 @@ sisu [-CcFLSVvW] <p> <br> sisu (--configure|--webrick|--sample-search-form) <h2><a name='sect2' href='#toc2'>Sisu - Manual,</a></h2> -RALPH AMISSAH <br> - +RALPH AMISSAH <p> -<h2><a name='sect3' href='#toc3'>What is Sisu?</a></h2> -<br> +<h2><a name='sect3' href='#toc3'>What +is Sisu?</a></h2> <p> <h2><a name='sect4' href='#toc4'>Introduction - What is Sisu?</a></h2> -<br> -<p> <br> -<b>SiSU</b> 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. -<p> <br> -<b>SiSU</b> is developed under an open source, software libre license ( <i>GPLv3</i> -). 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. - -<p> <br> -<b>SiSU</b> both defines a markup syntax and provides an engine that produces -open standards format outputs from documents prepared with <b>SiSU</b> 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 <b>SiSU</b> markup is more sparse than html and -outputs which include <i>HTML,</i> <i>EPUB,</i> <i>ODT</i> (Open Document Format text), <i>LaTeX,</i> -landscape and portrait <i>PDF,</i> all of which can be added to and updated. <b>SiSU</b> -is also able to populate <i>SQL</i> type databases at an object level, which means -that searches can be made with that degree of granularity. -<p> <br> -Source document preparation and output generation is a two step process: +<p> +<p> <b>SiSU</b> 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. +<p> <b>SiSU</b> is developed under an open source, software +libre license ( <i>GPLv3</i> ). 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. +<p> <b>SiSU</b> both defines a markup syntax and provides +an engine that produces open standards format outputs from documents prepared +with <b>SiSU</b> 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 <b>SiSU</b> markup is more sparse +than html and outputs which include <i>HTML,</i> <i>EPUB,</i> <i>ODT</i> (Open Document Format +text), <i>LaTeX,</i> landscape and portrait <i>PDF,</i> all of which can be added to +and updated. <b>SiSU</b> is also able to populate <i>SQL</i> type databases at an object +level, which means that searches can be made with that degree of granularity. + +<p> 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 @@ -90,41 +87,40 @@ 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. -<p> <br> -In preparing a <b>SiSU</b> 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. -<p> <br> -<b>SiSU</b> 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</b> 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</b> is able -to take advantage of. -<p> <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</b> provides the flexibility of producing documents in multiple non-proprietary -open formats including <i>HTML,</i> <i>EPUB,</i> [^5] <i>ODT,</i> [^6] <i>PDF</i> [^7] <i>ODF,</i> [^8]. Whilst -<b>SiSU</b> 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</b> -can be migrated to other document formats. Further security is provided -by the fact that the software itself, <b>SiSU</b> is available under <i>GPLv3</i> a licence +<p> In preparing a <b>SiSU</b> +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. +<p> <b>SiSU</b> 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</b> 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</b> is able to take advantage of. +<p> 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</b> provides the +flexibility of producing documents in multiple non-proprietary open formats +including <i>HTML,</i> <i>EPUB,</i> [^5] <i>ODT,</i> [^6] <i>PDF</i> [^7] <i>ODF,</i> [^8]. Whilst <b>SiSU</b> 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</b> can +be migrated to other document formats. Further security is provided by the +fact that the software itself, <b>SiSU</b> is available under <i>GPLv3</i> 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 @@ -137,1150 +133,948 @@ related module has been updated repeatedly over the years, presumably when the World Wide Web Consortium (w3c) finalises <i>HTML</i> 5 which is currently under development, the <i>HTML</i> module will again be updated allowing all existing documents to be regenerated as <i>HTML</i> 5). -<p> <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. -<p> <br> -<b>SiSU</b> 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</b> -offers great possibilities. -<p> <br> -<b>SiSU</b> is primarily for published works, which can take advantage of the -citation system to reliably reference its documents. <b>SiSU</b> 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.</b> -<p> <br> -<<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> 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. +<p> <b>SiSU</b> 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</b> offers great possibilities. +<p> <b>SiSU</b> is primarily for published works, +which can take advantage of the citation system to reliably reference its +documents. <b>SiSU</b> 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.</b> +<p> <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > -<p> <br> -<<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> +<p> <<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> > -<p> + <h2><a name='sect5' href='#toc5'>Commands Summary</a></h2> -<br> <p> <h2><a name='sect6' href='#toc6'>Description</a></h2> -<p> <br> -<b>SiSU</b> is a document publishing system, that from a simple single marked-up -document, produces multiple output formats including: <i>plaintext,</i> <i>HTML,</i> -<i>XHTML,</i> <i>XML,</i> <i>EPUB,</i> <i>ODT</i> ( <i>OpenDocument</i> ( <i>ODF</i> ) text), <i>LaTeX,</i> <i>PDF,</i> info, and -<i>SQL</i> ( <i>PostgreSQL</i> and <i>SQLite</i> ) , which share text object numbers ("object -citation numbering") and the same document structure information. For more -see: <<a href='http://sisudoc.org'>http://sisudoc.org</a> +<p> <b>SiSU</b> is a document publishing system, that +from a simple single marked-up document, produces multiple output formats +including: <i>plaintext,</i> <i>HTML,</i> <i>XHTML,</i> <i>XML,</i> <i>EPUB,</i> <i>ODT</i> ( <i>OpenDocument</i> ( <i>ODF</i> +) text), <i>LaTeX,</i> <i>PDF,</i> info, and <i>SQL</i> ( <i>PostgreSQL</i> and <i>SQLite</i> ) , which share +text object numbers ("object citation numbering") and the same document +structure information. For more see: <<a href='http://sisudoc.org'>http://sisudoc.org</a> > or <<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> > -<p> -<h2><a name='sect7' href='#toc7'>Document Processing -Command Flags</a></h2> + +<h2><a name='sect7' href='#toc7'>Document Processing Command Flags</a></h2> <p> <dl> <dt><b>-a [filename/wildcard]</b> </dt> -<dd>produces <i>plaintext</i> with Unix linefeeds -and without markup, (object numbers are omitted), has footnotes at end -of each paragraph that contains them [ -A for 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) -<p> </dd> - -<dt><b>-b [filename/wildcard]</b> </dt> -<dd>see --xhtml -<p> </dd> +<dd>produces <i>plaintext</i> +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) </dd> + +<dt><b>-b [filename/wildcard]</b> +</dt> +<dd>see --xhtml </dd> <dt><b>--by-*</b> </dt> -<dd>see --output-by-* -<p> </dd> +<dd>see --output-by-* </dd> <dt><b>-C</b> </dt> -<dd>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. -<p> </dd> +<dd>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. </dd> -<dt><b>-CC</b> </dt> -<dd>see --configure -<p> </dd> +<dt><b>-CC</b> +</dt> +<dd>see --configure </dd> <dt><b>-c [filename/wildcard]</b> </dt> -<dd>see --color-toggle -<p> </dd> +<dd>see --color-toggle </dd> -<dt><b>--color-toggle -[filename/wildcard]</b> </dt> -<dd>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 +<dt><b>--color</b> </dt> +<dd>see --color-on </dd> -<p>- -<p>c -<p> </dd> +<dt><b>--color-off</b> +</dt> +<dd>turn off color in output to terminal </dd> -<dt><b>--configure</b> </dt> -<dd>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. -<p> </dd> +<dt><b>--color-on</b> </dt> +<dd>turn on color in output to +terminal </dd> -<dt><b>--concordance -[filename/wildcard]</b> </dt> -<dd>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 -<p> </dd> +<dt><b>--color-toggle [filename/wildcard]</b> </dt> +<dd>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 </dd> + +<dt><b>--configure</b> </dt> +<dd>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. </dd> + +<dt><b>--concordance [filename/wildcard]</b> </dt> +<dd>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 </dd> <dt><b>-D [instruction] [filename]</b> </dt> -<dd>see --pg -<p> </dd> +<dd>see +--pg </dd> -<dt><b>-d [--db-[database type - (sqlite|pg)]] --[instruction] [filename]</b> </dt> +<dt><b>-d [--db-[database type (sqlite|pg)]] --[instruction] [filename]</b> </dt> <dd>see --sqlite -<p> </dd> - -<dt><b>--dal [filename/wildcard/url]</b> -</dt> -<dd>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. +</dd> -<p>Alias -m -<p> </dd> +<dt><b>--dal [filename/wildcard/url]</b> </dt> +<dd>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 </dd> <dt><b>--delete [filename/wildcard]</b> </dt> -<dd>see --zap -<p> </dd> +<dd>see --zap </dd> -<dt><b>--dump[=directory_path] [filename/wildcard]</b> -</dt> -<dd>places output in directory specified, if none is specified in the current -directory (pwd). Compare --redirect -<p> </dd> +<dt><b>--dump[=directory_path] +[filename/wildcard]</b> </dt> +<dd>places output in directory specified, if none is specified +in the current directory (pwd). Compare --redirect </dd> <dt><b>-e [filename/wildcard]</b> </dt> -<dd>see --epub -<p> </dd> - -<dt><b>--epub -[filename/wildcard]</b> </dt> -<dd>produces an epub document, [sisu version >=2 ] (filename.epub). +<dd>see +--epub </dd> -<p>Alias -e -<p> </dd> +<dt><b>--epub [filename/wildcard]</b> </dt> +<dd>produces an epub document, [sisu version +>=2 ] (filename.epub). Alias -e </dd> <dt><b>--exc-*</b> </dt> -<dd>exclude output feature, overrides configuration settings ---exc- <i>ocn,</i> (exclude <i>object</i> citation numbering, (switches off <i>object</i> 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-* -<p> </dd> +<dd>exclude output feature, overrides configuration +settings --exc-ocn, (exclude <i>object</i> citation numbering, (switches off <i>object</i> +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-* </dd> <dt><b>-F [--webserv=webrick]</b> </dt> -<dd>see --sample-search-form +<dd>see --sample-search-form </dd> -<p> </dd> - -<dt><b>-f [optional string part of filename]</b> </dt> -<dd>see --find -<p> </dd> +<dt><b>-f [optional string +part of filename]</b> </dt> +<dd>see --find </dd> -<dt><b>--find [optional string part - of filename]</b> </dt> -<dd>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 -<p> </dd> +<dt><b>--find [optional string part of filename]</b> </dt> +<dd>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 </dd> -<dt><b>-G [optional string part of filename]</b> </dt> -<dd>see --find -<p> </dd> - -<dt><b>-g [filename/wildcard]</b> +<dt><b>-G [optional string part of filename]</b> </dt> -<dd> -<p>see --git -<p> </dd> +<dd>see --find </dd> -<dt><b>--git [filename/wildcard]</b> </dt> -<dd>produces or updates markup source file -structure in a git repo (experimental and subject to change). Alias -g -<p> </dd> +<dt><b>-g [filename/wildcard]</b> </dt> +<dd>see --git </dd> -<dt><b>--glob -[optional string part of filename]</b> </dt> -<dd>see --find -<p> </dd> +<dt><b>--git [filename/wildcard]</b> </dt> +<dd>produces +or updates markup source file structure in a git repo (experimental and +subject to change). Alias -g </dd> -<dt><b>-h [filename/wildcard]</b> </dt> +<dt><b>--glob [optional string part of filename]</b> </dt> <dd>see +--find </dd> -<p>- -<p>- -<p>html -<p> </dd> +<dt><b>-h [filename/wildcard]</b> </dt> +<dd>see --html </dd> <dt><b>--harvest *.ss[tm]</b> </dt> -<dd>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. -<p> </dd> +<dd>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. </dd> -<dt><b>--help [topic]</b> </dt> -<dd>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. -<p> </dd> +<dt><b>--help [topic]</b> +</dt> +<dd>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. </dd> <dt><b>--html [filename/wildcard]</b> </dt> -<dd>produces html output, segmented text -with table of contents (toc.html and index.html) and the document in a single -file (scroll.html). Alias -h -<p> </dd> +<dd>produces html output, segmented +text with table of contents (toc.html and index.html) and the document in +a single file (scroll.html). Alias -h </dd> <dt><b>-I [filename/wildcard]</b> </dt> -<dd>see --texinfo -<p> </dd> +<dd>see --texinfo </dd> -<dt><b>-i [filename/wildcard]</b> -</dt> -<dd> -<p>see --manpage -<p> </dd> +<dt><b>-i +[filename/wildcard]</b> </dt> +<dd>see --manpage </dd> <dt><b>--inc-*</b> </dt> -<dd>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-* -<p> </dd> +<dd>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-* </dd> -<dt><b>-j [filename/wildcard]</b> -</dt> -<dd>copies images associated with a file for use by html, xhtml & xml outputs -(automatically invoked by --dump & redirect). -<p> </dd> +<dt><b>-j [filename/wildcard]</b> </dt> +<dd>copies images associated with a file for use +by html, xhtml & xml outputs (automatically invoked by --dump & redirect). </dd> -<dt><b>--keep-processing-files [filename/wildcard/url]</b> +<dt><b>-k</b> </dt> -<dd> -<p>see --maintenance -<p> </dd> +<dd>see --color-off </dd> + +<dt><b>--keep-processing-files [filename/wildcard/url]</b> </dt> +<dd>see --maintenance +</dd> <dt><b>-L</b> </dt> -<dd>prints license information. -<p> </dd> +<dd>prints license information. </dd> -<dt><b>-M [filename/wildcard/url]</b> -</dt> -<dd> -<p>see --maintenance -<p> </dd> +<dt><b>-M [filename/wildcard/url]</b> </dt> +<dd>see --maintenance +</dd> <dt><b>-m [filename/wildcard/url]</b> </dt> -<dd>see --dal (document abstraction -level/layer) -<p> </dd> +<dd>see --dal (document abstraction level/layer) </dd> -<dt><b>--machine [filename/wildcard/url]</b> </dt> -<dd>see --dal (document abstraction -level/layer) -<p> </dd> +<dt><b>--machine +[filename/wildcard/url]</b> </dt> +<dd>see --dal (document abstraction level/layer) </dd> -<dt><b>--maintenance [filename/wildcard/url]</b> </dt> -<dd>maintenance mode, interim -processing files are preserved and their locations indicated. (also see --V). Aliases -M and --keep-processing-files. -<p> </dd> +<dt><b>--maintenance +[filename/wildcard/url]</b> </dt> +<dd>maintenance mode, interim processing files are +preserved and their locations indicated. (also see -V). Aliases -M and --keep-processing-files. +</dd> <dt><b>--manpage [filename/wildcard]</b> </dt> -<dd>produces -man page of file, not suitable for all outputs. Alias -i -<p> </dd> - -<dt><b>-N [filename/wildcard/url]</b> -</dt> -<dd>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. -<p> </dd> - -<dt><b>-n -[filename/wildcard/url]</b> </dt> -<dd>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. -<p> </dd> +<dd>produces man page of file, not suitable for +all outputs. Alias -i </dd> + +<dt><b>-N [filename/wildcard/url]</b> </dt> +<dd>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. </dd> + +<dt><b>-n [filename/wildcard/url]</b> </dt> +<dd>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. </dd> <dt><b>--no-*</b> </dt> -<dd>see --exc-* - -<p> </dd> +<dd>see --exc-* </dd> <dt><b>-o [filename/wildcard/url]</b> </dt> <dd>see --odt -<p> </dd> +</dd> <dt><b>--odf [filename/wildcard/url]</b> </dt> -<dd>see --odt - -<p> </dd> +<dd>see --odt </dd> <dt><b>--odt [filename/wildcard/url]</b> </dt> -<dd>output basic document in opendocument file -format (opendocument.odt). Alias -o -<p> </dd> +<dd>output +basic document in opendocument file format (opendocument.odt). Alias -o </dd> -<dt><b>--output-by-*</b> </dt> -<dd>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> </dd> - -<dt><b>-P [language_directory/filename language_directory]</b> </dt> -<dd>see --po4a - -<p> </dd> - -<dt><b>-p [filename/wildcard]</b> </dt> -<dd>see --pdf -<p> </dd> +<dt><b>--output-by-*</b> +</dt> +<dd>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-* +</dd> -<dt><b>--pdf [filename/wildcard]</b> </dt> -<dd>produces <i>LaTeX</i> -pdf (portrait.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). Alias -p -<p> </dd> +<dt><b>-P [language_directory/filename language_directory]</b> </dt> +<dd>see --po4a </dd> -<dt><b>--pg [instruction] [filename]</b> +<dt><b>-p [filename/wildcard]</b> </dt> -<dd>database <i>PostgreSQL</i> ( --pgsql may be used instead) possible instructions, -include: --createdb; --create; --dropall; --import [filename]; --update [filename]; ---remove [filename]; see database section below. Alias -D -<p> </dd> +<dd>see --pdf </dd> -<dt><b>--po [language_directory/filename - language_directory]</b> </dt> +<dt><b>--pdf [filename/wildcard]</b> </dt> +<dd>produces <i>LaTeX</i> pdf (portrait.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). +Alias -p </dd> + +<dt><b>--pg [instruction] [filename]</b> </dt> +<dd>database <i>PostgreSQL</i> ( --pgsql may be +used instead) possible instructions, include: --createdb; --create; --dropall; +--import [filename]; --update [filename]; --remove [filename]; see database section +below. Alias -D </dd> + +<dt><b>--po [language_directory/filename language_directory]</b> </dt> <dd>see --po4a -<p> </dd> - -<dt><b>--po4a [language_directory/filename language_directory]</b> -</dt> -<dd>produces .pot and po files for the file in the languages specified by the -language directory. <b>SiSU</b> 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 -<p> </dd> +</dd> -<dt><b>-Q [filename/wildcard]</b> -</dt> -<dd> -<p>see --qrcode -<p> </dd> +<dt><b>--po4a [language_directory/filename language_directory]</b> </dt> +<dd>produces .pot and +po files for the file in the languages specified by the language directory. +<b>SiSU</b> 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 </dd> -<dt><b>-q [filename/wildcard]</b> </dt> -<dd>see --quiet -<p> </dd> +<dt><b>-Q [filename/wildcard]</b> </dt> +<dd>see --qrcode </dd> -<dt><b>--qrcode [filename/wildcard]</b> +<dt><b>-q [filename/wildcard]</b> </dt> -<dd>generate QR code image of metadata (used in manifest). v3 only. -<p> </dd> +<dd>see --quiet </dd> -<dt><b>--quiet [filename/wildcard]</b> -</dt> -<dd>quiet less output to screen. -<p> </dd> +<dt><b>--qrcode [filename/wildcard]</b> </dt> +<dd>generate QR code image of metadata +(used in manifest). v3 only. </dd> + +<dt><b>--quiet [filename/wildcard]</b> </dt> +<dd>quiet less output +to screen. </dd> <dt><b>-R [filename/wildcard]</b> </dt> -<dd>see --rsync -<p> </dd> +<dd>see --rsync </dd> -<dt><b>-r [filename/wildcard]</b> -</dt> -<dd> -<p>see --scp -<p> </dd> +<dt><b>-r [filename/wildcard]</b> </dt> +<dd>see --scp +</dd> <dt><b>--redirect[=directory_path] [filename/wildcard]</b> </dt> -<dd>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). Compare --dump -<p> </dd> - -<dt><b>--rsync [filename/wildcard]</b> -</dt> -<dd>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 - -<p>- -<p>R -<p> </dd> +<dd>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). Compare --dump </dd> + +<dt><b>--rsync [filename/wildcard]</b> </dt> +<dd>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 </dd> <dt><b>-S</b> </dt> <dd>see --sisupod -<p> </dd> +</dd> <dt><b>-S [filename/wildcard]</b> </dt> -<dd>see --sisupod -<p> </dd> - -<dt><b>-s [filename/wildcard]</b> -</dt> -<dd> -<p>see --source -<p> </dd> - -<dt><b>--sample-search-form [--webserv=webrick]</b> </dt> -<dd>generate examples of (naive) -cgi search form for <i>SQLite</i> and PgSQL depends on your already having used -sisu to populate an <i>SQLite</i> and/or PgSQL database, (the <i>SQLite</i> version scans -the output directories for existing sisu_sqlite databases, so it is first -necessary to create them, before generating the search form) see -d -D and -the database section below. 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 -<p> </dd> - -<dt><b>--scp [filename/wildcard]</b> +<dd>see --sisupod </dd> + +<dt><b>-s [filename/wildcard]</b> </dt> +<dd>see --source </dd> + +<dt><b>--sample-search-form +[--webserv=webrick]</b> </dt> +<dd>generate examples of (naive) cgi search form for <i>SQLite</i> +and PgSQL depends on your already having used sisu to populate an <i>SQLite</i> +and/or PgSQL database, (the <i>SQLite</i> version scans the output directories +for existing sisu_sqlite databases, so it is first necessary to create +them, before generating the search form) see -d -D and the database section +below. 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 </dd> + +<dt><b>--scp [filename/wildcard]</b> </dt> +<dd>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 </dd> + +<dt><b>--sqlite --[instruction] [filename]</b> </dt> -<dd>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 -<p> </dd> - -<dt><b>--sqlite ---[instruction] [filename]</b> </dt> -<dd>database type set to <i>SQLite,</i> this produces one -of two possible databases, without additional database related instructions -it produces a discreet <i>SQLite</i> file for the document processed; with additional -instructions it produces a common <i>SQLite</i> 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 -<p> </dd> +<dd>database type set to <i>SQLite,</i> this produces one of two possible databases, +without additional database related instructions it produces a discreet +<i>SQLite</i> file for the document processed; with additional instructions it +produces a common <i>SQLite</i> 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 </dd> <dt><b>--sisupod</b> </dt> -<dd>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<br> - option is tested only with zsh). Alias -S -<p> </dd> +<dd>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 </dd> <dt><b>--sisupod [filename/wildcard]</b> </dt> -<dd>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. <b>SiSU</b> 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 -<p> </dd> +<dd>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. <b>SiSU</b> 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 </dd> <dt><b>--source [filename/wildcard]</b> </dt> -<dd>copies sisu markup -file to output directory. Alias -s -<p> </dd> +<dd>copies sisu markup file to output directory. +Alias -s </dd> -<dt><b>-T [filename/wildcard (*.termsheet.rb)]</b> -</dt> -<dd>standard form document builder, preprocessing feature -<p> </dd> +<dt><b>-T [filename/wildcard (*.termsheet.rb)]</b> </dt> +<dd>standard form document builder, +preprocessing feature </dd> -<dt><b>-t [filename/wildcard]</b> -</dt> -<dd> -<p>see --txt -<p> </dd> - -<dt><b>--texinfo [filename/wildcard]</b> </dt> -<dd>produces texinfo and info file, (view -with pinfo). Alias -I -<p> </dd> +<dt><b>-t [filename/wildcard]</b> </dt> +<dd>see --txt </dd> -<dt><b>--txt [filename/wildcard]</b> </dt> -<dd>produces <i>plaintext</i> with Unix -linefeeds and without markup, (object numbers are omitted), has footnotes -at end of each paragraph that contains them [ -A for 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 -<p> </dd> - -<dt><b>-U [filename/wildcard]</b> </dt> -<dd>see --urls -<p> </dd> +<dt><b>--texinfo [filename/wildcard]</b> +</dt> +<dd>produces texinfo and info file, (view with pinfo). Alias -I </dd> -<dt><b>-u [filename/wildcard]</b> +<dt><b>--txt [filename/wildcard]</b> </dt> -<dd>provides url mapping of output files for the flags requested for processing, +<dd>produces <i>plaintext</i> 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 </dd> -<p>also see -U -<p> </dd> +<dt><b>-U [filename/wildcard]</b> </dt> +<dd>see --urls </dd> -<dt><b>--urls [filename/wildcard]</b> </dt> -<dd>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. +<dt><b>-u [filename/wildcard]</b> </dt> +<dd>provides url mapping +of output files for the flags requested for processing, also see -U </dd> -<p>Alias -U -<p> </dd> +<dt><b>--urls +[filename/wildcard]</b> </dt> +<dd>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 </dd> <dt><b>-V</b> </dt> -<dd>on its own, provides <b>SiSU</b> version and environment information -(sisu --help env) -<p> </dd> +<dd>on its own, +provides <b>SiSU</b> version and environment information (sisu --help env) </dd> -<dt><b>-V [filename/wildcard]</b> </dt> -<dd>even more verbose than the -v flag. - -<p> </dd> +<dt><b>-V [filename/wildcard]</b> +</dt> +<dd>even more verbose than the -v flag. </dd> <dt><b>-v</b> </dt> <dd>on its own, provides <b>SiSU</b> version information -<p> </dd> +</dd> -<dt><b>-v [filename/wildcard]</b> -</dt> -<dd> -<p>see --verbose -<p> </dd> +<dt><b>-v [filename/wildcard]</b> </dt> +<dd>see --verbose </dd> <dt><b>--v3 [filename/wildcard]</b> </dt> -<dd>invokes the sisu v3 document parser/generator. -You may run sisu3 instead. -<p> </dd> - -<dt><b>--v4 [filename/wildcard]</b> </dt> -<dd>invokes the sisu v4 document -parser/generator. This is the default and is normally omitted. -<p> </dd> +<dd>invokes the sisu +v3 document parser/generator. You may run sisu3 instead. </dd> -<dt><b>--verbose [filename/wildcard]</b> +<dt><b>--v4 [filename/wildcard]</b> </dt> -<dd>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 -<p> </dd> +<dd>invokes the sisu v4 document parser/generator. This is the default and is +normally omitted. </dd> -<dt><b>-W</b> </dt> -<dd>see --webrick +<dt><b>--verbose [filename/wildcard]</b> </dt> +<dd>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 </dd> -<p> </dd> +<dt><b>-W</b> </dt> +<dd>see --webrick </dd> -<dt><b>-w [filename/wildcard]</b> </dt> -<dd>see --concordance -<p> </dd> +<dt><b>-w [filename/wildcard]</b> +</dt> +<dd>see --concordance </dd> <dt><b>--webrick</b> </dt> -<dd>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 also, note -F webrick ]. Alias -W -<p> </dd> +<dd>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 </dd> -<dt><b>--wordmap [filename/wildcard]</b> -</dt> -<dd> -<p>see --concordance -<p> </dd> +<dt><b>--wordmap [filename/wildcard]</b> </dt> +<dd>see --concordance +</dd> <dt><b>--xhtml [filename/wildcard]</b> </dt> -<dd>produces xhtml/ <i>XML</i> output for -browser viewing (sax parsing). Alias -b -<p> </dd> +<dd>produces xhtml/ <i>XML</i> output for browser viewing +(sax parsing). Alias -b </dd> <dt><b>--xml-dom [filename/wildcard]</b> </dt> -<dd>produces -<i>XML</i> output with deep document structure, in the nature of dom. Alias -X -<p> -</dd> - -<dt><b>--xml-sax [filename/wildcard]</b> </dt> -<dd>produces <i>XML</i> output shallow structure (sax parsing). +<dd>produces <i>XML</i> output with +deep document structure, in the nature of dom. Alias -X </dd> -<p>Alias -x -<p> </dd> +<dt><b>--xml-sax [filename/wildcard]</b> +</dt> +<dd>produces <i>XML</i> output shallow structure (sax parsing). Alias -x </dd> -<dt><b>-X [filename/wildcard]</b> </dt> -<dd>see --xml-dom -<p> </dd> +<dt><b>-X [filename/wildcard]</b> +</dt> +<dd>see --xml-dom </dd> <dt><b>-x [filename/wildcard]</b> </dt> -<dd>see --xml-sax - -<p> </dd> +<dd>see --xml-sax </dd> <dt><b>-Y [filename/wildcard]</b> </dt> -<dd>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]) -<p> </dd> +<dd>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]) </dd> <dt><b>-y [filename/wildcard]</b> </dt> -<dd>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. -<p> </dd> +<dd>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. +</dd> <dt><b>-Z [filename/wildcard]</b> </dt> -<dd>see - -<p>- -<p>- -<p>zap -<p> </dd> +<dd>see --zap </dd> <dt><b>--zap [filename/wildcard]</b> </dt> -<dd>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. - -<p>Alias -Z -<p> </dd> +<dd>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 </dd> </dl> <h2><a name='sect8' href='#toc8'>Command Line Modifiers</a></h2> -<br> <p> <dl> -<dt><b>--no-</b> </dt> -<dd><i>ocn</i> [with --html --pdf or --epub] switches off <i>object</i> citation numbering. -Produce output without identifying numbers in margins of html or <i>LaTeX</i> -/pdf output. -<p> </dd> - -<dt><b>--no-annotate</b> </dt> -<dd>strips output text of editor endnotes[^*1] denoted +<dt><b>--no-ocn</b> </dt> +<dd>[with --html +--pdf or --epub] switches off <i>object</i> citation numbering. Produce output without +identifying numbers in margins of html or <i>LaTeX</i> /pdf output. </dd> -<p>by asterisk or dagger/plus sign -<p> </dd> +<dt><b>--no-annotate</b> +</dt> +<dd>strips output text of editor endnotes[^*1] denoted by asterisk or dagger/plus +sign </dd> <dt><b>--no-asterisk</b> </dt> -<dd>strips output text of editor -endnotes[^*2] denoted by asterisk sign -<p> </dd> +<dd>strips output text of editor endnotes[^*2] denoted by asterisk +sign </dd> <dt><b>--no-dagger</b> </dt> -<dd>strips output text of editor -endnotes[^+1] denoted by dagger/plus sign -<p> </dd> +<dd>strips output text of editor endnotes[^+1] denoted by dagger/plus +sign </dd> </dl> <h2><a name='sect9' href='#toc9'>Database Commands</a></h2> -<br> -<p> <br> -<b>dbi - database interface</b> -<p> <br> -<b>-D or --pgsql</b> set for <i>PostgreSQL</i> <b>-d or --sqlite</b> default set for <i>SQLite</i> -d is modifiable -with --db=[database type (PgSQL or .I SQLite ) ] -<p> +<p> <b>dbi - database interface</b> +<p> <b>-D or --pgsql</b> set for <i>PostgreSQL</i> +<b>-d or --sqlite</b> default set for <i>SQLite</i> -d is modifiable with --db=[database type +(PgSQL or <i>SQLite</i> ) ] <dl> <dt><b>--pg -v --createall</b> </dt> -<dd>initial step, -creates required relations (tables, indexes) in existing <i>PostgreSQL</i> database -(a database should be created manually and given the same name as working -directory, as requested) (rb.dbi) [ -dv --createall .I SQLite equivalent] it -may be necessary to run sisu -Dv --createdb initially NOTE: at the present -time for <i>PostgreSQL</i> it may be necessary to manually create the database. -The command would be working directory name (without path)]. Please use -only alphanumerics and underscores. -<p> </dd> - -<dt><b>--pg -v --import</b> </dt> -<dd>[filename/wildcard] imports -data specified to <i>PostgreSQL</i> db (rb.dbi) [ -dv --import .I SQLite equivalent] - -<p> </dd> +<dd>initial step, creates required relations +(tables, indexes) in existing <i>PostgreSQL</i> database (a database should be +created manually and given the same name as working directory, as requested) +(rb.dbi) [ -dv --createall <i>SQLite</i> equivalent] it may be necessary to run sisu +-Dv --createdb initially NOTE: at the present time for <i>PostgreSQL</i> it may be +necessary to manually create the database. The command would be directory +name (without path)]. Please use only alphanumerics and underscores. </dd> + +<dt><b>--pg -v +--import</b> </dt> +<dd>[filename/wildcard] imports data specified to <i>PostgreSQL</i> db (rb.dbi) +[ -dv --import <i>SQLite</i> equivalent] </dd> <dt><b>--pg -v --update</b> </dt> -<dd>[filename/wildcard] updates/imports specified data to <i>PostgreSQL</i> -db (rb.dbi) [ -dv --update .I SQLite equivalent] -<p> </dd> +<dd>[filename/wildcard] updates/imports +specified data to <i>PostgreSQL</i> db (rb.dbi) [ -dv --update <i>SQLite</i> equivalent] +</dd> <dt><b>--pg --remove</b> </dt> -<dd>[filename/wildcard] -removes specified data to <i>PostgreSQL</i> db (rb.dbi) [ -d --remove .I SQLite equivalent] - -<p> </dd> +<dd>[filename/wildcard] removes specified data to <i>PostgreSQL</i> db (rb.dbi) +[ -d --remove <i>SQLite</i> equivalent] </dd> <dt><b>--pg --dropall</b> </dt> -<dd>kills data" and drops ( <i>PostgreSQL</i> or <i>SQLite</i> ) db, tables & -indexes [ -d --dropall .I SQLite equivalent] -<p> <br> -The -v is for verbose output. -<p> </dd> +<dd>kills data" and drops ( <i>PostgreSQL</i> +or <i>SQLite</i> ) db, tables & indexes [ -d --dropall <i>SQLite</i> equivalent] +<p> The -v +is for verbose output. </dd> </dl> <h2><a name='sect10' href='#toc10'>Shortcuts, Shorthand for Multiple Flags</a></h2> -<br> <p> <dl> -<dt><b>--update [filename/wildcard]</b> </dt> -<dd>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. -<p> </dd> - -<dt><b>-0 to -5 [filename or wildcard]</b> </dt> -<dd>Default -shorthand mappings (for v3, note that the defaults can be changed/configured -in the sisurc.yml file): -<p> </dd> +<dt><b>--update [filename/wildcard]</b> +</dt> +<dd>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. </dd> + +<dt><b>-0 to -5 [filename or wildcard]</b> </dt> +<dd>Default shorthand mappings (for v3, +note that the defaults can be changed/configured in the sisurc.yml file): +</dd> <dt><b>-0</b> </dt> -<dd>-NQhewpotbxXyYv [this is the default action run - when no options are give, i.e. on ’sisu [filename]’] -<p> </dd> +<dd>-NQhewpotbxXyYv [this is the default action run when no options are give, +i.e. on ’sisu [filename]’] </dd> <dt><b>-1</b> </dt> -<dd>-Qhewpoty -<p> </dd> +<dd>-Qhewpoty </dd> <dt><b>-2</b> </dt> -<dd>-NQhewpotbxXy - -<p> </dd> +<dd>-NQhewpotbxXy </dd> <dt><b>-3</b> </dt> -<dd>-NQhewpotbxXyY -<p> </dd> +<dd>-NQhewpotbxXyY </dd> <dt><b>-4</b> </dt> -<dd>-NQhewpotbxXDyY --update -<p> </dd> +<dd>-NQhewpotbxXDyY +--update </dd> <dt><b>-5</b> </dt> <dd>-NQhewpotbxXDyYv --update -<p> <br> -add -v for verbose mode and -c to toggle color state, e.g. sisu -2vc [filename - or wildcard] -<p> <br> +<p> add -v for verbose mode and -c to toggle +color state, e.g. sisu -2vc [filename or wildcard] +<p> consider -u for appended -<p>consider -u for appended url info or -v for verbose output +<p>url info or -v for verbose output <p> </dd> </dl> -<h2><a name='sect11' href='#toc11'>Command Line -with Flags - Batch Processing</a></h2> +<h2><a name='sect11' href='#toc11'>Command Line with Flags - Batch Processing</a></h2> -<p> <br> -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. -<p> <br> -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. <p> + 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. +<p> 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. <h2><a name='sect12' href='#toc12'>Help</a></h2> -<br> <p> + <h2><a name='sect13' href='#toc13'>Sisu Manual</a></h2> -<p> <br> -The most up to date information on sisu should be contained in the sisu_manual, -available at: -<p> <br> - <<a href='http://sisudoc.org/sisu/sisu_manual/'>http://sisudoc.org/sisu/sisu_manual/</a> -><br> +<p> The most up to date information on sisu should be contained +in the sisu_manual, available at: +<p> <<a href='http://sisudoc.org/sisu/sisu_manual/'>http://sisudoc.org/sisu/sisu_manual/</a> +> -<p> <br> -The manual can be generated from source, found respectively, either within +<p> The manual can be generated from source, found respectively, either within the <b>SiSU</b> tarball or installed locally at: -<p> <br> - ./data/doc/sisu/markup-samples/sisu_manual<br> - -<p> <br> - /usr/share/doc/sisu/markup-samples/sisu_manual<br> - -<p> <br> -move to the respective directory and type e.g.: -<p> <br> - sisu sisu_manual.ssm<br> - <p> -<h2><a name='sect14' href='#toc14'>Sisu Man Pages</a></h2> +<p> /usr/share/doc/sisu/markup-samples/sisu_manual -<p> <br> -If <b>SiSU</b> is installed on your system usual man commands should be available, -try: -<p> <br> - man sisu<br> +<p> move to the respective directory and type e.g.: +<p> sisu sisu_manual.ssm +<h2><a name='sect14' href='#toc14'>Sisu +Man Pages</a></h2> -<p> <br> -Most <b>SiSU</b> 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 <b>SiSU</b> tarball at: -<p> <br> - ./data/doc/sisu/markup-samples/sisu_manual<br> +<p> If <b>SiSU</b> is installed on your system usual man commands should +be available, try: +<p> man sisu +<p> Most <b>SiSU</b> 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 <b>SiSU</b> tarball at: +<p> ./data/doc/sisu/markup-samples/sisu_manual<br> -<p> <br> -Once installed, directory equivalent to: -<p> <br> - /usr/share/doc/sisu/markup-samples/sisu_manual<br> +<p> Once installed, directory equivalent to: +<p> /usr/share/doc/sisu/markup-samples/sisu_manual<br> -<p> <br> -Available man pages are converted back to html using man2html: -<p> <br> - /usr/share/doc/sisu/html/<br> +<p> Available man pages are converted back to html using man2html: +<p> /usr/share/doc/sisu/html/<br> -<p> <br> - ./data/doc/sisu/html<br> +<p> ./data/doc/sisu/html<br> -<p> <br> -An online version of the sisu man page is available here: -<p> <br> -* various sisu man pages <<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a> +<p> An online version of the sisu man page is available here: +<p> * various +sisu man pages <<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a> > [^9] -<p> <br> -* sisu.1 <<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a> -> [^10] -<p> -<h2><a name='sect15' href='#toc15'>Sisu Built-in Interactive -Help</a></h2> - -<p> <br> -This is particularly useful for getting the current sisu setup/environment -information: -<p> <br> - sisu --help<br> - -<p> <br> - sisu --help [subject]<br> - -<p> <br> - sisu --help commands<br> - -<p> <br> - sisu --help markup<br> - -<p> <br> - sisu --help env [for feedback on the way your system is <br> - setup with regard to sisu ]<br> - -<p> <br> - sisu -V [environment information, same as above command]<br> - -<p> <br> - sisu (on its own provides version and some help information)<br> - -<p> <br> -Apart from real-time information on your current configuration the <b>SiSU</b> -manual and man pages are likely to contain more up-to-date information than -the sisu interactive help (for example on commands and markup). -<p> <br> -NOTE: Running the command 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. -<p> -<h2><a name='sect16' href='#toc16'>Introduction to Sisu Markup[^11]</a></h2> -<br> +<p> * sisu.1 <<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a> +> +[^10] +<p> +<h2><a name='sect15' href='#toc15'>Sisu Built-in Interactive Help</a></h2> + +<p> This is particularly useful for getting +the current sisu setup/environment information: +<p> sisu --help +<p> sisu --help +[subject] +<p> sisu --help commands +<p> sisu --help markup +<p> sisu --help env [for +feedback on the way your system is setup with regard to sisu ]<br> + +<p> sisu -V [environment information, same as above command] +<p> sisu (on its +own provides version and some help information) +<p> Apart from real-time information +on your current configuration the <b>SiSU</b> manual and man pages are likely +to contain more up-to-date information than the sisu interactive help (for +example on commands and markup). +<p> NOTE: Running the command 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. +<h2><a name='sect16' href='#toc16'>Introduction +to Sisu Markup[^11]</a></h2> <p> <h2><a name='sect17' href='#toc17'>Summary</a></h2> -<p> <br> -<b>SiSU</b> source documents are <i>plaintext</i> ( <i>UTF-8</i> )[^12] files -<p> <br> -All paragraphs are separated by an empty line. -<p> <br> -Markup is comprised of: -<p> <br> -* 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) -<p> <br> -* 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: -<p> <br> - * heading levels defines document structure<br> - -<p> <br> - * text basic attributes, italics, bold etc.<br> - -<p> <br> - * grouped text (objects), which are to be treated differently, such as -code<br> +<p> <b>SiSU</b> source documents are <i>plaintext</i> ( <i>UTF-8</i> +)[^12] files +<p> All paragraphs are separated by an empty line. +<p> Markup is +comprised of: +<p> * 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) +<p> * 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: +<p> * heading levels defines document +structure<br> + +<p> * text basic attributes, italics, bold etc.<br> + +<p> * grouped text (objects), which are to be treated differently, such +as code<br> blocks or poems.<br> -<p> <br> - * footnotes/endnotes<br> - -<p> <br> - * linked text and images<br> - -<p> <br> - * paragraph actions, such as indent, bulleted, numbered-lists, etc.<br> - -<p> <br> -Some interactive help on markup is available, by typing sisu and selecting - -<p>markup or sisu --help markup -<p> <br> -To check the markup in a file: -<p> <br> - sisu --identify [filename].sst<br> - -<p> <br> +<p> * footnotes/endnotes<br> -<p>For brief descriptive summary of markup history -<p> <br> - sisu --query-history<br> +<p> * linked text and images +<p> * paragraph actions, such as indent, bulleted, +numbered-lists, etc. +<p> Some interactive help on markup is available, by typing -<p> <br> -or if for a particular version: -<p> <br> - sisu --query-0.38<br> +<p>sisu and selecting markup or sisu --help markup +<p> To check the markup in +a file: +<p> sisu --identify [filename].sst +<p> For brief descriptive summary of +<p>markup history +<p> sisu --query-history +<p> or if for a particular version: <p> +sisu --query-0.38 <h2><a name='sect18' href='#toc18'>Markup Examples</a></h2> <p> <h2><a name='sect19' href='#toc19'>Online</a></h2> -<p> <br> -Online markup examples are available together with the respective outputs -produced from <<a href='http://www.jus.uio.no/sisu/SiSU/examples.html'>http://www.jus.uio.no/sisu/SiSU/examples.html</a> -> or from <<a href='http://www.jus.uio.no/sisu/sisu_examples/'>http://www.jus.uio.no/sisu/sisu_examples/</a> +<p> Online markup examples are available +together with the respective outputs produced from <<a href='http://www.jus.uio.no/sisu/SiSU/examples.html'>http://www.jus.uio.no/sisu/SiSU/examples.html</a> > - -<p> <br> -There is of course this document, which provides a cursory overview of -sisu markup and the respective output produced: <<a href='http://www.jus.uio.no/sisu/sisu_markup/'>http://www.jus.uio.no/sisu/sisu_markup/</a> +or from <<a href='http://www.jus.uio.no/sisu/sisu_examples/'>http://www.jus.uio.no/sisu/sisu_examples/</a> > - -<p> <br> -an alternative presentation of markup syntax: /usr/share/doc/sisu/on_markup.txt.gz - +<p> There is of course this +document, which provides a cursory overview of sisu markup and the respective +output produced: <<a href='http://www.jus.uio.no/sisu/sisu_markup/'>http://www.jus.uio.no/sisu/sisu_markup/</a> +> +<p> an alternative +presentation of markup syntax: /usr/share/doc/sisu/on_markup.txt.gz <p> <h2><a name='sect20' href='#toc20'>Installed</a></h2> -<p> <br> -With <b>SiSU</b> installed sample skins may be found in: /usr/share/doc/sisu/markup-samples +<p> + With <b>SiSU</b> 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: <p>/usr/share/doc/sisu/markup-samples-non-free <p> <h2><a name='sect21' href='#toc21'>Markup of Headers</a></h2> -<br> -<p> <br> -Headers contain either: semantic meta-data about a document, which can be -used by any output module of the program, or; processing instructions. <p> -<br> -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: +<p> Headers contain +either: semantic meta-data about a document, which can be used by any output +module of the program, or; processing instructions. +<p> 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: <p> <br> <pre>% this would be a comment </pre> <p> <h2><a name='sect22' href='#toc22'>Sample Header</a></h2> +<p> This current document is loaded by a master document that +has a header similar to this one: <p> <br> -This current document is loaded by a master document that has a header -similar to this one: -<p> <br> -<pre>% SiSU master 2.0 +<pre>% SiSU master 4.0 @title: SiSU -:subtitle: Manual + :subtitle: Manual @creator: -:author: Amissah, Ralph -@publisher: [publisher name] + :author: Amissah, Ralph +@publisher: [publisher name] @rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 @classify: -:type: information -:topic_register: SiSU:manual;electronic documents:SiSU:manual -:subject: ebook, epublishing, electronic book, electronic publishing, + :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 + :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 + :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 + { 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 </pre> <p> <h2><a name='sect23' href='#toc23'>Available Headers</a></h2> -<p> <br> -Header tags appear at the beginning of a document and provide meta information -on the document (such as the <i>Dublin</i> 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: +<p> Header tags appear at the beginning of a document and +provide meta information on the document (such as the <i>Dublin</i> 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 <i>Dublin</i> Core meta tags are available +<p> + <b>@indentifier:</b> information or instructions +<p> where the "identifier" is +a tag recognised by the program, and the "information" or "instructions" -<p>All <i>Dublin</i> Core meta tags are available -<p> <br> -<b>@indentifier:</b> information or instructions -<p> <br> -where the "identifier" is a tag recognised by the program, and the "information" -or "instructions" belong to the tag/indentifier specified -<p> <br> -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. -<p> <br> +<p>belong to the tag/identifier specified +<p> 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. -<p>This is a sample header +<p> This is a sample header <p> <br> -<pre>% SiSU 2.0 [declared file-type identifier with markup version] +<pre>% SiSU 2.0 [declared file-type identifier with markup version] </pre> <p> <br> -<pre>@title: [title text] [this header is the only one that is mandatory] - :subtitle: [subtitle if any] +<pre>@title: [title text] [this header is the only one that is mandatory] + :subtitle: [subtitle if any] :language: English </pre> <p> <br> <pre>@creator: -:author: [Lastname, First names] -:illustrator: [Lastname, First names] -:translator: [Lastname, First names] -:prepared_by: [Lastname, First names] + :author: [Lastname, First names] + :illustrator: [Lastname, First names] + :translator: [Lastname, First names] + :prepared_by: [Lastname, First names] </pre> <p> <br> <pre>@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] + :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] </pre> <p> <br> <pre>@rights: -:copyright: Copyright (C) [Year and Holder] -:license: [Use License granted] -:text: [Year and Holder] -:translation: [Name, Year] -:illustrations: [Name, Year] + :copyright: Copyright (C) [Year and Holder] + :license: [Use License granted] + :text: [Year and Holder] + :translation: [Name, Year] + :illustrations: [Name, Year] </pre> <p> <br> <pre>@classify: -:topic_register: SiSU:markup sample:book;book:novel:fantasy -:type: -:subject: -:description: -:keywords: -:abstract: -:loc: [Library of Congress classification] -:dewey: Dewey classification + :topic_register: SiSU:markup sample:book;book:novel:fantasy + :type: + :subject: + :description: + :keywords: + :abstract: + :loc: [Library of Congress classification] + :dewey: [Dewey classification </pre> <p> <br> <pre>@identify: -:isbn: [ISBN] -:oclc: + :isbn: [ISBN] + :oclc: </pre> <p> <br> <pre>@links: { SiSU }http://www.sisudoc.org @@ -1288,62 +1082,58 @@ structure, and can be useful to know. </pre> <p> <br> <pre>@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 + :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 </pre> <p> <br> <pre>@original: -:language: [language] + :language: [language] </pre> <p> <br> <pre>@notes: -:comment: -:prefix: [prefix is placed just after table of contents] + :comment: + :prefix: [prefix is placed just after table of contents] </pre> <p> <h2><a name='sect24' href='#toc24'>Markup of Substantive Text</a></h2> -<br> <p> <h2><a name='sect25' href='#toc25'>Heading Levels</a></h2> -<p> <br> -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) -<p> <br> -<b>:A~ [heading text]</b> 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 -<p> <br> -<b>:B~ [heading text]</b> Second level heading [this is a heading level divider] - -<p> <br> -<b>:C~ [heading text]</b> Third level heading [this is a heading level divider] - -<p> <br> -<b>1~ [heading text]</b> 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 - -<p> <br> -<b>2~ [heading text]</b> 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. -<p> <br> -<b>3~ [heading text]</b> 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 - +<p> 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) +<p> <b>:A~ [heading +text]</b> Top level heading [this usually has similar content to the title +@title: ] NOTE: the heading levels described here are in 0.38 notation, + +<p>see heading +<p> <b>:B~ [heading text]</b> Second level heading [this is a heading +level divider] +<p> <b>:C~ [heading text]</b> Third level heading [this is a heading +level divider] +<p> <b>1~ [heading text]</b> 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 + +<p> <b>2~ [heading text]</b> 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. +<p> <b>3~ [heading text]</b> 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 <p> <br> <pre>1~filename level 1 heading, % the primary division such as Chapter that is followed by substantive @@ -1353,15 +1143,14 @@ html segments are made) <p> <h2><a name='sect26' href='#toc26'>Font Attributes</a></h2> -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>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] +*{emphasis}* [note: can be configured to be represented by bold, italics +or underscore] !{bold text}! /{italics}/ _{underscore}_ @@ -1372,86 +1161,58 @@ _{underscore}_ -{strikethrough}- #{monospace}# </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -normal text, <b>emphasis,</b> <b>bold text</b> , <i>italics,</i> <i>underscore,</i> "citation", ^superscript^, -[subscript], ++inserted text++, --strikethrough--, monospace -<p> <br> - -<p>normal text -<p> <br> -<b>emphasis</b> [note: can be configured to be represented by bold, italics italics - or underscore] or underscore] -<p> <br> +<p> <b>resulting output:</b> +<p> normal text, <b>emphasis,</b> <b>bold text</b> , <i>italics,</i> <i>underscore,</i> +"citation", ^superscript^, [subscript], ++inserted text++, --strikethrough--, -<p><b>bold text</b> -<p> <br> +<p>monospace +<p> normal text +<p> <b>emphasis</b> [note: can be configured to be represented +by bold, italics or underscore] +<p> <b>bold text</b> +<p> <i>italics</i> +<p> <i>underscore</i> +<p> "citation" -<p><i>italics</i> -<p> <br> +<p> ^superscript^ +<p> [subscript] +<p> ++inserted text++ +<p> --strikethrough-- +<p> monospace -<p><i>underscore</i> -<p> <br> -"citation" -<p> <br> -^superscript^ -<p> <br> -[subscript] -<p> <br> -++inserted text++ -<p> <br> ---strikethrough-- -<p> <br> - -<p>monospace <p> <h2><a name='sect27' href='#toc27'>Indentation and Bullets</a></h2> -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>ordinary paragraph _1 indent paragraph one step _2 indent paragraph two steps _9 indent paragraph nine steps </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> +<p> <b>resulting output:</b> +<p> ordinary paragraph +<p> indent paragraph one step<br> -<p>ordinary paragraph -<p> <br> - indent paragraph one step<br> +<p> indent paragraph two steps<br> -<p> <br> - indent paragraph two steps<br> +<p> indent paragraph nine steps<br> -<p> <br> - indent paragraph nine steps<br> - -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>_* bullet text _1* bullet text, first indent _2* bullet text, two step indent </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -* bullet text -<p> <br> - * bullet text, first indent<br> +<p> <b>resulting output:</b> +<p> * bullet text +<p> * bullet text, first indent<br> -<p> <br> - * bullet text, two step indent<br> +<p> * bullet text, two step indent<br> -<p> <br> -Numbered List (not to be confused with headings/titles, (document structure)) +<p> Numbered List (not to be confused with headings/titles, (document structure)) -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre># numbered list numbered list 1., 2., 3, etc. _# numbered list numbered list indented a., b., c., d., etc. @@ -1459,8 +1220,7 @@ _# numbered list numbered list indented a., b., c., d., etc. <p> <h2><a name='sect28' href='#toc28'>Hanging Indents</a></h2> -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>_0_1 first line no indent, rest of paragraph indented one step @@ -1468,125 +1228,127 @@ _1_0 first line indented, rest of paragraph no indent in each case level may be 0-9 </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> - first line no indent, rest of paragraph indented one step<br> - -<p> <br> +<p> <b>resulting output:</b> +<p> 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<br> + paragraph indented one step; first line no indent, rest of paragraph +indented<br> + one step; first line no indent, rest of paragraph indented one step; +first<br> + line no indent, rest of paragraph indented one step; first line no indent,<br> + rest of paragraph indented one step; first line no indent, rest of paragraph<br> + indented one step; first line no indent, rest of paragraph indented +one step;<br> + +<p> A regular paragraph. +<p> 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 -<p> <br> +<p> in each case level may + +<p>be 0-9 +<p> <b>live-build</b> A collection of scripts used to build customized Debian<br> + Livesystems.<br> + .I live-build<br> + was formerly known as live-helper, and even earlier known as live-package.<br> + +<p> <b>live-build</b> +<p> A collection of scripts used to build customized Debian<br> + Livesystems. live-build was formerly known as live-helper, and even earlier<br> + known as live-package.<br> -<p>in each case level may be 0-9 -<p> <h2><a name='sect29' href='#toc29'>Footnotes / Endnotes</a></h2> -<p> <br> -Footnotes and endnotes are marked up at the location where they would be -indicated within a text. They are automatically numbered. The output type +<p> Footnotes and endnotes are marked up at the location +where they would be indicated within a text. They are automatically numbered. -<p>determines whether footnotes or endnotes will be produced -<p> <br> -<b>markup example:</b> +<p>The output type determines whether footnotes or endnotes will be produced + +<p> <b>markup example:</b> <p> <br> <pre>~{ a footnote or endnote }~ </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -[^13] -<p> <br> -<b>markup example:</b> +<p> <b>resulting output:</b> +<p> [^13] +<p> <b>markup example:</b> <p> <br> <pre>normal text~{ self contained endnote marker & endnote in one }~ continues </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -normal text[^14] continues -<p> <br> -<b>markup example:</b> +<p> <b>resulting output:</b> +<p> normal text[^14] continues +<p> <b>markup example:</b> <p> <br> <pre>normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks if required }~ continues normal text ~{** another unnumbered asterisk footnote/endnote }~ continues </pre> +<p> <b>resulting output:</b> +<p> normal text [^*] continues +<p> normal text [^**] continues + +<p> <b>markup example:</b> <p> <br> -<b>resulting output:</b> -<p> <br> -normal text [^*] continues -<p> <br> -normal text [^**] continues -<p> <br> -<b>markup example:</b> -<p> <br> -<pre>normal text ~[* editors notes, numbered asterisk footnote/endnote series - ]~ continues -normal text ~[+ editors notes, numbered asterisk footnote/endnote series - ]~ continues +<pre>normal text ~[* editors notes, numbered asterisk footnote/endnote series +]~ continues +normal text ~[+ editors notes, numbered asterisk footnote/endnote series +]~ continues </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -normal text [^*3] continues -<p> <br> -normal text [^+2] continues -<p> <br> -<b>Alternative endnote pair notation for footnotes/endnotes:</b> +<p> <b>resulting output:</b> +<p> normal text [^*3] continues +<p> normal text [^+2] continues + +<p> <b>Alternative endnote pair notation for footnotes/endnotes:</b> <p> <br> <pre>% note the endnote marker "~^" normal text~^ continues ^~ endnote text following the paragraph in which the marker occurs </pre> -<p> <br> - -<p>the standard and pair notation cannot be mixed in the same document +<p> the standard and pair notation cannot be mixed in the same document <p> + <h2><a name='sect30' href='#toc30'>Links</a></h2> <p> - <h2><a name='sect31' href='#toc31'>Naked Urls Within Text, Dealing with Urls</a></h2> -<p> <br> -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). -<p> <br> -<b>markup example:</b> +<p> 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). +<p> <b>markup example:</b> <p> <br> <pre>normal text http://www.sisudoc.org/ continues </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -normal text <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> <b>resulting output:</b> +<p> normal text <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > continues -<p> <br> +<p> An -<p>An escaped url without decoration -<p> <br> -<b>markup example:</b> +<p>escaped url without decoration +<p> <b>markup example:</b> <p> <br> <pre>normal text _http://www.sisudoc.org/ continues deb _http://www.jus.uio.no/sisu/archive unstable main non-free </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -normal text <_<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> <b>resulting output:</b> +<p> normal text <_<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > continues -<p> <br> -deb <_<a href='http://www.jus.uio.no/sisu/archive'>http://www.jus.uio.no/sisu/archive</a> +<p> deb +<_<a href='http://www.jus.uio.no/sisu/archive'>http://www.jus.uio.no/sisu/archive</a> > unstable main non-free -<p> <br> -where a code block is used there is neither decoration nor hyperlinking, +<p> where a code block +is used there is neither decoration nor hyperlinking, code blocks are discussed -<p>code blocks are discussed later in this document -<p> <br> -<b>resulting output:</b> +<p>later in this document +<p> <b>resulting output:</b> <p> <br> <pre>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 @@ -1594,63 +1356,50 @@ deb-src http://www.jus.uio.no/sisu/archive unstable main non-free <p> <h2><a name='sect32' href='#toc32'>Linking Text</a></h2> -<p> <br> +<p> To link text or an image to a url the markup is as follows -<p>To link text or an image to a url the markup is as follows -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>about { SiSU }http://url.org markup </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -aboutSiSU <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> <b>resulting output:</b> +<p> aboutSiSU <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > markup -<p> <br> +<p> A shortcut -<p>A shortcut notation is available so the url link may also be provided automatically +<p>notation is available so the url link may also be provided automatically <p>as a footnote -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>about {~^ SiSU }http://url.org markup </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -aboutSiSU <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> <b>resulting output:</b> +<p> aboutSiSU <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > [^15] markup -<p> <br> -Internal document links to a tagged location, including an <i>ocn</i> -<p> <br> -<b>markup example:</b> +<p> Internal +document links to a tagged location, including an ocn +<p> <b>markup example:</b> + <p> <br> <pre>about { text links }#link_text </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -about ⌠text links⌡⌈link_text⌋ -<p> <br> +<p> <b>resulting output:</b> +<p> about ⌠text links⌡⌈link_text⌋ +<p> Shared document -<p>Shared document collection link -<p> <br> -<b>markup example:</b> +<p>collection link +<p> <b>markup example:</b> <p> <br> <pre>about { SiSU book markup examples }:SiSU/examples.html </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -about ⌠ <b>SiSU</b> book markup examples⌡⌈:SiSU/examples.html⌋ +<p> <b>resulting output:</b> +<p> about ⌠ <b>SiSU</b> book markup examples⌡⌈:SiSU/examples.html⌋ + <p> -<h2><a name='sect33' href='#toc33'>Linking -Images</a></h2> +<h2><a name='sect33' href='#toc33'>Linking Images</a></h2> -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>{ tux.png 64x80 }image % various url linked images @@ -1659,48 +1408,41 @@ Images</a></h2> and Ruby" }http://www.sisudoc.org/ {~^ ruby_logo.png "Ruby" }http://www.ruby-lang.org/en/ </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -[ tux.png ] -<p> <br> -tux.png 64x80 "Gnu/Linux - a better way" <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> <b>resulting output:</b> +<p> [ tux.png ] +<p> tux.png 64x80 "Gnu/Linux - a better way" +<<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > -<p> <br> -GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian -and Ruby" <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +<p> GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better +- with Gnu/Linux, Debian and Ruby" <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > -<p> <br> -ruby_logo.png 70x90 "Ruby" <<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a> +<p> ruby_logo.png +70x90 "Ruby" <<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a> > [^16] -<p> <br> +<p> <b>linked url footnote shortcut</b> -<p><b>linked url footnote shortcut</b> <p> <br> -<pre>{~^ [text to link] }http://url.org -% maps to: { [text to link] }http://url.org ~{ http://url.org }~ +<pre>{~^ [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 </pre> <p> <br> <pre>text marker *~name </pre> -<p> <br> -note at a heading level the same is automatically achieved by providing +<p> 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. -<p> -<h2><a name='sect34' href='#toc34'>Link Shortcut for -Multiple Versions of a Sisu Document in the Same Directory</a></h2> +<h2><a name='sect34' href='#toc34'>Link Shortcut for Multiple +Versions of a Sisu Document in the Same Directory</a></h2> TREE -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> + <p> <br> <pre>!_ /{"Viral Spiral"}/, David Bollier { "Viral Spiral", David Bollier [3sS]}viral_spiral.david_bollier.sst </pre> -<p> <br> -<b></b> <i>Viral Spiral</i>, David Bollier +<p> <b></b> <i>Viral Spiral</i>, David Bollier <p> "Viral Spiral", David Bollier <<a href='http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html'>http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html</a> > document manifest <<a href='http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html'>http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html</a> @@ -1738,11 +1480,9 @@ TREE <p> <h2><a name='sect36' href='#toc36'>Tables</a></h2> -<p> <br> +<p> Tables may be prepared in two either of two forms -<p>Tables may be prepared in two either of two forms -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>table{ c3; 40; 30; 30; This is a table @@ -1753,19 +1493,16 @@ column two of row two column three of row two, and so on }table </pre> -<p> <br> -<b>resulting output:</b> -<p> 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』 -<p> <br> +<p> <b>resulting output:</b> +<p> 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』 +<p> a second form may -<p>a second form may be easier to work with in cases where there is not much +<p>be easier to work with in cases where there is not much information in -<p>information in each column -<p> <br> -<b>markup example:</b> [^18] -<p> <br> +<p>each column +<p> <b>markup example:</b> [^17] <br> <pre>!_ 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 @@ -1782,31 +1519,26 @@ No. of articles, all languages | 25| 19,000| 138,000| 490,000| 862,0 * Contributed at least ten times; ** at least 5 times in last month; *** more than 100 times in last month. </pre> -<p> <br> -<b>resulting output:</b> -<p> <br> -<b>Table 3.1: Contributors to Wikipedia, January 2001 - June 2005</b> -<p> |Jan. 2001|Jan. -2002|Jan. 2003|Jan. 2004|July 2004|June 2006』Contributors*|10|472|2,188|9,653|25,011|48,721』Active +<p> <b>resulting output:</b> +<p> <b>Table 3.1: Contributors to Wikipedia, January 2001 +- June 2005</b> |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』 -<p> <br> -* Contributed at least ten times; ** at least 5 times in last month; *** -more than 100 times in last month. +<p> * Contributed +at least ten times; ** at least 5 times in last month; *** more than 100 +times in last month. <p> <h2><a name='sect37' href='#toc37'>Poem</a></h2> -<p> <br> -<b>basic markup:</b> +<p> <b>basic markup:</b> <p> <br> <pre>poem{ Your poem here }poem Each verse in a poem is given an object number. </pre> -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>poem{ ‘Fury said to a @@ -1855,8 +1587,7 @@ Each verse in a poem is given an object number. death."’ }poem </pre> -<p> <br> -<b>resulting output:</b> +<p> <b>resulting output:</b> <p> ‘Fury said to a<br> mouse, That he<br> met in the<br> @@ -1905,16 +1636,14 @@ Each verse in a poem is given an object number. <p> <h2><a name='sect38' href='#toc38'>Group</a></h2> -<p> <br> -<b>basic markup:</b> +<p> <b>basic markup:</b> <p> <br> <pre>group{ Your grouped text here }group A group is treated as an object and given a single object number. </pre> -<p> <br> -<b>markup example:</b> +<p> <b>markup example:</b> <p> <br> <pre>group{ ‘Fury said to a @@ -1963,8 +1692,7 @@ A group is treated as an object and given a single object number. death."’ }group </pre> -<p> <br> -<b>resulting output:</b> +<p> <b>resulting output:</b> <p> ‘Fury said to a<br> mouse, That he<br> met in the<br> @@ -2013,18 +1741,16 @@ A group is treated as an object and given a single object number. <p> <h2><a name='sect39' href='#toc39'>Code</a></h2> -<p> <br> -Code tags code{ ... }code (used as with other group tags described above) -are used to escape regular sisu markup, and have been used extensively +<p> 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 <b>SiSU</b> markup. You cannot however use code tags to escape code tags. They are however used in the same way as group or poem tags. -<p> <br> -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] - -<p> <br> -<b>use of code tags instead of poem compared, resulting output:</b> +<p> 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] +<p> <b>use of code tags instead of poem compared, resulting +output:</b> <p> <br> <pre> ‘Fury said to a mouse, That he @@ -2071,8 +1797,7 @@ option to number each line of code may to death."’ </pre> -<p> <br> -From <b>SiSU</b> 2.7.7 on you can number codeblocks by placing a hash after the +<p> From <b>SiSU</b> 2.7.7 on you can number codeblocks by placing a hash after the opening code tag code{# as demonstrated here: <p> <br> <pre>1 | ‘Fury said to a @@ -2127,8 +1852,7 @@ opening code tag code{# as demonstrated here: <h2><a name='sect41' href='#toc41'>Line-breaks</a></h2> <p> -<br> -To break a line within a "paragraph object", two backslashes \\ with a space + To break a line within a "paragraph object", two backslashes \\ with a space before and a space or newline after them may be used. <p> <br> <pre>To break a line within a "paragraph object", @@ -2136,30 +1860,26 @@ two backslashes \\ with a space before and a space or newline after them \\ may be used. </pre> -<p> <br> -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). +<p> 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). <p> <h2><a name='sect42' href='#toc42'>Page Breaks</a></h2> -<p> <br> -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: -<p> <br> -page new =\= or breaks the page, starts a new page. -<p> <br> -page break -\- or breaks a column, starts a new column, if using columns, -else breaks the page, starts a new page. +<p> 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: +<p> page new =\= +or breaks the page, starts a new page. +<p> page break -\- or breaks a column, +starts a new column, if using columns, else breaks the page, starts a new +page. <p> <br> <pre>-\\- or <:pb> </pre> -<p> <br> - -<p>or +<p> or <p> <br> <pre>=\\= or @@ -2168,50 +1888,43 @@ or <p> <h2><a name='sect43' href='#toc43'>Book Index</a></h2> -<p> <br> -To make an index append to paragraph the book index term relates to it, -using an equal sign and curly braces. -<p> <br> -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. -<p> <br> +<p> To make an index append to paragraph the book index term relates +to it, using an equal sign and curly braces. +<p> 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. <br> <pre> Paragraph containing main term and sub-term. ={Main term:sub-term} </pre> -<p> <br> -The index syntax starts on a new line, but there should not be an empty +<p> The index syntax starts on a new line, but there should not be an empty line between paragraph and index markup. -<p> <br> -The structure of the resulting index would be: +<p> The structure of the resulting +index would be: <p> <br> <pre> Main term, 1 sub-term, 1 </pre> -<p> <br> -Several terms may relate to a paragraph, they are separated by a semicolon. +<p> 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. <p> <br> <pre> Paragraph containing main term, second term and sub-term. ={first term; second term: sub-term} </pre> -<p> <br> -The structure of the resulting index would be: +<p> The structure of the resulting index would be: <p> <br> <pre> First term, 1, Second term, 1, sub-term, 1 </pre> -<p> <br> -If multiple sub-terms appear under one paragraph, they are separated under +<p> If multiple sub-terms appear under one paragraph, they are separated under the main term heading from each other by a pipe symbol. <p> <br> <pre> 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 </pre> -<p> <br> -The plus one in the example provided indicates the first sub-term spans +<p> 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: <p> <br> @@ -2221,97 +1934,88 @@ be: </pre> <p> <h2><a name='sect44' href='#toc44'>Composite Documents Markup</a></h2> -<br> -<p> <br> -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 <b>.ssm</b> 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 <b>.sst</b> regular markup -file, or <b>.ssi</b> (insert/information) A secondary file of the composite document - -<p>is built prior to processing with the same prefix and the suffix <b>._sst</b> -<p> -<br> +<p> 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 <b>.ssm</b> 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 <b>.sst</b> regular markup file, or <b>.ssi</b> (insert/information) + +<p>A secondary file of the composite document is built prior to processing + +<p>with the same prefix and the suffix <b>._sst</b> +<p> basic markup for importing a -<p>basic markup for importing a document into a master document +<p>document into a master document <p> <br> <pre><< filename1.sst << filename2.ssi </pre> -<p> <br> -The form described above should be relied on. Within the <i>Vim</i> editor it results -in the text thus linked becoming hyperlinked to the document it is calling -in which is convenient for editing. +<p> The form described above should be relied on. Within the <i>Vim</i> editor it +results in the text thus linked becoming hyperlinked to the document it +is calling in which is convenient for editing. <p> <h2><a name='sect45' href='#toc45'>Sisu Filetypes</a></h2> -<br> -<p> <br> -<b>SiSU</b> has <i>plaintext</i> and binary filetypes, and can process either type of -document. +<p> <b>SiSU</b> has +<i>plaintext</i> and binary filetypes, and can process either type of document. + <p> <h2><a name='sect46' href='#toc46'>.sst .ssm .ssi Marked Up Plain Text</a></h2> <p> <dl> -<dt><b>SiSU¤b〕 documents are prepared -as plain-text (utf-8) files with</b> </dt> -<dd><b>SiSU</b> markup. They may make reference to and -contain images (for example), which are stored in the directory beneath -them _sisu/image. 〔b¤SiSU <i>plaintext</i> 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.<br> - -<p> <br> -<b>SiSU</b> 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. -<p> <br> -<b>SiSU</b> source markup can be shared with the command: -<p> <br> - sisu -s [filename]<br> - +<dt><b>SiSU</b> </dt> +<dd>documents are prepared as plain-text +(utf-8) files with <b>SiSU</b> markup. They may make reference to and contain images +(for example), which are stored in the directory beneath them _sisu/image. +〔b¤SiSU <i>plaintext</i> 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. +<p> <b>SiSU</b> 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. +<p> <b>SiSU</b> source markup can be shared +with the command: +<p> sisu -s [filename] <p> </dd> </dl> <h2><a name='sect47' href='#toc47'>Sisu Text - Regular Files (.sst)</a></h2> -<p> <br> +<p> The most common form of document in <b>SiSU,</b> see the section on <b>SiSU</b> markup. <p> <h2><a name='sect48' href='#toc48'>Sisu Master Files (.ssm)</a></h2> -<p> <br> -Composite documents which incorporate other <b>SiSU</b> documents which may be -either regular <b>SiSU</b> text .sst which may be generated independently, or inserts -prepared solely for the purpose of being incorporated into one or more -master documents. -<p> <br> -The mechanism by which master files incorporate other documents is described -as one of the headings under under <b>SiSU</b> markup in the <b>SiSU</b> manual. -<p> <br> -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. -<p> <br> -Note: a secondary file of the composite document is built prior to processing -with the same prefix and the suffix ._sst [^19] +<p> Composite documents which incorporate other <b>SiSU</b> +documents which may be either regular <b>SiSU</b> text .sst which may be generated +independently, or inserts prepared solely for the purpose of being incorporated +into one or more master documents. +<p> The mechanism by which master files +incorporate other documents is described as one of the headings under under +<b>SiSU</b> markup in the <b>SiSU</b> manual. +<p> 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. +<p> Note: +a secondary file of the composite document is built prior to processing +with the same prefix and the suffix ._sst [^18] <p> <h2><a name='sect49' href='#toc49'>Sisu Insert Files (.ssi)</a></h2> <p> -<br> -Inserts are documents prepared solely for the purpose of being incorporated + Inserts are documents prepared solely for the purpose of being incorporated into one or more master documents. They resemble regular <b>SiSU</b> text files except they are ignored by the <b>SiSU</b> processor. Making a file a .ssi file is a quick and convenient way of flagging that it is not intended that @@ -2320,170 +2024,134 @@ the file should be processed on its own. <h2><a name='sect50' href='#toc50'>Sisupod, Zipped Binary Container (sisupod.zip, .ssp)</a></h2> -<p> <br> -A sisupod is a zipped <b>SiSU</b> text file or set of <b>SiSU</b> text files and any -associated images that they contain (this will be extended to include sound -and multimedia-files) +<p> A sisupod is a zipped <b>SiSU</b> text file or set of <b>SiSU</b> +text files and any associated images that they contain (this will be extended +to include sound and multimedia-files) <p> <dl> <dt><b>SiSU</b> </dt> -<dd><i>plaintext</i> 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 +<dd><i>plaintext</i> 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. -<p> <br> -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 <b>SiSU</b> documents. -<p> <br> -The command to create a sisupod is: -<p> <br> - sisu -S [filename]<br> - -<p> <br> -Alternatively, make a pod of the contents of a whole directory: -<p> <br> - sisu -S<br> - -<p> <br> -<b>SiSU</b> processing can be done directly against a sisupod; which may be located -locally or on a remote server for which a url is provided. -<p> <br> -<<a href='http://www.sisudoc.org/sisu/sisu_commands'>http://www.sisudoc.org/sisu/sisu_commands</a> +<p> 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 <b>SiSU</b> documents. + +<p> The command to create a sisupod is: +<p> sisu -S [filename] +<p> Alternatively, +make a pod of the contents of a whole directory: +<p> sisu -S +<p> <b>SiSU</b> processing +can be done directly against a sisupod; which may be located locally or +on a remote server for which a url is provided. +<p> <<a href='http://www.sisudoc.org/sisu/sisu_commands'>http://www.sisudoc.org/sisu/sisu_commands</a> > -<p> <br> -<<a href='http://www.sisudoc.org/sisu/sisu_manual'>http://www.sisudoc.org/sisu/sisu_manual</a> + +<p> <<a href='http://www.sisudoc.org/sisu/sisu_manual'>http://www.sisudoc.org/sisu/sisu_manual</a> > <p> </dd> </dl> <h2><a name='sect51' href='#toc51'>Configuration</a></h2> -<br> <p> <h2><a name='sect52' href='#toc52'>Configuration Files</a></h2> <p> + <h2><a name='sect53' href='#toc53'>Config.yml</a></h2> -<p> <br> -<b>SiSU</b> 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. -<p> <br> -The <b>SiSU</b> configuration file is a yaml file, which means indentation is -significant. -<p> <br> -<b>SiSU</b> resource configuration is determined by looking at the following files -if they exist: -<p> <br> - ./_sisu/v4/sisurc.yml<br> +<p> <b>SiSU</b> 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. +<p> The <b>SiSU</b> configuration file is +a yaml file, which means indentation is significant. +<p> <b>SiSU</b> resource configuration +is determined by looking at the following files if they exist: +<p> ./_sisu/v4/sisurc.yml<br> -<p> <br> - ./_sisu/sisurc.yml<br> +<p> ./_sisu/sisurc.yml<br> -<p> <br> - ~/.sisu/v4/sisurc.yml<br> +<p> ~/.sisu/v4/sisurc.yml<br> -<p> <br> - ~/.sisu/sisurc.yml<br> +<p> ~/.sisu/sisurc.yml<br> -<p> <br> - /etc/sisu/v4/sisurc.yml<br> +<p> /etc/sisu/v4/sisurc.yml<br> -<p> <br> - /etc/sisu/sisurc.yml<br> +<p> /etc/sisu/sisurc.yml<br> -<p> <br> -The search is in the order listed, and the first one found is used. -<p> <br> -In the absence of instructions in any of these it falls back to the internal +<p> The search is in the order listed, and the first one found is used. +<p> + In the absence of instructions in any of these it falls back to the internal program defaults. -<p> <br> -Configuration determines the output and processing directories and the -database access details. -<p> <br> - -<p>If <b>SiSU</b> is installed a sample sisurc.yml may be found in /etc/sisu/sisurc.yml +<p> Configuration determines the output and processing directories +and the database access details. +<p> If <b>SiSU</b> is installed a sample sisurc.yml +<p>may be found in /etc/sisu/sisurc.yml <p> <h2><a name='sect54' href='#toc54'>Sisu_document_make</a></h2> -<p> <br> -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. +<p> 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. +<p> The search order +is as for resource configuration: +<p> ./_sisu/v4/sisu_document_make<br> -<p> <br> -The search order is as for resource configuration: -<p> <br> - ./_sisu/v4/sisu_document_make<br> +<p> ./_sisu/sisu_document_make<br> -<p> <br> - ./_sisu/sisu_document_make<br> +<p> ~/.sisu/v4/sisu_document_make<br> -<p> <br> - ~/.sisu/v4/sisu_document_make<br> +<p> ~/.sisu/sisu_document_make<br> -<p> <br> - ~/.sisu/sisu_document_make<br> +<p> /etc/sisu/v4/sisu_document_make<br> -<p> <br> - /etc/sisu/v4/sisu_document_make<br> +<p> /etc/sisu/sisu_document_make<br> -<p> <br> - /etc/sisu/sisu_document_make<br> - -<p> <br> -A sample sisu_document_make can be found in the _sisu/ directory under +<p> A sample sisu_document_make can be found in the _sisu/ directory under along with the provided sisu markup samples. <p> <h2><a name='sect55' href='#toc55'>Css - Cascading Style Sheets (for Html, Xhtml and Xml)</a></h2> -<br> - -<p> <br> -CSS files to modify the appearance of <b>SiSU</b> html, <i>XHTML</i> or <i>XML</i> 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. -<p> <br> -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. -<p> <br> -<i>HTML:</i> html. css -<p> <br> -<i>XML</i> DOM: dom.css -<p> <br> -<i>XML</i> SAX: sax.css -<p> <br> -<i>XHTML:</i> xhtml. css -<p> <br> -The default homepage may use homepage.css or html. css -<p> <br> -Under consideration is to permit the placement of a CSS file with a different -name in directory _sisu/css directory or equivalent.[^20] -<p> -<h2><a name='sect56' href='#toc56'>Organising Content -- Directory Structure and Mapping</a></h2> -<br> -<p> <br> -<b>SiSU</b> v3 has new options for the source directory tree, and output directory +<p> CSS files to modify the appearance of <b>SiSU</b> html, +<i>XHTML</i> or <i>XML</i> 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. +<p> 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. +<p> <i>HTML:</i> html. css +<p> <i>XML</i> +DOM: dom.css +<p> <i>XML</i> SAX: sax.css +<p> <i>XHTML:</i> xhtml. css +<p> The default homepage +may use homepage.css or html. css +<p> Under consideration is to permit the +placement of a CSS file with a different name in directory _sisu/css directory +or equivalent.[^19] +<p> +<h2><a name='sect56' href='#toc56'>Organising Content - Directory Structure and Mapping</a></h2> + +<p> + <b>SiSU</b> v3 has new options for the source directory tree, and output directory structures of which there are 3 alternatives. <p> <h2><a name='sect57' href='#toc57'>Document Source Directory</a></h2> <p> -<br> -The document source directory is the directory in which sisu processing + 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/, @@ -2512,35 +2180,34 @@ is limited to langagues supported by XeTeX polyglosia. <p> <h2><a name='sect60' href='#toc60'>Output Directory Root</a></h2> -<p> <br> -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 +<p> 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) -<p> <br> -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. +<p> 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. <p> <h2><a name='sect61' href='#toc61'>Alternative Output Structures</a></h2> -<p> <br> -There are 3 possibile output structures described as being, by language, +<p> + There are 3 possibile output structures described as being, by language, by filetype or by filename, the selection is made in sisurc.yml <p> <br> <pre>#% output_dir_structure_by: language; filetype; or filename @@ -2552,18 +2219,15 @@ v2) <p> <h2><a name='sect62' href='#toc62'>by Language</a></h2> -<p> <br> - -<p>The by language directory structure places output files -<p> <br> -The by language directory structure separates output files by language +<p> The by language directory structure places output files +<p> + The by language directory structure separates output files by language code (all files of a given language), and within the language directory by filetype. -<p> <br> +<p> Its selection is configured in sisurc.yml +<p> output_dir_structure_by: -<p>Its selection is configured in sisurc.yml -<p> <br> -output_dir_structure_by: language +<p>language <p> <br> <pre> |-- en |-- epub @@ -2592,20 +2256,18 @@ output_dir_structure_by: language |-- rng ‘-- xsd </pre> -<p> <br> -#by: language subject_dir/en/manifest/filename.html +<p> #by: language subject_dir/en/manifest/filename.html <p> <h2><a name='sect63' href='#toc63'>by Filetype</a></h2> -<p> <br> -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. -<p> <br> +<p> 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. +<p> Its selection is configured in sisurc.yml +<p> output_dir_structure_by: -<p>Its selection is configured in sisurc.yml -<p> <br> -output_dir_structure_by: filetype +<p>filetype <p> <br> <pre> |-- epub |-- hashes @@ -2633,19 +2295,17 @@ output_dir_structure_by: filetype |-- xhtml ‘-- xml </pre> -<p> <br> -#by: filetype subject_dir/html/filename/manifest.en.html +<p> #by: filetype subject_dir/html/filename/manifest.en.html <p> <h2><a name='sect64' href='#toc64'>by Filename</a></h2> -<p> <br> +<p> The by filename directory structure places most output of a particular file (the different filetypes) in a common directory. -<p> <br> +<p> Its selection is -<p>Its selection is configured in sisurc.yml -<p> <br> -output_dir_structure_by: filename +<p>configured in sisurc.yml +<p> output_dir_structure_by: filename <p> <br> <pre> |-- epub |-- po4a @@ -2666,13 +2326,14 @@ output_dir_structure_by: filename |-- pod ‘-- viral_spiral.david_bollier </pre> -<p> <br> -#by: filename subject_dir/filename/manifest.en.html +<p> #by: filename subject_dir/filename/manifest.en.html <p> <h2><a name='sect65' href='#toc65'>Remote Directories</a></h2> -<p> <br> -<pre>% containing sub_directories named after the generated files from which +<p> +<br> +<pre> ./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 @@ -2689,7 +2350,8 @@ they are made <h2><a name='sect66' href='#toc66'>Sisupod</a></h2> <p> <br> -<pre>% files stored at this level e.g. sisu_manual.sst +<pre> ./sisupod/ +% files stored at this level e.g. sisu_manual.sst ./sisupod/_sisu % configuration file e.g. sisurc.yml ./sisupod/_sisu/skin @@ -2704,60 +2366,52 @@ they are made <p> <h2><a name='sect68' href='#toc68'>Homepages</a></h2> -<br> -<p> <br> -<b>SiSU</b> is about the ability to auto-generate documents. Home pages are regarded -as custom built items, and are not created by <b>SiSU.</b> More accurately, <b>SiSU</b> -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: -<p> <br> -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) -<p> <br> -2. through providing what you want as the home page in a skin, -<p> <br> -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. -<p> -<h2><a name='sect69' href='#toc69'>Home Page and Other -Custom Built Pages in a Sub-directory</a></h2> - -<p> <br> -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: -<p> <br> - sisu -CC<br> - -<p> +<p> <b>SiSU</b> is about the ability to auto-generate +documents. Home pages are regarded as custom built items, and are not created +by <b>SiSU.</b> More accurately, <b>SiSU</b> 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: +<p> 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) +<p> 2. through providing what you want as the +home page in a skin, +<p> 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. +<p> +<h2><a name='sect69' href='#toc69'>Home +Page and Other Custom Built Pages in a Sub-directory</a></h2> + +<p> 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: +<p> + sisu -CC <h2><a name='sect70' href='#toc70'>Markup and Output Examples</a></h2> -<br> <p> <h2><a name='sect71' href='#toc71'>Markup Examples</a></h2> -<p> <br> -Current markup examples and document output samples are provided off <<a href='http://sisudoc.org'>http://sisudoc.org</a> +<p> Current markup examples +and document output samples are provided off <<a href='http://sisudoc.org'>http://sisudoc.org</a> +> or <<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> > -or <<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> -> and in the sisu -markup-sample package available -off <<a href='http://sources.sisudoc.org'>http://sources.sisudoc.org</a> +and in the sisu -markup-sample package available off <<a href='http://sources.sisudoc.org'>http://sources.sisudoc.org</a> > -<p> <br> -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. + +<p> 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. <p> <h2><a name='sect72' href='#toc72'>Sisu Markup Samples</a></h2> -<p> <br> -A few additional sample books prepared as sisu markup samples, output formats +<p> A few +additional sample books prepared as sisu markup samples, output formats to be generated using <b>SiSU</b> 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 @@ -2766,320 +2420,284 @@ requirements that do not meet the <b>Debian</b> Free Software Guidelines for var reasons, most commonly that they require that the original substantive text remain unchanged, and sometimes that the works be used only non-commercially. -<p> <br> -<i>Accelerando,</i> Charles Stross (2005) accelerando.charles_stross.sst -<p> <br> -<i>Alice’s</i> Adventures in Wonderland, Lewis Carroll (1865) alices_adventures_in_wonderland.lewis_carroll.sst +<p> <i>Accelerando,</i> Charles Stross (2005) accelerando.charles_stross.sst +<p> <i>Alice’s</i> +Adventures in Wonderland, Lewis Carroll (1865) alices_adventures_in_wonderland.lewis_carroll.sst -<p> <br> -<i>CONTENT,</i> Cory Doctorow (2008) content.cory_doctorow.sst -<p> <br> -<i>Democratizing</i> Innovation, Eric von Hippel (2005) democratizing_innovation.eric_von_hippel.sst +<p> <i>CONTENT,</i> Cory Doctorow (2008) content.cory_doctorow.sst +<p> <i>Democratizing</i> +Innovation, Eric von Hippel (2005) democratizing_innovation.eric_von_hippel.sst -<p> <br> -<i>Down</i> and Out in the Magic Kingdom, Cory Doctorow (2003) down_and_out_in_the_magic_kingdom.cory_doctorow.sst +<p> <i>Down</i> and Out in the Magic Kingdom, Cory Doctorow (2003) down_and_out_in_the_magic_kingdom.cory_doctorow.sst -<p> <br> -<i>For</i> the Win, Cory Doctorow (2010) for_the_win.cory_doctorow.sst -<p> <br> -<i>Free</i> as in Freedom - Richard Stallman’s Crusade for Free Software, Sam Williams +<p> <i>For</i> the Win, Cory Doctorow (2010) for_the_win.cory_doctorow.sst +<p> <i>Free</i> +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 -<p> <br> -<i>Free</i> as in Freedom 2.0 - Richard Stallman and the Free Software Revolution, +<p> <i>Free</i> 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 -<p> <br> -<i>Free</i> Culture - How Big Media Uses Technology and the Law to Lock Down Culture -and Control Creativity, Lawrence Lessig (2004) free_culture.lawrence_lessig.sst +<p> <i>Free</i> Culture - How Big Media Uses Technology and the Law to Lock Down +Culture and Control Creativity, Lawrence Lessig (2004) free_culture.lawrence_lessig.sst -<p> <br> -<i>Free</i> For All - How Linux and the Free Software Movement Undercut the High +<p> <i>Free</i> For All - How Linux and the Free Software Movement Undercut the High Tech Titans, Peter Wayner (2002) free_for_all.peter_wayner.sst -<p> <br> -<i>GNU</i> GENERAL PUBLIC LICENSE v2, Free Software Foundation (1991) gpl2.fsf.sst +<p> <i>GNU</i> GENERAL +PUBLIC LICENSE v2, Free Software Foundation (1991) gpl2.fsf.sst +<p> <i>GNU</i> GENERAL +PUBLIC LICENSE v3, Free Software Foundation (2007) gpl3.fsf.sst +<p> <i>Gulliver’s</i> +Travels, Jonathan Swift (1726 / 1735) gullivers_travels.jonathan_swift.sst -<p> <br> -<i>GNU</i> GENERAL PUBLIC LICENSE v3, Free Software Foundation (2007) gpl3.fsf.sst +<p> <i>Little</i> Brother, Cory Doctorow (2008) little_brother.cory_doctorow.sst +<p> + <i>The</i> Cathederal and the Bazaar, Eric Raymond (2000) the_cathedral_and_the_bazaar.eric_s_raymond.sst -<p> <br> -<i>Gulliver’s</i> Travels, Jonathan Swift (1726 / 1735) gullivers_travels.jonathan_swift.sst - -<p> <br> -<i>Little</i> Brother, Cory Doctorow (2008) little_brother.cory_doctorow.sst -<p> <br> -<i>The</i> Cathederal and the Bazaar, Eric Raymond (2000) the_cathedral_and_the_bazaar.eric_s_raymond.sst - -<p> <br> -<i>The</i> Public Domain - Enclosing the Commons of the Mind, James Boyle (2008) +<p> <i>The</i> Public Domain - Enclosing the Commons of the Mind, James Boyle (2008) <p>the_public_domain.james_boyle.sst -<p> <br> -<i>The</i> Wealth of Networks - How Social Production Transforms Markets and Freedom, -Yochai Benkler (2006) the_wealth_of_networks.yochai_benkler.sst -<p> <br> -<i>Through</i> the Looking Glass, Lewis Carroll (1871) through_the_looking_glass.lewis_carroll.sst +<p> <i>The</i> Wealth of Networks - How Social Production +Transforms Markets and Freedom, Yochai Benkler (2006) the_wealth_of_networks.yochai_benkler.sst -<p> <br> -<i>Two</i> Bits - The Cultural Significance of Free Software, Christopher Kelty +<p> <i>Through</i> the Looking Glass, Lewis Carroll (1871) through_the_looking_glass.lewis_carroll.sst + +<p> <i>Two</i> Bits - The Cultural Significance of Free Software, Christopher Kelty (2008) two_bits.christopher_kelty.sst -<p> <br> -<i>UN</i> Contracts for International Sale of Goods, UN (1980) un_contracts_international_sale_of_goods_convention_1980.sst +<p> <i>UN</i> Contracts for International Sale +of Goods, UN (1980) un_contracts_international_sale_of_goods_convention_1980.sst -<p> <br> -<i>Viral</i> Spiral, David Bollier (2008) viral_spiral.david_bollier.sst +<p> <i>Viral</i> Spiral, David Bollier (2008) viral_spiral.david_bollier.sst <p> -<h2><a name='sect73' href='#toc73'>Sisu Search -- Introduction</a></h2> -<br> +<h2><a name='sect73' href='#toc73'>Sisu +Search - Introduction</a></h2> -<p> <br> -<b>SiSU</b> output can easily and conveniently be indexed by a number of standalone -indexing tools, such as Lucene, Hyperestraier. -<p> <br> -Because the document structure of sites created is clearly defined, and +<p> <b>SiSU</b> output can easily and conveniently be indexed +by a number of standalone indexing tools, such as Lucene, Hyperestraier. + +<p> Because the document structure of sites created is clearly defined, and the text <i>object</i> 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. -<p> <br> -In addition to this <b>SiSU</b> 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. +<p> In addition to this <b>SiSU</b> 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. <p> <h2><a name='sect74' href='#toc74'>Sql</a></h2> -<br> <p> <h2><a name='sect75' href='#toc75'>Populating Sql Type Databases</a></h2> -<p> <br> -<b>SiSU</b> feeds sisu markupd documents into sql type databases <i>PostgreSQL</i> [^21] -and/or <i>SQLite</i> [^22] database together with information related to document -structure. -<p> <br> -This is one of the more interesting output forms, as all the structural +<p> <b>SiSU</b> feeds +sisu markupd documents into sql type databases <i>PostgreSQL</i> [^20] and/or <i>SQLite</i> +[^21] database together with information related to document structure. +<p> + 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: -<p> <br> - * one containing semantic (and other) headers, including, title, author,<br> - subject, (the<br> +<p> * one containing semantic (and other) headers, +including, title, author, subject, (the<br> .I Dublin Core.<br> ..);<br> -<p> <br> - * another the substantive texts by individual "paragraph" (or object) --<br> - along with structural information, each paragraph being identifiable +<p> * another the substantive texts by individual "paragraph" (or object) +- along with structural information, each paragraph being identifiable by its<br> paragraph number (if it has one which almost all of them do), and the<br> substantive text of each paragraph quite naturally being searchable (both in<br> formatted and clean text versions for searching); and<br> -<p> <br> - * a third containing endnotes cross-referenced back to the paragraph from<br> - which they are referenced (both in formatted and clean text versions +<p> * a third containing endnotes cross-referenced back to the paragraph +from which they are referenced (both in formatted and clean text versions for<br> searching).<br> -<p> <br> - * a fourth table with a one to one relation with the headers table contains<br> - full text versions of output, eg. pdf, html, xml, and<br> +<p> * a fourth table with a one to one relation with the headers table contains + full text versions of output, eg. pdf, html, xml, and<br> .I ascii.<br> -<p> <br> -There is of course the possibility to add further structures. -<p> <br> -At this level <b>SiSU</b> 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 +<p> There is of course the possibility to add further structures. +<p> At this +level <b>SiSU</b> 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. -<p> <br> -Being able to search a relational database at an object level with the -<b>SiSU</b> citation system is an effective way of locating content generated -by <b>SiSU.</b> 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 <i>Dublin</i> Core is incorporated it is easy to make -use of that as well). +<p> Being able to search a relational +database at an object level with the <b>SiSU</b> citation system is an effective +way of locating content generated by <b>SiSU.</b> 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 +<i>Dublin</i> Core is incorporated it is easy to make use of that as well). <p> <h2><a name='sect76' href='#toc76'>Postgresql</a></h2> -<br> <p> -<h2><a name='sect77' href='#toc77'>Name</a></h2> -<p> <br> -<b>SiSU</b> - Structured information, Serialized Units - a document publishing system, +<h2><a name='sect77' href='#toc77'>Name</a></h2> -<p>postgresql dependency package +<p> <b>SiSU</b> - Structured information, Serialized Units - a document publishing +system, postgresql dependency package <p> <h2><a name='sect78' href='#toc78'>Description</a></h2> -<p> <br> -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 <b>SiSU</b> to populate a postgresql database, this being part of <b>SiSU</b> - man -sisu) . +<p> 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 <b>SiSU</b> +to populate a postgresql database, this being part of <b>SiSU</b> - man sisu) . + <p> <h2><a name='sect79' href='#toc79'>Synopsis</a></h2> -<p> <br> - sisu -D [instruction] [filename/wildcard if required]<br> - -<p> <br> - sisu -D --pg --[instruction] [filename/wildcard if required]<br> - +<p> sisu -D [instruction] [filename/wildcard if required] +<p> sisu +-D --pg --[instruction] [filename/wildcard if required] <p> <h2><a name='sect80' href='#toc80'>Commands</a></h2> -<p> <br> -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, +<p> 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 -<p>alternatively --sqlite or --pgsql may be used -<p> <br> -<b>-D or --pgsql</b> may be used interchangeably. +<p>- +<p>- +<p>sqlite or --pgsql may be used +<p> <b>-D or --pgsql</b> may be used interchangeably. <p> -<h2><a name='sect81' href='#toc81'>Create and Destroy Database</a></h2> +<h2><a name='sect81' href='#toc81'>Create +and Destroy Database</a></h2> <p> <dl> -<dt><b>--pgsql ---createall</b> </dt> -<dd>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) +<dt><b>--pgsql --createall</b> </dt> +<dd>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) <p> </dd> -<dt><b>sisu -D ---createdb</b> </dt> +<dt><b>sisu -D --createdb</b> </dt> <dd>creates database where no database existed before + <p> </dd> -<dt><b>sisu -D --create</b> -</dt> -<dd> -<p>creates database tables where no database tables existed before +<dt><b>sisu -D --create</b> </dt> +<dd>creates database tables where no database tables existed + +<p>before <p> </dd> -<dt><b>sisu -D ---Dropall</b> </dt> -<dd>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). +<dt><b>sisu -D --Dropall</b> </dt> +<dd>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). <p> </dd> <dt><b>sisu -D --recreate</b> </dt> -<dd>destroys existing database and builds +<dd>destroys existing database -<p>a new empty database structure +<p>and builds a new empty database structure <p> </dd> </dl> <h2><a name='sect82' href='#toc82'>Import and Remove Documents</a></h2> <p> -<dl> -<dt><b>sisu -D --import --v [filename/wildcard]</b> </dt> -<dd>populates database with the contents of the file. -Imports documents(s) specified to a postgresql database (at an object level). +<dl> +<dt><b>sisu -D --import -v [filename/wildcard]</b> </dt> +<dd>populates database with the contents +of the file. Imports documents(s) specified to a postgresql database (at +an object level). <p> </dd> <dt><b>sisu -D --update -v [filename/wildcard]</b> </dt> -<dd>updates file contents in database +<dd>updates file contents +<p>in database <p> </dd> <dt><b>sisu -D --remove -v [filename/wildcard]</b> </dt> -<dd>removes specified document from postgresql -database. +<dd>removes specified document +from postgresql database. <p> </dd> </dl> <h2><a name='sect83' href='#toc83'>Sqlite</a></h2> -<br> <p> <h2><a name='sect84' href='#toc84'>Name</a></h2> -<p> <br> -<b>SiSU</b> - Structured information, Serialized Units - a document publishing system. - +<p> <b>SiSU</b> - Structured information, Serialized +Units - a document publishing system. <p> <h2><a name='sect85' href='#toc85'>Description</a></h2> -<p> <br> -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 <b>SiSU</b> to populate an sqlite database, this being part of <b>SiSU</b> - man sisu) -. +<p> 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 <b>SiSU</b> to populate +an sqlite database, this being part of <b>SiSU</b> - man sisu) . <p> <h2><a name='sect86' href='#toc86'>Synopsis</a></h2> -<p> <br> - sisu -d [instruction] [filename/wildcard if required]<br> - -<p> <br> - sisu -d --(sqlite|pg) --[instruction] [filename/wildcard if <br> - required]<br> - +<p> sisu +-d [instruction] [filename/wildcard if required] +<p> sisu -d --(sqlite|pg) --[instruction] +[filename/wildcard if required] <p> <h2><a name='sect87' href='#toc87'>Commands</a></h2> -<p> <br> -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, +<p> 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 -<p>alternatively --sqlite or --pgsql may be used -<p> <br> -<b>-d or --sqlite</b> may be used interchangeably. +<p>may be used +<p> <b>-d or --sqlite</b> may be used interchangeably. <p> -<h2><a name='sect88' href='#toc88'>Create and Destroy Database</a></h2> +<h2><a name='sect88' href='#toc88'>Create and Destroy +Database</a></h2> <p> <dl> -<dt><b>--sqlite ---createall</b> </dt> -<dd>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) +<dt><b>--sqlite --createall</b> </dt> +<dd>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) <p> </dd> -<dt><b>sisu -d --createdb</b> -</dt> -<dd> -<p>creates database where no database existed before +<dt><b>sisu +-d --createdb</b> </dt> +<dd>creates database where no database existed before <p> </dd> -<dt><b>sisu -d --create</b> </dt> -<dd>creates - -<p>database tables where no database tables existed before +<dt><b>sisu -d --create</b> +</dt> +<dd> +<p>creates database tables where no database tables existed before <p> </dd> -<dt><b>sisu -d --dropall</b> -</dt> -<dd>destroys database (including all its content)! kills data and drops tables, -indexes and database associated with a given directory (and directories +<dt><b>sisu -d +--dropall</b> </dt> +<dd>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). <p> </dd> @@ -3114,43 +2732,38 @@ database. </dl> <h2><a name='sect90' href='#toc90'>Introduction</a></h2> -<br> <p> -<h2><a name='sect91' href='#toc91'>Search - Database Frontend Sample, Utilising Database and Sisu Features,</a></h2> -INCLUDING -OBJECT CITATION NUMBERING (BACKEND CURRENTLY POSTGRESQL) -<p> <br> -Sample search frontend <<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a> -> [^23] A small database and -sample query front-end (search from) that makes use of the citation system, -<i>object</i> citation numbering to demonstrates functionality.[^24] -<p> <br> -<b>SiSU</b> can provide information on which documents are matched and at what +<h2><a name='sect91' href='#toc91'>Search - Database Frontend Sample, Utilising Database +and Sisu Features,</a></h2> +INCLUDING OBJECT CITATION NUMBERING (BACKEND CURRENTLY +POSTGRESQL) +<p> Sample search frontend <<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a> +> [^22] A small +database and sample query front-end (search from) that makes use of the +citation system, .I object citation numbering to demonstrates functionality.[^23] + +<p> <b>SiSU</b> 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 <i>object</i> citation numbering, which includes html, <i>XML,</i> <i>EPUB,</i> <i>LaTeX,</i> <i>PDF</i> and indeed the <i>SQL</i> database. You can then refer to one of the other outputs or in the <i>SQL</i> database expand the text within the matched objects (paragraphs) in the documents matched. -<p> <br> -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] +<p> 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.[^24] <p> <dl> <dt><b>sisu -F --webserv-webrick</b> </dt> -<dd>builds a cgi web - -<p>search frontend for the database created -<p> <br> -The following is feedback on the setup on a machine provided by the help -command: -<p> <br> - sisu --help sql<br> +<dd>builds a cgi web search -<p> <br> +<p>frontend for the database created +<p> The following is feedback on the setup +on a machine provided by the help command: +<p> sisu --help sql <br> <pre>Postgresql user: ralph current db set: SiSU_sisu @@ -3160,156 +2773,138 @@ sqlite current db set: /home/ralph/sisu_www/sisu/sisu_sqlite.db dbi connect DBI:SQLite:/home/ralph/sisu_www/sisu/sisu_sqlite.db </pre> -<p> <br> - -<p>Note on databases built -<p> <br> -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 -<p> </dd> +<p> Note on databases built +<p> 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] </dd> </dl> -<h2><a name='sect92' href='#toc92'>Search -Form</a></h2> +<h2><a name='sect92' href='#toc92'>Search Form</a></h2> <p> <dl> <dt><b>sisu -F</b> </dt> -<dd>generates a sample search form, which must be copied to the +<dd>generates a sample search form, which -<p>web-server cgi directory +<p>must be copied to the web-server cgi directory <p> </dd> <dt><b>sisu -F --webserv-webrick</b> </dt> -<dd>generates a sample search -form for use with the webrick server, which must be copied to the web-server +<dd>generates +a sample search form for use with the webrick server, which must be copied -<p>cgi directory +<p>to the web-server cgi directory <p> </dd> <dt><b>sisu -W</b> </dt> -<dd>starts the webrick server which should be available +<dd>starts the webrick server which -<p>wherever sisu is properly installed -<p> <br> +<p>should be available wherever sisu is properly installed +<p> The generated -<p>The generated search form must be copied manually to the webserver directory +<p>search form must be copied manually to the webserver directory as instructed -<p>as instructed <p> </dd> </dl> <h2><a name='sect93' href='#toc93'>Sisu_webrick</a></h2> -<br> <p> <h2><a name='sect94' href='#toc94'>Name</a></h2> -<p> <br> -<b>SiSU</b> - Structured information, Serialized Units - a document publishing system +<p> <b>SiSU</b> - Structured information, Serialized Units - a document +<p>publishing system <p> <h2><a name='sect95' href='#toc95'>Synopsis</a></h2> -<p> <br> -sisu_webrick [port] -<p> <br> - -<p>or -<p> <br> -sisu -W [port] +<p> sisu_webrick [port] +<p> or +<p> sisu -W [port] <p> + <h2><a name='sect96' href='#toc96'>Description</a></h2> -<p> <br> -sisu_webrick is part of <b>SiSU</b> (man sisu) sisu_webrick starts <b>Ruby</b> <b>SiSU</b> -output is written, providing a list of these directories (assuming <b>SiSU</b> -is in use and they exist). -<p> <br> -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). +<p> sisu_webrick is part of <b>SiSU</b> (man sisu) sisu_webrick starts +<b>Ruby</b> <b>SiSU</b> output is written, providing a list of these directories (assuming +<b>SiSU</b> is in use and they exist). +<p> 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). <p> <h2><a name='sect97' href='#toc97'>Summary of Man Page</a></h2> -<p> <br> -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] -<p> <br> - -<p>where no port is given and settings are unchanged the default port is 8081 +<p> 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] +<p> where no port is given and settings are unchanged +<p>the default port is 8081 <p> <h2><a name='sect98' href='#toc98'>Document Processing Command Flags</a></h2> -<p> <br> -sisu -W [port] starts <b>Ruby</b> Webrick web-server, serving <b>SiSU</b> output directories, -on the port provided, or if no port is provided and the defaults have not +<p> sisu -W [port] +starts <b>Ruby</b> Webrick web-server, serving <b>SiSU</b> output directories, on the +port provided, or if no port is provided and the defaults have not been -<p>been changed in ~/.sisu/sisurc.yaml then on port 8081 +<p>changed in ~/.sisu/sisurc.yaml then on port 8081 <p> <h2><a name='sect99' href='#toc99'>Summary of Features</a></h2> -<br> -<p> <br> -* sparse/minimal markup (clean utf-8 source texts). Documents are prepared +<p> * +sparse/minimal markup (clean utf-8 source texts). Documents are prepared in a single <i>UTF-8</i> file using a minimalistic mnemonic syntax. Typical literature, documents like "War and Peace" require almost no markup, and most of the headers are optional. -<p> <br> -* markup is easily readable/parsable by the human eye, (basic markup is -simpler and more sparse than the most basic <i>HTML</i> ) , [this may also be - converted to .I XML representations of the same input/source document]. -<p> -<br> -* 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. <b>SiSU</b> 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) -<p> <br> -* 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: -<p> <br> -* <i>HTML</i> - both as a single scrollable text and a segmented document -<p> <br> -* <i>XHTML</i> -<p> <br> -* <i>EPUB</i> -<p> <br> -* <i>XML</i> - both in sax and dom style xml structures for further development - -<p>as required -<p> <br> -* <i>ODT</i> - Open Document Format text, the iso standard for document storage - -<p> <br> -* <i>LaTeX</i> - used to generate pdf -<p> <br> -* <i>PDF</i> (via <i>LaTeX</i> ) -<p> <br> -* <i>SQL</i> - population of an sql database ( <i>PostgreSQL</i> or <i>SQLite</i> ) , (at the -same object level that is used to cite text within a document) -<p> <br> -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 <i>LaTeX,</i> databases populated with documents at an individual object/paragraph -level, making possible <i>granular</i> search (and related possibilities)) -<p> <br> -* ensuring content can be cited in a meaningful way regardless of selected +<p> * markup is easily readable/parsable by the human +eye, (basic markup is simpler and more sparse than the most basic <i>HTML</i> +) , [this may also be converted to <i>XML</i> representations of the same input/source +document]. +<p> * 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. <b>SiSU</b> 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) +<p> * 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: +<p> * <i>HTML</i> - both as a single scrollable + +<p>text and a segmented document +<p> * <i>XHTML</i> +<p> * <i>EPUB</i> +<p> * <i>XML</i> - both in sax and + +<p>dom style xml structures for further development as required +<p> * <i>ODT</i> - Open +Document Format text, the iso standard for document storage +<p> * <i>LaTeX</i> - + +<p>used to generate pdf +<p> * <i>PDF</i> (via <i>LaTeX</i> ) +<p> * <i>SQL</i> - population of an sql +database ( <i>PostgreSQL</i> or <i>SQLite</i> ) , (at the same object level that is used +to cite text within a document) +<p> 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 <i>LaTeX,</i> databases populated with documents at an individual +object/paragraph level, making possible <i>granular</i> search (and related possibilities)) + +<p> * 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 @@ -3319,229 +2914,178 @@ 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, <i>HTML,</i> <i>EPUB,</i> xml, sqlite, postgresql) , this numbering system can be used to reference content. -<p> <br> -* Granular search within documents. <i>SQL</i> 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 -<p> <br> -* 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 -<p> <br> -* <i>SQL</i> search aside, documents are generated as required and static once -generated. -<p> <br> -* 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) -<p> <br> -* document source ( <i>plaintext</i> utf-8) if shared on the net may be used as - -<p>input and processed locally to produce the different document outputs -<p> -<br> -* document source may be bundled together (automatically) with associated +<p> * Granular search within +documents. <i>SQL</i> 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]. +<p> * 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, + +<p>without modification of existing prepared texts +<p> * <i>SQL</i> search aside, documents +are generated as required and static once generated. +<p> * 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) + +<p> * document source ( <i>plaintext</i> utf-8) if shared on the net may be used + +<p>as input and processed locally to produce the different document outputs + +<p> * 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 <p>these too may be processed locally to produce the desired document outputs -<p> <br> -* generated document outputs may automatically be posted to remote sites. +<p> * generated document outputs may automatically be posted to remote sites. -<p> <br> -* for basic document generation, the only software dependency is <b>Ruby,</b> +<p> * for basic document generation, the only software dependency is <b>Ruby,</b> and a few standard Unix tools (this covers <i>plaintext,</i> <i>HTML,</i> <i>EPUB,</i> <i>XML,</i> <i>ODF,</i> <i>LaTeX</i> ) . To use a database you of course need that, and to convert the <i>LaTeX</i> generated to pdf, a latex processor like tetex or texlive. -<p> <br> -* as a developers tool it is flexible and extensible -<p> <br> -Syntax highlighting for <b>SiSU</b> markup is available for a number of text editors. - -<p> <br> -<b>SiSU</b> 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 -<p> <br> -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) ... -<p> <br> -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. +<p> * + +<p>as a developers tool it is flexible and extensible +<p> Syntax highlighting +for <b>SiSU</b> markup is available for a number of text editors. +<p> <b>SiSU</b> 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 +<p> 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) ... +<p> 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. <p> <ol> -<b>.</b><li>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. -<p> <br> -</li><b>.</b><li>i.e. the -<p> <br> -<i>HTML,</i> -<p> <br> -<i>PDF,</i> -<p> <br> -<i>EPUB,</i> -<p> <br> - -<p><i>ODT</i> -<p> <br> -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. -<p> <br> -</li><b>.</b><li> -<p>the different heading levels -<p> <br> -</li><b>.</b><li>units of text, primarily paragraphs and headings, also any tables, poems, - -<p>code-blocks -<p> <br> -</li><b>.</b><li> -<p>An open standard format for e-books -<p> <br> -</li><b>.</b><li>Open Document Format ( -<p> <br> - -<p><i>ODF</i> -<p> <br> -) text -<p> <br> -</li><b>.</b><li> -<p>Specification submitted by Adobe to ISO to become a full open ISO specification - -<p> <br> -<<a href='http://www.linux-watch.com/news/NS7542722606.html'>http://www.linux-watch.com/news/NS7542722606.html</a> +<b>.</b><li>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. +<p> </li><b>.</b><li>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. +<p> </li><b>.</b><li>the different + +<p>heading levels +<p> </li><b>.</b><li>units of text, primarily paragraphs and headings, also +any tables, poems, code-blocks +<p> </li><b>.</b><li>An open standard format for e-books +<p> </li><b>.</b><li>Open +Document Format ( ODF ) text +<p> </li><b>.</b><li>Specification submitted by Adobe to ISO +to become a full open ISO specification <<a href='http://www.linux-watch.com/news/NS7542722606.html'>http://www.linux-watch.com/news/NS7542722606.html</a> > -<p> <br> -</li><b>.</b><li> -<p>ISO standard ISO/IEC 26300:2006 -<p> <br> -</dd> + +<p> </li><b>.</b><li>ISO standard ISO/IEC 26300:2006 +<p> </dd> <dt><b>*1.</b> </dt> <dd>square brackets -<p> <br> -</dd> +<p> </dd> <dt><b>*2.</b> </dt> <dd>square brackets -<p> <br> -</dd> + +<p> </dd> <dt><b>+1.</b> </dt> <dd>square brackets -<p> <br> -</li><b>.</b><li><<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a> +<p> </li><b>.</b><li><<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a> > -<p> <br> -</li><b>.</b><li><<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a> +<p> </li><b>.</b><li><<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a> > -<p> <br> -</li><b>.</b><li>From sometime after SiSU 0.58 it should be possible to describe SiSU markup + +<p> </li><b>.</b><li>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. -<p> <br> -</li><b>.</b><li> -<p>files should be prepared using -<p> <br> +<p> </li><b>.</b><li>files -<p><i>UTF-8</i> -<p> <br> +<p>should be prepared using UTF-8 character encoding +<p> </li><b>.</b><li>a footnote or endnote -<p>character encoding -<p> <br> -</li><b>.</b><li> -<p>a footnote or endnote -<p> <br> -</li><b>.</b><li>self contained endnote marker & endnote in one -<p> <br> -</dd> +<p> </li><b>.</b><li>self contained endnote marker & endnote in one +<p> </dd> <dt><b>*.</b> </dt> -<dd>unnumbered asterisk footnote/endnote, insert multiple asterisks if required - -<p> <br> -</dd> +<dd>unnumbered asterisk +footnote/endnote, insert multiple asterisks if required +<p> </dd> <dt><b>**.</b> </dt> -<dd>another unnumbered asterisk footnote/endnote -<p> <br> -</dd> +<dd>another unnumbered + +<p>asterisk footnote/endnote +<p> </dd> <dt><b>*3.</b> </dt> -<dd>editors notes, numbered asterisk footnote/endnote series -<p> <br> -</dd> +<dd>editors notes, numbered asterisk footnote/endnote + +<p>series +<p> </dd> <dt><b>+2.</b> </dt> <dd>editors notes, numbered asterisk footnote/endnote series -<p> <br> +<p> </li><b>.</b><li><<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> > -<p> <br> -</li><b>.</b><li><<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a> +<p> </li><b>.</b><li><<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a> > -<p> <br> -</li><b>.</b><li> -<p>Table from the Wealth of Networks by Yochai Benkler -<p> <br> -<<a href='http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler'>http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler</a> +<p> </li><b>.</b><li>Table from the Wealth +of Networks by Yochai Benkler <<a href='http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler'>http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler</a> > -<p> <br> -</li><b>.</b><li>.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 + +<p> </li><b>.</b><li>.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. -<p> <br> -</li><b>.</b><li><<a href='http://www.postgresql.org/'>http://www.postgresql.org/</a> -> -<p> <br> -<<a href='http://advocacy.postgresql.org/'>http://advocacy.postgresql.org/</a> +<p> </li><b>.</b><li>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. +<p> </li><b>.</b><li><<a href='http://www.postgresql.org/'>http://www.postgresql.org/</a> +> <<a href='http://advocacy.postgresql.org/'>http://advocacy.postgresql.org/</a> > -<p> <br> <<a href='http://en.wikipedia.org/wiki/Postgresql'>http://en.wikipedia.org/wiki/Postgresql</a> > -<p> <br> -</li><b>.</b><li><<a href='http://www.hwaci.com/sw/sqlite/'>http://www.hwaci.com/sw/sqlite/</a> -> -<p> <br> -<<a href='http://en.wikipedia.org/wiki/Sqlite'>http://en.wikipedia.org/wiki/Sqlite</a> +<p> </li><b>.</b><li><<a href='http://www.hwaci.com/sw/sqlite/'>http://www.hwaci.com/sw/sqlite/</a> +> <<a href='http://en.wikipedia.org/wiki/Sqlite'>http://en.wikipedia.org/wiki/Sqlite</a> > -<p> <br> -</li><b>.</b><li><<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a> + +<p> </li><b>.</b><li><<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a> > -<p> <br> -</li><b>.</b><li>(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. -<p> <br> -</li><b>.</b><li>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. -<p> <br> +<p> </li><b>.</b><li>(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. +<p> </li><b>.</b><li>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. +<p> <p> </li> </ol> diff --git a/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_markup.sst b/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_markup.sst index e3fbb226..3af84ad9 100644 --- a/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_markup.sst +++ b/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_markup.sst @@ -119,37 +119,37 @@ code{ % SiSU master 2.0 @title: SiSU - :subtitle: Manual + :subtitle: Manual @creator: - :author: Amissah, Ralph + :author: Amissah, Ralph @publisher: [publisher name] @rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 @classify: - :type: information - :topic_register: SiSU:manual;electronic documents:SiSU:manual - :subject: ebook, epublishing, electronic book, electronic publishing, + :type: information + :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 + :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 - :skin: skin_sisu_manual - :bold: /Gnu|Debian|Ruby|SiSU/ - :manpage: name=sisu - documents: markup, structuring, publishing in multiple standard formats, and search; + :num_top: 1 + :breaks: new=C; break=1 + :skin: skin_sisu_manual + :bold: /Gnu|Debian|Ruby|SiSU/ + :manpage: name=sisu - documents: markup, structuring, publishing in multiple standard formats, and search; synopsis=sisu [-abcDdeFhIiMmNnopqRrSsTtUuVvwXxYyZz0-9] [filename/wildcard ] . sisu [-Ddcv] [instruction] . sisu [-CcFLSVvW] @@ -157,16 +157,16 @@ code{ . 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 + { 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 @@ -174,10 +174,10 @@ code{ 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: +!_ @identifier: information or instructions -where the "identifier" is a tag recognised by the program, and the "information" or "instructions" belong to the tag/indentifier specified +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. @@ -191,7 +191,6 @@ code{ }code - code{ @title: [title text] [this header is the only one that is mandatory] @@ -203,50 +202,50 @@ code{ code{ @creator: - :author: [Lastname, First names] - :illustrator: [Lastname, First names] - :translator: [Lastname, First names] - :prepared_by: [Lastname, First names] + :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] + :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] + :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: - :isbn: [ISBN] - :loc: [Library of Congress classification] - :dewey: [Dewey classification + :topic_register: SiSU:markup sample:book;book:novel:fantasy + :type: + :subject: + :description: + :keywords: + :abstract: + :isbn: [ISBN] + :loc: [Library of Congress classification] + :dewey: [Dewey classification }code @@ -260,29 +259,29 @@ code{ code{ @make: - :skin: skin_name [skins change default settings related to the appearance of documents generated] - :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] + :skin: skin_name [skins change default settings related to the appearance of documents generated] + :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] }code code{ @original: - :language: [language] + :language: [language] }code code{ @notes: - :comment: - :prefix: [prefix is placed just after table of contents] + :comment: + :prefix: [prefix is placed just after table of contents] }code @@ -458,12 +457,19 @@ in each case level may be 0-9 !_ resulting output: -_0_1 first line no indent, rest of paragraph indented one step +_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; -_1_0 first line indented, rest of paragraph no indent +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 @@ -1266,232 +1272,4 @@ code{ }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. Alternative markup for importation of documents under consideration, and occasionally supported have been. - -code{ - -<< filename.ssi - -<<{filename.ssi} - -% using textlink alternatives - -<< |filename.ssi|@|^| - -}code - -1~syntax_history Markup Syntax History - -2~ Notes related to Files-types and Markup Syntax - -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{ +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. diff --git a/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_markup_syntax_history.sst b/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_markup_syntax_history.sst new file mode 100644 index 00000000..f0b621ff --- /dev/null +++ b/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_markup_syntax_history.sst @@ -0,0 +1,256 @@ +% SiSU 2.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 + +@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 + +@make: + :num_top: 1 + :breaks: new=C; break=1 + +:A~? @title @creator + +1~syntax_history Markup Syntax History + +2~ Notes related to Files-types and Markup Syntax + +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/v4/sisu_manual/_sisu/sisu_document_make b/data/doc/sisu/markup-samples/v4/sisu_manual/_sisu/sisu_document_make index 17c6bbf8..72706d10 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/_sisu/sisu_document_make +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/_sisu/sisu_document_make @@ -2,7 +2,7 @@ :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/ + :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 diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup.sst index 9027817a..98377850 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup.sst @@ -97,41 +97,40 @@ This current document is loaded by a master document that has a header similar t code{ -% SiSU master 2.0 +% SiSU master 4.0 @title: SiSU - :subtitle: Manual + :subtitle: Manual @creator: - :author: Amissah, Ralph + :author: Amissah, Ralph @publisher: [publisher name] @rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 @classify: - :type: information - :topic_register: SiSU:manual;electronic documents:SiSU:manual - :subject: ebook, epublishing, electronic book, electronic publishing, + :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 + :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; + :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] @@ -139,16 +138,16 @@ code{ . 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 + { 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 @@ -156,10 +155,10 @@ code{ 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: +!_ @identifier: information or instructions -where the "identifier" is a tag recognised by the program, and the "information" or "instructions" belong to the tag/indentifier specified +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. @@ -173,7 +172,6 @@ code{ }code - code{ @title: [title text] [this header is the only one that is mandatory] @@ -185,57 +183,57 @@ code{ code{ @creator: - :author: [Lastname, First names] - :illustrator: [Lastname, First names] - :translator: [Lastname, First names] - :prepared_by: [Lastname, First names] + :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] + :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] + :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 + :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: + :isbn: [ISBN] + :oclc: }code @@ -250,30 +248,30 @@ code{ code{ @make: - :num_top: 1 - :headings: [text to match for each level + :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 + :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] + :language: [language] }code code{ @notes: - :comment: - :prefix: [prefix is placed just after table of contents] + :comment: + :prefix: [prefix is placed just after table of contents] }code @@ -449,12 +447,19 @@ in each case level may be 0-9 !_ resulting output: -_0_1 first line no indent, rest of paragraph indented one step +_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 +_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 diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup_syntax_history.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup_syntax_history.sst index a5b56f1f..c6da0a14 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup_syntax_history.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup_syntax_history.sst @@ -25,22 +25,6 @@ :B~? SiSU Markup Syntax History -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~syntax_history Markup Syntax History 2~ Notes related to Files-types and Markup Syntax @@ -66,16 +50,16 @@ same as 1.0, apart from the changing of headers and the addition of a monospace code{ @title: - :subtitle: + :subtitle: @creator: - :author: - :translator: - :illustrator: + :author: + :translator: + :illustrator: @rights: - :text: - :illustrations: + :text: + :illustrations: }code diff --git a/man/man1/sisu.1 b/man/man1/sisu.1 index ccf359c0..b297f3e3 100644 --- a/man/man1/sisu.1 +++ b/man/man1/sisu.1 @@ -1,4 +1,4 @@ -.TH "sisu" "1" "2012-10-03" "4.0.0" "SiSU" +.TH "sisu" "1" "2012-10-03" "4.0.1" "SiSU" .br .SH NAME .br @@ -28,17 +28,15 @@ sisu [\-CcFLSVvW] .br sisu (\-\-configure|\-\-webrick|\-\-sample\-search\-form) -.SH SISU \- MANUAL, +.SH SISU - MANUAL, RALPH AMISSAH -.br .SH WHAT IS SISU? -.br -.SH INTRODUCTION \- WHAT IS SISU? -.br +.SH INTRODUCTION - WHAT IS SISU? -.br + +.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 @@ -48,7 +46,7 @@ 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 +.BR .B SiSU is developed under an open source, software libre license ( .I GPLv3 @@ -56,9 +54,9 @@ is developed under an open source, software libre license ( 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. +output) share a common mechanism for cross-output-format citation. -.br +.BR .B SiSU both defines a markup syntax and provides an engine that produces open standards format outputs from documents prepared with @@ -85,12 +83,12 @@ is also able to populate type databases at an object level, which means that searches can be made with that degree of granularity. -.br +.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 +generated by re-running the engine against the prepared source. Using .B SiSU markup applied to a document, .B SiSU @@ -107,7 +105,7 @@ or .I PDF files, and populate an .I SQL -database with objects[^1] (equating generally to paragraph\-sized chunks) so +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 @@ -115,7 +113,7 @@ 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. -.br +.BR In preparing a .B SiSU document you optionally provide semantic information related to the document in @@ -125,7 +123,7 @@ 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. -.br +.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 @@ -143,7 +141,7 @@ also has implications for search that .B SiSU is able to take advantage of. -.br +.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 @@ -151,7 +149,7 @@ 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 +provides the flexibility of producing documents in multiple non-proprietary open formats including .I HTML, .I EPUB, @@ -194,12 +192,12 @@ as .I HTML 5). -.br -The document formats are written to the file\-system and available for indexing +.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. -.br +.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 @@ -209,7 +207,7 @@ maps and thesauri, together with the flexibility of .B SiSU offers great possibilities. -.br +.BR .B SiSU is primarily for published works, which can take advantage of the citation system to reliably reference its documents. @@ -219,20 +217,19 @@ Wikis, which can take advantage of and be used to discuss the substance of content prepared in .B SiSU. -.br +.BR <http://www.sisudoc.org/> -.br +.BR <http://www.jus.uio.no/sisu> .SH COMMANDS SUMMARY -.br .SH DESCRIPTION -.br +.BR .B SiSU -is a document publishing system, that from a simple single marked\-up document, +is a document publishing system, that from a simple single marked-up document, produces multiple output formats including: .I plaintext, .I HTML, @@ -260,353 +257,297 @@ document structure information. For more see: <http://sisudoc.org> or .SH DOCUMENT PROCESSING COMMAND FLAGS .TP -.B \-a [filename/wildcard] +.B -a [filename/wildcard] produces .I 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) - +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) .TP -.B \-b [filename/wildcard] -see \-\-xhtml - +.B -b [filename/wildcard] +see --xhtml .TP -.B \-\-by\-* -see \-\-output\-by\-* - +.B --by-* +see --output-by-* .TP -.B \-C +.B -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 +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. - .TP -.B \-CC -see \-\-configure - +.B -CC +see --configure .TP -.B \-c [filename/wildcard] -see \-\-color\-toggle - +.B -c [filename/wildcard] +see --color-toggle +.TP +.B --color +see --color-on +.TP +.B --color-off +turn off color in output to terminal .TP -.B \-\-color\-toggle [filename/wildcard] -screen toggle ansi screen colour on or off depending on default set (unless \-c +.B --color-on +turn on color in output to terminal +.TP +.B --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 - +screen output will be without colour). Alias -c .TP -.B \-\-configure +.B --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 +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. - +and dtd files are updated if -CC is used. .TP -.B \-\-concordance [filename/wildcard] +.B --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 - +words unless this limit is increased in the file sisurc.yml). Alias -w .TP -.B \-D [instruction] [filename] -see \-\-pg - +.B -D [instruction] [filename] +see --pg .TP -.B \-d [\-\-db\-[database \ type \ (sqlite|pg)]] \-\-[instruction] [filename] -see \-\-sqlite - +.B -d [--db-[database type (sqlite|pg)]] --[instruction] [filename] +see --sqlite .TP -.B \-\-dal [filename/wildcard/url] +.B --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 - +output. This step is assumed for most processing flags. To skip it see -n. +Alias -m .TP -.B \-\-delete [filename/wildcard] -see \-\-zap - +.B --delete [filename/wildcard] +see --zap .TP -.B \-\-dump[=directory_path] [filename/wildcard] +.B --dump[=directory_path] [filename/wildcard] places output in directory specified, if none is specified in the current -directory (pwd). Compare \-\-redirect - +directory (pwd). Compare --redirect .TP -.B \-e [filename/wildcard] -see \-\-epub - +.B -e [filename/wildcard] +see --epub .TP -.B \-\-epub [filename/wildcard] -produces an epub document, [sisu \ version \ >=2 \ ] (filename.epub). Alias \-e - +.B --epub [filename/wildcard] +produces an epub document, [sisu version >=2 ] (filename.epub). Alias -e .TP -.B \-\-exc\-* -exclude output feature, overrides configuration settings \-\-exc\- -.I ocn, -(exclude +.B --exc-* +exclude output feature, overrides configuration settings --exc-ocn, (exclude .I object citation numbering, (switches off .I 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, +) , 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\-* - +--exc-segsubtoc (exclude sub table of contents, affects html (seg), epub) ; see +also --inc-* .TP -.B \-F [\-\-webserv=webrick] -see \-\-sample\-search\-form - +.B -F [--webserv=webrick] +see --sample-search-form .TP -.B \-f [optional \ string \ part \ of \ filename] -see \-\-find - +.B -f [optional string part of filename] +see --find .TP -.B \-\-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 - +.B --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 .TP -.B \-G [optional \ string \ part \ of \ filename] -see \-\-find - +.B -G [optional string part of filename] +see --find .TP -.B \-g [filename/wildcard] -see \-\-git - +.B -g [filename/wildcard] +see --git .TP -.B \-\-git [filename/wildcard] +.B --git [filename/wildcard] produces or updates markup source file structure in a git repo (experimental -and subject to change). Alias \-g - +and subject to change). Alias -g .TP -.B \-\-glob [optional \ string \ part \ of \ filename] -see \-\-find - +.B --glob [optional string part of filename] +see --find .TP -.B \-h [filename/wildcard] -see \-\-html - +.B -h [filename/wildcard] +see --html .TP -.B \-\-harvest *.ss[tm] +.B --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. - +title, date, topic_register). Can be used with maintenance (-M) and remote +placement (-R) flags. .TP -.B \-\-help [topic] +.B --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. - .TP -.B \-\-html [filename/wildcard] +.B --html [filename/wildcard] produces html output, segmented text with table of contents (toc.html and -index.html) and the document in a single file (scroll.html). Alias \-h - +index.html) and the document in a single file (scroll.html). Alias -h .TP -.B \-I [filename/wildcard] -see \-\-texinfo - +.B -I [filename/wildcard] +see --texinfo .TP -.B \-i [filename/wildcard] -see \-\-manpage - +.B -i [filename/wildcard] +see --manpage .TP -.B \-\-inc\-* +.B --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\-* - +if none set), has precedence over --exc-* (exclude output feature). Some detail +provided under --exc-*, see --exc-* .TP -.B \-j [filename/wildcard] +.B -j [filename/wildcard] copies images associated with a file for use by html, xhtml & xml outputs -(automatically invoked by \-\-dump & redirect). - +(automatically invoked by --dump & redirect). .TP -.B \-\-keep\-processing\-files [filename/wildcard/url] -see \-\-maintenance - +.B -k +see --color-off +.TP +.B --keep-processing-files [filename/wildcard/url] +see --maintenance .TP -.B \-L +.B -L prints license information. - .TP -.B \-M [filename/wildcard/url] -see \-\-maintenance - +.B -M [filename/wildcard/url] +see --maintenance .TP -.B \-m [filename/wildcard/url] -see \-\-dal (document abstraction level/layer) - +.B -m [filename/wildcard/url] +see --dal (document abstraction level/layer) .TP -.B \-\-machine [filename/wildcard/url] -see \-\-dal (document abstraction level/layer) - +.B --machine [filename/wildcard/url] +see --dal (document abstraction level/layer) .TP -.B \-\-maintenance [filename/wildcard/url] +.B --maintenance [filename/wildcard/url] maintenance mode, interim processing files are preserved and their locations -indicated. (also see \-V). Aliases \-M and \-\-keep\-processing\-files. - +indicated. (also see -V). Aliases -M and --keep-processing-files. .TP -.B \-\-manpage [filename/wildcard] -produces man page of file, not suitable for all outputs. Alias \-i - +.B --manpage [filename/wildcard] +produces man page of file, not suitable for all outputs. Alias -i .TP -.B \-N [filename/wildcard/url] +.B -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. - +that produced it) (digest.txt). -NV for verbose digest output to screen. .TP -.B \-n [filename/wildcard/url] +.B -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 +they already exist, this skips the equivalent of -m which is otherwise assumed by most processing flags. - .TP -.B \-\-no\-* -see \-\-exc\-* - +.B --no-* +see --exc-* .TP -.B \-o [filename/wildcard/url] -see \-\-odt - +.B -o [filename/wildcard/url] +see --odt .TP -.B \-\-odf [filename/wildcard/url] -see \-\-odt - +.B --odf [filename/wildcard/url] +see --odt .TP -.B \-\-odt [filename/wildcard/url] -output basic document in opendocument file format (opendocument.odt). Alias \-o - +.B --odt [filename/wildcard/url] +output basic document in opendocument file format (opendocument.odt). Alias -o .TP -.B \-\-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\-* - +.B --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-* .TP -.B \-P [language_directory/filename \ language_directory] -see \-\-po4a - +.B -P [language_directory/filename language_directory] +see --po4a .TP -.B \-p [filename/wildcard] -see \-\-pdf - +.B -p [filename/wildcard] +see --pdf .TP -.B \-\-pdf [filename/wildcard] +.B --pdf [filename/wildcard] produces .I LaTeX pdf (portrait.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). Alias \-p - +--papersize-a4 preset sizes include: 'A4', U.S. 'letter' and 'legal' and book +sizes 'A5' and 'B5' (system defaults to A4). Alias -p .TP -.B \-\-pg [instruction] [filename] +.B --pg [instruction] [filename] database .I PostgreSQL -( \-\-pgsql may be used instead) possible instructions, include: \-\-createdb; -\-\-create; \-\-dropall; \-\-import [filename]; \-\-update [filename]; -\-\-remove [filename]; see database section below. Alias \-D - +( --pgsql may be used instead) possible instructions, include: --createdb; +--create; --dropall; --import [filename]; --update [filename]; --remove +[filename]; see database section below. Alias -D .TP -.B \-\-po [language_directory/filename \ language_directory] -see \-\-po4a - +.B --po [language_directory/filename language_directory] +see --po4a .TP -.B \-\-po4a [language_directory/filename \ language_directory] -produces \.pot and po files for the file in the languages specified by the +.B --po4a [language_directory/filename language_directory] +produces .pot and po files for the file in the languages specified by the language directory. .B 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 - .TP -.B \-Q [filename/wildcard] -see \-\-qrcode - +.B -Q [filename/wildcard] +see --qrcode .TP -.B \-q [filename/wildcard] -see \-\-quiet - +.B -q [filename/wildcard] +see --quiet .TP -.B \-\-qrcode [filename/wildcard] +.B --qrcode [filename/wildcard] generate QR code image of metadata (used in manifest). v3 only. - .TP -.B \-\-quiet [filename/wildcard] +.B --quiet [filename/wildcard] quiet less output to screen. - .TP -.B \-R [filename/wildcard] -see \-\-rsync - +.B -R [filename/wildcard] +see --rsync .TP -.B \-r [filename/wildcard] -see \-\-scp - +.B -r [filename/wildcard] +see --scp .TP -.B \-\-redirect[=directory_path] [filename/wildcard] +.B --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). Compare \-\-dump - +subdirectory under the current directory (pwd). Compare --dump .TP -.B \-\-rsync [filename/wildcard] +.B --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 - +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 .TP -.B \-S -see \-\-sisupod - +.B -S +see --sisupod .TP -.B \-S [filename/wildcard] -see \-\-sisupod - +.B -S [filename/wildcard] +see --sisupod .TP -.B \-s [filename/wildcard] -see \-\-source - +.B -s [filename/wildcard] +see --source .TP -.B \-\-sample\-search\-form [\-\-webserv=webrick] +.B --sample-search-form [--webserv=webrick] generate examples of (naive) cgi search form for .I SQLite and PgSQL depends on your already having used sisu to populate an @@ -614,22 +555,20 @@ and PgSQL depends on your already having used sisu to populate an and/or PgSQL database, (the .I 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 \-d -\-D and the database section below. 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 - -.TP -.B \-\-scp [filename/wildcard] +is first necessary to create them, before generating the search form) see -d -D +and the database section below. 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 +.TP +.B --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 - +that you have your "keys" and ssh agent in place. Also see --rsync. Alias -r .TP -.B \-\-sqlite \-\-[instruction] [filename] +.B --sqlite --[instruction] [filename] database type set to .I SQLite, this produces one of two possible databases, without additional database @@ -640,23 +579,21 @@ common .I 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 - +path (possible instructions include: --createdb; --create; --dropall; --import +[filename]; --update [filename]; --remove [filename]); see database section +below. Alias -d .TP -.B \-\-sisupod +.B --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 - +./_sisu not those in ~/.sisu -S [filename/wildcard] option. Note: (this option +is tested only with zsh). Alias -S .TP -.B \-\-sisupod [filename/wildcard] +.B --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 +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 @@ -664,347 +601,303 @@ skin. .B 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 +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 - +for sending). See the -S option without [filename/wildcard]. Alias -S .TP -.B \-\-source [filename/wildcard] -copies sisu markup file to output directory. Alias \-s - +.B --source [filename/wildcard] +copies sisu markup file to output directory. Alias -s .TP -.B \-T [filename/wildcard \ (*.termsheet.rb)] +.B -T [filename/wildcard (*.termsheet.rb)] standard form document builder, preprocessing feature - .TP -.B \-t [filename/wildcard] -see \-\-txt - +.B -t [filename/wildcard] +see --txt .TP -.B \-\-texinfo [filename/wildcard] -produces texinfo and info file, (view with pinfo). Alias \-I - +.B --texinfo [filename/wildcard] +produces texinfo and info file, (view with pinfo). Alias -I .TP -.B \-\-txt [filename/wildcard] +.B --txt [filename/wildcard] produces .I 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 - +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 .TP -.B \-U [filename/wildcard] -see \-\-urls - +.B -U [filename/wildcard] +see --urls .TP -.B \-u [filename/wildcard] +.B -u [filename/wildcard] provides url mapping of output files for the flags requested for processing, -also see \-U - +also see -U .TP -.B \-\-urls [filename/wildcard] +.B --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 +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 - +file system paths in sisurc.yml. Alias -U .TP -.B \-V +.B -V on its own, provides .B SiSU -version and environment information (sisu \-\-help env) - +version and environment information (sisu --help env) .TP -.B \-V [filename/wildcard] -even more verbose than the \-v flag. - +.B -V [filename/wildcard] +even more verbose than the -v flag. .TP -.B \-v +.B -v on its own, provides .B SiSU version information - .TP -.B \-v [filename/wildcard] -see \-\-verbose - +.B -v [filename/wildcard] +see --verbose .TP -.B \-\-v3 [filename/wildcard] +.B --v3 [filename/wildcard] invokes the sisu v3 document parser/generator. You may run sisu3 instead. - .TP -.B \-\-v4 [filename/wildcard] +.B --v4 [filename/wildcard] invokes the sisu v4 document parser/generator. This is the default and is normally omitted. - .TP -.B \-\-verbose [filename/wildcard] +.B --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 - +error messages if any), as with -u flag provides a url mapping of files created +for each of the processing flag requests. Alias -v .TP -.B \-W -see \-\-webrick - +.B -W +see --webrick .TP -.B \-w [filename/wildcard] -see \-\-concordance - +.B -w [filename/wildcard] +see --concordance .TP -.B \-\-webrick +.B --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 - +[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 .TP -.B \-\-wordmap [filename/wildcard] -see \-\-concordance - +.B --wordmap [filename/wildcard] +see --concordance .TP -.B \-\-xhtml [filename/wildcard] +.B --xhtml [filename/wildcard] produces xhtml/ .I XML -output for browser viewing (sax parsing). Alias \-b - +output for browser viewing (sax parsing). Alias -b .TP -.B \-\-xml\-dom [filename/wildcard] +.B --xml-dom [filename/wildcard] produces .I XML -output with deep document structure, in the nature of dom. Alias \-X - +output with deep document structure, in the nature of dom. Alias -X .TP -.B \-\-xml\-sax [filename/wildcard] +.B --xml-sax [filename/wildcard] produces .I XML -output shallow structure (sax parsing). Alias \-x - +output shallow structure (sax parsing). Alias -x .TP -.B \-X [filename/wildcard] -see \-\-xml\-dom - +.B -X [filename/wildcard] +see --xml-dom .TP -.B \-x [filename/wildcard] -see \-\-xml\-sax - +.B -x [filename/wildcard] +see --xml-sax .TP -.B \-Y [filename/wildcard] +.B -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]) - +sisu_manifest. --sitemaps generates/updates the sitemap index of existing +sitemaps. (Experimental, [g,y,m announcement this week]) .TP -.B \-y [filename/wildcard] +.B -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. - .TP -.B \-Z [filename/wildcard] -see \-\-zap - +.B -Z [filename/wildcard] +see --zap .TP -.B \-\-zap [filename/wildcard] +.B --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 - +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 .SH COMMAND LINE MODIFIERS -.br .TP -.B \-\-no\- -.I ocn -[with \ \-\-html \ \-\-pdf \ or \ \-\-epub] switches off +.B --no-ocn +[with --html --pdf or --epub] switches off .I object citation numbering. Produce output without identifying numbers in margins of html or .I LaTeX /pdf output. - .TP -.B \-\-no\-annotate +.B --no-annotate strips output text of editor endnotes[^*1] denoted by asterisk or dagger/plus sign - .TP -.B \-\-no\-asterisk +.B --no-asterisk strips output text of editor endnotes[^*2] denoted by asterisk sign - .TP -.B \-\-no\-dagger +.B --no-dagger strips output text of editor endnotes[^+1] denoted by dagger/plus sign - .SH DATABASE COMMANDS -.br -.br -.B dbi \- database interface +.BR +.B dbi - database interface -.br -.B \-D or \-\-pgsql +.BR +.B -D or --pgsql set for .I PostgreSQL -.B \-d or \-\-sqlite +.B -d or --sqlite default set for .I SQLite -\-d is modifiable with \-\-db=[database \ type \ (PgSQL \ or \ .I \ SQLite \ ) -\ ] - +-d is modifiable with --db=[database type (PgSQL or +.I SQLite +) ] .TP -.B \-\-pg \-v \-\-createall +.B --pg -v --createall initial step, creates required relations (tables, indexes) in existing .I PostgreSQL database (a database should be created manually and given the same name as -working directory, as requested) (rb.dbi) [ \ \-dv \ \-\-createall \ .I \ -SQLite \ equivalent] it may be necessary to run sisu \-Dv \-\-createdb -initially NOTE: at the present time for +working directory, as requested) (rb.dbi) [ -dv --createall +.I SQLite +equivalent] it may be necessary to run sisu -Dv --createdb initially NOTE: at +the present time for .I 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. - +'createdb [database name]' where database name would be SiSU_[present working +directory name (without path)]. Please use only alphanumerics and underscores. .TP -.B \-\-pg \-v \-\-import +.B --pg -v --import [filename/wildcard] imports data specified to .I PostgreSQL -db (rb.dbi) [ \ \-dv \ \-\-import \ .I \ SQLite \ equivalent] - +db (rb.dbi) [ -dv --import +.I SQLite +equivalent] .TP -.B \-\-pg \-v \-\-update +.B --pg -v --update [filename/wildcard] updates/imports specified data to .I PostgreSQL -db (rb.dbi) [ \ \-dv \ \-\-update \ .I \ SQLite \ equivalent] - +db (rb.dbi) [ -dv --update +.I SQLite +equivalent] .TP -.B \-\-pg \-\-remove +.B --pg --remove [filename/wildcard] removes specified data to .I PostgreSQL -db (rb.dbi) [ \ \-d \ \-\-remove \ .I \ SQLite \ equivalent] - +db (rb.dbi) [ -d --remove +.I SQLite +equivalent] .TP -.B \-\-pg \-\-dropall +.B --pg --dropall kills data" and drops ( .I PostgreSQL or .I SQLite -) db, tables & indexes [ \ \-d \ \-\-dropall \ .I \ SQLite \ equivalent] - -.br -The \-v is for verbose output. +) db, tables & indexes [ -d --dropall +.I SQLite +equivalent] +.BR +The -v is for verbose output. .SH SHORTCUTS, SHORTHAND FOR MULTIPLE FLAGS -.br .TP -.B \-\-update [filename/wildcard] +.B --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. - +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. .TP -.B \-0 to \-5 [filename \ or \ wildcard] +.B -0 to -5 [filename or wildcard] Default shorthand mappings (for v3, note that the defaults can be changed/configured in the sisurc.yml file): - .TP -.B \-0 -\-NQhewpotbxXyYv [this \ is \ the \ default \ action \ run \ when \ no \ -options \ are \ give, \ i.e. \ on \ 'sisu \ [filename]'] - +.B -0 +-NQhewpotbxXyYv [this is the default action run when no options are give, i.e. +on 'sisu [filename]'] .TP -.B \-1 -\-Qhewpoty - +.B -1 +-Qhewpoty .TP -.B \-2 -\-NQhewpotbxXy - +.B -2 +-NQhewpotbxXy .TP -.B \-3 -\-NQhewpotbxXyY - +.B -3 +-NQhewpotbxXyY .TP -.B \-4 -\-NQhewpotbxXDyY \-\-update - +.B -4 +-NQhewpotbxXDyY --update .TP -.B \-5 -\-NQhewpotbxXDyYv \-\-update +.B -5 +-NQhewpotbxXDyYv --update -.br -add \-v for verbose mode and \-c to toggle color state, e.g. sisu \-2vc -[filename \ or \ wildcard] +.BR +add -v for verbose mode and -c to toggle color state, e.g. sisu -2vc [filename +or wildcard] -.br -consider \-u for appended url info or \-v for verbose output +.BR +consider -u for appended url info or -v for verbose output -.SH COMMAND LINE WITH FLAGS \- BATCH PROCESSING +.SH COMMAND LINE WITH FLAGS - BATCH PROCESSING -.br -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. +.BR +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. -.br +.BR 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. .SH HELP -.br .SH SISU MANUAL -.br +.BR The most up to date information on sisu should be contained in the sisu_manual, available at: -.br +.BR <http://sisudoc.org/sisu/sisu_manual/> -.br +.BR The manual can be generated from source, found respectively, either within the .B SiSU tarball or installed locally at: -.br - ./data/doc/sisu/markup\-samples/sisu_manual +.BR + ./data/doc/sisu/markup-samples/sisu_manual -.br - /usr/share/doc/sisu/markup\-samples/sisu_manual +.BR + /usr/share/doc/sisu/markup-samples/sisu_manual -.br +.BR move to the respective directory and type e.g.: -.br +.BR sisu sisu_manual.ssm .SH SISU MAN PAGES -.br +.BR If .B SiSU is installed on your system usual man commands should be available, try: -.br +.BR man sisu -.br +.BR Most .B SiSU man pages are generated directly from sisu documents that are used to prepare @@ -1012,177 +905,175 @@ the sisu manual, the sources files for which are located within the .B SiSU tarball at: -.br - ./data/doc/sisu/markup\-samples/sisu_manual +.BR + ./data/doc/sisu/markup-samples/sisu_manual -.br +.BR Once installed, directory equivalent to: -.br - /usr/share/doc/sisu/markup\-samples/sisu_manual +.BR + /usr/share/doc/sisu/markup-samples/sisu_manual -.br +.BR Available man pages are converted back to html using man2html: -.br +.BR /usr/share/doc/sisu/html/ -.br +.BR ./data/doc/sisu/html -.br +.BR An online version of the sisu man page is available here: -.br +.BR * various sisu man pages <http://www.jus.uio.no/sisu/man/> [^9] -.br +.BR * sisu.1 <http://www.jus.uio.no/sisu/man/sisu.1.html> [^10] .SH SISU BUILT\-IN INTERACTIVE HELP -.br +.BR This is particularly useful for getting the current sisu setup/environment information: -.br - sisu \-\-help +.BR + sisu --help -.br - sisu \-\-help [subject] +.BR + sisu --help [subject] -.br - sisu \-\-help commands +.BR +sisu --help commands -.br - sisu \-\-help markup +.BR +sisu --help markup -.br - sisu \-\-help env [for \ feedback \ on \ the \ way \ your \ system \ is \ - setup \ with \ regard \ to \ sisu \ ] +.BR +sisu --help env [for feedback on the way your system is setup with regard + to sisu ] -.br - sisu \-V [environment \ information, \ same \ as \ above \ command] +.BR + sisu -V [environment information, same as above command] -.br +.BR sisu (on its own provides version and some help information) -.br -Apart from real\-time information on your current configuration the +.BR +Apart from real-time information on your current configuration the .B SiSU -manual and man pages are likely to contain more up\-to\-date information than -the sisu interactive help (for example on commands and markup). +manual and man pages are likely to contain more up-to-date information than the +sisu interactive help (for example on commands and markup). -.br +.BR NOTE: Running the command 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. .SH INTRODUCTION TO SISU MARKUP[^11] -.br .SH SUMMARY -.br +.BR .B SiSU source documents are .I plaintext ( -.I UTF\-8 +.I UTF-8 )[^12] files -.br +.BR All paragraphs are separated by an empty line. -.br +.BR Markup is comprised of: -.br -* at the top of a document, the document header made up of semantic meta\-data +.BR +* 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) -.br +.BR * 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: -.br +.BR * heading levels defines document structure -.br +.BR * text basic attributes, italics, bold etc. -.br +.BR * grouped text (objects), which are to be treated differently, such as code blocks or poems. -.br +.BR * footnotes/endnotes -.br +.BR * linked text and images -.br - * paragraph actions, such as indent, bulleted, numbered\-lists, etc. +.BR + * paragraph actions, such as indent, bulleted, numbered-lists, etc. -.br +.BR Some interactive help on markup is available, by typing sisu and selecting -markup or sisu \-\-help markup +markup or sisu --help markup -.br +.BR To check the markup in a file: -.br - sisu \-\-identify [filename].sst +.BR + sisu --identify [filename].sst -.br +.BR For brief descriptive summary of markup history -.br - sisu \-\-query\-history +.BR + sisu --query-history -.br +.BR or if for a particular version: -.br - sisu \-\-query\-0.38 - +.BR + sisu --query-0.38 .SH MARKUP EXAMPLES .SH ONLINE -.br +.BR 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/> -.br +.BR 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/> -.br +.BR an alternative presentation of markup syntax: /usr/share/doc/sisu/on_markup.txt.gz .SH INSTALLED -.br +.BR With .B 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 +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 .SH MARKUP OF HEADERS -.br -.br -Headers contain either: semantic meta\-data about a document, which can be used + +.BR +Headers contain either: semantic meta-data about a document, which can be used by any output module of the program, or; processing instructions. -.br +.BR 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 @@ -1194,59 +1085,67 @@ a space and the comment: .SH SAMPLE HEADER -.br +.BR This current document is loaded by a master document that has a header similar to this one: .nf -% SiSU master 2.0 +% SiSU master 4.0 + @title: SiSU -:subtitle: Manual + :subtitle: Manual + @creator: -:author: Amissah, Ralph -@publisher: [publisher \ name] + :author: Amissah, Ralph + +@publisher: [publisher name] + @rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 + @classify: -:type: information -:topic_register: SiSU:manual;electronic documents:SiSU:manual -:subject: ebook, epublishing, electronic book, electronic publishing, + :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 + :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] + :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 + { 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 .fi .SH AVAILABLE HEADERS -.br +.BR Header tags appear at the beginning of a document and provide meta information on the document (such as the .I Dublin Core @@ -1256,77 +1155,77 @@ by once space :subheadername: All .I Dublin Core meta tags are available -.br +.BR .B @indentifier: information or instructions -.br +.BR where the "identifier" is a tag recognised by the program, and the -"information" or "instructions" belong to the tag/indentifier specified +"information" or "instructions" belong to the tag/identifier specified -.br +.BR 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. -.br +.BR This is a sample header .nf -% SiSU 2.0 [declared \ file\-type \ identifier \ with \ markup \ version] +% SiSU 2.0 [declared file-type identifier with markup version] .fi .nf -@title: [title \ text] [this \ header \ is \ the \ only \ one \ that \ is \ mandatory] - :subtitle: [subtitle \ if \ any] +@title: [title text] [this header is the only one that is mandatory] + :subtitle: [subtitle if any] :language: English .fi .nf @creator: -:author: [Lastname, \ First \ names] -:illustrator: [Lastname, \ First \ names] -:translator: [Lastname, \ First \ names] -:prepared_by: [Lastname, \ First \ names] + :author: [Lastname, First names] + :illustrator: [Lastname, First names] + :translator: [Lastname, First names] + :prepared_by: [Lastname, First names] .fi .nf @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] + :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] .fi .nf @rights: -:copyright: Copyright (C) [Year \ and \ Holder] -:license: [Use \ License \ granted] -:text: [Year \ and \ Holder] -:translation: [Name, \ Year] -:illustrations: [Name, \ Year] + :copyright: Copyright (C) [Year and Holder] + :license: [Use License granted] + :text: [Year and Holder] + :translation: [Name, Year] + :illustrations: [Name, Year] .fi .nf @classify: -:topic_register: SiSU:markup sample:book;book:novel:fantasy -:type: -:subject: -:description: -:keywords: -:abstract: -:loc: [Library \ of \ Congress \ classification] -:dewey: Dewey classification + :topic_register: SiSU:markup sample:book;book:novel:fantasy + :type: + :subject: + :description: + :keywords: + :abstract: + :loc: [Library of Congress classification] + :dewey: [Dewey classification .fi .nf @identify: -:isbn: [ISBN] -:oclc: + :isbn: [ISBN] + :oclc: .fi .nf @@ -1336,495 +1235,534 @@ This is a sample header .nf @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 + :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 .fi .nf @original: -:language: [language] + :language: [language] .fi .nf @notes: -:comment: -:prefix: [prefix \ is \ placed \ just \ after \ table \ of \ contents] + :comment: + :prefix: [prefix is placed just after table of contents] .fi .SH MARKUP OF SUBSTANTIVE TEXT -.br .SH HEADING LEVELS -.br -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) +.BR +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) -.br -.B :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 +.BR +.B :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 -.br -.B :B~ [heading \ text] -Second level heading [this \ is \ a \ heading \ level \ divider] +.BR +.B :B~ [heading text] +Second level heading [this is a heading level divider] -.br -.B :C~ [heading \ text] -Third level heading [this \ is \ a \ heading \ level \ divider] +.BR +.B :C~ [heading text] +Third level heading [this is a heading level divider] -.br -.B 1~ [heading \ text] -Top level heading preceding substantive text of document or sub\-heading 2, the +.BR +.B 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 -.br -.B 2~ [heading \ text] -Second level heading preceding substantive text of document or sub\-heading 3 , +.BR +.B 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. -.br -.B 3~ [heading \ text] +.BR +.B 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 .nf 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) .fi .SH FONT ATTRIBUTES -.br +.BR .B markup example: - .nf normal text, *{emphasis}*, !{bold text}!, /{italics}/, _{underscore}_, "{citation}", -^{superscript}^, ,{subscript},, +{inserted text}+, \-{strikethrough}\-, #{monospace}# +^{superscript}^, ,{subscript},, +{inserted text}+, -{strikethrough}-, #{monospace}# + normal text -*{emphasis}* [note: \ can \ be \ configured \ to \ be \ represented \ by \ bold, \ italics \ or \ underscore] + +*{emphasis}* [note: can be configured to be represented by bold, italics or underscore] + !{bold text}! + /{italics}/ + _{underscore}_ + "{citation}" + ^{superscript}^ + ,{subscript}, + +{inserted text}+ -\-{strikethrough}\- + +-{strikethrough}- + #{monospace}# .fi -.br +.BR .B resulting output: -.br +.BR normal text, .B emphasis, .B bold text , .I italics, .I underscore, -"citation", ^superscript^, [subscript], ++inserted text++, -\-\-strikethrough\-\-, monospace +"citation", ^superscript^, [subscript], ++inserted text++, --strikethrough--, +monospace -.br +.BR normal text -.br +.BR .B emphasis -[note: \ can \ be \ configured \ to \ be \ represented \ by \ bold, \ italics \ -or \ underscore] +[note: can be configured to be represented by bold, italics or underscore] -.br +.BR .B bold text -.br +.BR .I italics -.br +.BR .I underscore -.br +.BR "citation" -.br +.BR ^superscript^ -.br +.BR [subscript] -.br +.BR ++inserted text++ -.br -\-\-strikethrough\-\- +.BR +--strikethrough-- -.br +.BR monospace .SH INDENTATION AND BULLETS -.br +.BR .B markup example: - .nf ordinary paragraph + _1 indent paragraph one step + _2 indent paragraph two steps + _9 indent paragraph nine steps .fi -.br +.BR .B resulting output: -.br +.BR ordinary paragraph -.br +.BR indent paragraph one step -.br +.BR indent paragraph two steps -.br +.BR indent paragraph nine steps -.br +.BR .B markup example: - .nf _* bullet text + _1* bullet text, first indent + _2* bullet text, two step indent .fi -.br +.BR .B resulting output: -.br +.BR * bullet text -.br +.BR * bullet text, first indent -.br +.BR * bullet text, two step indent -.br +.BR Numbered List (not to be confused with headings/titles, (document structure)) -.br +.BR .B markup example: - .nf # numbered list numbered list 1., 2., 3, etc. + _# numbered list numbered list indented a., b., c., d., etc. .fi .SH HANGING INDENTS -.br +.BR .B markup example: - .nf _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 + +in each case level may be 0-9 .fi -.br +.BR .B resulting output: -.br - first line no indent, rest of paragraph indented one step - -.br -first line indented, rest of paragraph no indent - -.br -in each case level may be 0\-9 - +.BR +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; + +.BR +A regular paragraph. + +.BR +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 + +.BR +in each case level may be 0-9 + +.BR +.B 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. + +.BR +.B 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. .SH FOOTNOTES / ENDNOTES -.br +.BR 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 -.br +.BR .B markup example: .nf ~{ a footnote or endnote }~ .fi -.br +.BR .B resulting output: -.br +.BR [^13] -.br +.BR .B markup example: - .nf normal text~{ self contained endnote marker & endnote in one }~ continues .fi -.br +.BR .B resulting output: -.br +.BR normal text[^14] continues -.br +.BR .B markup example: - .nf normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks if required }~ continues + normal text ~{** another unnumbered asterisk footnote/endnote }~ continues .fi -.br +.BR .B resulting output: -.br +.BR normal text [^*] continues -.br +.BR normal text [^**] continues -.br +.BR .B markup example: .nf -normal text ~[* \ editors \ notes, \ numbered \ asterisk \ footnote/endnote \ series \ ]~ continues -normal text ~[+ \ editors \ notes, \ numbered \ asterisk \ footnote/endnote \ series \ ]~ continues +normal text ~[* editors notes, numbered asterisk footnote/endnote series ]~ continues + +normal text ~[+ editors notes, numbered asterisk footnote/endnote series ]~ continues .fi -.br +.BR .B resulting output: -.br +.BR normal text [^*3] continues -.br +.BR normal text [^+2] continues -.br +.BR .B Alternative endnote pair notation for footnotes/endnotes: - .nf % note the endnote marker "~^" + normal text~^ continues + ^~ endnote text following the paragraph in which the marker occurs .fi -.br +.BR the standard and pair notation cannot be mixed in the same document .SH LINKS .SH NAKED URLS WITHIN TEXT, DEALING WITH URLS -.br +.BR 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). -.br +.BR .B markup example: - .nf normal text http://www.sisudoc.org/ continues .fi -.br +.BR .B resulting output: -.br +.BR normal text <http://www.sisudoc.org/> continues -.br +.BR An escaped url without decoration -.br +.BR .B markup example: - .nf normal text _http://www.sisudoc.org/ continues -deb _http://www.jus.uio.no/sisu/archive unstable main non\-free + +deb _http://www.jus.uio.no/sisu/archive unstable main non-free .fi -.br +.BR .B resulting output: -.br +.BR normal text <_http://www.sisudoc.org/> continues -.br -deb <_http://www.jus.uio.no/sisu/archive> unstable main non\-free +.BR +deb <_http://www.jus.uio.no/sisu/archive> unstable main non-free -.br +.BR where a code block is used there is neither decoration nor hyperlinking, code blocks are discussed later in this document -.br +.BR .B resulting output: - .nf -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 +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 .fi .SH LINKING TEXT -.br +.BR To link text or an image to a url the markup is as follows -.br +.BR .B markup example: - .nf about { SiSU }http://url.org markup .fi -.br +.BR .B resulting output: -.br +.BR aboutSiSU <http://www.sisudoc.org/> markup -.br +.BR A shortcut notation is available so the url link may also be provided automatically as a footnote -.br +.BR .B markup example: - .nf about {~^ SiSU }http://url.org markup .fi -.br +.BR .B resulting output: -.br +.BR aboutSiSU <http://www.sisudoc.org/> [^15] markup -.br -Internal document links to a tagged location, including an -.I ocn +.BR +Internal document links to a tagged location, including an ocn -.br +.BR .B markup example: - .nf about { text links }#link_text .fi -.br +.BR .B resulting output: -.br +.BR about ⌠text links⌡⌈link_text⌋ -.br +.BR Shared document collection link -.br +.BR .B markup example: - .nf about { SiSU book markup examples }:SiSU/examples.html .fi -.br +.BR .B resulting output: -.br +.BR about ⌠ .B SiSU book markup examples⌡⌈:SiSU/examples.html⌋ .SH LINKING IMAGES -.br +.BR .B markup example: - .nf { 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/ + +{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/ .fi -.br +.BR .B resulting output: -.br +.BR [ tux.png ] -.br -tux.png 64x80 "Gnu/Linux \- a better way" <http://www.sisudoc.org/> +.BR +tux.png 64x80 "Gnu/Linux - a better way" <http://www.sisudoc.org/> -.br -GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better \- with Gnu/Linux, Debian +.BR +GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian and Ruby" <http://www.sisudoc.org/> -.br -ruby_logo.png 70x90 "Ruby" <http://www.ruby\-lang.org/en/> [^16] +.BR +ruby_logo.png 70x90 "Ruby" <http://www.ruby-lang.org/en/> [^16] -.br +.BR .B linked url footnote shortcut - .nf -{~^ [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 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 .fi .nf text marker *~name .fi -.br +.BR 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. - +auto-heading numbering, without further intervention. .SH LINK SHORTCUT FOR MULTIPLE VERSIONS OF A SISU DOCUMENT IN THE SAME DIRECTORY TREE -.br +.BR .B markup example: - .nf !_ /{"Viral Spiral"}/, David Bollier + { "Viral Spiral", David Bollier [3sS]}viral_spiral.david_bollier.sst .fi -.br +.BR .B .I "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」 @@ -1845,38 +1783,41 @@ David Bollier .SH TABLES -.br +.BR Tables may be prepared in two either of two forms -.br +.BR .B markup example: - .nf 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 .fi -.br +.BR .B 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』 -.br +.BR a second form may be easier to work with in cases where there is not much information in each column -.br +.BR .B markup example: [^18] .nf -!_ Table 3.1: Contributors to Wikipedia, January 2001 \- June 2005 +!_ 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 @@ -1884,38 +1825,40 @@ Active contributors** | 9| 212| 846| 3,228| 8,4 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. .fi -.br +.BR .B resulting output: -.br -.B Table 3.1: Contributors to Wikipedia, January 2001 \- June 2005 - +.BR +.B 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』 -.br +.BR * Contributed at least ten times; ** at least 5 times in last month; *** more than 100 times in last month. .SH POEM -.br +.BR .B basic markup: - .nf poem{ + Your poem here + }poem + Each verse in a poem is given an object number. .fi -.br +.BR .B markup example: - .nf poem{ + `Fury said to a mouse, That he met in the @@ -1924,7 +1867,7 @@ poem{ both go to law: I will prosecute - YOU. \-\-Come, + YOU. --Come, I'll take no denial; We must have a @@ -1960,12 +1903,12 @@ poem{ you to death."' + }poem .fi -.br +.BR .B resulting output: - `Fury said to a mouse, That he met in the @@ -1974,7 +1917,7 @@ poem{ both go to law: I will prosecute - YOU. \-\-Come, + YOU. --Come, I'll take no denial; We must have a @@ -2013,21 +1956,23 @@ poem{ .SH GROUP -.br +.BR .B basic markup: - .nf group{ + Your grouped text here + }group + A group is treated as an object and given a single object number. .fi -.br +.BR .B markup example: - .nf group{ + `Fury said to a mouse, That he met in the @@ -2036,7 +1981,7 @@ group{ both go to law: I will prosecute - YOU. \-\-Come, + YOU. --Come, I'll take no denial; We must have a @@ -2072,12 +2017,12 @@ group{ you to death."' + }group .fi -.br +.BR .B resulting output: - `Fury said to a mouse, That he met in the @@ -2086,7 +2031,7 @@ group{ both go to law: I will prosecute - YOU. \-\-Come, + YOU. --Come, I'll take no denial; We must have a @@ -2125,22 +2070,20 @@ group{ .SH CODE -.br -Code tags code{ \... }code (used as with other group tags described above) are +.BR +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 .B 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. -.br -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] +.BR +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] -.br +.BR .B use of code tags instead of poem compared, resulting output: - .nf `Fury said to a mouse, That he @@ -2150,7 +2093,7 @@ some \ later \ time] both go to law: I will prosecute - YOU. \-\-Come, + YOU. --Come, I'll take no denial; We must have a @@ -2188,7 +2131,7 @@ some \ later \ time] death."' .fi -.br +.BR From .B SiSU 2.7.7 on you can number codeblocks by placing a hash after the opening code tag @@ -2203,7 +2146,7 @@ code{# as demonstrated here: 6 | both go to 7 | law: I will 8 | prosecute -9 | YOU. \-\-Come, +9 | YOU. --Come, 10 | I'll take no 11 | denial; We 12 | must have a @@ -2241,11 +2184,11 @@ code{# as demonstrated here: 44 | death."' .fi -.SH ADDITIONAL BREAKS \- LINEBREAKS WITHIN OBJECTS, COLUMN AND PAGE\-BREAKS +.SH ADDITIONAL BREAKS - LINEBREAKS WITHIN OBJECTS, COLUMN AND PAGE-BREAKS -.SH LINE\-BREAKS +.SH LINE-BREAKS -.br +.BR To break a line within a "paragraph object", two backslashes \e\e with a space before and a space or newline after them may be used. @@ -2257,34 +2200,33 @@ and a space or newline after them \e\e may be used. .fi -.br +.BR 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). .SH PAGE BREAKS -.br +.BR 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: -.br +.BR page new =\e= or breaks the page, starts a new page. -.br -page break \-\\- or breaks a column, starts a new column, if using columns, +.BR +page break -\\- or breaks a column, starts a new column, if using columns, else breaks the page, starts a new page. - .nf -\-\e\e\- +-\e\e- + or <:pb> .fi -.br +.BR or - .nf =\e\e= or @@ -2293,143 +2235,140 @@ or .SH BOOK INDEX -.br +.BR To make an index append to paragraph the book index term relates to it, using an equal sign and curly braces. -.br -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. - +.BR +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. .nf - Paragraph containing main term and sub\-term. - ={Main term:sub\-term} + Paragraph containing main term and sub-term. + ={Main term:sub-term} .fi -.br +.BR The index syntax starts on a new line, but there should not be an empty line between paragraph and index markup. -.br +.BR The structure of the resulting index would be: .nf Main term, 1 - sub\-term, 1 + sub-term, 1 .fi -.br +.BR 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. .nf - Paragraph containing main term, second term and sub\-term. - ={first term; second term: sub\-term} + Paragraph containing main term, second term and sub-term. + ={first term; second term: sub-term} .fi -.br +.BR The structure of the resulting index would be: - .nf First term, 1, Second term, 1, - sub\-term, 1 + sub-term, 1 .fi -.br -If multiple sub\-terms appear under one paragraph, they are separated under the +.BR +If multiple sub-terms appear under one paragraph, they are separated under the main term heading from each other by a pipe symbol. - .nf - 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 + 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 .fi -.br -The plus one in the example provided indicates the first sub\-term spans one +.BR +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: - .nf Main term, 1, - sub\-term, 1\-3, - second sub\-term, 1, + sub-term, 1-3, + second sub-term, 1, .fi .SH COMPOSITE DOCUMENTS MARKUP -.br -.br +.BR 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 -.B \.ssm +.B .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 -.B \.sst +.B .sst regular markup file, or -.B \.ssi +.B .ssi (insert/information) A secondary file of the composite document is built prior to processing with the same prefix and the suffix -.B \._sst +.B ._sst -.br +.BR basic markup for importing a document into a master document .nf << filename1.sst + << filename2.ssi .fi -.br +.BR The form described above should be relied on. Within the .I Vim editor it results in the text thus linked becoming hyperlinked to the document it is calling in which is convenient for editing. .SH SISU FILETYPES -.br -.br +.BR .B SiSU has .I plaintext and binary filetypes, and can process either type of document. -.SH .SST \.SSM \.SSI MARKED UP PLAIN TEXT +.SH .SST .SSM .SSI MARKED UP PLAIN TEXT .TP -.B SiSU¤b〕 documents are prepared as plain\-text (utf\-8) files with +.B SiSU +documents are prepared as plain-text (utf-8) files with .B SiSU markup. They may make reference to and contain images (for example), which are stored in the directory beneath them _sisu/image. 〔b¤SiSU .I 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. +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. -.br +.BR .B 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. -.br +.BR .B SiSU source markup can be shared with the command: -.br - sisu \-s [filename] +.BR + sisu -s [filename] -.SH SISU TEXT \- REGULAR FILES (.SST) +.SH SISU TEXT - REGULAR FILES (.SST) -.br +.BR The most common form of document in .B SiSU, see the section on @@ -2438,15 +2377,15 @@ markup. .SH SISU MASTER FILES (.SSM) -.br +.BR Composite documents which incorporate other .B SiSU documents which may be either regular .B SiSU -text \.sst which may be generated independently, or inserts prepared solely for +text .sst which may be generated independently, or inserts prepared solely for the purpose of being incorporated into one or more master documents. -.br +.BR The mechanism by which master files incorporate other documents is described as one of the headings under under .B SiSU @@ -2454,48 +2393,46 @@ markup in the .B SiSU manual. -.br +.BR 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 +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. -.br +.BR Note: a secondary file of the composite document is built prior to processing -with the same prefix and the suffix \._sst [^19] - +with the same prefix and the suffix ._sst [^19] .SH SISU INSERT FILES (.SSI) -.br +.BR Inserts are documents prepared solely for the purpose of being incorporated into one or more master documents. They resemble regular .B SiSU text files except they are ignored by the .B SiSU -processor. Making a file a \.ssi file is a quick and convenient way of flagging +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. +.SH SISUPOD, ZIPPED BINARY CONTAINER (SISUPOD.ZIP, .SSP) -.SH SISUPOD, ZIPPED BINARY CONTAINER (SISUPOD.ZIP, \.SSP) - -.br +.BR A sisupod is a zipped .B SiSU text file or set of .B SiSU text files and any associated images that they contain (this will be extended -to include sound and multimedia\-files) +to include sound and multimedia-files) .TP .B SiSU .I 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 +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. -.br +.BR 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 @@ -2503,201 +2440,204 @@ prepared .B SiSU documents. -.br +.BR The command to create a sisupod is: -.br - sisu \-S [filename] +.BR + sisu -S [filename] -.br +.BR Alternatively, make a pod of the contents of a whole directory: -.br - sisu \-S +.BR + sisu -S -.br +.BR .B 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. -.br +.BR <http://www.sisudoc.org/sisu/sisu_commands> -.br +.BR <http://www.sisudoc.org/sisu/sisu_manual> .SH CONFIGURATION -.br .SH CONFIGURATION FILES .SH CONFIG.YML -.br +.BR .B 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. -.br +.BR The .B SiSU configuration file is a yaml file, which means indentation is significant. -.br +.BR .B SiSU resource configuration is determined by looking at the following files if they exist: -.br +.BR ./_sisu/v4/sisurc.yml -.br +.BR ./_sisu/sisurc.yml -.br +.BR ~/.sisu/v4/sisurc.yml -.br +.BR ~/.sisu/sisurc.yml -.br +.BR /etc/sisu/v4/sisurc.yml -.br +.BR /etc/sisu/sisurc.yml -.br +.BR The search is in the order listed, and the first one found is used. -.br +.BR In the absence of instructions in any of these it falls back to the internal program defaults. -.br +.BR Configuration determines the output and processing directories and the database access details. -.br +.BR If .B SiSU is installed a sample sisurc.yml may be found in /etc/sisu/sisurc.yml .SH SISU_DOCUMENT_MAKE -.br +.BR 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. -.br +.BR The search order is as for resource configuration: -.br +.BR ./_sisu/v4/sisu_document_make -.br +.BR ./_sisu/sisu_document_make -.br +.BR ~/.sisu/v4/sisu_document_make -.br +.BR ~/.sisu/sisu_document_make -.br +.BR /etc/sisu/v4/sisu_document_make -.br +.BR /etc/sisu/sisu_document_make -.br +.BR A sample sisu_document_make can be found in the _sisu/ directory under along with the provided sisu markup samples. -.SH CSS \- CASCADING STYLE SHEETS (FOR HTML, XHTML AND XML) -.br +.SH CSS - CASCADING STYLE SHEETS (FOR HTML, XHTML AND XML) -.br +.BR CSS files to modify the appearance of .B SiSU html, .I XHTML or .I XML -may be placed in the configuration directory: \./_sisu/css ; ~/.sisu/css or; +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. +command sisu -CC. -.br +.BR 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. -.br +.BR .I HTML: html. css -.br +.BR .I XML DOM: dom.css -.br +.BR .I XML SAX: sax.css -.br +.BR .I XHTML: xhtml. css -.br +.BR The default homepage may use homepage.css or html. css -.br +.BR Under consideration is to permit the placement of a CSS file with a different name in directory _sisu/css directory or equivalent.[^20] -.SH ORGANISING CONTENT \- DIRECTORY STRUCTURE AND MAPPING -.br +.SH ORGANISING CONTENT - DIRECTORY STRUCTURE AND MAPPING -.br +.BR .B SiSU v3 has new options for the source directory tree, and output directory structures of which there are 3 alternatives. .SH DOCUMENT SOURCE DIRECTORY -.br +.BR 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. - +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. .SH GENERAL DIRECTORIES .nf -./subject_name/ + ./subject_name/ + % files stored at this level e.g. sisu_manual.sst or -% for sisu v3 may be under language sub\-directories +% 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 + + ./subject_name/en + + ./subject_name/fr + + ./subject_name/es + + ./subject_name/_sisu + + ./subject_name/_sisu/css + + ./subject_name/_sisu/image .fi .SH DOCUMENT OUTPUT DIRECTORY STRUCTURES .SH OUTPUT DIRECTORY ROOT -.br +.BR 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 @@ -2705,10 +2645,10 @@ 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) +stripped (.sst .ssm) -.br -The last part of a directory path, representing the sub\-directory in which a +.BR +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 @@ -2725,7 +2665,7 @@ appearance. .SH ALTERNATIVE OUTPUT STRUCTURES -.br +.BR There are 3 possibile output structures described as being, by language, by filetype or by filename, the selection is made in sisurc.yml @@ -2738,171 +2678,190 @@ output_dir_structure_by: language #(language & filetype, preferred?) .SH BY LANGUAGE -.br +.BR The by language directory structure places output files -.br +.BR The by language directory structure separates output files by language code (all files of a given language), and within the language directory by filetype. -.br +.BR Its selection is configured in sisurc.yml -.br +.BR output_dir_structure_by: language .nf - |\-\- 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 + |-- 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 .fi -.br +.BR #by: language subject_dir/en/manifest/filename.html .SH BY FILETYPE -.br +.BR 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. -.br +.BR Its selection is configured in sisurc.yml -.br +.BR output_dir_structure_by: filetype .nf - |\-\- 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 + |-- 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 .fi -.br +.BR #by: filetype subject_dir/html/filename/manifest.en.html .SH BY FILENAME -.br +.BR The by filename directory structure places most output of a particular file (the different filetypes) in a common directory. -.br +.BR Its selection is configured in sisurc.yml -.br +.BR output_dir_structure_by: filename .nf - |\-\- 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 + |-- 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 .fi -.br +.BR #by: filename subject_dir/filename/manifest.en.html .SH REMOTE DIRECTORIES .nf -./subject_name/ + ./subject_name/ + % containing sub_directories named after the generated files from which they are made - \./subject_name/src + + ./subject_name/src + % contains shared source files text and binary e.g. sisu_manual.sst and sisu_manual.sst.zip - \./subject_name/_sisu + + ./subject_name/_sisu + % configuration file e.g. sisurc.yml - \./subject_name/_sisu/skin + + ./subject_name/_sisu/skin + % skins in various skin directories doc, dir, site, yml - \./subject_name/_sisu/css - \./subject_name/_sisu/image + + ./subject_name/_sisu/css + + ./subject_name/_sisu/image + % images for documents contained in this directory - \./subject_name/_sisu/mm + + ./subject_name/_sisu/mm .fi .SH SISUPOD .nf -./sisupod/ + ./sisupod/ + % files stored at this level e.g. sisu_manual.sst - \./sisupod/_sisu + + ./sisupod/_sisu + % configuration file e.g. sisurc.yml - \./sisupod/_sisu/skin + + ./sisupod/_sisu/skin + % skins in various skin directories doc, dir, site, yml - \./sisupod/_sisu/css - \./sisupod/_sisu/image + + ./sisupod/_sisu/css + + ./sisupod/_sisu/image + % images for documents contained in this directory - \./sisupod/_sisu/mm + + ./sisupod/_sisu/mm .fi .SH ORGANISING CONTENT .SH HOMEPAGES -.br -.br +.BR .B SiSU -is about the ability to auto\-generate documents. Home pages are regarded as +is about the ability to auto-generate documents. Home pages are regarded as custom built items, and are not created by .B SiSU. More accurately, @@ -2911,179 +2870,176 @@ 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: -.br +.BR 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) -.br +.BR 2. through providing what you want as the home page in a skin, -.br +.BR 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. -.SH HOME PAGE AND OTHER CUSTOM BUILT PAGES IN A SUB\-DIRECTORY +.SH HOME PAGE AND OTHER CUSTOM BUILT PAGES IN A SUB-DIRECTORY -.br +.BR 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 +for the configuration directory, namely ./_sisu ; ~/_sisu ; /etc/sisu From there they are copied to the root of the output directory with the command: -.br - sisu \-CC - +.BR + sisu -CC .SH MARKUP AND OUTPUT EXAMPLES -.br .SH MARKUP EXAMPLES -.br +.BR 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> +-markup-sample package available off <http://sources.sisudoc.org> -.br +.BR 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. .SH SISU MARKUP SAMPLES -.br +.BR A few additional sample books prepared as sisu markup samples, output formats to be generated using .B 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 +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 .B Debian Project as they have requirements that do not meet the .B 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. +works be used only non-commercially. -.br +.BR .I Accelerando, Charles Stross (2005) accelerando.charles_stross.sst -.br +.BR .I Alice's Adventures in Wonderland, Lewis Carroll (1865) alices_adventures_in_wonderland.lewis_carroll.sst -.br +.BR .I CONTENT, Cory Doctorow (2008) content.cory_doctorow.sst -.br +.BR .I Democratizing Innovation, Eric von Hippel (2005) democratizing_innovation.eric_von_hippel.sst -.br +.BR .I Down and Out in the Magic Kingdom, Cory Doctorow (2003) down_and_out_in_the_magic_kingdom.cory_doctorow.sst -.br +.BR .I For the Win, Cory Doctorow (2010) for_the_win.cory_doctorow.sst -.br -.I Free as in Freedom \- Richard Stallman's Crusade for Free Software, +.BR +.I 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 -.br -.I Free as in Freedom 2.0 \- Richard Stallman and the Free Software Revolution, +.BR +.I 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 -.br -.I Free Culture \- How Big Media Uses Technology and the Law to Lock Down +.BR +.I 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 -.br -.I Free For All \- How Linux and the Free Software Movement Undercut the High +.BR +.I Free For All - How Linux and the Free Software Movement Undercut the High Tech Titans, Peter Wayner (2002) free_for_all.peter_wayner.sst -.br +.BR .I GNU GENERAL PUBLIC LICENSE v2, Free Software Foundation (1991) gpl2.fsf.sst -.br +.BR .I GNU GENERAL PUBLIC LICENSE v3, Free Software Foundation (2007) gpl3.fsf.sst -.br +.BR .I Gulliver's Travels, Jonathan Swift (1726 / 1735) gullivers_travels.jonathan_swift.sst -.br +.BR .I Little Brother, Cory Doctorow (2008) little_brother.cory_doctorow.sst -.br +.BR .I The Cathederal and the Bazaar, Eric Raymond (2000) the_cathedral_and_the_bazaar.eric_s_raymond.sst -.br -.I The Public Domain \- Enclosing the Commons of the Mind, +.BR +.I The Public Domain - Enclosing the Commons of the Mind, James Boyle (2008) the_public_domain.james_boyle.sst -.br -.I The Wealth of Networks \- How Social Production Transforms Markets and +.BR +.I The Wealth of Networks - How Social Production Transforms Markets and Freedom, Yochai Benkler (2006) the_wealth_of_networks.yochai_benkler.sst -.br +.BR .I Through the Looking Glass, Lewis Carroll (1871) through_the_looking_glass.lewis_carroll.sst -.br -.I Two Bits \- The Cultural Significance of Free Software, +.BR +.I Two Bits - The Cultural Significance of Free Software, Christopher Kelty (2008) two_bits.christopher_kelty.sst -.br +.BR .I UN Contracts for International Sale of Goods, UN (1980) un_contracts_international_sale_of_goods_convention_1980.sst -.br +.BR .I Viral Spiral, David Bollier (2008) viral_spiral.david_bollier.sst -.SH SISU SEARCH \- INTRODUCTION -.br +.SH SISU SEARCH - INTRODUCTION -.br +.BR .B SiSU output can easily and conveniently be indexed by a number of standalone indexing tools, such as Lucene, Hyperestraier. -.br +.BR Because the document structure of sites created is clearly defined, and the text .I object citation system @@ -3091,7 +3047,7 @@ 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. -.br +.BR In addition to this .B SiSU has the ability to populate a relational sql type database with documents at an @@ -3102,11 +3058,10 @@ each document, which can be viewed within the database directly or in various output formats. .SH SQL -.br .SH POPULATING SQL TYPE DATABASES -.br +.BR .B SiSU feeds sisu markupd documents into sql type databases .I PostgreSQL @@ -3114,39 +3069,39 @@ feeds sisu markupd documents into sql type databases .I SQLite [^22] database together with information related to document structure. -.br +.BR 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: -.br +.BR * one containing semantic (and other) headers, including, title, author, subject, (the .I Dublin Core. ..); -.br - * another the substantive texts by individual "paragraph" (or object) \- - along with structural information, each paragraph being identifiable by its +.BR + * 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 -.br - * a third containing endnotes cross\-referenced back to the paragraph from +.BR + * a third containing endnotes cross-referenced back to the paragraph from which they are referenced (both in formatted and clean text versions for searching). -.br +.BR * 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. -.br +.BR There is of course the possibility to add further structures. -.br +.BR At this level .B SiSU loads a relational database with documents chunked into objects, their smallest @@ -3156,7 +3111,7 @@ 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. -.br +.BR Being able to search a relational database at an object level with the .B SiSU citation system is an effective way of locating content generated by @@ -3173,181 +3128,176 @@ headings etc. (as the is incorporated it is easy to make use of that as well). .SH POSTGRESQL -.br .SH NAME -.br +.BR .B SiSU -\- Structured information, Serialized Units \- a document publishing system, +- Structured information, Serialized Units - a document publishing system, postgresql dependency package .SH DESCRIPTION -.br +.BR 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 .B SiSU to populate a postgresql database, this being part of .B SiSU -\- man sisu) . +- man sisu) . .SH SYNOPSIS -.br - sisu \-D [instruction] [filename/wildcard \ if \ required] - -.br - sisu \-D \-\-pg \-\-[instruction] [filename/wildcard \ if \ required] +.BR + sisu -D [instruction] [filename/wildcard if required] +.BR + sisu -D --pg --[instruction] [filename/wildcard if required] .SH COMMANDS -.br +.BR 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 (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, +alternatively --sqlite or --pgsql may be used -.br -.B \-D or \-\-pgsql +.BR +.B -D or --pgsql may be used interchangeably. .SH CREATE AND DESTROY DATABASE .TP -.B \-\-pgsql \-\-createall +.B --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) .TP -.B sisu \-D \-\-createdb +.B sisu -D --createdb creates database where no database existed before .TP -.B sisu \-D \-\-create +.B sisu -D --create creates database tables where no database tables existed before .TP -.B sisu \-D \-\-Dropall +.B 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). .TP -.B sisu \-D \-\-recreate +.B sisu -D --recreate destroys existing database and builds a new empty database structure .SH IMPORT AND REMOVE DOCUMENTS .TP -.B sisu \-D \-\-import \-v [filename/wildcard] +.B 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). .TP -.B sisu \-D \-\-update \-v [filename/wildcard] +.B sisu -D --update -v [filename/wildcard] updates file contents in database .TP -.B sisu \-D \-\-remove \-v [filename/wildcard] +.B sisu -D --remove -v [filename/wildcard] removes specified document from postgresql database. .SH SQLITE -.br .SH NAME -.br +.BR .B SiSU -\- Structured information, Serialized Units \- a document publishing system. +- Structured information, Serialized Units - a document publishing system. .SH DESCRIPTION -.br +.BR 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 .B SiSU to populate an sqlite database, this being part of .B SiSU -\- man sisu) . +- man sisu) . .SH SYNOPSIS -.br - sisu \-d [instruction] [filename/wildcard \ if \ required] +.BR + sisu -d [instruction] [filename/wildcard if required] -.br - sisu \-d \-\-(sqlite|pg) \-\-[instruction] [filename/wildcard \ if \ - required] +.BR + sisu -d --(sqlite|pg) --[instruction] [filename/wildcard if required] .SH COMMANDS -.br +.BR 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 (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, +alternatively --sqlite or --pgsql may be used -.br -.B \-d or \-\-sqlite +.BR +.B -d or --sqlite may be used interchangeably. .SH CREATE AND DESTROY DATABASE .TP -.B \-\-sqlite \-\-createall +.B --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) .TP -.B sisu \-d \-\-createdb +.B sisu -d --createdb creates database where no database existed before .TP -.B sisu \-d \-\-create +.B sisu -d --create creates database tables where no database tables existed before .TP -.B sisu \-d \-\-dropall +.B 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). .TP -.B sisu \-d \-\-recreate +.B sisu -d --recreate destroys existing database and builds a new empty database structure .SH IMPORT AND REMOVE DOCUMENTS .TP -.B sisu \-d \-\-import \-v [filename/wildcard] +.B 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). .TP -.B sisu \-d \-\-update \-v [filename/wildcard] +.B sisu -d --update -v [filename/wildcard] updates file contents in database .TP -.B sisu \-d \-\-remove \-v [filename/wildcard] +.B sisu -d --remove -v [filename/wildcard] removes specified document from sqlite database. .SH INTRODUCTION -.br -.SH SEARCH \- DATABASE FRONTEND SAMPLE, UTILISING DATABASE AND SISU FEATURES, +.SH SEARCH - DATABASE FRONTEND SAMPLE, UTILISING DATABASE AND SISU FEATURES, INCLUDING OBJECT CITATION NUMBERING (BACKEND CURRENTLY POSTGRESQL) -.br +.BR Sample search frontend <http://search.sisudoc.org> [^23] A small database and -sample query front\-end (search from) that makes use of the citation system, +sample query front-end (search from) that makes use of the citation system, .I object citation numbering to demonstrates functionality.[^24] -.br +.BR .B 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 @@ -3365,23 +3315,22 @@ database. You can then refer to one of the other outputs or in the database expand the text within the matched objects (paragraphs) in the documents matched. -.br +.BR 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] .TP -.B sisu \-F \-\-webserv\-webrick +.B sisu -F --webserv-webrick builds a cgi web search frontend for the database created -.br +.BR The following is feedback on the setup on a machine provided by the help command: -.br - sisu \-\-help sql - +.BR + sisu --help sql .nf Postgresql user: ralph @@ -3393,177 +3342,173 @@ sqlite dbi connect DBI:SQLite:/home/ralph/sisu_www/sisu/sisu_sqlite.db .fi -.br +.BR Note on databases built -.br -By default, [unless \ otherwise \ specified] databases are built on a directory +.BR +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] - +used. [otherwise a manual mapping for the collection is necessary] .SH SEARCH FORM .TP -.B sisu \-F -generates a sample search form, which must be copied to the web\-server cgi +.B sisu -F +generates a sample search form, which must be copied to the web-server cgi directory .TP -.B sisu \-F \-\-webserv\-webrick +.B 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 +copied to the web-server cgi directory .TP -.B sisu \-W +.B sisu -W starts the webrick server which should be available wherever sisu is properly installed -.br +.BR The generated search form must be copied manually to the webserver directory as instructed .SH SISU_WEBRICK -.br .SH NAME -.br +.BR .B SiSU -\- Structured information, Serialized Units \- a document publishing system +- Structured information, Serialized Units - a document publishing system .SH SYNOPSIS -.br +.BR sisu_webrick [port] -.br +.BR or -.br -sisu \-W [port] +.BR +sisu -W [port] .SH DESCRIPTION -.br +.BR sisu_webrick is part of .B SiSU (man sisu) sisu_webrick starts .B Ruby -' s Webrick web\-server and points it to the directories to which +' s Webrick web-server and points it to the directories to which .B SiSU output is written, providing a list of these directories (assuming .B SiSU is in use and they exist). -.br +.BR 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). .SH SUMMARY OF MAN PAGE -.br +.BR 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] +or using the sisu command with the -W flag: sisu -W [port] -.br +.BR where no port is given and settings are unchanged the default port is 8081 .SH DOCUMENT PROCESSING COMMAND FLAGS -.br -sisu \-W [port] starts +.BR +sisu -W [port] starts .B Ruby -Webrick web\-server, serving +Webrick web-server, serving .B 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 .SH SUMMARY OF FEATURES -.br -.br -* sparse/minimal markup (clean utf\-8 source texts). Documents are prepared in -a single -.I UTF\-8 +.BR +* sparse/minimal markup (clean utf-8 source texts). Documents are prepared in a +single +.I 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. -.br +.BR * markup is easily readable/parsable by the human eye, (basic markup is simpler and more sparse than the most basic .I HTML -) , [this \ may \ also \ be \ converted \ to \ .I \ XML \ representations \ of -\ the \ same \ input/source \ document]. +) , [this may also be converted to +.I XML +representations of the same input/source document]. -.br +.BR * 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 +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. .B 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) +practical standard ways of representing documents [be that browser viewing, +paper publication, sql search etc.] (html, epub, xml, odf, latex, pdf, sql) -.br +.BR * 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: -.br +.BR * .I HTML -\- both as a single scrollable text and a segmented document +- both as a single scrollable text and a segmented document -.br +.BR * .I XHTML -.br +.BR * .I EPUB -.br +.BR * .I XML -\- both in sax and dom style xml structures for further development as required +- both in sax and dom style xml structures for further development as required -.br +.BR * .I ODT -\- Open Document Format text, the iso standard for document storage +- Open Document Format text, the iso standard for document storage -.br +.BR * .I LaTeX -\- used to generate pdf +- used to generate pdf -.br +.BR * .I PDF (via .I LaTeX ) -.br +.BR * .I SQL -\- population of an sql database ( +- population of an sql database ( .I PostgreSQL or .I SQLite ) , (at the same object level that is used to cite text within a document) -.br +.BR 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 @@ -3574,7 +3519,7 @@ making possible .I granular search (and related possibilities)) -.br +.BR * 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 @@ -3589,51 +3534,51 @@ oriented, (pdf, xml, sqlite, postgresql) , this numbering system can be used to reference content. -.br +.BR * Granular search within documents. .I 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]. +paragraphs of the documents in the database; [output indexing also work well +with search indexing tools like hyperestraier]. -.br +.BR * 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 +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 -.br +.BR * .I SQL search aside, documents are generated as required and static once generated. -.br +.BR * 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) -.br +.BR * document source ( .I plaintext -utf\-8) if shared on the net may be used as input and processed locally to +utf-8) if shared on the net may be used as input and processed locally to produce the different document outputs -.br +.BR * 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 -.br +.BR * generated document outputs may automatically be posted to remote sites. -.br +.BR * for basic document generation, the only software dependency is .B Ruby, and a few standard Unix tools (this covers @@ -3647,15 +3592,15 @@ and a few standard Unix tools (this covers .I LaTeX generated to pdf, a latex processor like tetex or texlive. -.br +.BR * as a developers tool it is flexible and extensible -.br +.BR Syntax highlighting for .B SiSU markup is available for a number of text editors. -.br +.BR .B 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 @@ -3663,15 +3608,15 @@ 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 -.br +.BR 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) \... +paper publication (e.g. pdf) ... -.br +.BR 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 @@ -3686,160 +3631,128 @@ objects include: headings, paragraphs, verse, tables, images, but not footnotes/endnotes which are numbered separately and tied to the object from which they are referenced. -.br +.BR .TP .BI 2. -i.e. the - -.br -.I HTML, - -.br -.I PDF, - -.br -.I EPUB, - -.br -.I ODT - -.br -outputs are each built individually and optimised for that form of +i.e. the HTML, PDF, EPUB, ODT outputs are each built individually and optimised for that form of presentation, rather than for example the html being a saved version of the odf, or the pdf being a saved version of the html. -.br +.BR .TP .BI 3. the different heading levels -.br +.BR .TP .BI 4. units of text, primarily paragraphs and headings, also any tables, poems, code-blocks -.br +.BR .TP .BI 5. An open standard format for e-books -.br +.BR .TP .BI 6. -Open Document Format ( - -.br -.I ODF - -.br -) text +Open Document Format ( ODF ) text -.br +.BR .TP .BI 7. Specification submitted by Adobe to ISO to become a full open ISO -specification - -.br -<http://www.linux-watch.com/news/NS7542722606.html> +specification <http://www.linux-watch.com/news/NS7542722606.html> -.br +.BR .TP .BI 8. ISO standard ISO/IEC 26300:2006 -.br +.BR .TP .BI *1. square brackets -.br +.BR .TP .BI *2. square brackets -.br +.BR .TP .BI +1. square brackets -.br +.BR .TP .BI 9. <http://www.jus.uio.no/sisu/man/> -.br +.BR .TP .BI 10. <http://www.jus.uio.no/sisu/man/sisu.1.html> -.br +.BR .TP .BI 11. From sometime after SiSU 0.58 it should be possible to describe SiSU markup using SiSU, which though not an original design goal is useful. -.br +.BR .TP .BI 12. -files should be prepared using - -.br -.I UTF-8 +files should be prepared using UTF-8 character encoding -.br -character encoding - -.br +.BR .TP .BI 13. a footnote or endnote -.br +.BR .TP .BI 14. self contained endnote marker & endnote in one -.br +.BR .TP .BI *. unnumbered asterisk footnote/endnote, insert multiple asterisks if required -.br +.BR .TP .BI **. another unnumbered asterisk footnote/endnote -.br +.BR .TP .BI *3. editors notes, numbered asterisk footnote/endnote series -.br +.BR .TP .BI +2. editors notes, numbered asterisk footnote/endnote series -.br +.BR .TP .BI 15. <http://www.sisudoc.org/> -.br +.BR .TP .BI 16. <http://www.ruby-lang.org/en/> -.br +.BR .TP .BI 18. Table from the Wealth of Networks by Yochai Benkler - -.br <http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler> -.br +.BR .TP .BI 19. \.ssc (for composite) is under consideration but \._sst makes clear that this @@ -3848,38 +3761,37 @@ 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. -.br +.BR .TP -.BI 21. -<http://www.postgresql.org/> - -.br -<http://advocacy.postgresql.org/> +.BI 20. +SiSU has worked this way in the past, though this was dropped as it was +thought the complexity outweighed the flexibility, however, the balance was +rather fine and this behaviour could be reinstated. -.br +.BR +.TP +.BI 21. +<http://www.postgresql.org/> <http://advocacy.postgresql.org/> <http://en.wikipedia.org/wiki/Postgresql> -.br +.BR .TP .BI 22. -<http://www.hwaci.com/sw/sqlite/> +<http://www.hwaci.com/sw/sqlite/> <http://en.wikipedia.org/wiki/Sqlite> -.br -<http://en.wikipedia.org/wiki/Sqlite> - -.br +.BR .TP .BI 23. <http://search.sisudoc.org> -.br +.BR .TP .BI 24. (which could be extended further with current back-end). As regards scaling of the database, it is as scalable as the database (here Postgresql) and hardware allow. -.br +.BR .TP .BI 25. of this feature when demonstrated to an IBM software innovations evaluator @@ -3889,7 +3801,7 @@ 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. -.br +.BR .TP .SH SEE ALSO |