Title: SiSU - Manual Creator: Ralph Amissah Rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3; Subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search Publisher: SiSU ‹<text:a xlink:type='simple' xlink:href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</text:a>› (this copy) Date created: 2002-08-28 Date issued: 2002-08-28 Date available: 2002-08-28 Date modified: 2011-02-07 Date: 2008-07-21 Sourcefile: sisu_manual.ssm.sst Filetype: SiSU text insert 2.0 Source digest: SHA256(sisu_manual.ssm.sst)= 6e9af9f4f6be91b82bddcaa3ed90e80f9a4a25d878cf4a64c168e41f223e246d Skin digest: SHA256(skin_sisu_manual.rb)= 689f79b53be3d51460af31dc82d6cbab4a253079db263cd715c8254a6af60eb8 Generated by: Generated by: SiSU 2.8.2 of 2011w10/5 (2011-03-11) Ruby version: ruby 1.8.7 (2008-08-11 patchlevel 72) [i486-linux] Document (dal) last generated: Fri Mar 11 23:48:55 +0100 2011 1 SiSU - Manual,
Ralph Amissah 2 What is SiSU? 3 1. Introduction - What is SiSU? 4 SiSU is a framework for document structuring, publishing (in multiple open standard formats) and search, comprising of: (a) a lightweight document structure and presentation markup syntax; and (b) an accompanying engine for generating standard document format outputs from documents prepared in sisu markup syntax, which is able to produce multiple standard outputs (including the population of sql databases) that (can) share a common numbering system for the citation of text within a document. 5 SiSU is developed under an open source, software libre license (GPL3). 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. 6 SiSU both defines a markup syntax and provides an engine that produces open standards format outputs from documents prepared with SiSU markup. From a single lightly prepared document sisu custom builds several standard output formats which share a common (text object) numbering system for citation of content within a document (that also has implications for search). The sisu engine works with an abstraction of the document's structure and content from which it is possible to generate different forms of representation of the document. Significantly SiSU markup is more sparse than html and outputs which include html, EPUB, LaTeX, landscape and portrait pdfs, Open Document Format (ODF), all of which can be added to and updated. SiSU is also able to populate SQL type databases at an object level, which means that searches can be made with that degree of granularity. 7 Source document preparation and output generation is a two step process: (i) document source is prepared, that is, marked up in sisu markup syntax and (ii) the desired output subsequently generated by running the sisu engine against document source. Output representations if updated (in the sisu engine) can be generated by re-running the engine against the prepared source. Using SiSU markup applied to a document, SiSU custom builds (to take advantage of the strengths of different ways of representing documents) various standard open output formats including plain text, HTML, XHTML, XML, EPUB, OpenDocument, LaTeX or PDF files, and populate an SQL database with objects1 (equating generally to paragraph-sized chunks) so searches may be performed and matches returned with that degree of granularity ( e.g. your search criteria is met by these documents and at these locations within each document). Document output formats share a common object numbering system for locating content. This is particularly suitable for "published" works (finalized texts as opposed to works that are frequently changed or updated) for which it provides a fixed means of reference of content. 1 objects include: headings, paragraphs, verse, tables, images, but not footnotes/endnotes which are numbered separately and tied to the object from which they are referenced. 8 In preparing a SiSU document you optionally provide semantic information related to the document in a document header, and in marking up the substantive text provide information on the structure of the document, primarily indicating heading levels and footnotes. You also provide information on basic text attributes where used. The rest is automatic, sisu from this information custom builds2 the different forms of output requested. 2 i.e. the html, pdf, epub, odf outputs are each built individually and optimised for that form of presentation, rather than for example the html being a saved version of the odf, or the pdf being a saved version of the html. 9 SiSU works with an abstraction of the document based on its structure which is comprised of its headings3 and objects4, which enables SiSU to represent the document in many different ways, and to take advantage of the strengths of different ways of presenting documents. The objects are numbered, and these numbers can be used to provide a common basis for citing material within a document across the different output format types. This is significant as page numbers are not well suited to the digital age, in web publishing, changing a browser's default font or using a different browser can mean that text will appear on a different page; and publishing in different formats, html, landscape and portrait pdf etc. again page numbers are not useful to cite text. Dealing with documents at an object level together with object numbering also has implications for search that SiSU is able to take advantage of. 3 the different heading levels 4 units of text, primarily paragraphs and headings, also any tables, poems, code-blocks 10 One of the challenges of maintaining documents is to keep them in a format that allows use of them independently of proprietary platforms. Consider issues related to dealing with legacy proprietary formats today and what guarantee you have that old proprietary formats will remain (or can be read without proprietary software/equipment) in 15 years time, or the way the way in which html has evolved over its relatively short span of existence. SiSU provides the flexibility of producing documents in multiple non-proprietary open formats including html, pdf5 ODF,6 and EPUB.7 Whilst SiSU relies on software, the markup is uncomplicated and minimalistic which guarantees that future engines can be written to run against it. It is also easily converted to other formats, which means documents prepared in SiSU can be migrated to other document formats. Further security is provided by the fact that the software itself, SiSU is available under GPL3 a licence that guarantees that the source code will always be open, and free as in libre, which means that that code base can be used, updated and further developed as required under the terms of its license. Another challenge is to keep up with a moving target. SiSU permits new forms of output to be added as they become important, (Open Document Format text was added in 2006 when it became an ISO standard for office applications and the archival of documents), EPUB was introduced in 2009; and allows the technical representations existing output to be updated (html has evolved and the related module has been updated repeatedly over the years, presumably when the World Wide Web Consortium (w3c) finalises html 5 which is currently under development, the html module will again be updated allowing all existing documents to be regenerated as html 5). 5 Specification submitted by Adobe to ISO to become a full open ISO specification
<http://www.linux-watch.com/news/NS7542722606.html> 6 ISO standard ISO/IEC 26300:2006 7 An open standard format for e-books 11 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. 12 SiSU also provides other features such as concordance files and document content certificates, and the working against an abstraction of document structure has further possibilities for the research and development of other document representations, the availability of objects is useful for example for topic maps and thesauri, together with the flexibility of SiSU offers great possibilities. 13 SiSU is primarily for published works, which can take advantage of the citation system to reliably reference its documents. SiSU works well in a complementary manner with such collaborative technologies as Wikis, which can take advantage of and be used to discuss the substance of content prepared in SiSU. 14 <http://www.sisudoc.org/> 15 <http://www.jus.uio.no/sisu> 16 2. How does sisu work? 17 SiSU markup is fairly minimalistic, it consists of: a (largely optional) document header, made up of information about the document (such as when it was published, who authored it, and granting what rights) and any processing instructions; and markup within the substantive text of the document, which is related to document structure and typeface. SiSU must be able to discern the structure of a document, (text headings and their levels in relation to each other), either from information provided in the document header or from markup within the text (or from a combination of both). Processing is done against an abstraction of the document comprising of information on the document's structure and its objects,[2] which the program serializes (providing the object numbers) and which are assigned hash sum values based on their content. This abstraction of information about document structure, objects, (and hash sums), provides considerable flexibility in representing documents different ways and for different purposes (e.g. search, document layout, publishing, content certification, concordance etc.), and makes it possible to take advantage of some of the strengths of established ways of representing documents, (or indeed to create new ones). 18 3. Summary of features 19 sparse/minimal markup (clean utf-8 source texts). Documents are prepared in a single UTF-8 file using a minimalistic mnemonic syntax. Typical literature, documents like "War and Peace" require almost no markup, and most of the headers are optional. 20 markup is easily readable/parsable by the human eye, (basic markup is simpler and more sparse than the most basic HTML), [this may also be converted to XML representations of the same input/source document]. 21 markup defines document structure (this may be done once in a header pattern-match description, or for heading levels individually); basic text attributes (bold, italics, underscore, strike-through etc.) as required; and semantic information related to the document (header information, extended beyond the Dublin core and easily further extended as required); the headers may also contain processing instructions. SiSU markup is primarily an abstraction of document structure and document metadata to permit taking advantage of the basic strengths of existing alternative practical standard ways of representing documents [be that browser viewing, paper publication, sql search etc.] (html, epub, xml, odf, latex, pdf, sql) 22 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: 23 html - both as a single scrollable text and a segmented document 24 xhtml 25 epub 26 XML - both in sax and dom style xml structures for further development as required 27 ODF - open document format, the iso standard for document storage 28 LaTeX - used to generate pdf 29 pdf (via LaTeX) 30 sql - population of an sql database, (at the same object level that is used to cite text within a document) 31 Also produces: concordance files; document content certificates (md5 or sha256 digests of headings, paragraphs, images etc.) and html manifests (and sitemaps of content). (b) takes advantage of the strengths implicit in these very different output types, (e.g. PDFs produced using typesetting of LaTeX, databases populated with documents at an individual object/paragraph level, making possible granular search (and related possibilities)) 32 ensuring content can be cited in a meaningful way regardless of selected output format. Online publishing (and publishing in multiple document formats) lacks a useful way of citing text internally within documents (important to academics generally and to lawyers) as page numbers are meaningless across browsers and formats. sisu seeks to provide a common way of pinpoint the text within a document, (which can be utilized for citation and by search engines). The outputs share a common numbering system that is meaningful (to man and machine) across all digital outputs whether paper, screen, or database oriented, (pdf, HTML, EPUB, xml, sqlite, postgresql), this numbering system can be used to reference content. 33 Granular search within documents. SQL databases are populated at an object level (roughly headings, paragraphs, verse, tables) and become searchable with that degree of granularity, the output information provides the object/paragraph numbers which are relevant across all generated outputs; it is also possible to look at just the matching paragraphs of the documents in the database; [output indexing also work well with search indexing tools like hyperestraier]. 34 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 35 SQL search aside, documents are generated as required and static once generated. 36 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) 37 document source (plaintext utf-8) if shared on the net may be used as input and processed locally to produce the different document outputs 38 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 39 generated document outputs may automatically be posted to remote sites. 40 for basic document generation, the only software dependency is Ruby, and a few standard Unix tools (this covers plaintext, HTML, EPUB, XML, ODF, LaTeX). To use a database you of course need that, and to convert the LaTeX generated to pdf, a latex processor like tetex or texlive. 41 as a developers tool it is flexible and extensible 42 Syntax highlighting for SiSU markup is available for a number of text editors. 43 SiSU is less about document layout than about finding a way with little markup to be able to construct an abstract representation of a document that makes it possible to produce multiple representations of it which may be rather different from each other and used for different purposes, whether layout and publishing, or search of content 44 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)... 45 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. 46 4. Help 47 4.1 SiSU Manual 48 The most up to date information on sisu should be contained in the sisu_manual, available at: 49 <http://sisudoc.org/sisu/sisu_manual/> 50 The manual can be generated from source, found respectively, either within the SiSU tarball or installed locally at: 51 ./data/doc/sisu/markup-samples/sisu_manual 52 /usr/share/doc/sisu/markup-samples/sisu_manual 53 move to the respective directory and type e.g.: 54 sisu sisu_manual.ssm 55 4.2 SiSU man pages 56 If SiSU is installed on your system usual man commands should be available, try: 57 man sisu 58 Most SiSU man pages are generated directly from sisu documents that are used to prepare the sisu manual, the sources files for which are located within the SiSU tarball at: 59 ./data/doc/sisu/markup-samples/sisu_manual 60 Once installed, directory equivalent to: 61 /usr/share/doc/sisu/markup-samples/sisu_manual 62 Available man pages are converted back to html using man2html: 63 /usr/share/doc/sisu/html/ 64 ./data/doc/sisu/html 65 An online version of the sisu man page is available here: 66 various sisu man pages 8 8 <http://www.jus.uio.no/sisu/man/> 67 sisu.1 9 9 <http://www.jus.uio.no/sisu/man/sisu.1.html> 68 4.3 SiSU built-in interactive help 69 This is particularly useful for getting the current sisu setup/environment information: 70 sisu --help 71 sisu --help [subject] 72 sisu --help commands 73 sisu --help markup 74 sisu --help env [for feedback on the way your system is setup with regard to sisu] 75 sisu -V [environment information, same as above command] 76 sisu (on its own provides version and some help information) 77 Apart from real-time information on your current configuration the 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). 78 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. 79 5. Commands Summary 80 5.1 Description 81 SiSU SiSU is a document publishing system, that from a simple single marked-up document, produces multiple of output formats including: plaintext, html, xhtml, XML, epub, odt (odf text), LaTeX, pdf, info, and SQL (PostgreSQL and SQLite), which share numbered text objects ("object citation numbering") and the same document structure information. For more see: <http://www.jus.uio.no/sisu> 82 5.2 Document Processing Command Flags 83 -a [filename/wildcard]
produces plaintext with Unix linefeeds and without markup, (object numbers are omitted), has footnotes at end of each paragraph that contains them [ -A for equivalent dos (linefeed) output file] [see -e for endnotes]. (Options include: --endnotes for endnotes --footnotes for footnotes at the end of each paragraph --unix for unix linefeed (default) --msdos for msdos linefeed) 84 -b [filename/wildcard]
see --xhtml 85 --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 86 --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 87 -C [--init-site]
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. 88 -CC
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. 89 -c [filename/wildcard]
see --color-toggle 90 --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 91 --delete [filename/wildcard]
see --zap 92 -D [instruction] [filename]
see --pg 93 -d [--db-[database type (sqlite|pg)]] --[instruction] [filename]
see --sqlite 94 --epub [filename/wildcard]
produces an epub document, [sisu version 2 only] (filename.epub). Alias -e 95 -e [filename/wildcard]
see --epub 96 -F [--webserv=webrick]
see --sample-search-form 97 --git [filename/wildcard]
produces or updates markup source file structure in a git repo (experimental and subject to change). Alias -g 98 -g [filename/wildcard]
see --git 99 --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. 100 --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 101 --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 102 -h [filename/wildcard]
see --html 103 -I [filename/wildcard]
see --texinfo 104 -i [filename/wildcard]
see --manpage 105 -L
prints license information. 106 --machine [filename/wildcard/url]
see --dal (document abstraction level/layer) 107 --maintenance [filename/wildcard/url]
maintenance mode files created for processing preserved and their locations indicated. (also see -V). Alias -M 108 --manpage [filename/wildcard]
produces man page of file, not suitable for all outputs. Alias -i 109 -M [filename/wildcard/url]
see --maintenance 110 -m [filename/wildcard/url]
see --dal (document abstraction level/layer) 111 --no-ocn
[with --html --pdf or --epub] switches off object citation numbering. Produce output without identifying numbers in margins of html or LaTeX/pdf output. 112 -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. 113 -n [filename/wildcard/url]
skip the creation of intermediate processing files (document abstraction) if they already exist, this skips the equivalent of -m which is otherwise assumed by most processing flags. 114 --odf [filename/wildcard/url]
see --odt 115 --odt [filename/wildcard/url]
output basic document in opendocument file format (opendocument.odt). Alias -o 116 -o [filename/wildcard/url]
see --odt 117 --pdf [filename/wildcard]
produces 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 118 --pg [instruction] [filename]
database postgresql ( --pgsql may be used instead) possible instructions, include: --createdb; --create; --dropall; --import [filename]; --update [filename]; --remove [filename]; see database section below. Alias -D 119 --po [language_directory/filename language_directory]
see --po4a 120 --po4a [language_directory/filename language_directory]
produces .pot and po files for the file in the languages specified by the language directory. SiSU markup is placed in subdirectories named with the language code, e.g. en/ fr/ es/. The sisu config file must set the output directory structure to multilingual. v3, experimental 121 -P [language_directory/filename language_directory]
see --po4a 122 -p [filename/wildcard]
see --pdf 123 --quiet [filename/wildcard]
quiet less output to screen. 124 -q [filename/wildcard]
see --quiet 125 --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 126 -R [filename/wildcard]
see --rsync 127 -r [filename/wildcard]
see --scp 128 --sample-search-form [--webserv=webrick]
generate examples of (naive) cgi search form for sqlite and pgsql depends on your already having used sisu to populate an sqlite and/or pgsql database, (the sqlite version scans the output directories for existing sisu_sqlite databases, so it is first necessary to create them, before generating the search form) see -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). -Fv (in addition to the above) provides some information on setting up hyperestraier for sisu. Alias -F 129 --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 130 --sqlite --[instruction] [filename]
database type default set to sqlite, (for which --sqlite may be used instead) or to specify another database --db-[pgsql, sqlite] (however see -D) possible instructions include: --createdb; --create; --dropall; --import [filename]; --update [filename]; --remove [filename]; see database section below. Alias -d 131 --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 132 --sisupod [filename/wildcard]
produces a zipped file of the prepared document specified along with associated images, by default named sisupod.zip they may alternatively be named with the filename extension .ssp This provides a quick way of gathering the relevant parts of a sisu document which can then for example be emailed. A sisupod includes sisu markup source file, (along with associated documents if a master file, or available in multilingual versions), together with related images and skin. SiSU commands can be run directly against a sisupod contained in a local directory, or provided as a url on a remote site. As there is a security issue with skins provided by other users, they are not applied unless the flag --trust or --trusted is added to the command instruction, it is recommended that file that are not your own are treated as untrusted. The directory structure of the unzipped file is understood by sisu, and sisu commands can be run within it. Note: if you wish to send multiple files, it quickly becomes more space efficient to zip the sisu markup directory, rather than the individual files for sending). See the -S option without [filename/wildcard]. Alias -S 133 --source [filename/wildcard]
copies sisu markup file to output directory. Alias -s 134 -S
see --sisupod 135 -S [filename/wildcard]
see --sisupod 136 -s [filename/wildcard]
see --source 137 --texinfo [filename/wildcard]
produces texinfo and info file, (view with pinfo). Alias -I 138 --txt [filename/wildcard]
produces plaintext with Unix linefeeds and without markup, (object numbers are omitted), has footnotes at end of each paragraph that contains them [ -A for equivalent dos (linefeed) output file] [see -e for endnotes]. (Options include: --endnotes for endnotes --footnotes for footnotes at the end of each paragraph --unix for unix linefeed (default) --msdos for msdos linefeed). Alias -t 139 -T [filename/wildcard (*.termsheet.rb)]
standard form document builder, preprocessing feature 140 -t [filename/wildcard]
see --txt 141 --urls [filename/wildcard]
prints url output list/map for the available processing flags options and resulting files that could be requested, (can be used to get a list of processing options in relation to a file, together with information on the output that would be produced), -u provides url output mapping for those flags requested for processing. The default assumes sisu_webrick is running and provides webrick url mappings where appropriate, but these can be switched to file system paths in sisurc.yml. Alias -U 142 -U [filename/wildcard]
see --urls 143 -u [filename/wildcard]
provides url mapping of output files for the flags requested for processing, also see -U 144 --v2 [filename/wildcard]
invokes the sisu v2 document parser/generator. This is the default and is normally omitted. 145 --v3 [filename/wildcard]
invokes the sisu v3 document parser/generator. Currently under development and incomplete, v3 requires > = ruby1.9.2p180. You may run sisu3 instead. 146 --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 147 -V
on its own, provides SiSU version and environment information (sisu --help env) 148 -V [filename/wildcard]
even more verbose than the -v flag. 149 -v
on its own, provides SiSU version information 150 -v [filename/wildcard]
see --verbose 151 --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 152 -W
see --webrick 153 --wordmap [filename/wildcard]
see --concordance 154 -w [filename/wildcard]
see --concordance 155 --xhtml [filename/wildcard]
produces xhtml/XML output for browser viewing (sax parsing). Alias -b 156 --xml-dom [filename/wildcard]
produces XML output with deep document structure, in the nature of dom. Alias -X 157 --xml-sax [filename/wildcard]
produces XML output shallow structure (sax parsing). Alias -x 158 -X [filename/wildcard]
see --xml-dom 159 -x [filename/wildcard]
see --xml-sax 160 -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]) 161 -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. 162 --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 163 -Z [filename/wildcard]
see --zap 164 6. command line modifiers 165 --no-ocn
[with --html --pdf or --epub] switches off object citation numbering. Produce output without identifying numbers in margins of html or LaTeX/pdf output. 166 --no-annotate
strips output text of editor endnotes*1 denoted by asterisk or dagger/plus sign *1 square brackets 167 --no-asterisk
strips output text of editor endnotes*2 denoted by asterisk sign *2 square brackets 168 --no-dagger
strips output text of editor endnotes+1 denoted by dagger/plus sign +1 square brackets 169 7. database commands 170 dbi - database interface 171 -D or --pgsql set for postgresql -d or --sqlite default set for sqlite -d is modifiable with --db=[database type (pgsql or sqlite)] 172 --pg -v --createall
initial step, creates required relations (tables, indexes) in existing postgresql database (a database should be created manually and given the same name as working directory, as requested) (rb.dbi) [ -dv --createall sqlite equivalent] it may be necessary to run sisu -Dv --createdb initially NOTE: at the present time for postgresql it may be necessary to manually create the database. The command would be 'createdb [database name]' where database name would be SiSU_[present working directory name (without path)]. Please use only alphanumerics and underscores. 173 --pg -v --import
[filename/wildcard] imports data specified to postgresql db (rb.dbi) [ -dv --import sqlite equivalent] 174 --pg -v --update
[filename/wildcard] updates/imports specified data to postgresql db (rb.dbi) [ -dv --update sqlite equivalent] 175 --pg --remove
[filename/wildcard] removes specified data to postgresql db (rb.dbi) [ -d --remove sqlite equivalent] 176 --pg --dropall
kills data" and drops (postgresql or sqlite) db, tables & indexes [ -d --dropall sqlite equivalent] 177 The -v is for verbose output. 178 8. Shortcuts, Shorthand for multiple flags 179 --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. 180 -0 to -5 [filename or wildcard]
Default shorthand mappings (note that the defaults can be changed/configured in the sisurc.yml file): 181 -0
-mNhwpAobxXyYv [this is the default action run when no options are give, i.e. on 'sisu [filename]'] 182 -1
-mhewpy 183 -2
-mhewpaoy 184 -3
-mhewpAobxXyY 185 -4
-mhewpAobxXDyY --import 186 -5
-mhewpAobxXDyY --update 187 add -v for verbose mode and -c for color, e.g. sisu -2vc [filename or wildcard] 188 consider -u for appended url info or -v for verbose output 189 8.1 Command Line with Flags - Batch Processing 190 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. 191 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. 192 9. Introduction to SiSU Markup10 10 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. 193 9.1 Summary 194 SiSU source documents are plaintext (UTF-8)11 files 11 files should be prepared using UTF-8 character encoding 195 All paragraphs are separated by an empty line. 196 Markup is comprised of: 197 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) 198 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: 199 heading levels defines document structure 200 text basic attributes, italics, bold etc. 201 grouped text (objects), which are to be treated differently, such as code blocks or poems. 202 footnotes/endnotes 203 linked text and images 204 paragraph actions, such as indent, bulleted, numbered-lists, etc. 205 Some interactive help on markup is available, by typing sisu and selecting markup or sisu --help markup 206 To check the markup in a file: 207 sisu --identify [filename].sst 208 For brief descriptive summary of markup history 209 sisu --query-history 210 or if for a particular version: 211 sisu --query-0.38 212 9.2 Markup Examples 213 9.2.1 Online 214 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/> 215 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/> 216 an alternative presentation of markup syntax: /usr/share/doc/sisu/on_markup.txt.gz 217 9.2.2 Installed 218 With SiSU installed sample skins may be found in: /usr/share/doc/sisu/markup-samples (or equivalent directory) and if sisu-markup-samples is installed also under: /usr/share/doc/sisu/markup-samples-non-free 219 10. Markup of Headers 220 Headers contain either: semantic meta-data about a document, which can be used by any output module of the program, or; processing instructions. 221 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: 222   % this would be a comment

 223 10.1 Sample Header 224 This current document is loaded by a master document that has a header similar to this one: 225   % SiSU master 2.0

     @title: SiSU
      :subtitle: Manual

     @creator: :author: Amissah, Ralph

     @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,
         electronic document, electronic citation, data structure,
          citation systems, search

     % used_by: manual

     @date:
      :published: 2008-05-22
      :created: 2002-08-28
      :issued: 2002-08-28
      :available: 2002-08-28
      :modified: 2010-03-03

     @make:
      :num_top: 1
      :breaks: new=C; break=1
      :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]
          . sisu --v2 [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

 226 10.2 Available Headers 227 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 228 @indentifier: information or instructions 229 where the "identifier" is a tag recognised by the program, and the "information" or "instructions" belong to the tag/indentifier specified 230 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. 231 This is a sample header 232   % SiSU 2.0 [declared file-type identifier with markup version]

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

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

 235   @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]

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

 237   @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
      :pg: [Project Gutenberg text number]

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

 239   @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]

 240   @original:
      :language: [language]

 241   @notes:
      :comment:
      :prefix: [prefix is placed just after table of contents]

 242 11. Markup of Substantive Text 243 11.1 Heading Levels 244 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) 245 :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 246 :B~ [heading text] Second level heading [this is a heading level divider] 247 :C~ [heading text] Third level heading [this is a heading level divider] 248 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 249 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. 250 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 251   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)

 252 11.2 Font Attributes 253 markup example: 254   normal text,  *{emphasis}*, !{bold text}!, /{italics}/, _{underscore}_, "{citation}",
     ^{superscript}^, ,{subscript},, +{inserted text}+, -{strikethrough}-, #{monospace}#

     normal text

     *{emphasis}* [note: can be configured to be represented by bold, italics or underscore]

     !{bold text}!

     /{italics}/

     _{underscore}_

     "{citation}"

     ^{superscript}^

     ,{subscript},

     +{inserted text}+

     -{strikethrough}-

     #{monospace}#

 255 resulting output: 256 normal text, emphasis, bold text, italics, underscore, citation, superscript, subscript, inserted text, strikethrough, monospace 257 normal text 258 emphasis [note: can be configured to be represented by bold, italics or underscore] 259 bold text 260 italics 261 underscore 262 citation 263 superscript 264 subscript 265 inserted text 266 strikethrough 267 monospace 268 11.3 Indentation and bullets 269 markup example: 270   ordinary paragraph

     _1 indent paragraph one step

     _2 indent paragraph two steps

     _9 indent paragraph nine steps

 271 resulting output: 272 ordinary paragraph 273 indent paragraph one step 274 indent paragraph two steps 275 indent paragraph nine steps 276 markup example: 277   _* bullet text

     _1* bullet text, first indent

     _2* bullet text, two step indent

 278 resulting output: 279 bullet text 280 bullet text, first indent 281 bullet text, two step indent 282 Numbered List (not to be confused with headings/titles, (document structure)) 283 markup example: 284   # numbered list                numbered list 1., 2., 3, etc.

     _# numbered list numbered list indented a., b., c., d., etc.

 285 11.4 Footnotes / Endnotes 286 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 287 markup example: 288   ~{ a footnote or endnote }~

 289 resulting output: 290 12 12 a footnote or endnote 291 markup example: 292   normal text~{ self contained endnote marker & endnote in one }~ continues

 293 resulting output: 294 normal text13 continues 13 self contained endnote marker & endnote in one 295 markup example: 296   normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks if required }~ continues

     normal text ~{** another unnumbered asterisk footnote/endnote }~ continues

 297 resulting output: 298 normal text * continues * unnumbered asterisk footnote/endnote, insert multiple asterisks if required 299 normal text ** continues ** another unnumbered asterisk footnote/endnote 300 markup example: 301   normal text ~[* editors notes, numbered asterisk footnote/endnote series ]~ continues

     normal text ~[+ editors notes, numbered asterisk footnote/endnote series ]~ continues

 302 resulting output: 303 normal text *3 continues *3 editors notes, numbered asterisk footnote/endnote series 304 normal text +2 continues +2 editors notes, numbered asterisk footnote/endnote series 305 Alternative endnote pair notation for footnotes/endnotes: 306   % note the endnote marker "~^"

     normal text~^ continues

     ^~ endnote text following the paragraph in which the marker occurs

 307 the standard and pair notation cannot be mixed in the same document 308 11.5 Links 309 11.5.1 Naked URLs within text, dealing with urls 310 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). 311 markup example: 312   normal text http://www.sisudoc.org/ continues

 313 resulting output: 314 normal text <http://www.sisudoc.org/> continues 315 An escaped url without decoration 316 markup example: 317   normal text _http://www.sisudoc.org/ continues

     deb http://www.jus.uio.no/sisu/archive unstable main non-free

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

 324 11.5.2 Linking Text 325 To link text or an image to a url the markup is as follows 326 markup example: 327   about { SiSU }http://url.org markup

 328 resulting output: 329 about SiSU markup 330 A shortcut notation is available so the url link may also be provided automatically as a footnote 331 markup example: 332   about {~^ SiSU }http://url.org markup

 333 resulting output: 334 about SiSU 14 markup 14 <http://www.sisudoc.org/> 335 Internal document links to a tagged location, including an ocn 336 markup example: 337   about { text links }#link_text

 338 resulting output: 339 about text links 340 Shared document collection link 341 markup example: 342   about { SiSU book markup examples }:SiSU/examples.html

 343 resulting output: 344 about SiSU book markup examples 345 11.5.3 Linking Images 346 markup example: 347   { 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/

 348 resulting output: 349 [tux.png] 350 [tux.png] "Gnu/Linux - a better way" 351 [GnuDebianLinuxRubyBetterWay.png] "Way Better - with Gnu/Linux, Debian and Ruby" 352 [ruby_logo.png] "Ruby" 15 15 <http://www.ruby-lang.org/en/> 353 linked url footnote shortcut 354   {~^ [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

 355   text marker

356 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. 357 11.6 Grouped Text 358 11.6.1 Tables 359 Tables may be prepared in two either of two forms 360 markup example: 361   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

 362 resulting output: 363
This is a tablethis would become column two of row onecolumn three of row one is here
And here begins another rowcolumn two of row twocolumn three of row two, and so on
 364 a second form may be easier to work with in cases where there is not much information in each column 365 markup example:16 16 Table from the Wealth of Networks by Yochai Benkler
<http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler> 366   !_ Table 3.1: Contributors to Wikipedia, January 2001 - June 2005

     {table~h 24; 12; 12; 12; 12; 12; 12;}
                                     |Jan. 2001|Jan. 2002|Jan. 2003|Jan. 2004|July 2004|June 2006
     Contributors*                   |       10|      472|    2,188|    9,653|   25,011|   48,721
     Active contributors**           |        9|      212|      846|    3,228|    8,442|   16,945
     Very active contributors***     |        0|       31|      190|      692|    1,639|    3,016
     No. of English language articles|       25|   16,000|  101,000|  190,000|  320,000|  630,000
     No. of articles, all languages  |       25|   19,000|  138,000|  490,000|  862,000|1,600,000

     \* Contributed at least ten times; \** at least 5 times in last month; \*\** more than 100 times in last month.

 367 resulting output: 368 Table 3.1: Contributors to Wikipedia, January 2001 - June 2005 369
Jan. 2001Jan. 2002Jan. 2003Jan. 2004July 2004June 2006
Contributors*104722,1889,65325,01148,721
Active contributors**92128463,2288,44216,945
Very active contributors***0311906921,6393,016
No. of English language articles2516,000101,000190,000320,000630,000
No. of articles, all languages2519,000138,000490,000862,0001,600,000
 370 * Contributed at least ten times; ** at least 5 times in last month; *** more than 100 times in last month. 371 11.6.2 Poem 372 basic markup: 373   poem{

       Your poem here

     }poem

     Each verse in a poem is given an object number.

 374 markup example: 375   poem{

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

     }poem

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

       Your grouped text here

     }group

     A group is treated as an object and given a single object number.

 381 markup example: 382   group{

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

     }group

 383 resulting output: 384                     `Fury said to a
                   mouse, That he
                 met in the
               house,
            "Let us
              both go to
                law:  I will
                  prosecute
                    YOU.  --Come,
                       I'll take no
                        denial; We
                     must have a
                 trial:  For
              really this
           morning I've
          nothing
         to do."
           Said the
             mouse to the
               cur, "Such
                 a trial,
                   dear Sir,
                         With
                     no jury
                  or judge,
                would be
              wasting
             our
              breath."
               "I'll be
                 judge, I'll
                   be jury,"
                         Said
                    cunning
                      old Fury:
                     "I'll
                      try the
                         whole
                          cause,
                             and
                        condemn
                       you
                      to
                       death."'
 385 11.6.4 Code 386 Code tags code{ ... }code (used as with other group tags described above) are used to escape regular sisu markup, and have been used extensively within this document to provide examples of SiSU markup. You cannot however use code tags to escape code tags. They are however used in the same way as group or poem tags. 387 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] 388 use of code tags instead of poem compared, resulting output: 389                       `Fury said to a
                        mouse, That he
                      met in the
                    house,
                 "Let us
                   both go to
                     law:  I will
                       prosecute
                         YOU.  --Come,
                            I'll take no
                             denial; We
                          must have a
                      trial:  For
                   really this
                morning I've
               nothing
              to do."
                Said the
                  mouse to the
                    cur, "Such
                      a trial,
                        dear Sir,
                              With
                          no jury
                       or judge,
                     would be
                   wasting
                  our
                   breath."
                    "I'll be
                      judge, I'll
                        be jury,"
                              Said
                         cunning
                           old Fury:
                          "I'll
                           try the
                              whole
                               cause,
                                  and
                             condemn
                            you
                           to
                            death."'

 390 From SiSU 2.7.7 on you can number codeblocks by placing a hash after the opening code tag code{# as demonstrated here: 391 1  ┆                      `Fury said to a
2  ┆                     mouse, That he
3  ┆                   met in the
4  ┆                 house,
5  ┆              "Let us
6  ┆                both go to
7  ┆                  law:  I will
8  ┆                    prosecute
9  ┆                      YOU.  --Come,
10 ┆                         I'll take no
11 ┆                          denial; We
12 ┆                       must have a
13 ┆                   trial:  For
14 ┆                really this
15 ┆             morning I've
16 ┆            nothing
17 ┆           to do."
18 ┆             Said the
19 ┆               mouse to the
20 ┆                 cur, "Such
21 ┆                   a trial,
22 ┆                     dear Sir,
23 ┆                           With
24 ┆                       no jury
25 ┆                    or judge,
26 ┆                  would be
27 ┆                wasting
28 ┆               our
29 ┆                breath."
30 ┆                 "I'll be
31 ┆                   judge, I'll
32 ┆                     be jury,"
33 ┆                           Said
34 ┆                      cunning
35 ┆                        old Fury:
36 ┆                       "I'll
37 ┆                        try the
38 ┆                           whole
39 ┆                            cause,
40 ┆                               and
41 ┆                          condemn
42 ┆                         you
43 ┆                        to
44 ┆                         death."'
 392 11.7 Book index 393 To make an index append to paragraph the book index term relates to it, using an equal sign and curly braces. 394 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. 395     Paragraph containing main term and sub-term.
       ={Main term:sub-term}

 396 The index syntax starts on a new line, but there should not be an empty line between paragraph and index markup. 397 The structure of the resulting index would be: 398     Main term, 1
         sub-term, 1

 399 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. 400     Paragraph containing main term, second term and sub-term.
       ={first term; second term: sub-term}

 401 The structure of the resulting index would be: 402     First term, 1,
       Second term, 1,
         sub-term, 1

 403 If multiple sub-terms appear under one paragraph, they are separated under the main term heading from each other by a pipe symbol. 404     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

 405 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: 406     Main term, 1,
         sub-term, 1-3,
         second sub-term, 1,

 407 12. Composite documents markup 408 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 409 basic markup for importing a document into a master document 410   _<_< filename1.sst

     _<_< filename2.ssi

 411 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. 412   _<_< filename.ssi

     _<_<{filename.ssi}

     % using textlink alternatives

     _<_< |filename.ssi|@|^|

 413 Markup Syntax History 414 13. Notes related to Files-types and Markup Syntax 415 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) 416 0.38 is substantially current for version 1.0 417 depreciated 0.16 supported, though file names were changed at 0.37 418 sisu --query=[sisu version [0.38] or 'history] 419 provides a short history of changes to SiSU markup 420 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. 421   @title:
      :subtitle:

     @creator:
      :author:
      :translator:
      :illustrator:

     @rights:
      :text:
      :illustrations:

 422 see document markup samples, and sisu --help headers 423 the monospace tag takes the form of a hash '#' 424   #{ this enclosed text would be monospaced }#

 425 1.0 (2009-12-19:50/6) same as 0.69 426 0.69 (2008-09-16:37/2) (same as 1.0) and as previous (0.57) with the addition of book index tags 427   /^={.+?}$/

 428 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" 429    ={GNU/Linux community distribution:Debian+2|Fedora|Gentoo;Free Software Foundation+5}

 430   Free Software Foundation, 1-6
     GNU/Linux community distribution, 1
         Debian, 1-3
         Fedora, 1
         Gentoo,

 431 0.66 (2008-02-24:07/7) same as previous, adds semantic tags, [experimental and not-used] 432   /[:;]{.+?}[:;][a-z+]/

 433 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:] 434   :A~ @title by @author

 435 0.52 (2007w14/6) declared document type identifier at start of text/document: 436 SiSU 0.52 437 or, backward compatible using the comment marker: 438 % SiSU 0.38 439 variations include 'SiSU (text|master|insert) [version]' and 'sisu-[version]' 440 0.51 (2007w13/6) skins changed (simplified), markup unchanged 441 0.42 (2006w27/4) * (asterisk) type endnotes, used e.g. in relation to author 442 SiSU 0.42 is the same as 0.38 with the introduction of some additional endnote types, 443 Introduces some variations on endnotes, in particular the use of the asterisk 444   ~{* for example for describing an author }~ and ~{** for describing a second author }~

 445 * for example for describing an author 446 ** for describing a second author 447 and 448   ~[* my note ]~ or ~[+ another note ]~

 449 which numerically increments an asterisk and plus respectively 450 *1 my note +1 another note 451 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) 452 SiSU 0.38 introduced alternative experimental header and heading/structure markers, 453   @headername: and headers :A~ :B~ :C~ 1~ 2~ 3~

 454 as the equivalent of: 455   0~headername and headers 1~ 2~ 3~ 4~ 5~ 6~

 456 The internal document markup of SiSU 0.16 remains valid and standard Though note that SiSU 0.37 introduced a new file naming convention 457 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 458 0.37 (2006w09/7) introduced new file naming convention, .sst (text), .ssm (master), .ssi (insert), markup syntax unchanged 459 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 460 this is captured by the following file 'rename' instruction: 461   rename 's/\.s[123]$/\.sst/' *.s{1,2,3}
     rename 's/\.r[123]$/\.ssm/' *.r{1,2,3}
     rename 's/\.si$/\.ssi/' *.si

 462 The internal document markup remains unchanged, from SiSU 0.16 463 0.35 (2005w52/3) sisupod, zipped content file introduced 464 0.23 (2005w36/2) utf-8 for markup file 465 0.22 (2005w35/3) image dimensions may be omitted if rmagick is available to be relied upon 466 0.20.4 (2005w33/4) header 0~links 467 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 468 SiSU 0.16 (0.15 development branch) introduced the use of 469 the header 0~ and headings/structure 1~ 2~ 3~ 4~ 5~ 6~ 470 in place of the 0.1 header, heading/structure notation 471 SiSU 0.1 headers and headings structure represented by header 0{~ and headings/structure 1{ 2{ 3{ 4{~ 5{ 6{ 472 14. SiSU filetypes 473 SiSU has plaintext and binary filetypes, and can process either type of document. 474 14.1 .sst .ssm .ssi marked up plain text 475 SiSU documents are prepared as plain-text (utf-8) files with SiSU markup. They may make reference to and contain images (for example), which are stored in the directory beneath them _sisu/image. SiSU plaintext markup files are of three types that may be distinguished by the file extension used: regular text .sst; master documents, composite documents that incorporate other text, which can be any regular text or text insert; and inserts the contents of which are like regular text except these are marked .ssi and are not processed. 476 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. 477 SiSU source markup can be shared with the command: 478 sisu -s [filename] 479 14.1.1 sisu text - regular files (.sst) 480 The most common form of document in SiSU, see the section on SiSU markup. 481 <http://www.sisudoc.org/sisu/sisu_markup> 482 <http://www.sisudoc.org/sisu/sisu_manual> 483 14.1.2 sisu master files (.ssm) 484 Composite documents which incorporate other SiSU documents which may be either regular SiSU text .sst which may be generated independently, or inserts prepared solely for the purpose of being incorporated into one or more master documents. 485 The mechanism by which master files incorporate other documents is described as one of the headings under under SiSU markup in the SiSU manual. 486 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. 487 Note: a secondary file of the composite document is built prior to processing with the same prefix and the suffix ._sst 17 17 .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. 488 <http://www.sisudoc.org/sisu/sisu_markup> 489 <http://www.sisudoc.org/sisu/sisu_manual> 490 14.1.3 sisu insert files (.ssi) 491 Inserts are documents prepared solely for the purpose of being incorporated into one or more master documents. They resemble regular SiSU text files except they are ignored by the SiSU processor. Making a file a .ssi file is a quick and convenient way of flagging that it is not intended that the file should be processed on its own. 492 14.2 sisupod, zipped binary container (sisupod.zip, .ssp) 493 A sisupod is a zipped SiSU text file or set of SiSU text files and any associated images that they contain (this will be extended to include sound and multimedia-files) 494 SiSU plaintext files rely on a recognised directory structure to find contents such as images associated with documents, but all images for example for all documents contained in a directory are located in the sub-directory _sisu/image. Without the ability to create a sisupod it can be inconvenient to manually identify all other files associated with a document. A sisupod automatically bundles all associated files with the document that is turned into a pod. 495 The structure of the sisupod is such that it may for example contain a single document and its associated images; a master document and its associated documents and anything else; or the zipped contents of a whole directory of prepared SiSU documents. 496 The command to create a sisupod is: 497 sisu -S [filename] 498 Alternatively, make a pod of the contents of a whole directory: 499 sisu -S 500 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. 501 <http://www.sisudoc.org/sisu/sisu_commands> 502 <http://www.sisudoc.org/sisu/sisu_manual> 503 15. Experimental Alternative Input Representations 504 15.1 Alternative XML 505 SiSU offers alternative XML input representations of documents as a proof of concept, experimental feature. They are however not strictly maintained, and incomplete and should be handled with care. 506 convert from sst to simple xml representations (sax, dom and node): 507 sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard] 508 sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard] 509 sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard] 510 convert to sst from any sisu xml representation (sax, dom and node): 511 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 512 or the same: 513 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 514 15.1.1 XML SAX representation 515 To convert from sst to simple xml (sax) representation: 516 sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard] 517 To convert from any sisu xml representation back to sst 518 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 519 or the same: 520 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 521 15.1.2 XML DOM representation 522 To convert from sst to simple xml (dom) representation: 523 sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard] 524 To convert from any sisu xml representation back to sst 525 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 526 or the same: 527 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 528 15.1.3 XML Node representation 529 To convert from sst to simple xml (node) representation: 530 sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard] 531 To convert from any sisu xml representation back to sst 532 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 533 or the same: 534 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 535 16. Configuration 536 16.1 Determining the Current Configuration 537 Information on the current configuration of SiSU should be available with the help command: 538 sisu -v 539 which is an alias for: 540 sisu --help env 541 Either of these should be executed from within a directory that contains sisu markup source documents. 542 16.2 Configuration files (config.yml) 543 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. 544 The SiSU configuration file is a yaml file, which means indentation is significant. 545 SiSU resource configuration is determined by looking at the following files if they exist: 546 ./_sisu/sisurc.yml 547 ~/.sisu/sisurc.yml 548 /etc/sisu/sisurc.yml 549 The search is in the order listed, and the first one found is used. 550 In the absence of instructions in any of these it falls back to the internal program defaults. 551 Configuration determines the output and processing directories and the database access details. 552 If SiSU is installed a sample sisurc.yml may be found in /etc/sisu/sisurc.yml 553 17. Skins 554 Skins modify the default appearance of document output on a document, directory, or site wide basis. Skins are looked for in the following locations: 555 ./_sisu/skin 556 ~/.sisu/skin 557 /etc/sisu/skin 558 Within the skin directory are the following the default sub-directories for document skins: 559 ./skin/doc 560 ./skin/dir 561 ./skin/site 562 A skin is placed in the appropriate directory and the file named skin_[name].rb 563 The skin itself is a ruby file which modifies the default appearances set in the program. 564 17.1 Document Skin 565 Documents take on a document skin, if the header of the document specifies a skin to be used. 566   @skin: skin_united_nations

 567 17.2 Directory Skin 568 A directory may be mapped on to a particular skin, so all documents within that directory take on a particular appearance. If a skin exists in the skin/dir with the same name as the document directory, it will automatically be used for each of the documents in that directory, (except where a document specifies the use of another skin, in the skin/doc directory). 569 A personal habit is to place all skins within the doc directory, and symbolic links as needed from the site, or dir directories as required. 570 17.3 Site Skin 571 A site skin, modifies the program default skin. 572 17.4 Sample Skins 573 With SiSU installed sample skins may be found in: 574 /etc/sisu/skin/doc and /usr/share/doc/sisu/markup-samples/samples/_sisu/skin/doc 575 (or equivalent directory) and if sisu-markup-samples is installed also under: 576 /usr/share/doc/sisu/markup-samples-non-free/samples/_sisu/skin/doc 577 Samples of list.yml and promo.yml (which are used to create the right column list) may be found in: 578 /usr/share/doc/sisu/markup-samples-non-free/samples/_sisu/skin/yml (or equivalent directory) 579 18. CSS - Cascading Style Sheets (for html, XHTML and XML) 580 CSS files to modify the appearance of SiSU html, XHTML or XML may be placed in the configuration directory: ./_sisu/css ; ~/.sisu/css or; /etc/sisu/css and these will be copied to the output directories with the command sisu -CC. 581 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. 582 HTML: html.css 583 XML DOM: dom.css 584 XML SAX: sax.css 585 XHTML: xhtml.css 586 The default homepage may use homepage.css or html.css 587 Under consideration is to permit the placement of a CSS file with a different name in directory _sisu/css directory or equivalent, and change the default CSS file that is looked for in a skin.18 18 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. 588 19. Organising Content 589 19.1 Directory Structure and Mapping 590 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) 591 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. 592 19.1.1 General Directories 593   ./subject_name/

     % files stored at this level e.g. sisu_manual.sst

     ./subject_name/_sisu

     % configuration file e.g. sisurc.yml

     ./subject_name/_sisu/skin

     % skins in various skin directories doc, dir, site, yml

     ./subject_name/_sisu/css

     ./subject_name/_sisu/image

     % images for documents contained in this directory

     ./subject_name/_sisu/mm

 594 19.1.2 Remote Directories 595   ./subject_name/

     % containing sub_directories named after the generated files from which they are made

     ./subject_name/src

     % contains shared source files text and binary e.g. sisu_manual.sst and sisu_manual.sst.zip

     ./subject_name/_sisu

     % configuration file e.g. sisurc.yml

     ./subject_name/_sisu/skin

     % skins in various skin directories doc, dir, site, yml

     ./subject_name/_sisu/css

     ./subject_name/_sisu/image

     % images for documents contained in this directory

     ./subject_name/_sisu/mm

 596 19.1.3 Sisupod 597   ./sisupod/

     % files stored at this level e.g. sisu_manual.sst

     ./sisupod/_sisu

     % configuration file e.g. sisurc.yml

     ./sisupod/_sisu/skin

     % skins in various skin directories doc, dir, site, yml

     ./sisupod/_sisu/css

     ./sisupod/_sisu/image

     % images for documents contained in this directory

     ./sisupod/_sisu/mm

 598 19.2 Organising Content 599 20. Homepages 600 SiSU is about the ability to auto-generate documents. Home pages are regarded as custom built items, and are not created by SiSU. More accurately, SiSU has a default home page, which will not be appropriate for use with other sites, and the means to provide your own home page instead in one of two ways as part of a site's configuration, these being: 601 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) 602 2. through providing what you want as the home page in a skin, 603 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. 604 20.1 Home page and other custom built pages in a sub-directory 605 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: 606 sisu -CC 607 20.2 Home page within a skin 608 Skins are described in a separate section, but basically are a file written in the programming language Ruby that may be provided to change the defaults that are provided with sisu with respect to individual documents, a directories contents or for a site. 609 If you wish to provide a homepage within a skin the skin should be in the directory _sisu/skin/dir and have the name of the directory for which it is to become the home page. Documents in the directory commercial_law would have the homepage modified in skin_commercial law.rb ; or the directory poems in skin_poems.rb 610     class Home
         def homepage
           # place the html content of your homepage here, this will become index.html
           _<_<HOME _<html_>
     _<head_>_</head_>
     _<doc_>
     _<p_>this is my new homepage._</p_>
     _</doc_>
     _</html_>
     HOME
         end
       end

 611 21. Markup and Output Examples 612 21.1 Markup examples 613 Current markup examples and document output samples are provided at <http://www.jus.uio.no/sisu/SiSU/examples.html> 614 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. 615 21.2 A few book (and other) examples 616 [aukio.png] "Aukio, by Leena Krohn" 19 19 Reproduced with the kind permission of author and artist Leena Krohn, <http://www.kaapeli.fi/krohn> "Aukio" is from the work "Sphinx or Robot" <http://www.jus.uio.no/sisu/sphinx_or_robot.leena_krohn.1996> which is included as a book example in this section, together with another of the author's works, "Tainaron" <http://www.jus.uio.no/sisu/tainaron.leena_krohn.1998> 617 21.2.1 "Viral Spiral", David Bollier 618 "Viral Spiral", David Bollier
     document manifest 20
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
20 <http://www.sisudoc.org/sisu/viral_spiral.david_bollier/sisu_manifest.html> 619 "The Wealth of Networks", Yochai Benkler 620 "The Wealth of Networks", Yochai Benkler
     document manifest 21
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
21 <http://www.sisudoc.org/sisu/the_wealth_of_networks.yochai_benkler/sisu_manifest.html> 621 "Two Bits", Christopher Kelty 622 "Two Bits", Christopher Kelty
     document manifest 22
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
22 <http://www.sisudoc.org/sisu/two_bits.christopher_kelty/sisu_manifest.html> 623 "Free Culture", Lawrence Lessig 624 "Free Culture", Lawrence Lessig
     document manifest 23
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
23 <http://www.sisudoc.org/sisu/free_culture.lawrence_lessig/sisu_manifest.html> 625 "CONTENT", Cory Doctorow 626 "CONTENT", Cory Doctorow
     document manifest 24
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
24 <http://www.sisudoc.org/sisu/content.cory_doctorow/sisu_manifest.html> 627 "Democratizing Innovation", by Eric von Hippel 628 "Democratizing Innovation", by Eric von Hippel
     document manifest 25
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
25 <http://www.sisudoc.org/sisu/democratizing_innovation.eric_von_hippel/sisu_manifest.html> 629 "Free as in Freedom: Richard Stallman's Crusade for Free Software", by Sam Williams 630 "Free as in Freedom: Richard Stallman's Crusade for Free Software", by Sam Williams
     document manifest 26
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
26 <http://www.sisudoc.org/sisu/free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams/sisu_manifest.html> 631 "Free For All: How Linux and the Free Software Movement Undercut the High Tech Titans", by Peter Wayner 632 "Free For All: How Linux and the Free Software Movement Undercut the High Tech Titans", by Peter Wayner
     document manifest 27
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
27 <http://www.sisudoc.org/sisu/free_for_all.peter_wayner/sisu_manifest.html> 633 "The Cathedral and the Bazaar", by Eric S. Raymond 634 "The Cathedral and the Bazaar", by Eric S. Raymond
     document manifest 28
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
28 <http://www.sisudoc.org/sisu/the_cathedral_and_the_bazaar.eric_s_raymond/sisu_manifest.html> 635 "Down and out in the Magic Kingdom", Cory Doctorow 636 "Down and out in the Magic Kingdom", Cory Doctorow
     document manifest 29
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
29 <http://www.sisudoc.org/sisu/down_and_out_in_the_magic_kingdom.cory_doctorow/sisu_manifest.html> 637 "Little Brother", Cory Doctorow 638 "Little Brother", Cory Doctorow
     document manifest 30
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
30 <http://www.sisudoc.org/sisu/little_brother.cory_doctorow/sisu_manifest.html> 639 "For the Win", Cory Doctorow 640 "For the Win", Cory Doctorow
     document manifest 31
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
31 <http://www.sisudoc.org/sisu/for_the_win.cory_doctorow/sisu_manifest.html> 641 "Accelerando", Charles Stross 642 "Accelerando", Charles Stross
     document manifest 32
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
32 <http://www.sisudoc.org/sisu/accelerando.charles_stross/sisu_manifest.html> 643 "Tainaron", Leena Krohn 644 "Tainaron", Leena Krohn
     document manifest 33
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
33 <http://www.sisudoc.org/sisu/tainaron.leena_krohn.1998/sisu_manifest.html> 645 "Sphinx or Robot", Leena Krohn 646 [i_sor.png] "Sphinx or Robot by Leena Krohn" 647 "Sphinx or Robot", Leena Krohn
     document manifest 34
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
34 <http://www.sisudoc.org/sisu/sphinx_or_robot.leena_krohn.1996/sisu_manifest.html> 648 "War and Peace", Leo Tolstoy, PG Etext 2600 649 "War and Peace", Leo Tolstoy 35
     document manifest 36
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
35 <http://www.jus.uio.no/sisu/war_and_peace.leo_tolstoy/toc.html>
The ascii text was taken from Project Gutenberg. The markup transforms required are trivial. Of interest, in this instance I am saved by having alternative syntaxes/(structural modes) for marking up endnotes... as it was possible to do a simple search and replace to make the Project Gutenberg ascii presentation suitable for SiSU, using the older endnote markup style. This example instructs the program to use regular expressions, in this example the words: none; none; BOOK|FIRST|SECOND; CHAPTER; occurring at the beginning of a line, to identify what should be treated as different levels of heading in a document (and used to make the table of contents). Note that there was very little markup required after the document headers and Project Gutenberg legal notices. As I presume the legal notices are similar in Project Gutenberg documents, (and I could not bear to think of preparing the same legal notices twice), I moved those to the "skin" for the Project, and these are now represented in the markup by <:insert1> and <:insert2> and the legal notices are available for similar insertion into the next Project Gutenberg text prepared for SiSU, should there be one.
I did a stylesheet/skin for the Gutenberg Project, ... I may have to remove. 36 <http://www.sisudoc.org/sisu/war_and_peace.leo_tolstoy/sisu_manifest.html> 650 "Don Quixote", Miguel de Cervantes [Saavedra], translated by John Ormsby, PG Etext 996 651 "Don Quixote", Miguel de Cervantes [Saavedra]
     document manifest 37
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
37 <http://www.sisudoc.org/sisu/don_quixote.miguel_de_cervantes/sisu_manifest.html> 652 "Gulliver's Travels", Jonathan Swift, transcribed from the 1892 George Bell and Sons edition by David Price, PG Etext 829 653 "Gulliver's Travels", Jonathan Swift
     document manifest 38
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
38 <http://www.sisudoc.org/sisu/gullivers_travels.jonathan_swift/sisu_manifest.html> 654 "Alice's Adventures in Wonderland", Lewis Carroll, PG Etext 11 655 "Alice's Adventures in Wonderland", Lewis Carroll
     document manifest 39
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
39 <http://www.sisudoc.org/sisu/alices_adventures_in_wonderland.lewis_carroll/sisu_manifest.html> 656 "Through The Looking-Glass", Lewis Carroll, PG Etext 12 657 "Through The Looking-Glass", Lewis Carroll
     document manifest 40
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
40 <http://www.sisudoc.org/sisu/through_the_looking_glass.lewis_carroll/sisu_manifest.html> 658 "Alice's Adventures in Wonderland" and "Through The Looking-Glass", Lewis Carroll, PG Etexts 11 and 12 659 "Alice's Adventures in Wonderland" and "Through The Looking-Glass", Lewis Carroll
     document manifest 41
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
41 <http://www.sisudoc.org/sisu/alices_adventures_in_wonderland_and_through_the_looking_glass.lewis_carroll/sisu_manifest.html> 660 "Gnu Public License 2", (GPL 2) Free Software Foundation 661 "Gnu Public License 2", (GPL 2) Free Software Foundation
     document manifest 42
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
42 <http://www.sisudoc.org/sisu/gpl2.fsf/sisu_manifest.html> 662 "Gnu Public License v3 - Third discussion draft", (GPLv3) Free Software Foundation 663 "Gnu Public License 3 - Third discussion draft", (GPL v3 draft3) Free Software Foundation
     document manifest 43
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
43 <http://www.sisudoc.org/sisu/gpl3_draft3.fsf/sisu_manifest.html> 664 "Debian Social Contract" 665 "Debian Social Contract"
     document manifest 44
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
44 <http://www.sisudoc.org/sisu/debian_social_contract_v1.1/sisu_manifest.html> 666 "Debian Constitution v1.3", (simple/default markup) 667 "Debian Constitution v1.3"
     document manifest 45
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
45 <http://www.sisudoc.org/sisu/debian_constitution_v1.3/sisu_manifest.html> 668 "Debian Constitution v1.3", (markup adjusted for output to more closely match the original) 669 "Debian Constitution v1.3", (markup adjusted for output to more closely match the original)
     document manifest 46
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
46 <http://www.sisudoc.org/sisu/debian_constitution_v1.3.adjusted/sisu_manifest.html> 670 "Debian Constitution v1.2", (simple/default markup) 671 "Debian Constitution v1.2 (more translations)"
     document manifest 47
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
47 <http://www.sisudoc.org/sisu/debian_constitution_v1.2/sisu_manifest.html> 672 "Debian Constitution v1.2", (markup adjusted for output to more closely match the original) 673 "Debian Constitution (more translations)", (markup adjusted for output to more closely match the original)
     document manifest 48
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
48 <http://www.sisudoc.org/sisu/debian_constitution_v1.2.adjusted/sisu_manifest.html> 674 "A Uniform Sales Terminology", Vikki Rogers and Albert Kritzer 675 "A Uniform Sales Terminology", Vikki Rogers and Albert Kritzer
     document manifest 49
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
49 <http://www.sisudoc.org/sisu/a_uniform_international_sales_terminology.vikki_rogers.and.albert_kritzer/sisu_manifest.html> 676 "The Autonomous Contract" 1997 - markup sample 677 "The Autonomous Contract" 1997 - markup sample
     document manifest 50
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
50 <http://www.sisudoc.org/sisu/the_autonomous_contract.amissah.19970710/sisu_manifest.html> 678 "The Autonomous Contract Revisited" - markup sample 679 "The Autonomous Contract Revisited" - markup sample 51
     document manifest 52
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
51 <http://www.jus.uio.no/sisu/autonomy_markup0/toc.html>
alternative markup variations revolving around endnotes
(i) as above, markup with embedded endnotes, and header list of words/phrases to emphasise
<http://www.jus.uio.no/sisu/sample/syntax/autonomy_markup0.sst.html>
<http://www.jus.uio.no/sisu/sample/markup/autonomy_markup0.sst>
(ii) Again markup with embedded endnotes, but font faces changed within paragraphs rather than in header as in i
<http://www.jus.uio.no/sisu/sample/syntax/autonomy_markup1.sst.html>
<http://www.jus.uio.no/sisu/sample/markup/autonomy_markup1.sst>
(iii) Markup with endnote placemarks within paragraphs, the endnotes following the paragraph that contains them <http://www.jus.uio.no/sisu/sample/syntax/autonomy_markup2.sst.html>
<http://www.jus.uio.no/sisu/sample/markup/autonomy_markup2.sst>
(iv) Another alternative is to place the marked up endnotes sequentially and at the end of the text. This also works. The paragraph variant iii is perhaps easier to visually check should there be missing endnotes; but this variant iv may better suit the conversion of alternatively pre-prepared documents. 52 <http://www.sisudoc.org/sisu/autonomy_markup0/sisu_manifest.html> 680 "United Nations Convention on Contracts for the International Sale of Goods" 681 "United Nations Convention on Contracts for the International Sale of Goods" 53
     document manifest 54
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
53 <http://www.jus.uio.no/sisu/un_contracts_international_sale_of_goods_convention_1980/toc.html>
This example instructs the program to use regular expressions, in this example the words: Part, Chapter, Section, Article occurring at the beginning of a line, to identify what should be treated as different levels of heading in a document (and used to make the table of contents).
This example instructs the program to use regular expressions, in this example the words: Part, Chapter, Section, Article occurring at the beginning of a line, to identify what should be treated as different levels of heading in a document (and used to make the table of contents). 54 <http://www.sisudoc.org/sisu/un_contracts_international_sale_of_goods_convention_1980/sisu_manifest.html> 682 /PECL/ the "Principles of European Contract Law" 683 "Principles of European Contract Law"
     document manifest 55
       html, segmented text
       html, scroll, document in one
       epub
       pdf, landscape
       pdf, portrait
       odf:odt, open document text
       xhtml scroll
       xml, sax
       xml, dom
       plain text utf-8
       concordance
       dcc, document content certificate (digests)
     markup source text
     markup source (zipped) pod
55 <http://www.sisudoc.org/sisu/eu_contract_principles_parts_1_to_3_2002/sisu_manifest.html> 684 21.3 SQL - PostgreSQL, SQLite 685 A Sample search form is available at <http://search.sisudoc.org> 686 A few canned searches, showing object numbers. Search for: 687 English documents matching Linux OR Debian 688 GPL OR Stallman 689 invention OR innovation 690 copyright in English language documents 691 Note that the searches done in this form are case sensitive. 692 Expand those same searches, showing the matching text in each document: 693 Linux OR Debian 694 GPL OR Stallman 695 invention OR innovation in English language 696 copyright in English language documents 697 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.56 56 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. 698 21.4 Lex Mercatoria as an example 699 There is quite a bit to peruse if you explore the site Lex Mercatoria: 700 <http://www.lexmercatoria.org/> 57 57 <http://www.jus.uio.no/lm/index> 701 or perhaps: 702 <http://lexmercatoria.org/treaties.and.organisations/lm.chronological> 58 58 <http://www.jus.uio.no/lm/treaties.and.organisations/lm.chronological> 703 21.5 For good measure the markup for a document with lots of (simple) tables 704 SiSU is not optimised for table making, but does handle simple tables. 705 Output of table file example 59 59 <http://www.jus.uio.no/lm/un.conventions.membership.status/toc.html> 706 21.6 And a link to the output of a reported case 707 <http://www.jus.uio.no/lm/england.fothergill.v.monarch.airlines.hl.1980/toc.html> 708 22. A Checklist of Output Features 709 This table gives an indication of the features that are available for various forms of output of SiSU. 710 sisu-2.0.0 on 2010-03-06 711
featuretxtltx/pdfHTMLEPUBXML/sXML/dODFSQLitepgSQL
headings*********
footnotes*********
bold, underscore, italics.********
strikethrough.******
superscript, subscript.******
extended ascii set (utf-8)********
indents*******
bullets.*****.
groups
* tables***.....
* poem****..*..
* code****..*..
url*******..
links*******..
images-***TT*TT
image caption-***
table of contents*****.
page header/footer?-*****t
line break*******
page break**
segments**
skins******
ocn.*****-?**
auto-heading numbers*********
minor list numbering*********
special characters....
 712 sisu-1.0.0 on 2009-10-28 713
featuretxtltx/pdfHTMLXML/sXML/dODFSQLitepgSQL
headings********
footnotes********
bold, underscore, italics.*******
strikethrough.*****
superscript, subscript.*****
extended ascii set (utf-8)*******
indents******
bullets.****.
groups
* tables**.....
* poem***..*..
* code***..*..
url******..
links******..
images-**TT*TT
image caption-**
table of contents****.
page header/footer?-****t
line break******
page break**
segments*
skins*****
ocn.****-?**
auto-heading numbers********
minor list numbering********
special characters...
 714 sisu-0.36.6 on 2006-01-23 715
featuretxtltx/pdfHTMLXHTMLXML/sXML/dODFSQLitepgSQL
headings*********
footnotes*********
bold, underscore, italics.********
strikethrough.******
superscript, subscript.******
extended ascii set (utf-8)********
indents*******
bullets.*****.
groups
* tables**......
* poem***...*..
* code***...*..
url*******..
links*******..
images-**TTT*TT
image caption-**
table of contents*****.
page header/footer?-*****t
line break*******
page break**
segments*
skins******
ocn.*****-?**
auto-heading numbers*********
minor list numbering*********
special characters...
 716   Done
  * yes/done
  . partial
  - not available/appropriate
  Not Done
  T task todo
  t lesser task/todo
    not done
 717 23. SiSU Search - Introduction 718 SiSU output can easily and conveniently be indexed by a number of standalone indexing tools, such as Lucene, Hyperestraier. 719 Because the document structure of sites created is clearly defined, and the text object citation system is available hypothetically at least, for all forms of output, it is possible to search the sql database, and either read results from that database, or just as simply map the results to the html output, which has richer text markup. 720 In addition to this SiSU has the ability to populate a relational sql type database with documents at an object level, with objects numbers that are shared across different output types, which make them searchable with that degree of granularity. Basically, your match criteria is met by these documents and at these locations within each document, which can be viewed within the database directly or in various output formats. 721 24. SQL 722 24.1 populating SQL type databases 723 SiSU feeds sisu markupd documents into sql type databases PostgreSQL60 and/or SQLite61 database together with information related to document structure. 60 <http://www.postgresql.org/>
<http://advocacy.postgresql.org/>
<http://en.wikipedia.org/wiki/Postgresql> 61 <http://www.hwaci.com/sw/sqlite/>
<http://en.wikipedia.org/wiki/Sqlite> 724 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: 725 one containing semantic (and other) headers, including, title, author, subject, (the Dublin Core...); 726 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 727 a third containing endnotes cross-referenced back to the paragraph from which they are referenced (both in formatted and clean text versions for searching). 728 a fourth table with a one to one relation with the headers table contains full text versions of output, eg. pdf, html, xml, and ascii. 729 There is of course the possibility to add further structures. 730 At this level SiSU loads a relational database with documents chunked into objects, their smallest logical structurally constituent parts, as text objects, with their object citation number and all other structural information needed to construct the document. Text is stored (at this text object level) with and without elementary markup tagging, the stripped version being so as to facilitate ease of searching. 731 Being able to search a relational database at an object level with the SiSU citation system is an effective way of locating content generated by SiSU. As individual text objects of a document stored (and indexed) together with object numbers, and all versions of the document have the same numbering, complex searches can be tailored to return just the locations of the search results relevant for all available output formats, with live links to the precise locations in the database or in html/xml documents; or, the structural information provided makes it possible to search the full contents of the database and have headings in which search content appears, or to search only headings etc. (as the Dublin Core is incorporated it is easy to make use of that as well). 732 25. Postgresql 733 25.1 Name 734 SiSU - Structured information, Serialized Units - a document publishing system, postgresql dependency package 735 25.2 Description 736 Information related to using postgresql with sisu (and related to the sisu_postgresql dependency package, which is a dummy package to install dependencies needed for SiSU to populate a postgresql database, this being part of SiSU - man sisu). 737 25.3 Synopsis 738 sisu -D [instruction] [filename/wildcard if required] 739 sisu -D --pg --[instruction] [filename/wildcard if required] 740 25.4 Commands 741 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 742 -D or --pgsql may be used interchangeably. 743 25.4.1 create and destroy database 744 --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) 745 sisu -D --createdb
creates database where no database existed before 746 sisu -D --create
creates database tables where no database tables existed before 747 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). 748 sisu -D --recreate
destroys existing database and builds a new empty database structure 749 25.4.2 import and remove documents 750 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). 751 sisu -D --update -v [filename/wildcard]
updates file contents in database 752 sisu -D --remove -v [filename/wildcard]
removes specified document from postgresql database. 753 26. Sqlite 754 26.1 Name 755 SiSU - Structured information, Serialized Units - a document publishing system. 756 26.2 Description 757 Information related to using sqlite with sisu (and related to the sisu_sqlite dependency package, which is a dummy package to install dependencies needed for SiSU to populate an sqlite database, this being part of SiSU - man sisu). 758 26.3 Synopsis 759 sisu -d [instruction] [filename/wildcard if required] 760 sisu -d --(sqlite|pg) --[instruction] [filename/wildcard if required] 761 26.4 Commands 762 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 763 -d or --sqlite may be used interchangeably. 764 26.4.1 create and destroy database 765 --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) 766 sisu -d --createdb
creates database where no database existed before 767 sisu -d --create
creates database tables where no database tables existed before 768 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). 769 sisu -d --recreate
destroys existing database and builds a new empty database structure 770 26.4.2 import and remove documents 771 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). 772 sisu -d --update -v [filename/wildcard]
updates file contents in database 773 sisu -d --remove -v [filename/wildcard]
removes specified document from sqlite database. 774 27. Introduction 775 27.1 Search - database frontend sample, utilising database and SiSU features, including object citation numbering (backend currently PostgreSQL) 776 Sample search frontend 62 A small database and sample query front-end (search from) that makes use of the citation system, object citation numbering to demonstrates functionality.63 62 <http://search.sisudoc.org> 63 (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. 777 SiSU can provide information on which documents are matched and at what locations within each document the matches are found. These results are relevant across all outputs using object citation numbering, which includes html, XML, EPUB, LaTeX, PDF and indeed the SQL database. You can then refer to one of the other outputs or in the SQL database expand the text within the matched objects (paragraphs) in the documents matched. 778 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.64 64 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. 779 sisu -F --webserv-webrick
builds a cgi web search frontend for the database created 780 The following is feedback on the setup on a machine provided by the help command: 781 sisu --help sql 782   Postgresql
       user:             ralph
       current db set:   SiSU_sisu
       port:             5432
       dbi connect:      DBI:Pg:database=SiSU_sisu;port=5432

     sqlite
       current db set:   /home/ralph/sisu_www/sisu/sisu_sqlite.db
       dbi connect       DBI:SQLite:/home/ralph/sisu_www/sisu/sisu_sqlite.db

 783 Note on databases built 784 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] 785 27.2 Search Form 786 sisu -F
generates a sample search form, which must be copied to the web-server cgi directory 787 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 788 sisu -Fv
as above, and provides some information on setting up hyperestraier 789 sisu -W
starts the webrick server which should be available wherever sisu is properly installed 790 The generated search form must be copied manually to the webserver directory as instructed 791 28. Hyperestraier 792 See the documentation for hyperestraier: 793 <http://hyperestraier.sourceforge.net/> 794 /usr/share/doc/hyperestraier/index.html 795 man estcmd 796 on sisu_hyperestraier: 797 man sisu_hyperestraier 798 /usr/share/doc/sisu/sisu-markup/sisu_hyperestraier/index.html 799 NOTE: the examples that follow assume that sisu output is placed in the directory /home/ralph/sisu_www 800 (A) to generate the index within the webserver directory to be indexed: 801 estcmd gather -sd [index name] [directory path to index] 802 the following are examples that will need to be tailored according to your needs: 803 cd /home/ralph/sisu_www 804 estcmd gather -sd casket /home/ralph/sisu_www 805 you may use the 'find' command together with 'egrep' to limit indexing to particular document collection directories within the web server directory: 806 find /home/ralph/sisu_www -type f | egrep '/home/ralph/sisu_www/sisu/.+?.html$' |estcmd gather -sd casket - 807 Check which directories in the webserver/output directory (~/sisu_www or elsewhere depending on configuration) you wish to include in the search index. 808 As sisu duplicates output in multiple file formats, it it is probably preferable to limit the estraier index to html output, and as it may also be desirable to exclude files 'plain.txt', 'toc.html' and 'concordance.html', as these duplicate information held in other html output e.g. 809 find /home/ralph/sisu_www -type f | egrep '/sisu_www/(sisu|bookmarks)/.+?.html$' | egrep -v '(doc|concordance).html$' |estcmd gather -sd casket - 810 from your current document preparation/markup directory, you would construct a rune along the following lines: 811 find /home/ralph/sisu_www -type f | egrep '/home/ralph/sisu_www/([specify first directory for inclusion]|[specify second directory for inclusion]|[another directory for inclusion? ...])/.+?.html$' | egrep -v '(doc|concordance).html$' |estcmd gather -sd /home/ralph/sisu_www/casket - 812 (B) to set up the search form 813 (i) copy estseek.cgi to your cgi directory and set file permissions to 755: 814 sudo cp -vi /usr/lib/estraier/estseek.cgi /usr/lib/cgi-bin 815 sudo chmod -v 755 /usr/lib/cgi-bin/estseek.cgi 816 sudo cp -v /usr/share/hyperestraier/estseek.* /usr/lib/cgi-bin 817 [see estraier documentation for paths] 818 (ii) edit estseek.conf, with attention to the lines starting 'indexname:' and 'replace:': 819 indexname: /home/ralph/sisu_www/casket 820 replace: ^file:///home/ralph/sisu_www{!} 821 replace: /index.html?${{!}}/ 822 (C) to test using webrick, start webrick: 823 sisu -W 824 and try open the url: <http://localhost:8081/cgi-bin/estseek.cgi> 825 29. sisu_webrick 826 29.1 Name 827 SiSU - Structured information, Serialized Units - a document publishing system 828 29.2 Synopsis 829 sisu_webrick [port] 830 or 831 sisu -W [port] 832 29.3 Description 833 sisu_webrick is part of SiSU (man sisu) sisu_webrick starts Ruby' s Webrick web-server and points it to the directories to which SiSU output is written, providing a list of these directories (assuming SiSU is in use and they exist). 834 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). 835 29.4 Summary of man page 836 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] 837 where no port is given and settings are unchanged the default port is 8081 838 29.5 Document processing command flags 839 sisu -W [port] starts Ruby Webrick web-server, serving SiSU output directories, on the port provided, or if no port is provided and the defaults have not been changed in ~/.sisu/sisurc.yaml then on port 8081 840 29.6 Further information 841 For more information on SiSU see: <http://www.sisudoc.org/> or <http://www.jus.uio.no/sisu> 842 or man sisu 843 29.7 Author 844 Ralph Amissah <ralph@amissah.com> or <ralph.amissah@gmail.com> 845 29.8 SEE ALSO 846 sisu(1) 847 sisu_vim(7) 848 30. Remote Source Documents 849 SiSU processing instructions can be run against remote source documents by providing the url of the documents against which the processing instructions are to be carried out. The remote SiSU documents can either be sisu marked up files in plaintext .sst or .ssm or; zipped sisu files, sisupod.zip or filename.ssp 850 .sst / .ssm - sisu text files 851 SiSU can be run against source text files on a remote machine, provide the processing instruction and the url. The source file and any associated parts (such as images) will be downloaded and generated locally. 852   sisu -3 http://[provide url to valid .sst or .ssm file]

 853 Any of the source documents in the sisu examples page can be used in this way, see <http://www.jus.uio.no/sisu/SiSU/examples.html> and use the url to the .sst for the desired document. 854 NOTE: to set up a remote machine to serve SiSU documents in this way, images should be in the directory relative to the document source ../_sisu/image 855 sisupod - zipped sisu files 856 A sisupod is the zipped content of a sisu marked up text or texts and any other associated parts to the document such as images. 857 SiSU can be run against a sisupod on a (local or) remote machine, provide the processing instruction and the url, the sisupod will be downloaded and the documents it contains generated locally. 858   sisu -3 http://[provide url to valid sisupod.zip or .ssp file]

 859 Any of the source documents in the sisu examples page can be used in this way, see <http://www.jus.uio.no/sisu/SiSU/examples.html> and use the url for the desired document. 860 Remote Document Output 861 31. Remote Output 862 Once properly configured SiSU output can be automatically posted once generated to a designated remote machine using either rsync, or scp. 863 In order to do this some ssh authentication agent and keychain or similar tool will need to be configured. Once that is done the placement on a remote host can be done seamlessly with the -r (for scp) or -R (for rsync) flag, which may be used in conjunction with other processing flags, e.g. 864   sisu -3R sisu_remote.sst

 865 31.1 commands 866 -R [filename/wildcard]
copies sisu output files to remote host using rsync. This requires that sisurc.yml has been provided with information on hostname and username, and that you have your "keys" and ssh agent in place. Note the behavior of rsync different if -R is used with other flags from if used alone. Alone the rsync --delete parameter is sent, useful for cleaning the remote directory (when -R is used together with other flags, it is not). Also see -r 867 -r [filename/wildcard]
copies sisu output files to remote host using scp. This requires that sisurc.yml has been provided with information on hostname and username, and that you have your "keys" and ssh agent in place. Also see -R 868 31.2 configuration 869 [expand on the setting up of an ssh-agent / keychain] 870 32. Remote Servers 871 As SiSU is generally operated using the command line, and works within a Unix type environment, SiSU the program and all documents can just as easily be on a remote server, to which you are logged on using a terminal, and commands and operations would be pretty much the same as they would be on your local machine. 872 Download information 873 33. Download SiSU - Linux/Unix 874 SiSU Current Version - Linux/Unix 875 Source (tarball tar.gz) 876 Download the latest version of SiSU (and SiSU markup samples): 877 sisu_3.0.4.orig.tar.gz (2011-03-11:10/5) 65 65 <http://www.jus.uio.no/sisu/pkg/src/sisu_3.0.4.orig.tar.gz>
145c409526b26cb0a14b43f4c46219fb828dc41c8211d8f77bad486a98300678 1920526 878 sisu-markup-samples_3.0.0.orig.tar.gz (of 2011-02-16:07/3 ) 66 66 <http://www.jus.uio.no/sisu/pkg/src/sisu-markup-samples_3.0.0.orig.tar.gz>
999f3cc572d0558a6af4539db0c51691dcff3371d4f92e096cbf5835806aeed4 8446814 879 For installation notes see <http://sisudoc.org/sisu/sisu_manual/installation.html> 880 For more general use see <http://sisudoc.org/sisu/sisu_manual> 881 For changelogs see <http://www.jus.uio.no/sisu/SiSU/changelog.html> 882 [tulva.png] "Tulva, by Leena Krohn" 67 67 Reproduced with the kind permission of author and artist Leena Krohn, <http://www.kaapeli.fi/krohn> Tulva is from the work Sphinx or Robot <http://www.jus.uio.no/sisu/sphinx_or_robot.leena_krohn.1996> other works available online include Tainaron <http://www.jus.uio.no/sisu/tainaron.leena_krohn.1998>, these two works can be found in the book sample section <http://www.jus.uio.no/sisu/SiSU/examples.html#sample> 883 Git (source control management) 884 Git repository currently at: 885 git clone git://git.sisudoc.org/git/code/sisu.git 886 <http://git.sisudoc.org/?p=code/sisu.git;a=summary> 887 On using git, see 888 Git documentation: Git User's Manual, 68 Everyday GIT With 20 Commands Or So, 69 A tutorial introduction to git, 70 A tutorial introduction to git: part two 71 68 <http://www.kernel.org/pub/software/scm/git/docs/user-manual.html> 69 <http://www.kernel.org/pub/software/scm/git/docs/everyday.html> 70 <http://www.kernel.org/pub/software/scm/git/docs/v1.4.4.4/tutorial.html> 71 <http://www.kernel.org/pub/software/scm/git/docs/v1.4.4.4/tutorial-2.html> 889 User contributed texts: The Git Community Book, 72 Git Magic, 73 Git From the Bottom Up (pdf) 74 72 <http://book.git-scm.com/index.html> 73 <http://www-cs-students.stanford.edu/~blynn/gitmagic/> 74 <http://www.newartisans.com/blog_assets/git.from.bottom.up.pdf> 890 Debian 891 This section contains information on the latest SiSU release. For installation notes see <http://sisudoc.org/sisu/sisu_manual/installation.html> 892 SiSU is updated fairly regularly in Debian testing and unstable, and should be available therefrom. 893 To add this archive, should you still choose to do so, add the following lines to your /etc/apt/sources.list 894   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

 895 <b>Source</b>
sisu_3.0.4.orig.tar.gz 75
sisu_3.0.4-1.debian.tar.gz 76
sisu_3.0.4-1.dsc 77
 75 <http://www.jus.uio.no/sisu/pkg/src/sisu_3.0.4.orig.tar.gz> 76 <http://www.jus.uio.no/sisu/pkg/src/sisu_3.0.4-1.diff.gz> 77 <http://www.jus.uio.no/sisu/pkg/src/sisu_3.0.4-1.dsc>
4886196e536e3ad48b29d27b1f0664f77b58ee4b4b21e41c0351c6b3a33dd156 1216 896 <b>Debs</b>
sisu_3.0.4-1_all.deb 78
sisu-complete_3.0.4-1_all.deb 79
sisu-pdf_3.0.4-1_all.deb 80
sisu-postgresql_3.0.4-1_all.deb 81
sisu-sqlite_3.0.4-1_all.deb 82
 78 <http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu_3.0.4-1_all.deb>
sisu, the base code, (the main package on which the others depend), without any dependencies other than ruby (and for convenience the ruby webrick web server), this generates a number of types of output on its own, other packages provide additional functionality, and have their dependencies
Depends: ruby (>=1.8.2), libwebrick-ruby
Recommends: sisu-pdf, sisu-sqlite, sisu-postgresql, sisu-examples, vim-sisu, librmagick-ruby, trang, tidy, libtidy, librexml-ruby, zip, unzip, openssl 79 <http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu-complete_3.0.4-1_all.deb>
a package that pulls in other packages to build the whole of sisu (excluding sisu-examples)
Depends: ruby (>=1.8.2), sisu, sisu-pdf, sisu-postgresql, sisu-remote, sisu-sqlite, vim-sisu
Recommends: sisu-examples 80 <http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu-pdf_3.0.4-1_all.deb>
dependencies used by sisu to produce pdf from LaTeX generated
Depends: sisu, tetex-bin, tetex-extra, latex-ucs
Suggests: evince, xpdf 81 <http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu-postgresql_3.0.4-1_all.deb>
dependencies used by sisu to populate postgresql database (further configuration is necessary)
Depends: sisu, postgresql-8.1, libdbi-ruby, libdbm-ruby, libdbd-pg-ruby
Suggests: pgaccess, libdbd-pgsql, postgresql-contrib-8.1 82 <http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu-sqlite_3.0.4-1_all.deb>
dependencies used by sisu to populate sqlite database
Depends: sisu, sqlite, libdbi-ruby, libdbm-ruby, libdbd-sqlite-ruby
Suggests: libdbd-sqlite 897 For changelogs see: 898 <http://www.jus.uio.no/sisu/SiSU/changelog.html> 899 <http://www.jus.uio.no/sisu/sisu_changelog/changelog.html> 900 non-free 901 Book markup samples have been moved to non-free as the substantive text of the documents are available under the author or original publisher's license, and usually do not comply with the Debian Free Software Guidelines. 902 sisu-markup-samples_3.0.0-1_all.deb 83 83 <http://www.jus.uio.no/sisu/archive/pool/non-free/s/sisu-markup-samples/sisu-markup-samples_3.0.0-1_all.deb>
marked up documents and other examples related to sisu, a larger package containing a number of texts
Depends: sisu 903 sisu-markup-samples_3.0.0-1.dsc 84 84 <http://www.jus.uio.no/sisu/pkg/src/sisu-markup-samples_3.0.0-1.dsc>
7d9d434c74a1e96da3732e420d483466d7ca1266d4e6fba4bf7f21b9e3f73aad 1307 sisu-markup-samples_3.0.0-1.dsc 904 For changelogs see: 905 <http://www.jus.uio.no/sisu/SiSU/changelog_markup_samples.html> 906 <http://www.jus.uio.no/sisu/sisu_markup_samples_changelog/changelog_markup_samples.html> 907 RPM 908 The RPM is generated from the source file using Alien.85 Dependencies are not handled, not even that of the essential Ruby. In the Howto section see the note on installing SiSU on Fedora 12 (2010-01-12). 85 <http://www.kitenet.net/programs/alien/> 909 sudo rpm -i [package name] 910 sisu-1.0.3-2.noarch.rpm 86 86 <http://www.jus.uio.no/sisu/pkg/rpm/sisu-1.0.3-2.noarch.rpm>
*
created using alien 911 sisu-markup-samples_2.0.3.orig-2.noarch.rpm 87 87 <http://www.jus.uio.no/sisu/pkg/rpm/sisu-markup-samples_2.0.3.orig-2.noarch.rpm>
***
<http://www.jus.uio.no/sisu/archive/pool/non-free/s/sisu-markup-samples/sisu-markup-samples_2.0.3-1_all.deb>
created using: alien -r sisu_1.0.3-1_all.deb 912 For changelogs see: 913 <http://www.jus.uio.no/sisu/SiSU/changelog_markup_samples.html> 914 <http://www.jus.uio.no/sisu/sisu_markup_samples_changelog/changelog_markup_samples.html> 915 Installation 916 34. Installation 917 See the download pages 88 for information related to installation. 88 <http://www.jus.uio.no/sisu/SiSU/download.html> 918 34.1 Debian 919 SiSU is developed on Debian, and packages are available for Debian that take care of the dependencies encountered on installation. 920 The package is divided into the following components: 921 *sisu*, the base code, (the main package on which the others depend), without any dependencies other than ruby (and for convenience the ruby webrick web server), this generates a number of types of output on its own, other packages provide additional functionality, and have their dependencies 922 *sisu-complete*, a dummy package that installs the whole of greater sisu as described below, apart from sisu-examples 923 *sisu-pdf*, dependencies used by sisu to produce pdf from LaTeX generated 924 *sisu-postgresql*, dependencies used by sisu to populate postgresql database (further configuration is necessary) 925 *sisu-remote*, dependencies used to place sisu output on a remote server (further configuration is necessary) 926 *sisu-sqlite*, dependencies used by sisu to populate sqlite database 927 *sisu-markup-samples*, sisu markup samples and other miscellany (under Debian Free Software Guidelines non-free) 928 SiSU is available off Debian Unstable and Testing 89 install it using apt-get, aptitude or alternative Debian install tools. SiSU is currently comprised of eight packages. 89 <http://packages.qa.debian.org/s/sisu.html> 929 Initial packaging is done here and to get the latest version of SiSU available you may add the following line(s) to your sources list: 930   #/etc/apt/sources.list

     deb http://www.jus.uio.no/sisu/archive unstable main non-free
     deb-src http://www.jus.uio.no/sisu/archive unstable main non-free

 931 The non-free section is for sisu markup samples provided, which contain authored works the substantive text of which cannot be changed, and which as a result do not meet the debian free software guidelines. 932 On Debian there is little more to know beyond how to install software on Debian using apt, aptitude or synaptic. 933   #Using aptitude:

       aptitude update

       aptitude install sisu-complete sisu-markup-samples

 934   Using apt-get

       apt-get update

       apt get install sisu-complete sisu-examples

 935 34.2 Other Unix / Linux 936 A source tarball or an rpms built using alien are available, (however dependencies have not been tested). SiSU is first packaged and tested with dependency handling for Debian. 90 Information on dependencies configured for Debian is provided as this may be of assistance. 90 Notes on dependencies are provided in the section that follows 937 34.2.1 source tarball 938 installation with provided install script 939 To install SiSU, in the root directory of the unpacked SiSU as root type:91 91 This makes use of rant and the provided Rantfile. Note however, that additional external package dependencies, such as tetex-extra are not taken care of for you. 940 ruby install 941 Once installed see man 8 sisu for information on additional programs that sisu makes use of. 942 Further notes on install script. 943 The install script is prepared using Rant, and a Rantfile is provided,92 with more comprehensive install options, and post install and setup configuration and generation of first test file, if you have installed Stefan Lang's Rant 93 installed. While in the package directory, type: rant help, or rant -T, or to install SiSU as root, type: 92 a Rantfile has been configured to do post installation setup 93 <http://make.rubyforge.org/> <http://make.rubyforge.org/>
<http://rubyforge.org/frs/?group_id=615> 944 *install* is an install script prepared using Stefan Lang's Rant 94 It should work whether you have previously installed Rant or not. It has fairly comprehensive install options, and can do some post install and setup configuration and generation of first test file. For options type: 94 <http://make.rubyforge.org/> <http://make.rubyforge.org/>
<http://rubyforge.org/frs/?group_id=615> 945 ruby install -T 946 To install as root type: 947 ruby install 948 For a minimal install type: 949 ruby install base 950 installation with setup.rb 951 setup.rb 95 is provided the package and will install SiSU96 installation is a 3 step process97 the following string assumes you are in the package directory and that you have root as sudo: 95 <http://i.loveruby.net/en/projects/setup/> 96 Minero Aoki
<http://i.loveruby.net/en/projects/setup/doc/> 97 Installation instructions
<http://i.loveruby.net/en/projects/setup/doc/usage.html> 952 ruby setup.rb config && ruby setup.rb setup && sudo ruby setup.rb install 953 installation of rpm 954 The RPM is generated from the source file using Alien.98 Dependencies are not handled, not even that of the essential Ruby. 98 <http://www.kitenet.net/programs/alien/> 955 35. SiSU Components, Dependencies and Notes 956 The dependency lists are from the Debian control file for SiSU version 0.36, and may assist in building SiSU on other distributions. 957 35.1 sisu 958 the base code, (the main package on which the others depend), without any dependencies other than ruby (and for convenience the ruby webrick web server), this generates a number of types of output on its own, other packages provide additional functionality, and have their dependencies 959 *Depends:* on ruby (>=1.8.2), libwebrick-ruby 960 *Recommends:* sisu-pdf, sisu-sqlite, sisu-postgresql, sisu-examples, librmagick-ruby, trang, tidy, libtidy, librexml-ruby, zip, unzip, openssl 961 initialise directory 962 sisu -CC 963 html 964 sisu -hv [filename/wildcard] 965 sisu -Hv [filename/wildcard] 966 LaTeX (but sisu-pdf dependencies required to convert that to pdf) 967 sisu -pv [filename/wildcard] 968 plain text Unix with footnotes 969 sisu -av [filename/wildcard] 970 plain text Dos with footnotes 971 sisu -Av [filename/wildcard] 972 plain text Unix with endnotes 973 sisu -ev [filename/wildcard] 974 plain text Dos with endnotes 975 sisu -Ev [filename/wildcard] 976 openoffice odt 977 sisu -ov [filename/wildcard] 978 xhtml 979 sisu -bv [filename/wildcard] 980 XML SAX 981 sisu -xv [filename/wildcard] 982 XML DOM 983 sisu -Xv [filename/wildcard] 984 wordmap (a rudimentary index of content) 985 sisu -wv [filename/wildcard] 986 document content certificate 987 sisu -Nv [filename/wildcard] 988 placement of sourcefile in output directory 989 sisu -sv [filename/wildcard] 990 creation of source tarball with images, and placement of source tarball in ouput directory 991 sisu -Sv [filename/wildcard] 992 manifest of output produced (polls output directory and provides links to existing output) 993 sisu -yv [filename/wildcard] 994 url for output files -u -U 995 sisu -uv[and other flags] [filename/wildcard] 996 sisu -Uv [filename/wildcard] 997 toggle screen colour 998 sisu -cv[and processing flags] [filename/wildcard] 999 verbose mode 1000 sisu -v[and processing flags] [filename/wildcard] 1001 sisu -V[and processing flags] [filename/wildcard] 1002 quiet mode 1003 sisu -q[and processing flags] [filename/wildcard] 1004 maintenance mode, intermediate files kept -M 1005 sisu -Mv[and other flags] [filename/wildcard] 1006 [the -v is for verbose] 1007 start the webrick server 1008 sisu -W 1009 35.2 sisu-complete 1010 a dummy package that installs the whole SiSU, apart from sisu-examples 1011 *Depends:* ruby (>=1.8.2), sisu, sisu-pdf, sisu-postgresql, sisu-remote, sisu-sqlite 1012 *Recommends:* sisu-examples 1013 35.3 sisu-examples 1014 installs sisu markup samples and other miscelleny 1015 *Depends:* sisu 1016 35.4 sisu-pdf 1017 dependencies used by sisu to produce pdf from LaTeX generated 1018 *Depends:* sisu, tetex-bin, tetex-extra, latex-ucs 1019 *Suggests:* evince, xpdf 1020 converts sisu LaTeX produced to pdf 1021 sisu -pv [filename/wildcard] 1022 [the -v is for verbose] 1023 35.5 sisu-postgresql 1024 dependencies used by sisu to populate postgresql database (further configuration is necessary) 1025 *Depends:* sisu, postgresql-8.1, libdbi-ruby, libdbm-ruby, libdbd-pg-ruby 1026 *Suggests:* pgaccess, libdbd-pgsql, postgresql-contrib-8.1 1027 installs dependencies for sisu to work with and populate postgresql database 1028 create database 1029 sisu -Dv createall 1030 drop database 1031 sisu -Dv dropall 1032 import content 1033 sisu -Div [filename/wildcard] 1034 sisu -Dv import [filename/wildcard] 1035 update content 1036 sisu -Duv [filename/wildcard] 1037 sisu -Dv update [filename/wildcard] 1038 [the -v is for verbose] 1039 The following are available without installation of the sisu-postgresql component, but are of interest in this context 1040 generate a sample database query form for use with webserver on port 80 1041 sisu -F 1042 or for use with webrick server 1043 sisu -F webrick 1044 to start webrick server 1045 sisu -W 1046 35.6 sisu-remote 1047 dependencies used to place sisu output on a remote server (further configuration is necessary) 1048 scp 1049 sisu -vr[and processing flags] [filename/wildcard] 1050 rsync 1051 sisu -vR[and processing flags] [filename/wildcard] 1052 [the -v is for verbose] 1053 *Depends:* sisu, rsync, openssh-client|lsh-client, keychain 1054 35.7 sisu-sqlite 1055 dependencies used by sisu to populate sqlite database 1056 *Depends:* sisu, sqlite, libdbi-ruby, libdbm-ruby, libdbd-sqlite-ruby 1057 *Suggests:* libdbd-sqlite 1058 installs dependencies for sisu to work with and populate sqlite database 1059 create database 1060 sisu -dv createall 1061 drop database 1062 sisu -dv dropall 1063 update content 1064 sisu -div [filename/wildcard] 1065 sisu -dv import [filename/wildcard] 1066 update content 1067 sisu -duv [filename/wildcard] 1068 sisu -dv update [filename/wildcard] 1069 [the -v is for verbose] 1070 The following are available without installation of the sisu-sqlite component, but are of interest in this context 1071 generate a sample database query form for use with webserver on port 80 1072 sisu -F 1073 or for use with webrick server 1074 sisu -F webrick 1075 to start webrick server 1076 sisu -W 1077 36. Quickstart - Getting Started Howto 1078 36.1 Installation 1079 Installation is currently most straightforward and tested on the Debian platform, as there are packages for the installation of sisu and all requirements for what it does. 1080 36.1.1 Debian Installation 1081 SiSU is available directly from the Debian Sid and testing archives (and possibly Ubuntu), assuming your /etc/apt/sources.list is set accordingly: 1082     aptitude update
       aptitude install sisu-complete

 1083 The following /etc/apt/sources.list setting permits the download of additional markup samples: 1084   #/etc/apt/sources.list

       deb http://ftp.fi.debian.org/debian/ unstable main non-free contrib
       deb-src http://ftp.fi.debian.org/debian/ unstable main non-free contrib

 1085 The aptitude commands become: 1086     aptitude update
       aptitude install sisu-complete sisu-markup-samples

 1087 If there are newer versions of SiSU upstream of the Debian archives, they will be available by adding the following to your /etc/apt/sources.list 1088   #/etc/apt/sources.list

       deb http://www.jus.uio.no/sisu/archive unstable main non-free
       deb-src http://www.jus.uio.no/sisu/archive unstable main non-free

 1089 repeat the aptitude commands 1090     aptitude update
       aptitude install sisu-complete sisu-markup-samples

 1091 Note however that it is not necessary to install sisu-complete if not all components of sisu are to be used. Installing just the package sisu will provide basic functionality. 1092 36.1.2 RPM Installation 1093 RPMs are provided though untested, they are prepared by running alien against the source package, and against the debs. 1094 They may be downloaded from: 1095 <http://www.jus.uio.no/sisu/SiSU/download.html#rpm> 1096 as root type: 1097 rpm -i [rpm package name] 1098 36.1.3 Installation from source 1099 To install SiSU from source check information at: 1100 <http://www.jus.uio.no/sisu/SiSU/download.html#current> 1101 download the source package 1102 Unpack the source 1103 Two alternative modes of installation from source are provided, setup.rb (by Minero Aoki) and a rant(by Stefan Lang) built install file, in either case: the first steps are the same, download and unpack the source file: 1104 For basic use SiSU is only dependent on the programming language in which it is written Ruby, and SiSU will be able to generate html, EPUB, various XMLs, including ODF (and will also produce LaTeX). Dependencies required for further actions, though it relies on the installation of additional dependencies which the source tarball does not take care of, for things like using a database (postgresql or sqlite)99 or converting LaTeX to pdf. 99 There is nothing to stop MySQL support being added in future. 1105 setup.rb 1106 This is a standard ruby installer, using setup.rb is a three step process. In the root directory of the unpacked SiSU as root type: 1107       ruby setup.rb config
         ruby setup.rb setup
         #[and as root:]
         ruby setup.rb install

 1108 further information on setup.rb is available from: 1109 <http://i.loveruby.net/en/projects/setup/> 1110 <http://i.loveruby.net/en/projects/setup/doc/usage.html> 1111 "install" 1112 The "install" file provided is an installer prepared using "rant". In the root directory of the unpacked SiSU as root type: 1113 ruby install base 1114 or for a more complete installation: 1115 ruby install 1116 or 1117 ruby install base 1118 This makes use of Rant (by Stefan Lang) and the provided Rantfile. It has been configured to do post installation setup setup configuration and generation of first test file. Note however, that additional external package dependencies, such as tetex-extra are not taken care of for you. 1119 Further information on "rant" is available from: 1120 <http://make.rubyforge.org/> 1121 <http://rubyforge.org/frs/?group_id=615> 1122 For a list of alternative actions you may type: 1123 ruby install help 1124 ruby install -T 1125 36.2 Testing SiSU, generating output 1126 To check which version of sisu is installed: 1127 sisu -v 1128 Depending on your mode of installation one or a number of markup sample files may be found either in the directory: 1129 or 1130 change directory to the appropriate one: 1131 cd /usr/share/doc/sisu/markup-samples/samples 1132 36.2.1 basic text, plaintext, html, XML, ODF, EPUB 1133 Having moved to the directory that contains the markup samples (see instructions above if necessary), choose a file and run sisu against it 1134 sisu -NhwoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst 1135 this will generate html including a concordance file, opendocument text format, plaintext, XHTML and various forms of XML, and OpenDocument text 1136 36.2.2 LaTeX / pdf 1137 Assuming a LaTeX engine such as tetex or texlive is installed with the required modules (done automatically on selection of sisu-pdf in Debian) 1138 Having moved to the directory that contains the markup samples (see instructions above if necessary), choose a file and run sisu against it 1139 sisu -pv free_as_in_freedom.rms_and_free_software.sam_williams.sst 1140 sisu -3 free_as_in_freedom.rms_and_free_software.sam_williams.sst 1141 should generate most available output formats: html including a concordance file, opendocument text format, plaintext, XHTML and various forms of XML, and OpenDocument text and pdf 1142 36.2.3 relational database - postgresql, sqlite 1143 Relational databases need some setting up - you must have permission to create the database and write to it when you run sisu. 1144 Assuming you have the database installed and the requisite permissions 1145 sisu --sqlite --recreate 1146 sisu --sqlite -v --import free_as_in_freedom.rms_and_free_software.sam_williams.sst 1147 sisu --pgsql --recreate 1148 sisu --pgsql -v --import free_as_in_freedom.rms_and_free_software.sam_williams.sst 1149 36.3 Getting Help 1150 36.3.1 The man pages 1151 Type: 1152 man sisu 1153 The man pages are also available online, though not always kept as up to date as within the package itself: 1154 sisu.1 100 100 <http://www.jus.uio.no/sisu/man/sisu.1.html> 1155 sisu.8 101 101 <http://www.jus.uio.no/sisu/man/sisu.8.html> 1156 man directory 102 102 <http://www.jus.uio.no/sisu/man> 1157 36.3.2 Built in help 1158 sisu --help 1159 sisu --help --env 1160 sisu --help --commands 1161 sisu --help --markup 1162 36.3.3 The home page 1163 <http://www.sisudoc.org/> 1164 <http://www.jus.uio.no/sisu> 1165 <http://www.jus.uio.no/sisu/SiSU> 1166 36.4 Markup Samples 1167 A number of markup samples (along with output) are available off: 1168 <http://www.jus.uio.no/sisu/SiSU/examples.html> 1169 Additional markup samples are packaged separately in the file: 1170 On Debian they are available in non-free103 to include them it is necessary to include non-free in your /etc/apt/source.list or obtain them from the sisu home site. 103 the Debian Free Software guidelines require that everything distributed within Debian can be changed - and the documents are authors' works that while freely distributable are not freely changeable. 1171 HowTo 1172 37. Getting Help 1173 An online manual of sorts should be available at: 1174 <http://www.jus.uio.no/sisu_manual/> 1175 The manual pages provided with SiSU are also available online, and there is an interactive help, which is being superseded by the man page, and possibly some document which contains this component. 1176 37.1 SiSU "man" pages 1177 If SiSU is installed on your system usual man commands should be available, try: 1178 man sisu 1179 The SiSU man pages can be viewed online at:104 104 generated from source using rman
<http://polyglotman.sourceforge.net/rman.html>
With regard to SiSU man pages the formatting generated for markup syntax is not quite right, for that you might prefer the links under:
<http://www.jus.uio.no/sample> 1180 An online version of the sisu man page is available here: 1181 various sisu man pages 105 105 <http://www.jus.uio.no/sisu/man/> 1182 sisu.1 106 106 <http://www.jus.uio.no/sisu/man/sisu.1.html> 1183 sisu.8 107 107 <http://www.jus.uio.no/sisu/man/sisu.8.html> 1184 sisu_webrick.1 108 108 <http://www.jus.uio.no/sisu/man/sisu_webrick.1.html> 1185 37.2 SiSU built-in help 1186 sisu --help 1187 sisu --help [subject] 1188 sisu --help env [for feedback on the way your system is setup with regard to sisu] 1189 sisu -V [same as above command] 1190 sisu --help commands 1191 sisu --help markup 1192 37.3 Command Line with Flags - Batch Processing 1193 Running sisu (alone without any flags, filenames or wildcards) brings up the interactive help, as does any sisu command that is not recognised. 1194 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. 1195 38. Setup, initialisation 1196 38.1 initialise output directory 1197 Images, css files for a document directory are copied to their respective locations in the output directory. 1198 while within your document markup/preparation directory, issue the following command 1199 sisu -CC 1200 38.1.1 Use of search functionality, an example using sqlite 1201 SiSU can populate PostgreSQL and Sqlite databases and provides a sample search form for querying these databases. 1202 This note provides an example to get you started and will use sqlite 1203 It is necessary to: 1204 (1) make sure the required dependencies have been installed 1205 (2) have a directory with sisu markup samples that is writable 1206 (3) use sisu to create a database 1207 (4) use sisu tp populate a database 1208 (5) use sisu to start the webrick (httpd) server 1209 (6) use sisu to create a search form 1210 (7) copy the search form to the cgi directory 1211 (8) open up the form in your browser 1212 (9) query the database using the search form 1213 (1) make sure the required dependencies have been installed 1214 if you use Debian, the following command will install the required dependencies 1215 aptitude install sisu-sqlite 1216 (2) have a directory with sisu markup samples that is writable 1217 ideally copy the sisu-examples directory to your home directory (because the directory in which you run this example should be writable) 1218 cp -rv /usr/share/doc/sisu/markup-samples/samples . 1219 you are better off installing the package sisu-markup-samples which will make the following available 1220 cp -rv /usr/share/doc/sisu/markup-samples-non-free/samples . 1221 (3) use sisu to create an sqlite database 1222 within the sisu-examples directory 1223 sisu -dv createall 1224 (4) use sisu tp populate a database with some text 1225 within the sisu-examples directory 1226 sisu -div free_*.sst 1227 or 1228 sisu -dv import free_*.sst debian_constitution_v1.2.sst debian_social_contract_v1.1.sst gpl2.fsf.sst 1229 (5) use sisu to start the webrick (httpd) server (if it has not already been started): 1230 sisu -W 1231 (6) use sisu to create a search form (for use with the webrick server, and your sample documents) 1232 within the sisu-examples directory 1233 sisu -F webserv=webrick 1234 and follow the instructions provided 1235 #here i run into a problem, you are working from a read only #directory..., not my usual mode of operation, to complete the example #the following is necessary sudo touch sisu_sqlite.cgi sisu_pgsql.cgi sudo -P chown $USER sisu_sqlite.cgi sisu_pgsql.cgi 1236 #now this should be possible: sisu -F webrick 1237 (7) copy the search form to the cgi directory 1238 sisu -F webserv=webrick 1239 and follow the instructions provided 1240 (8) open up the form in your browser and query it 1241 url: 1242 <http://localhost:8081/cgi-bin/sisu_sqlite.cgi> 1243 or as instructed by command sisu -F webrick 1244 (9) query the database using the search form 1245 if there are other options in the dropdown menu select 1246 document_samples_sisu_markup 1247 and search for some text, e.g.: 1248 aim OR project 1249 selecting the *index* radio button gives an index of results using the object numbers 1250 selecting the *text* radio button gives the content of the matched paragraphs with the match highlighted 1251 (10) to start again with a new database 1252 to start from scratch you can drop the database with the command 1253 sisu -dv dropall 1254 and go to step 3 1255 to get to step 3 in one step with a single command 1256 sisu -dv recreate 1257 continue subsequent steps 1258 38.2 misc 1259 38.2.1 url for output files -u -U 1260 sisu -uv[and other flags] [filename/wildcard] 1261 sisu -Uv [filename/wildcard] 1262 38.2.2 toggle screen color 1263 sisu -cv[and processing flags] [filename/wildcard] 1264 38.2.3 verbose mode 1265 sisu -v[and processing flags] [filename/wildcard] 1266 sisu -V[and processing flags] [filename/wildcard] 1267 38.2.4 quiet mode 1268 sisu -q[and processing flags] [filename/wildcard] 1269 38.2.5 maintenance mode intermediate files kept -M 1270 sisu -Mv[and other flags] [filename/wildcard] 1271 38.2.6 start the webrick server 1272 sisu -W 1273 38.3 remote placement of output 1274 configuration is necessary 1275 scp 1276 sisu -vr[and processing flags] [filename/wildcard] 1277 rsync 1278 sisu -vR[and processing flags] [filename/wildcard] 1279 39. Configuration Files 1280 Sample provided, on untarring the source tarball: 1281 conf/sisu/v2/sisurc.yml 1282 conf/sisu/v3/sisurc.yml 1283 and on installation under: 1284 /etc/sisu/v2/sisurc.yml 1285 /etc/sisu/v3/sisurc.yml 1286 The following paths are searched: 1287 ./_sisu/v2/sisurc.yml or ./_sisu/v3/sisurc.yml 1288 ./_sisu/sisurc.yml 1289 ~/.sisu/v2/sisurc.yml or ~/.sisu/v3/sisurc.yml 1290 ~/.sisu/sisurc.yml 1291 /etc/sisu/v2/sisurc.yml /etc/sisu/v3/sisurc.yml 1292 /etc/sisu/sisurc.yml 1293 40. Markup 1294 See sample markup provided on 1295 <http://www.sisudoc.org/> 1296 <http://www.jus.uio.no/sisu> 1297 <http://www.jus.uio.no/sisu_markup> 1298 <http://www.jus.uio.no/sisu/SiSU> 1299 in particular for each of the document output samples provided, the source document is provided as well 1300 <http://www.jus.uio.no/sisu/SiSU/examples.html> 1301 on untarring the source tarball: 1302 data/doc/sisu/markup-samples 1303 or the same once source is installed (or sisu-examples) under: 1304 /usr/share/doc/sisu/markup-samples/ 1305 and if you have sisu-markup-samples installed, under 1306 data/doc/sisu/markup-samples-non-free/ 1307 /usr/share/doc/sisu/markup-samples-non-free/ 1308 Some notes are contained within the man page, man sisu and within sisu help via the commands sisu help markup and sisu help headers 1309 SiSU is for literary and legal text, also for some social science material. In particular it does not do formula, and is not particularly suited to technical documentation. Despite the latter caveat, some notes will be provided here and added to over time: 1310 40.1 Headers 1311 Headers @headername: provide information related to the document, this may relate to 1312 1. how it is to be processed, such as whether headings are to be numbered, what skin is to be used and markup instructions, such as the document structure, or words to be made bold within the document 1313 2. semantic information about the document including the dublin core 1314 40.2 Font Face 1315 Defaults are set. You may change the face to: bold, italics, underscore, strikethrough, ... 1316 40.2.1 Bold 1317 \@bold: [list of words that should be made bold within document] 1318 bold line 1319 !_ bold line 1320 bold word or sentence 1321 !{ bold word or sentence }! 1322 *{ bold word or sentence }* 1323 *boldword* or !boldword! 1324 *boldword* or !boldword! 1325 40.2.2 Italics 1326 \@italics: [list of words that should be italicised within document] 1327 italicise word or sentence 1328 /{ italicise word or sentence }/ 1329 /italicisedword/ 1330 /italicisedword/ 1331 40.2.3 Underscore 1332 underscore word or sentence 1333 _{ underscore word or sentence }_ 1334 _underscoreword_ 1335 40.2.4 Strikethrough 1336 strikethrough word or sentence 1337 -{ strikethrough word or sentence }- 1338 -strikeword- 1339 -strikeword- 1340 40.3 Endnotes 1341 There are two forms of markup for endnotes, they cannot be mixed within the same document 1342 here109 109 this is an endnote 1343 1. preferred endnote markup 1344 here~{ this is an endnote }~ 1345 2. alternative markup equivalent, kept because it is possible to search and replace to get markup in existing texts such as Project Gutenberg 1346 here~^ 1347 ^~ this is an endote 1348 40.4 Links 1349 SiSU 1350   { SiSU }http://www.sisudoc.org

 1351 [sisu.png] 1352   {sisu.png }http://www.sisudoc.org

 1353 [tux.png] 1354   { tux.png 64x80 }image

 1355 SiSU 110 110 <http://www.sisudoc.org> 1356   {~^ SiSU }http://www.sisudoc.org

 1357 is equivalent to: 1358   { SiSU }http://www.sisudoc.org ~{ http://www.sisudoc.org }~

 1359 the same can be done with an image: 1360 [sisu.png] "SiSU" 111 111 <http://www.sisudoc.org> 1361   {~^ sisu.png "SiSU" }http://www.sisudoc.org

 1362 40.5 Number Titles 1363 Set with the header @markup: 1364 40.6 Line operations 1365 Line Operations (marker placed at start of line) 1366 !_ bold line 1367 bold line 1368 _1 indent paragraph one level 1369 indent paragraph one level 1370 _2 indent paragraph two steps 1371 indent paragraph two steps 1372 _* bullet paragraph 1373 bullet paragraph 1374 # number paragraph (see headers for numbering document headings) 1375 1. number paragraph (see headers for numbering document headings) 1376 _# number paragraph level 2 (see headers for numbering document headings) 1377 a. number paragraph level 2 (see headers for numbering document headings) 1378 40.7 Tables 1379 Table markup sample 1380   table{~h c3; 26; 32; 32;

     This is a table, column1
     this would become row one of column two
     column three of row one is here

     column one row 2
     column two of row two
     column three of row two, and so on

     column one row three
     and so on
     here

     }table

 1381 Alternative form of table markup 1382   {t~h}
          |Mon|Tue|Wed|Thu|Fri|Sat|Sun
     0    | * | * | * | * | * | * | *
     1    | * | * | * | * |   |   |
     2    | - | * | * | * | * | * |
     3    | - | * | * | * | * | * | *
     4    | - |   |   | * | * | * |
     5    | * | * | * | * | * | * | *

 1383 40.8 Grouped Text 1384     5.times { puts 'Ruby' }

 1385 code{ 1386     5.times { puts 'Ruby' }

 1387 }code 1388 A Limerick
 1389 There was a young lady from Clyde,
who ate a green apple and died,
but the apple fermented inside the lamented,
and made cider inside her inside.
 1390   poem{

     There was a young lady from Clyde,
     who ate a green apple and died,
     but the apple fermented inside the lamented,
     and made cider inside her inside.

     }poem

 1391 40.9 Composite Document 1392 To import another document, the master document or importing document should be named filename.r3 (r for require) 1393 << { filename.sst } 1394 << { filename.ssi } 1395 41. Change Appearance 1396 41.1 Skins 1397 "Skins" may be used to change various aspects related to the output documents appearance, including such things as the url for the home page on which the material will be published, information on the credit band, and for html documents colours and icons used in navigation bars. Skins are ruby files which permit changing of the default values set within the program for SiSU output. 1398 There are a few examples provided, on untarring the source tarball: 1399 conf/sisu/skin/doc/ 1400 data/doc/sisu/markup-samples/samples/_sisu/skin/doc/ 1401 and on installation under: 1402 /etc/sisu/skin/doc/ 1403 /usr/share/doc/sisu-markup-samples/v2/samples/_sisu/skin/doc 1404 The following paths are searched: 1405 ./_sisu/skin 1406 ~/.sisu/skin 1407 /etc/sisu/skin 1408 Skins under the searched paths in a per document directory, a per directory directory, or a site directory, named: 1409 doc [may be specified individually in each document] 1410 dir [used if identifier part of name matches markup directory name] 1411 site 1412 It is usual to place all skins in the document directory, with symbolic links as required from dir or site directories. 1413 41.2 CSS 1414 The appearance of html and XML related output can be changed for an ouput collection directory by prepareing and placing a new css file in one of the sisu css directories searched in the sisu configuration path. These are located at: 1415 _./_sisu/css 1416 ~/.sisu/css 1417 and 1418 /etc/sisu/css 1419 The contents of the first directory found in the search path are copied to the corresponding sisu output directory with the commnd: 1420 sisu -CC 1421 The SiSU standard css files for SiSU output are: 1422 dom.css html.css html_tables.css index.css sax.css xhtml.css 1423 A document may specify its own/bespoke css file using the css header. 1424 \@css: 1425 [expand] 1426 Extracts from the README 1427 42. README 1428 SiSU 0.55 2007w27/6 2007-07-07 1429 Homepage: <http://www.sisudoc.org> 1430 old homepage: <http://www.jus.uio.no/sisu> 1431 Description 1432 SiSU is lightweight markup based document creation and publishing framework that is controlled from the command line. Prepare documents for SiSU using your text editor of choice, then use SiSU to generate various output document formats. 1433 With minimal preparation of a plain-text (UTF-8) file using its native markup-syntax, SiSU produces: plain-text, HTML, XHTML, EPUB, XML, ODF:ODT (Opendocument), LaTeX, PDF, and populates an SQL database (PostgreSQL or SQLite) in paragraph sized chunks so that document searches are done at this "atomic" level of granularity. 1434 Outputs share a common citation numbering system, and any semantic meta-data provided about the document. 1435 SiSU also provides concordance files, document content certificates and manifests of generated output. 1436 SiSU takes advantage of well established open standard ways of representing text, and provides a bridge to take advantage of the strengths of each, while remaining simple. SiSU implements across document formats a "useful common feature set" [coming from a humanities, law, and possibly social sciences perspective, rather than technical or scientific writing] ... focus is primarily on content and data integrity rather than appearance, (though outputs in the various formats are respectable). 1437 A vim syntax highlighting file and an ftplugin with folds for sisu markup is provided. Vim 7 includes syntax highlighting for SiSU. 1438 man pages, and interactive help are provided. 1439 Dependencies for various features are taken care of in sisu related packages. The package sisu-complete installs the whole of SiSU. 1440 Additional document markup samples are provided in the package sisu-markup-samples which is found in the non-free archive the licenses for the substantive content of the marked up documents provided is that provided by the author or original publisher. 1441 Homepage: <http://www.sisudoc.org> 1442 old homepage: <http://www.jus.uio.no/sisu> 1443 SiSU - simple information structuring universe, is a publishing tool, document generation and management, (and search enabling) tool primarily for literary, academic and legal published works. 1444 SiSU can be used for Internet, Intranet, local filesystem or cd publishing. 1445 SiSU can be used directly off the filesystem, or from a database. 1446 SiSU' s scalability, is be dependent on your hardware, and filesystem (in my case Reiserfs), and/or database Postgresql. 1447 Amongst it's characteristics are: 1448 simple mnemonoic markup style, 1449 the ability to produce multiple output formats, including html, structured XML, LaTeX, pdf (via LaTeX), stream to a relational database whilst retaining document structure - Postgresql and Sqlite, 1450 that all share a common citation system (a simple idea from which much good), possibly most exciting, the following: if fed into a relational database (as it can be automatically), the document set is searchable, with results displayed at a paragraph level, or the possibility of an indexed display of documents in which the match is found together with a hyperlinked listing for each of each paragraph in which the match is found. In any event citations using this system (with or without the relational database) are relevant for all output formats. 1451 it is command line driven, and can be set up on a remote server 1452 Documents are marked up in SiSU syntax in your favourite editor. SiSU syntax may be regarded as a type of smart ascii - which in its basic form is simpler than the most elementary html. There is currently a syntax highlighter, and folding for Vim. Syntax highlighters for other editors are welcome. 1453 Input files should be UTF-8 1454 Once set up it is simple to use. 1455 42.1 Online Information, places to look 1456 <http://www.sisudoc.org> 1457 <http://www.jus.uio.no/sisu> 1458 Download Sources: 1459 <http://www.jus.uio.no/sisu/SiSU/download.html#current> 1460 <http://www.jus.uio.no/sisu/SiSU/download.html#debian> 1461 42.2 Installation 1462 NB. Platform is Unix / Linux. 1463 42.2.1 Debian 1464 If you use Debian use the Debian packages, check the information at: 1465 <http://www.jus.uio.no/sisu/SiSU/download.html#debian> 1466 (A) SiSU is available directly off the Debian archives for Sid and testing. It should necessary only to run as root: 1467 aptitude update 1468 aptitude install sisu-complete 1469 (B) If there are newer versions of SiSU upstream of the Debian archives, they will be available by adding the following to your /etc/apt/sources.list 1470 deb <http://www.jus.uio.no/sisu/archive> unstable main non-free 1471 deb-src <http://www.jus.uio.no/sisu/archive> unstable main non-free 1472 [the non-free line is for document markup samples, for which the substantive text is provided under the author or original publisher's license and which in most cases will not be debian free software guideline compliant] 1473 Then as root run: 1474 aptitude update 1475 aptitude install sisu-complete 1476 42.2.2 RPM 1477 RPMs are provided though untested, they are prepared by running alien against the source package, and against the debs. 1478 They may be downloaded from: 1479 <http://www.jus.uio.no/sisu/SiSU/download.html#rpm> 1480 42.2.3 Source package .tgz 1481 Otherwise to install SiSU from source, check information at: 1482 <http://www.jus.uio.no/sisu/SiSU/download.html#current> 1483 alternative modes of installation from source are provided, setup.rb (by Minero Aoki), rake (by Jim Weirich) built install file, rant (by Stefan Lang) built install file, 1484 Ruby is the essential dependency for the basic operation of SiSU 1485 1. Download the latest source (information available) from: 1486 <http://www.jus.uio.no/sisu/SiSU/download.html#current> 1487 2. Unpack the source 1488 Note however, that additional external package dependencies, such as texlive or postgresql should you desire to use it are not taken care of for you. 1489 42.2.4 to use setup.rb 1490 this is a three step process, in the root directory of the unpacked SiSU as root type: 1491 ruby setup.rb config 1492 ruby setup.rb setup 1493 as root: 1494 ruby setup.rb install 1495 further information: 1496 <http://i.loveruby.net/en/projects/setup/> 1497 <http://i.loveruby.net/en/projects/setup/doc/usage.html> 1498 42.2.5 to use install (prapared with "Rake") 1499 Rake must be installed on your system: 1500 <http://rake.rubyforge.org/> 1501 <http://rubyforge.org/frs/?group_id=50> 1502 in the root directory of the unpacked SiSU as root type: 1503 rake 1504 or 1505 rake base 1506 This makes use of Rake (by Jim Weirich) and the provided Rakefile 1507 For a list of alternative actions you may type: 1508 rake help 1509 rake -T 1510 42.2.6 to use install (prapared with "Rant") 1511 (you may use the instructions above for rake substituting rant if rant is installed on your system, or you may use an independent installer created using rant as follows:) 1512 in the root directory of the unpacked SiSU as root type: 1513 ruby ./sisu-install 1514 or 1515 ruby ./sisu-install base 1516 This makes use of Rant (by Stefan Lang) and the provided Rantfile. It has been configured to do post installation setup setup configuration and generation of first test file. Note however, that additional external package dependencies, such as tetex-extra are not taken care of for you. 1517 further information: 1518 <http://make.rubyforge.org/> 1519 <http://rubyforge.org/frs/?group_id=615> 1520 For a list of alternative actions you may type: 1521 ruby ./sisu-install help 1522 ruby ./sisu-install -T 1523 42.3 Dependencies 1524 Once installed see 'man 8 sisu' for some information on additional programs that sisu makes use of, and that you may need or wish to install. (this will depend on such factors as whether you want to generate pdf, whether you will be using SiSU with or without a database, ...) 'man sisu-markup-samples' may also be of interest if the sisu-markup-samples package has also been installed. 1525 The information in man 8 may not be most up to date, and it is possible that more useful information can be gleaned from the following notes taken from the Debian control file (end edited), gives an idea of additional packages that SiSU can make use of if available, (the use/requirement of some of which are interdependent for specific actions by SiSU) . 1526 The following is from the debian/control file of sisu-3.0.2, which amongst other things provides the dependencies of sisu within Debian. 1527   Source: sisu
     Section: text
     Priority: optional
     Maintainer: SiSU Project _<sisu@lists.sisudoc.org_>
     Uploaders: Ralph Amissah _<ralph@amissah.com_>
     Build-Depends: debhelper (_>= 8)
     Standards-Version: 3.9.1
     Homepage: http://www.sisudoc.org/
     Vcs-Browser: http://git.sisudoc.org/?p=code/sisu.git
     Vcs-Git: git://git.sisudoc.org/git/code/sisu.git
     XS-Dm-Upload-Allowed: yes

 1528   Package: sisu
     Architecture: all
     Depends: ${misc:Depends}, ruby (_>= 1.8.2), libwebrick-ruby, rsync, unzip, zip
     Recommends:
      sisu-pdf, sisu-sqlite, sisu-postgresql, imagemagick, keychain, librmagick-ruby,
      librexml-ruby, openssl, openssh-client | lsh-client, tidy, vim-addon-manager
     Suggests: lv, calibre, pinfo, texinfo, trang
     Conflicts: sisu-markup-samples (_<= 1.0.11)
     Replaces: sisu-markup-samples (_<= 1.0.11)
     Description: documents - structuring, publishing in multiple formats and search
      SiSU is a lightweight markup based, command line oriented, document
      structuring, publishing and search framework for document collections.
      .
      With minimal preparation of a plain-text, (UTF-8) file, using its native
      markup syntax in your text editor of choice, SiSU can generate various
      document formats (most of which share a common object numbering system for
      locating content), including plain text, HTML, XHTML, XML, EPUB, OpenDocument
      text (ODF:ODT), LaTeX, PDF files, and populate an SQL database with objects
      (roughly paragraph-sized chunks) so searches may be performed and matches
      returned with that degree of granularity: your search criteria is met by these
      documents and at these locations within each document. Object numbering is
      particularly suitable for "published" works (finalized texts as opposed to
      works that are frequently changed or updated) for which it provides a fixed
      means of reference of content. Document outputs also share semantic meta-data
      provided.
      .
      SiSU also provides concordance files, document content certificates and
      manifests of generated output.
      .
      A vim syntax highlighting file and an ftplugin with folds for sisu markup is
      provided, as are syntax highlighting files for kate, kwrite, gedit and
      diakonos. Vim 7 includes syntax highlighting for SiSU.
      .
      man pages, and interactive help are provided.
      .
      Dependencies for various features are taken care of in sisu related packages.
      The package sisu-complete installs the whole of SiSU.
      .
      Additional document markup samples are provided in the package
      sisu-markup-samples which is found in the non-free archive the licenses for
      the substantive content of the marked up documents provided is that provided
      by the author or original publisher.

 1529   Package: sisu-complete
     Architecture: all
     Depends:
      ${misc:Depends}, ruby (_>= 1.8.2), sisu (= ${source:Version}),

      sisu-pdf (= ${source:Version}), sisu-postgresql (= ${source:Version}),

      sisu-sqlite (= ${source:Version})
     Description: installs all SiSU related packages
      SiSU is a lightweight markup based document structuring, publishing and search
      framework for document collections.
      .
      This package installs SiSU and related packages that enable sisu to produce
      pdf and to populate PostgreSQL and sqlite databases.
      .
      See sisu for a description of the package.

 1530   Package: sisu-pdf
     Architecture: all
     Depends:
      ${misc:Depends}, sisu, texlive-latex-base, texlive-fonts-recommended,
      texlive-latex-recommended, texlive-latex-extra, texlive-xetex, lmodern,
      ttf-liberation
     Suggests: evince | pdf-viewer
     Description: dependencies to convert SiSU LaTeX output to pdf
      SiSU is a lightweight markup based document structuring, publishing and search
      framework for document collections.
      .
      This package enables the conversion of SiSU LaTeX output to pdf.

 1531   Package: sisu-pdf
     Architecture: all
     Depends:
      ${misc:Depends}, sisu, texlive-latex-base, texlive-fonts-recommended,
      texlive-latex-recommended, texlive-latex-extra, texlive-xetex, lmodern,
      ttf-liberation
     Suggests: evince | pdf-viewer
     Description: dependencies to convert SiSU LaTeX output to pdf
      SiSU is a lightweight markup based document structuring, publishing and search
      framework for document collections.
      .
      This package enables the conversion of SiSU LaTeX output to pdf.

 1532   Package: sisu-postgresql
     Architecture: all
     Depends:
      ${misc:Depends}, sisu, libdbd-pg-ruby, libdbd-pg-ruby1.8, libdbi-ruby,
      libdbi-ruby1.8, libdbm-ruby, postgresql, libfcgi-ruby1.8 | libfcgi-ruby1.9.1
     Suggests: postgresql-contrib
     Description: SiSU dependencies for use with PostgreSQL database
      SiSU is a lightweight markup based document structuring, publishing and search
      framework for document collections.
      .
      This package enables SiSU to populate a PostgreSQL database. This is done at
      an object/paragraph level, making granular searches of documents possible.
      .
      This relational database feature of SiSU is not required but provides
      interesting possibilities, including that of granular searches of documents
      for matching units of text, primarily paragraphs that can be displayed or
      identified by object citation number, from which an index of documents
      matched and each matched paragraph within them can be displayed.

 1533   Package: sisu-sqlite
     Architecture: all
     Depends:
      ${misc:Depends}, sisu, sqlite3, libsqlite3-ruby, libdbd-sqlite3-ruby,
      libdbd-sqlite3-ruby1.8, libdbi-ruby, libdbi-ruby1.8, libdbm-ruby,
      libfcgi-ruby1.8 | libfcgi-ruby1.9.1
     Description: SiSU dependencies for use with SQLite database
      SiSU is a lightweight markup based document structuring, publishing and search
      framework for document collections.
      .
      This package enables SiSU to populate an SQLite database. This is done at an
      object/paragraph level, making granular searches of documents possible.
      .
      This relational database feature of SiSU is not required but provides
      interesting possibilities, including that of granular searches of documents
      for matching units of text, primarily paragraphs that can be displayed or
      identified by object citation number, from which an index of documents
      matched and each matched paragraph within them can be displayed.

 1534 42.4 Quick start 1535 Most of the installation should be taken care of by the aptitude or rant install. (The rant install if run in full will also test run the generation of the first document). 1536 After installation of sisu-complete, move to the document samples directory 1537 cd /usr/share/doc/sisu/markup-samples/samples 1538 and run 1539 sisu -3 free_as_in_freedom.rms_and_free_software.sam_williams.sst 1540 or the same: 1541 sisu -NhwpoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst 1542 look at output results, see the "sisu_manifest" page created for the document 1543 or to generate an online document move to a writable directory, as the file will be downloaded there and e.g. 1544 sisu -3 <http://www.jus.uio.no/sisu/src/free_culture.lawrence_lessig.sst> 1545 the database stuff is extra perhaps, the latex stuff could be considered extra perhaps but neither needs to be installed for most of sisu output to work 1546 examine source document, vim has syntax support 1547 gvim free_as_in_freedom.rms_and_free_software.sam_williams.sst 1548 additional markup samples in 1549 <http://www.jus.uio.no/sisu/SiSU/examples.html> 1550 For help 1551 man sisu 1552 or 1553 sisu --help 1554 e.g. 1555 for the way sisu "sees/maps" your system 1556 sisu --help env 1557 for list of commands and so on 1558 sisu --help commands 1559 42.5 Configuration files 1560 The default configuration/setup is contained within the program and is altered by configuration settings in /etc/[sisu version]/sisurc.yml or in ~/.sisu/sisurc.yml 1561 configuration file - a yaml file 1562 /etc/sisu/[sisu version]/sisurc.yml 1563 ~/.sisu/sisurc.yml 1564 directory structure - setting up of output and working directory. 1565 * skins - changing the appearance of a project, directory or individual documents within ~/.sisu/skin 1566 ~/.sisu/skin/doc contains individual skins, with symbolic links from 1567 ~/.sisu/skin/dir if the contents of a directory are to take a particular document skin. 1568 additional software - eg. Tex and LaTeX (tetex, tetex-base, tetex-extra on Debian) , Postgresql, [sqlite], trang, tidy, makeinfo, ... none of which are required for basic html or XML processing. 1569 if you use Vim as editor there is a syntax highlighter and fold resource config file for SiSU. I hope more syntax highlighters follow. 1570 There are post installation steps (which are really part of the overall installation) 1571 sisu -C in your marked up document directory, should do some auto-configuring provided you have the right permissions for the output directories. (and provided the output directories have already been specified if you are not using the defaults). 1572 42.6 Use General Overview 1573 Documents are marked up in SiSU syntax and kept in an ordinary text editable file, named with the suffix .sst, or .ssm 1574 Marked up SiSU documents are usually kept in a sub-directory of your choosing 1575 use the interactive help and man pages 1576 sisu --help 1577 man sisu 1578 42.7 Help 1579 interactive help described below, or man page: 1580 man sisu 1581 man 8 sisu 1582 'man sisu_markup-samples' [if the sisu-markup-samples package is also installed] 1583 Once installed an interactive help is available typing 'sisu' (without) any flags, and select an option: 1584 sisu 1585 alternatively, you could type e.g. 1586 sisu --help commands 1587 sisu --help env 1588 sisu --help headers 1589 sisu --help markup 1590 sisu --help headings 1591 etc. 1592 for questions about mappings, output paths etc. 1593 sisu --help env 1594 sisu --help path 1595 sisu --help directory 1596 42.8 Directory Structure 1597 Once installed, type: 1598 sisu --help env 1599 or 1600 sisu -V 1601 42.9 Configuration File 1602 The defaults can be changed via SiSU' s configure file sisurc.yml which the program expects to find in ./_sisu ~/.sisu or /etc/sisu (searched in that order, stopping on the first one found) 1603 42.10 Markup 1604 See man pages. 1605 man sisu 1606 man 8 sisu 1607 Once installed there is some information on SiSU Markup in its help: 1608 sisu --help markup 1609 and 1610 sisu --help headers 1611 Sample marked up document are provided with the download tarball in the directory: 1612 ./data/doc/sisu/markup-samples/ 1613 These are installed on the system usually at: 1614 /usr/share/doc/sisu/markup-samples/ 1615 More markup samples are available in the package sisu-markup-samples, which if installed should be available at: 1616 /usr/share/doc/sisu/markup-samples-non-free/ 1617 Many more are available online off: 1618 <http://www.jus.uio.no/sisu/SiSU/examples.html> 1619 42.11 Additional Things 1620 There is syntax support for some editors provided (together with a README file) in 1621 ./data/sisu/v2/conf/editor-syntax-etc 1622 usually installed to: 1623 /usr/share/sisu/v2/conf/editor-syntax-etc 1624 42.12 License 1625 License: GPL 3 or later see the copyright file in 1626 ./data/doc/sisu 1627 usually installed to: 1628 /usr/share/doc/sisu 1629 42.13 SiSU Standard 1630 SiSU uses: 1631 Standard SiSU markup syntax, 1632 Standard SiSU meta-markup syntax, and the 1633 Standard SiSU object citation numbering and system 1634 © Ralph Amissah 1997, current 2006 All Rights Reserved. 1635 however note the License section 1636 CHANGELOG 1637 ./CHANGELOG 1638 and see 1639 <http://www.jus.uio.no/sisu/SiSU/changelog.html> 1640 <http://www.jus.uio.no/sisu/SiSU/changelog_markup_samples.html> 1641 Extracts from man 8 sisu 1642 43. Post Installation Setup 1643 43.1 Post Installation Setup - Quick start 1644 After installation of sisu-complete, move to the document samples directory, 1645 cd /usr/share/doc/sisu/markup-samples/samples 1646 [this is not where you would normally work but provides sample documents for testing, you may prefer instead to copy the contents of that directory to a local directory before proceeding] 1647 and in that directory, initialise the output directory with the command 1648 sisu -CC 1649 then run: 1650 sisu -1 free_as_in_freedom.rms_and_free_software.sam_williams.sst 1651 or the same: 1652 sisu -NhwpoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst 1653 look at output results, see the "sisu_manifest" page created for the document 1654 for an overview of your current sisu setup, type: 1655 sisu --help env 1656 or 1657 sisu -V 1658 To generate a document from a remote url accessible location move to a writable directory, (create a work directory and cd into it) as the file will be downloaded there and e.g. 1659 sisu -1 <http://www.jus.uio.no/sisu/src/gpl.fsf.sst> 1660 sisu -3 <http://www.jus.uio.no/sisu/src/free_culture.lawrence_lessig.sst> 1661 examine source document, vim has syntax highlighting support 1662 gvim free_as_in_freedom.rms_and_free_software.sam_williams.sst 1663 additional markup samples in 1664 <http://www.jus.uio.no/sisu/SiSU/examples.html> 1665 it should also be possible to run sisu against sisupods (prepared zip files, created by running the command sisu -S [filename]), whether stored locally or remotely. 1666 sisu -3 <http://www.jus.uio.no/sisu/pod/free_culture.lawrence_lessig.sst.zip> 1667 there is a security issue associated with the running of document skins that are not your own, so these are turned of by default, and the use of the following command, which switches on the associated skin is not recommended: 1668 sisu -3 --trust <http://www.jus.uio.no/sisu/pod/free_culture.lawrence_lessig.sst.zip> 1669 For help 1670 man sisu 1671 sisu --help 1672 sisu --help env for the way sisu "sees/maps" your system 1673 sisu --help commands for list of commands and so on 1674 43.2 Document markup directory 1675 Perhaps the easiest way to begin is to create a directory for sisu marked up documents within your home directory, and copy the file structure (and document samples) provided in the document sample directory: 1676 mkdir ~/sisu_test 1677 cd ~/sisu_test 1678 cp -a /usr/share/doc/sisu/markup-samples/samples/* ~/sisu_test/. 1679 better if you have installed sisu-markup-samples 1680 cp -a /usr/share/doc/sisu/markup-samples-non-free/samples/* ~/sisu_test/. 1681 Tip: 1682 sisu -U [sisu markup filename] 1683 should printout the different possible outputs and where sisu would place them. 1684 Tip: if you want to toggle ansi color add 1685 c 1686 to your flags. 1687 43.2.1 Configuration files 1688 SiSU configuration file search path is: 1689 ./_sisu/sisurc.yaml 1690 ~/.sisu/sisurc.yaml 1691 /etc/sisu/sisurc.yaml 1692 .\"%% Debian Installation Note 1693 43.2.2 Debian INSTALLATION Note 1694 It is best you see 1695 <http://www.jus.uio.no/sisu/SiSU/download.html#debian> 1696 for up the most up to date information. 1697 notes taken from the Debian control file (end edited), gives an idea of additional packages that SiSU can make use of if available, (the use/requirement of some of which are interdependent for specific actions by SiSU) : 1698 Package: sisu 1699 SiSU is a lightweight markup based, command line oriented, document structuring, publishing and search framework for document collections. 1700 With minimal preparation of a plain-text, (UTF-8) file, using its native markup syntax in your text editor of choice, SiSU can generate various document formats (most of which share a common object numbering system for locating content), including plain text, HTML, XHTML, XML, OpenDocument text (ODF:ODT), EPUB, LaTeX, PDF files, and populate an SQL database with objects (roughly paragraph-sized chunks) so searches may be performed and matches returned with that degree of granularity: your search criteria is met by these documents and at these locations within each document. Object numbering is particularly suitable for "published" works (finalized texts as opposed to works that are frequently changed or updated) for which it provides a fixed means of reference of content. Document outputs also share semantic meta-data provided. 1701 SiSU also provides concordance files, document content certificates and manifests of generated output. 1702 A vim syntax highlighting file and an ftplugin with folds for sisu markup is provided, as are syntax highlighting files for kate, kwrite, gedit and diakonos. Vim 7 includes syntax highlighting for SiSU. 1703 man pages, and interactive help are provided. 1704 Dependencies for various features are taken care of in sisu related packages. The package sisu-complete installs the whole of SiSU. 1705 Additional document markup samples are provided in the package sisu-markup-samples which is found in the non-free archive the licenses for the substantive content of the marked up documents provided is that provided by the author or original publisher. 1706 Homepage: <http://www.sisudoc.org> 1707 old homepage: <http://www.jus.uio.no/sisu> 1708 43.2.3 Document Resource Configuration 1709 sisu resource configuration information is obtained from sources (where they exist): 1710 ~/.sisu/sisurc.yaml 1711 /etc/sisu/[sisu version]/sisurc.yaml 1712 sisu program defaults 1713 43.2.4 Skins 1714 Skins default document appearance may be modified using skins contained in sub-directories located at the following paths: 1715 ./_sisu/skin 1716 ~/.sisu/skin 1717 /etc/sisu/skin 1718 more specifically, the following locations (or their /etc/sisu equivalent) should be used: 1719 ~/.sisu/skin/doc 1720 skins for individual documents; 1721 ~/.sisu/skin/dir 1722 skins for directories of matching names; 1723 ~/.sisu/skin/site 1724 site-wide skin modifying the site-wide appearance of documents. 1725 Usually all skin files are placed in the document skin directory: 1726 ~/.sisu/skin/doc 1727 with softlinks being made to the skins contained there from other skin directories as required. 1728 44. FAQ - Frequently Asked/Answered Questions 1729 44.1 Why are urls produced with the -v (and -u) flag that point to a web server on port 8081 ? 1730 Try the following rune: 1731 sisu -W 1732 This should start the ruby webserver. It should be done after having produced some output as it scans the output directory for what to serve. 1733 44.2 I cannot find my output, where is it? 1734 The following should provide help on output paths: 1735 sisu --help env 1736 sisu -V [same as the previous command] 1737 sisu --help directory 1738 sisu --help path 1739 sisu -U [filename] 1740 man sisu 1741 44.3 I do not get any pdf output, why? 1742 SiSU produces LaTeX and pdflatex is run against that to generate pdf files. 1743 If you use Debian the following will install the required dependencies 1744 aptitude install sisu-pdf 1745 the following packages are required: tetex-bin, tetex-extra, latex-ucs 1746 44.4 Where is the latex (or some other interim) output? 1747 Try adding -M (for maintenance) to your command flags, e.g.: 1748 sisu -HpMv [filename] 1749 this should result in the interim processing output being retained, and information being provided on where to find it. 1750 sisu --help directory 1751 sisu --help path 1752 should also provide some relevant information as to where it is placed. 1753 44.5 Why isn't SiSU markup XML 1754 I worked with text and (though I find XML immensely valuable) disliked noise ... better to sidestep the question and say: 1755 SiSU currently "understands" three XML input representations - or more accurately, converts from three forms of XML to native SiSU markup for processing. The three types correspond to SAX (structure described), DOM (structure embedded, whole document must be read before structure is correctly discernable) and node based (a tree) forms of XML document structure representation. Problem is I use them very seldom and check that all is as it should be with them seldom, so I would not be surprised if something breaks there, but as far as I know they are working. I will check and add an XML markup help page before the next release. There already is a bit of information in the man page under the title SiSU VERSION CONVERSION 1756 sisu --to-sax [filename/wildcard] 1757 sisu --to-dom [filename/wildcard] 1758 sisu --to-node [filename/wildcard] 1759 The XML should be well formed... must check, but lacks sensible headers. Suggestions welcome as to what to make of them. [For the present time I am satisfied that I can convert (both ways) between 3 forms of XML representation and SiSU markup]. 1760 sisu --from-xml2sst [filename/wildcard] 1761 44.6 LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU? 1762 SiSU is not really about type-setting. 1763 LaTeX is the ultimate computer instruction type-setting language for paper based publication. 1764 LaTeX is able to control just about everything that happens on page and pixel, position letters kerning, space variation between characters, words, paragraphs etc. formula. 1765 SiSU is not really about type-setting at all. It is about a lightweight markup instruction that provides enough information for an abstraction of the documents structure and objects, from which different forms of representation of the document can be generated. 1766 SiSU with very little markup instruction is able to produce relatively high quality pdf by virtue of being able to generate usable default LaTeX; it produces "quality" html by generating the html directly; likewise it populates an SQL database in a useful way with the document in object sized chunks and its meta-data. But SiSU works on an abstraction of the document's structure and content and custom builds suitable uniform output. The html for browser viewing and pdf for paper viewing/publishing are rather different things with different needs for layout - as indeed is what is needed to store information in a database in searchable objects. 1767 The pdfs or html produced for example by open office based on open document format and other office/word processor suits usually attempt to have similar looking outputs - your document rendered in html looks much the same, or in pdf... sisu is less this way, it seeks to have a starting point with as little information about appearance as possible, and to come up with the best possible appearance for each output that can be derived based on this minimal information. 1768 Where there are large document sets, it provides consistency in appearance in each output format for the documents. 1769 The excuse for going this way is, it is a waste of time to think much about appearance when working on substantive content, it is the substantive content that is relevant, not the way it looks beyond the basic informational tags - and yet you want to be able to take advantage of as many useful different ways of representing documents as are available, and for various types of output to to be/look as good as it can for each medium/format in which it is presented, (with different mediums having different focuses) and SiSU tries to achieve this from minimal markup. 1770 44.7 Can the SiSU markup be used to prepare for a LaTex automatic building of an index to the work? 1771 Has not been, is of interest though the question on introducing such possibilities is how to keep them as unobtrusive as possible, and as generically relevant as possible to other output formats (which is why the focus on object numbers). Unobtrusive refers both to the markup (where there is no big problem with introducing optional extras); and, more challengingly how to minimise impact on competing ideas/interests, such allowing the addition of semantic tags which could be tied to objects, mapped against the objects that contain them, (permitting mapping and mining of content in various ways that would be largely agnostic of output format - object numbering being an attempt to move beyond output format based content locators (such as page numbers). The desire being to (be a meta markup and) maintain agnosticism as to what is being generated and in development to favor solutions of that nature. Keep bridging LaTeX, XML, SQL ... make use of objects and serialisation for mapping whether against content or meta-content (such as semantic [or additional structural] markers). 1772 44.8 Can the conversion from SiSU to LaTeX be modified if we have special needs for the LaTeX, or do we need to modify the LaTeX manually? 1773 Should be possible to modify code, it is GPLv3, should be possible either to modify existing modules or write an independent module for generating bespoke latex. Generic improvements are welcome for inclusion/incorporation in the existing code base. 1774 If there are tools to generate mathematical/scientific formula from latex to images (jpg, png), the latex parser could conceivably be used to make these available to other output formats. 1775 44.9 How do I create GIN or GiST index in Postgresql for use in SiSU 1776 This at present needs to be done "manually" and it is probably necessary to alter the sample search form. The following is a helpful response from one of the contributors of GiN to Postgresql Oleg Bartunov 2006-12-06: 1777 "I have tsearch2 slides which introduces tsearch2 <http://www.sai.msu.su/~megera/wiki/tsearch2slides> 1778 FTS in PostgreSQL is provided by tsearch2, which should works without any indices (GiST or GIN) ! Indices provide performance, not functionality. 1779 In your example I'd do ( simple way, just for demo): 1780 0. compile, install tsearch2 and load tsearch2 into your database 1781 cd contrib/tsearch2; make&&make&&install&&make installcheck; psql DB < tsearch2.sql 1782 1. Add column fts, which holds tsvector 1783 alter table documents add column fts tsvector; 1784 2. Fill fts column 1785 update document set fts = to_tsvector(clean); 1786 3. create index - just for performance ! 1787 create index fts_gin_idx on document using gin(fts); 1788 4. Run vacuum 1789 vacuum analyze document; 1790 That's all. 1791 Now you can search: 1792 select lid, metadata_tid, rank_cd(fts, q,2)as rank from document, plainto_tsquery('markup syntax') q where q @@ fts order by rank desc limit 10; 1793 44.10 Are there some examples of using Ferret Search with a SiSU repository? 1794 Heard good things about Ferret, but have not used it. The output directory structure and content produced by SiSU is very uniform. Have looked at a couple of other engines (hyperestraier, lucene). There it was enough to identify the files that needed to be indexed and pass them to the search indexing tool. Some Unix rune doing the job, such as: 1795   find /home/ralph/sisu_www -type f | \
     egrep '/sisu_www/(sisu|document_archive)/.+?.html$' | \
     egrep -v '(doc|concordance).html$' | \
     estcmd gather -sd casket -

 1796 you would have to experiment with what gives the desired result, the file doc.html is the complete text in html (there are additional smaller html segments), and plain.txt the document as a text file. It may be possible to index the text file and return the html document. 1797 Have you had any reports of building SiSU from tar on Mac OS 10.4? 1798 None. In the early days of its release a Mac friend built and run the ruby code part that did not rely on system calls to bits like the latex engine. That is already some years back. He was not into writing or document markup, and did it as a favour at the time. I have not followed up that thread of development. 1799 It should however be possible, much of the output relies on plain ruby, and the system commands to latex etc. could be made appropriate for the underlying OS. 1800 44.12 Where is version 1? 1801 Version 1 was finally released on December 21, 2009, and largely to make a version 1 branch available as version 2 was in the pipeline with an imminent release. Most of SiSU was mature and stable long before the release of version 1. 1802 44.13 What is the difference between version 1 and 2? 1803 Input and output of version 1 and 2 are largely the same with the following significant exceptions. On the input side, document headers, that is metadata and processing instructions have changed in version 2. On the output side, version 2 was introduced with EPUB documents as a possible output, and over time is likely to be developed further. 1804 Version 2 introduces a new processing layer, which relies more on the programming language Ruby' s objects (and regular expressions), than version 1 does which relies on regular expressions. The thinking behind version 1 use of regular expressions was that it made it more straightforward to switch languages for processing, as many languages support regular expressions; the thinking behind version 2 was version 1 was more complicated than it need be, and since Ruby was the language used, why not make programming more straightforward, as it would be easier to develop further. 1805 Version 1 was removed with the introduction of the version 3 development branch 1806 45. Who might be interested in the SiSU feature set? 1807 SiSU is most likely to be of interest to people who are working with medium to large volumes of published texts that would like to have the presented in a uniform way that is searchable (either using sisu database integration or an appropriate indexing tool), with the possibility of multiple alternative output formats that may be added to and upgraded/updated over time. SiSU should be of interest to institutions/ organisations/ governments/ individuals with document collections and some technical knowhow that are interested in: 1808 long term maintenance and reducing downstream/future costs of maintaining those document sets for which SiSU is suited. 1809 the ability to output multiple standard format outputs for various purposes. 1810 the implications for search offered 1811 46. Work Needed 1812 SiSU is fairly mature and for most purposes the syntax and what it is supposed to do is clear. For the most part additions and changes are minor and backward compatible, (in particular there may be things of interest that to be able to achieve will require additions to the syntax). 1813 Amongst the most requested features is a way to represent and extract bibliographies from scholarly and other writings. This involves an extension of sisu markup syntax and a new module to extract the bibliography. 1814 Integration of postgresql tsearch2 / gin indexing, (which currently needs to be done manually, and) which has been waiting for the integration of tsearch2 / gin into Postgresql main, which is supposed to occur in Postgresql 8.3 1815 Internationalisation always. SiSU is utf-8 and for those parts that are utf-8 friendly will work out of the box - html and postgresql for example work out of the box (and for example comfortably represent Chinese text), LaTeX and odf do not work out of the box, they need additional work for extended language sets. 1816 Refinements and improvements to output representations, some are fairly mature, others (such as manpages and info files (and even ODF) remain young. 1817 Simple extension to contain, link and share included audio and multi-media files, (including sisupod.zip) 1818 47. Wishlist 1819 SiSU provides a lot of "plumbing" and is readily usable as a tool by those comfortable with marking up documents with an editor. The syntax is fairly easy to learn, especially the subset required to start using SiSU effectively. 1820 SiSU might also be of interest to developers interested in: 1821 experimenting with the search implications offered 1822 producing additional output formats 1823 producing conversion tools 1824 producing input interfaces, (experimenting with additional interfaces for producing sisu source documents) 1825 Several tools that are of interest would come under the heading interface and conversion. Amongst others, the following are of interest: 1826 Converters from various document formats, such as Open Document Text (ODF), MS Word(TM) and Word Perfect(TM), even html. The problem here is one of the most important things for SiSU is to be able to recognise the structure of a document, and many documents prepared in other formats have not been prepared strictly with a view to representing structure, but appearance - so heading levels may be "painted" to look right rather than have the correct structural representation. Even if conversion is not perfect this may serve as a first step in assisting in conversion of documents to SiSU for those with legacy document sets that they would like to have in sisu format. (once in SiSU it is easier to get out in various other formats as this is what sisu does, within the constraints of the information that sisu uses to generate output) 1827 The possibility to save directly from from various word processors, and possibly templates within them to assist in making sure the document structure is "understood" by SiSU. 1828 Web interface/front-end, a form like front end for the writing or submission of sisu documents to a server which uses SiSU to generate output. Headers could be made available as separate small entry forms with help provided to explain where they might be used. Apart from the most important headers such as title, author, date and possibly subject the remainder of the header forms could be placed after the form for substantive content. This would offer a more Web 2.0 like approach to the use of SiSU and the possibility of using it for collaborative editing of content (possibly for documents that are to be finalised/published as the citation system is most suited to published works). [Collaborative editing is currently possible through use of a collaborative editor such as Gobby which makes use of the Obby protocol]. 1829 48. Editor Files, Syntax Highlighting 1830 The directory: 1831 ./data/sisu/v2/conf/editor-syntax-etc/ 1832 ./data/sisu/v3/conf/editor-syntax-etc/ 1833 /usr/share/sisu/v2/conf/editor-syntax-etc 1834 /usr/share/sisu/v3/conf/editor-syntax-etc 1835 contains rudimentary sisu syntax highlighting files for: 1836 (g)vim <http://www.vim.org> 1837 package: sisu-vim 1838 status: largely done 1839 there is a vim syntax highlighting and folds component 1840 gedit <http://www.gnome.org/projects/gedit> 1841 gobby <http://gobby.0x539.de/> 1842 file: sisu.lang 1843 place in: 1844 /usr/share/gtksourceview-1.0/language-specs 1845 or 1846 ~/.gnome2/gtksourceview-1.0/language-specs 1847 status: very basic syntax highlighting 1848 comments: this editor features display line wrap and is used by Goby! 1849 nano <http://www.nano-editor.org> 1850 file: nanorc 1851 save as: 1852 ~/.nanorc 1853 status: basic syntax highlighting 1854 comments: assumes dark background; no display line-wrap; does line breaks 1855 diakonos (an editor written in ruby) <http://purepistos.net/diakonos> 1856 file: diakonos.conf 1857 save as: 1858 ~/.diakonos/diakonos.conf 1859 includes: 1860 status: basic syntax highlighting 1861 comments: assumes dark background; no display line-wrap 1862 kate & kwrite <http://kate.kde.org> 1863 file: sisu.xml 1864 place in: 1865 /usr/share/apps/katepart/syntax 1866 or 1867 ~/.kde/share/apps/katepart/syntax 1868 [settings::configure kate::{highlighting,filetypes}] 1869 [tools::highlighting::markup,scripts] 1870 nedit <http://www.nedit.org> 1871 file: sisu_nedit.pats 1872 nedit -import sisu_nedit.pats 1873 status: a very clumsy first attempt [not really done] 1874 comments: this editor features display line wrap 1875 emacs <http://www.gnu.org/software/emacs/emacs.html> 1876 files: sisu-mode.el 1877 to file ~/.emacs add the following 2 lines: 1878 (add-to-list 'load-path "/usr/share/sisu/v2/conf/editor-syntax-etc/emacs") 1879 (require 'sisu-mode.el) 1880 [not done / not yet included] 1881 vim & gvim <http://www.vim.org> 1882 files: 1883 package is the most comprehensive sisu syntax highlighting and editor environment provided to date (is for vim/ gvim, and is separate from the contents of this directory) 1884 status: this includes: syntax highlighting; vim folds; some error checking 1885 comments: this editor features display line wrap 1886 NOTE: 1887 [SiSU parses files with long lines or line breaks, but, display linewrap (without line-breaks) is a convenient editor feature to have for sisu markup] 1888 49. Help Sources 1889 49.1 man pages 1890 man sisu 1891 man sisu-concordance 1892 man sisu-epub 1893 man sisu-git 1894 man sisu-harvest 1895 man sisu-html 1896 man sisu-odf 1897 man sisu-pdf 1898 man sisu-pg 1899 man sisu-po 1900 man sisu-sqlite 1901 man sisu-txt 1902 man 7 sisu_complete 1903 man 7 sisu_pdf 1904 man 7 sisu_postgresql 1905 man 7 sisu_sqlite 1906 man sisu_termsheet 1907 man sisu_webrick 1908 49.2 sisu generated output - links to html 1909 Note SiSU documentation is prepared in SiSU and output is available in multiple formats including amongst others html, pdf, odf and epub, which may be also be accessed via the html pages112 112 named index.html or more extensively through sisu_manifest.html 1910 49.2.1 www.sisudoc.org 1911 <http://sisudoc.org/sisu/sisu_manual/index.html> 1912 <http://sisudoc.org/sisu/sisu_manual/index.html> 1913 49.3 man2html 1914 49.3.1 locally installed 1915 file:///usr/share/doc/sisu/html/sisu.1.html 1916 file:///usr/share/doc/sisu/html/sisu.1.html 1917 /usr/share/doc/sisu/html/sisu_pdf.7.html 1918 /usr/share/doc/sisu/html/sisu_postgresql.7.html 1919 /usr/share/doc/sisu/html/sisu_sqlite.7.html 1920 /usr/share/doc/sisu/html/sisu_webrick.1.html 1921 49.3.2 www.jus.uio.no/sisu 1922 <http://www.jus.uio.no/sisu/man/sisu.1.html> 1923 <http://www.jus.uio.no/sisu/man/sisu.1.html> 1924 <http://www.jus.uio.no/sisu/man/sisu_complete.7.html> 1925 <http://www.jus.uio.no/sisu/man/sisu_pdf.7.html> 1926 <http://www.jus.uio.no/sisu/man/sisu_postgresql.7.html> 1927 <http://www.jus.uio.no/sisu/man/sisu_sqlite.7.html> 1928 <http://www.jus.uio.no/sisu/man/sisu_webrick.1.html> 1929 Endnotes 1930 Endnotes