Title: SiSU - SiSU information Structuring Universe - Manual [0.58]
Creator: Ralph Amissah
Rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3
Type: information
Subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search
Date created: 2002-08-28
Date issued: 2002-08-28
Date available: 2002-08-28
Date modified: 2007-08-30
Date: 2007-08-30
1 SiSU - SiSU information Structuring Universe - Manual [0.58],
Ralph Amissah
2 What is SiSU? 3 sisu_intro 1. Introduction - What is SiSU? 4 SiSU is a system for document markup, publishing (in multiple open standard formats) and search 5 SiSU1"SiSU information Structuring Universe" or "Structured information, Serialized Units".
also chosen for the meaning of the Finnish term "sisu".
is a2Unix command line oriented framework for document structuring, publishing and search, comprising of (a) a lightweight document structure and presentation markup syntax and (b) an accompanying engine for generating standard document format outputs from documents prepared in sisu markup syntax, which is able to produce multiple standard outputs that (can) share a common numbering system for the citation of text within a document.
6 SiSU is developed under an open source, software libre license (GPL3). It has been developed in the context of coping with large document sets with evolving markup related technologies, for which you want multiple output formats, a common mechanism for cross-output-format citation, and search. 7 SiSU both defines a markup syntax and provides an engine that produces open standards format outputs from documents prepared with SiSU markup. From a single lightly prepared document sisu custom builds several standard output formats which share a common (text object) numbering system for citation of content within a document (that also has implications for search). The sisu engine works with an abstraction of the document's structure and content from which it is possible to generate different forms of representation of the document. Significantly SiSU markup is more sparse than html and outputs which include html, LaTeX, landscape and portrait pdfs, Open Document Format (ODF), all of which can be added to and updated. SiSU is also able to populate SQL type databases at an object level, which means that searches can be made with that degree of granularity. Results of objects (primarily paragraphs and headings) can be viewed directly in the database, or just the object numbers shown - your search criteria is met in these documents and at these locations within each document. 8 Source document preparation and output generation is a two step process: (i) document source is prepared, that is, marked up in sisu markup syntax and (ii) the desired output subsequently generated by running the sisu engine against document source. Output representations if updated (in the sisu engine) can be generated by re-running the engine against the prepared source. Using SiSU markup applied to a document, SiSU custom builds various standard open output formats including plain text, HTML, XHTML, XML, OpenDocument, LaTeX or PDF files, and populate an SQL database with objects3objects include: headings, paragraphs, verse, tables, images, but not footnotes/endnotes which are numbered separately and tied to the object from which they are referenced. (equating generally to paragraph-sized chunks) so searches may be performed and matches returned with that degree of granularity ( e.g. your search criteria is met by these documents and at these locations within each document). Document output formats share a common object numbering system for locating content. This is particularly suitable for "published" works (finalized texts as opposed to works that are frequently changed or updated) for which it provides a fixed means of reference of content. 9 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 builds4i.e. the html, pdf, odf outputs are each built individually and optimised for that form of presentation, rather than for example the html being a saved version of the odf, or the pdf being a saved version of the html. the different forms of output requested. 10 SiSU works with an abstraction of the document based on its structure which is comprised of its frame5the different heading levels and the objects6units of text, primarily paragraphs and headings, also any tables, poems, code-blocks it contains, which enables SiSU to represent the document in many different ways, and to take advantage of the strengths of different ways of presenting documents. The objects are numbered, and these numbers can be used to provide a common base for citing material within a document across the different output format types. This is significant as page numbers are not suited to the digital age, in web publishing, changing a browser's default font or using a different browser means that text appears on different pages; and in publishing in different formats, html, landscape and portrait pdf etc. again page numbers are of no use to cite text in a manner that is relevant against the different output types. Dealing with documents at an object level together with object numbering also has implications for search. 11 One of the challenges of maintaining documents is to keep them in a format that would allow users to use them without depending on a proprietary software popular at the time. Consider the ease of dealing with legacy proprietary formats today and what guarantee you have that old proprietary formats will remain (or can be read without proprietary software/equipment) in 15 years time, or the way the way in which html has evolved over its relatively short span of existence. SiSU provides the flexibility of outputing documents in multiple non-proprietary open formats including html, pdf7Specification submitted by Adobe to ISO to become a full open ISO specification
<http://www.linux-watch.com/news/NS7542722606.html>
and the ISO standard ODF.8ISO/IEC 26300:2006 Whilst SiSU relies on software, the markup is uncomplicated and minimalistic which guarantees that future engines can be written to run against it. It is also easily converted to other formats, which means documents prepared in SiSU can be migrated to other document formats. Further security is provided by the fact that the software itself, SiSU is available under GPL3 a licence that guarantees that the source code will always be open, and free as in libre which means that that code base can be used updated and further developed as required under the terms of its license. Another challenge is to keep up with a moving target. SiSU permits new forms of output to be added as they become important, (Open Document Format text was added in 2006), and existing output to be updated (html has evolved and the related module has been updated repeatedly over the years, presumably when the World Wide Web Consortium (w3c) finalises html 5 which is currently under development, the html module will again be updated allowing all existing documents to be regenerated as html 5).
12 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. 13 SiSU also provides other features such as concordance files and document content certificates, and the working against an abstraction of document structure has further possibilities for the research and development of other document representations, the availability of objects is useful for example for topic maps and the commercial law thesaurus by Vikki Rogers and Al Krtizer, together with the flexibility of SiSU offers great possibilities. 14 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. 15 <http://www.jus.uio.no/sisu>
16 sisu_how 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 sisu_feature_summary 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, 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 XML - both in sax and dom style xml structures for further development as required 26 ODF - open document format, the iso standard for document storage 27 LaTeX - used to generate pdf 28 pdf (via LaTeX) 29 sql - population of an sql database, (at the same object level that is used to cite text within a document) 30 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)) 31 ensuring content can be cited in a meaningful way regardless of selected output format. Online publishing (and publishing in multiple document formats) lacks a useful way of citing text internally within documents (important to academics generally and to lawyers) as page numbers are meaningless across browsers and formats. sisu seeks to provide a common way of pinpoint the text within a document, (which can be utilized for citation and by search engines). The outputs share a common numbering system that is meaningful (to man and machine) across all digital outputs whether paper, screen, or database oriented, (pdf, HTML, xml, sqlite, postgresql), this numbering system can be used to reference content. 32 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]. 33 long term maintainability of document collections in a world of changing formats, having a very sparsely marked-up source document base. there is a considerable degree of future-proofing, output representations are "upgradeable", and new document formats may be added. e.g. addition of odf (open document text) module in 2006 and in future html5 output sometime in future, without modification of existing prepared texts 34 SQL search aside, documents are generated as required and static once generated. 35 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) 36 document source (plaintext utf-8) if shared on the net may be used as input and processed locally to produce the different document outputs 37 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 38 generated document outputs may automatically be posted to remote sites. 39 for basic document generation, the only software dependency is Ruby, and a few standard Unix tools (this covers plaintext, HTML, XML, ODF, LaTeX). To use a database you of course need that, and to convert the LaTeX generated to pdf, a latex processor like tetex or texlive. 40 as a developers tool it is flexible and extensible 41 Syntax highlighting for SiSU markup is available for a number of text editors. 42 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 43 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)... 44 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. 45 help 4. Help 46 4.1 4.1 SiSU Manual 47 The most up to date information on sisu should be contained in the sisu_manual, available at: 48 <http://www.jus.uio.no/sisu/sisu_manual/> 49 and (from SiSU 0.59 onwards) installed locally at: 50 /usr/share/doc/sisu/sisu_manual/ 51 or equivalent directory 52 Within the SiSU tarball at: 53 ./data/doc/sisu/sisu_manual/ 54 4.2 4.2 SiSU man pages 55 If SiSU is installed on your system usual man commands should be available, try: 56 man sisu 57 man sisu_markup 58 man sisu_commands 59 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: 60 ./data/doc/sisu/sisu_manual/ 61 Once installed, directory equivalent to: 62 /usr/share/doc/sisu/sisu_manual/ 63 Available man pages are converted back to html using man2html: 64 /usr/share/doc/sisu/html/ 65 ./data/doc/sisu/html/ 66 The SiSU man pages can be viewed online at:9generated 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>
67 An online version of the sisu man page is available here: 68 various sisu man pages 10<http://www.jus.uio.no/sisu/man/> 69 sisu.1 11<http://www.jus.uio.no/sisu/man/sisu.1.html> 70 sisu.8 12<http://www.jus.uio.no/sisu/man/sisu.8.html> 71 sisu_examples.1 13<http://www.jus.uio.no/sisu/man/sisu_examples.1.html> 72 sisu_webrick.1 14<http://www.jus.uio.no/sisu/man/sisu_webrick.1.html>
73 4.3 4.3 SiSU built-in interactive help 74 This is particularly useful when current installation information is obtained as the interactive help is able to provide information on your sisu configuration and setup. 75 sisu --help 76 sisu --help [subject] 77 sisu --help env [for feedback on the way your system is setup with regard to sisu] 78 sisu -V [same as above command] 79 sisu --help commands 80 sisu --help markup 81 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). 82 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. 83 4.4 4.4 Help Sources 84 For lists of alternative help sources, see: 85 man page 86 man sisu_help_sources 87 man2html 88 /usr/share/doc/sisu/sisu_manual/sisu_help_sources/index.html 89 sisu generated html 90 /usr/share/doc/sisu/html/sisu_help_sources/index.html 91 <http://sisudoc.org/sisu_manual/sisu_help_sources/index.html> 92 <http://www.jus.uio.no/sisu/sisu_manual/sisu_help_sources/index.html>
93 commands 5. Commands Summary 94 5.1 5.1 Synopsis 95 SiSU - Structured information, Serialized Units - a document publishing system 96 sisu [ -abcDdFHhIiMmNnopqRrSsTtUuVvwXxYyZz0-9 ] [ filename/ wildcard ] 97 sisu [ -Ddcv ] [ instruction ] 98 sisu [ -CcFLSVvW ] 99 Note: commands should be issued from within the directory that contains the marked up files, cd to markup directory. 100 5.2 5.2 Description 101 SiSU SiSU is a document publishing system, that from a simple single marked-up document, produces multiple of output formats including: plaintext, html, LaTeX, pdf, xhtml, XML, 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> 102 5.3 5.3 Document Processing Command Flags 103 -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)
104 -b [filename/wildcard]
produces xhtml/XML output for browser viewing (sax parsing).
105 -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.
106 -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.
107 -c [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).
108 -D [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.
109 -d [--db-[database type (sqlite|pg)]] --[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.
110 -F [--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
111 -H [filename/wildcard]
produces html without link suffixes (.html .pdf etc.) ("Hide"). Requires an appropriately configured web server. [behaviour switched after 0.35 see -h].
112 -h [filename/wildcard]
produces html (with hardlinks i.e. with name suffixes in links/local urls). html, with internal document links that include the document suffix, i.e. whether it is .html or .pdf (required for browsing directly off a file system, and works with most web servers). [behaviour switched after 0.35 see -H].
113 -I [filename/wildcard]
produces texinfo and info file, (view with pinfo).
114 -L
prints license information.
115 -M [filename/wildcard/url]
maintenance mode files created for processing preserved and their locations indicated. (also see -V)
116 -m [filename/wildcard/url]
assumed for most other flags, creates new meta-markup file, (the metaverse ) that is used in all subsequent processing of other output. This step is assumed for most processing flags. To skip it see -n
117 -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.
118 -n [filename/wildcard/url]
skip meta-markup (building of "metaverse"), this skips the equivalent of -m which is otherwise assumed by most processing flags.
119 -o [filename/wildcard/url]
output basic document in opendocument file format (opendocument.odt).
120 -p [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).
121 -q [filename/wildcard]
quiet less output to screen.
122 -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
123 -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
124 -S
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).
125 -S [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].
126 -s [filename/wildcard]
copies sisu markup file to output directory.
127 -t [filename/wildcard (*.termsheet.rb)]
standard form document builder, preprocessing feature
128 -U [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
129 -u [filename/wildcard]
provides url mapping of output files for the flags requested for processing, also see -U
130 -V
on its own, provides SiSU version and environment information (sisu --help env)
131 -V [filename/wildcard]
even more verbose than the -v flag. (also see -M)
132 -v
on its own, provides SiSU version information
133 -v [filename/wildcard]
provides verbose output of what is being built, where it is being built (and error messages if any), as with -u flag provides a url mapping of files created for each of the processing flag requests. See also -V
134 -W
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 ].
135 -w [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)
136 -X [filename/wildcard]
produces XML output with deep document structure, in the nature of dom.
137 -x [filename/wildcard]
produces XML output shallow structure (sax parsing).
138 -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])
139 -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.
140 -Z [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.
141 -z [filename/wildcard]
produces php (zend) [this feature is disabled for the time being]
142 command_modifiers 6. command line modifiers 143 --no-ocn
[with -h -H or -p] switches off object citation numbering. Produce output without identifying numbers in margins of html or LaTeX/pdf output.
144 --no-annotate
strips output text of editor endnotes*1square brackets denoted by asterisk or dagger/plus sign
145 --no-asterisk
strips output text of editor endnotes*2square brackets denoted by asterisk sign
146 --no-dagger
strips output text of editor endnotes+1square brackets denoted by dagger/plus sign
147 commands_database 7. database commands 148 dbi - database interface 149 -D or --pgsql set for postgresql -d or --sqlite default set for sqlite -d is modifiable with --db=[database type (pgsql or sqlite)] 150 -Dv --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.
151 -Dv --import
[filename/wildcard] imports data specified to postgresql db (rb.dbi) [ -dv --import sqlite equivalent]
152 -Dv --update
[filename/wildcard] updates/imports specified data to postgresql db (rb.dbi) [ -dv --update sqlite equivalent]
153 -D --remove
[filename/wildcard] removes specified data to postgresql db (rb.dbi) [ -d --remove sqlite equivalent]
154 -D --dropall
kills data" and drops (postgresql or sqlite) db, tables & indexes [ -d --dropall sqlite equivalent]
155 The v in e.g. -Dv is for verbose output.
156 command_shorcuts 8. Shortcuts, Shorthand for multiple flags 157 --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.
158 -0 to -5 [filename or wildcard]
Default shorthand mappings (note that the defaults can be changed/configured in the sisurc.yml file):
159 -0
-mNhwpAobxXyYv [this is the default action run when no options are give, i.e. on 'sisu [filename]']
160 -1
-mNHwpy
161 -2
-mNHwpaoy
162 -3
-mNhwpAobxXyY
163 -4
-mNhwpAobxXDyY --import
164 -5
-mNhwpAobxXDyY --update
165 add -v for verbose mode and -c for color, e.g. sisu -2vc [filename or wildcard] 166 consider -u for appended url info or -v for verbose output
167 8.0.1 8.0.1 Command Line with Flags - Batch Processing 168 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. 169 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.
170 markup 9. Introduction to SiSU Markup15From sometime after SiSU 0.58 it should be possible to describe SiSU markup using SiSU, which though not an original design goal is useful. 171 9.1 9.1 Summary 172 SiSU source documents are plaintext (UTF-8)16files should be prepared using UTF-8 character encoding files 173 All paragraphs are separated by an empty line. 174 Markup is comprised of: 175 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) 176 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: 177 heading levels defines document structure 178 text basic attributes, italics, bold etc. 179 grouped text (objects), which are to be treated differently, such as code blocks or poems. 180 footnotes/endnotes 181 linked text and images 182 paragraph actions, such as indent, bulleted, numbered-lists, etc. 183 Some interactive help on markup is available, by typing sisu and selecting markup or sisu --help markup 184 9.2 9.2 Markup Examples 185 9.2.1 9.2.1 Online 186 Online markup examples are available together with the respective outputs produced from <http://www.jus.uio.no/sisu/SiSU/2.html> or from <http://www.jus.uio.no/sisu/sisu_examples/> 187 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/> 188 Some example marked up files are available as html with syntax highlighting for viewing: <http://www.jus.uio.no/sisu/sample/syntax> 189 an alternative presentation of markup syntax: <http://www.jus.uio.no/sisu/sample/on_markup.txt> 190 9.2.2 9.2.2 Installed 191 With SiSU installed sample skins may be found in: /usr/share/doc/sisu/sisu_markup_samples/dfsg (or equivalent directory) and if sisu-markup-samples is installed also under: /usr/share/doc/sisu/sisu_markup_samples/non-free 192 headers 10. Markup of Headers 193 Headers consist of semantic meta-data about a document, which can be used by any output module of the program; and may in addition include extra processing instructions. 194 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: 195      % this would be a comment     196 10.1 10.1 Sample Header 197 This current document has a header similar to this one (without the comments): 198      % SiSU 0.57

     @title: SiSU

     @subtitle: Markup [0.58]

     @creator: Ralph Amissah

     @rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3

     @type: information

     @subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search

     @date.created: 2002-08-28

     @date.issued: 2002-08-28

     @date.available: 2002-08-28

     @date.modified: 2007-09-16

     @date: 2007-09-16

     @level: new=C; break=1; num_top=1

     % comment: in this @level header num_top=1 starts automatic heading numbering at heading level 1 (numbering continues 3 levels down); the new and break instructions are used by the LaTeX/pdf and odf output to determine where to put page breaks (that are not used by html output or say sql database population).

     @skin: skin_sisu_manual

     % skins modify the appearance of a document and are placed in a sub-directory under ./_sisu/skin ~/.sisu/skin or /etc/sisu/skin. A skin may affect single documents that request them, all documents in a directory, or be site-wide. (A document is affected by a single skin)

     @bold: /Gnu|Debian|Ruby|SiSU/

     @links: { SiSU Manual }http://www.jus.uio.no/sisu/sisu_manual/
     { Book Samples and Markup Examples }http://www.jus.uio.no/sisu/SiSU/2.html
     { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU
     { SiSU @ Freshmeat }http://freshmeat.net/projects/sisu/
     { SiSU @ Ruby Application Archive }http://raa.ruby-lang.org/project/sisu/
     { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html
     { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html
     { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html

    
199 10.2 10.2 Available Headers 200 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 either the form @headername: or 0~headername. All Dublin Core meta tags are available 201 @indentifier: information or instructions 202 where the "identifier" is a tag recognised by the program, and the "information" or "instructions" belong to the tag/indentifier specified 203 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. 204 This is a sample header 205 % SiSU 0.38 [declared file-type identifier with markup version] 206 @title: [title text] This is the title of the document and used as such, this header is the only one that is mandatory 207 @subtitle: The Subtitle if any 208 @creator: [or @author:] Name of Author 209 @subject: (whatever your subject) 210 @description: 211 @publisher: 212 @contributor: 213 @translator: [or @translated_by:] 214 @illustrator: [or @illustrated_by:] 215 @prepared_by: [or @digitized_by:] 216 @date: 2000-08-27 [ also @date.created: @date.issued: @date.available: @date.valid: @date.modified: ] 217 @type: article 218 @format: 219 @identifier: 220 @source: 221 @language: [or @language.document:] [country code for language if available, or language, English, en is the default setting] (en - English, fr - French, de - German, it - Italian, es - Spanish, pt - Portuguese, sv - Swedish, da - Danish, fi - Finnish, no - Norwegian, is - Icelandic, nl - Dutch, et - Estonian, hu - Hungarian, pl - Polish, ro - Romanian, ru - Russian, el - Greek, uk - Ukranian, tr - Turkish, sk - Slovak, sl - Slovenian, hr - Croatian, cs - Czech, bg - Bul garian ) [however, encodings are not available for all of the languages listed.] 222 [@language.original: original language in which the work was published] 223 @papersize: (A4|US_letter|book_B5|book_A5|US_legal) 224 @relation: 225 @coverage: 226 @rights: Copyright (c) Name of Right Holder, all rights reserved, or as granted: public domain, copyleft, creative commons variant, etc. 227 @owner: 228 @keywords: text document generation processing management latex pdf structured xml citation [your keywords here, used for example by rss feeds, and in sql searches] 229 @abstract: [paper abstract, placed after table of contents] 230 @comment: [...] 231 @catalogue: loc=[Library of Congress classification]; dewey=[Dewey classification]; isbn=[ISBN]; pg=[Project Gutenberg text number] 232 @classify_loc: [Library of Congress classification] 233 @classify_dewey: [Dewey classification] 234 @classify_isbn: [ISBN] 235 @classify_pg: [Project Gutenberg text number] 236 @prefix: [prefix is placed just after table of contents] 237 @prefix_a: [prefix is placed just before table of contents - not implemented] 238 @prefix_b: 239 @rcs: $Id: sisu_markup.sst,v 1.2 2007/09/08 17:12:47 ralph Exp $ [used by rcs or cvs to embed version (revision control) information into document, rcs or cvs can usefully provide a history of updates to a document ] 240 @structure: PART; CHAPTER; SECTION; ARTICLE; none; none;
optional, document structure can be defined by words to match or regular expression (the regular expression is assumed to start at the beginning of a line of text i.e. ^) default markers :A~ to :C~ and 1~ to 6~ can be used within text instead, without this header tag, and may be used to supplement the instructions provided in this header tag if provided (@structure: is a synonym for @toc:)
241 @level: newpage=3; breakpage=4
[paragraph level, used by latex to breakpages, the page is optional eg. in newpage]
242 @markup: information on the markup used, e.g. new=1,2,3; break=4; num_top=4 [or newpage=1,2,3; breakpage=4; num_top=4] newpage and breakpage, heading level, used by LaTeX to breakpages. breakpage: starts on a new page in single column text and on a new column in double column text; newpage: starts on a new page for both single and double column texts.
num_top=4 [auto-number document, starting at level 4. the default is to provide 3 levels, as in 1 level 4, 1.1 level 5, 1.1.1 level 6, markup to be merged within level]
num_extract [take numbering of headings provided (manually in marked up source document), and use for numbering of segments. Available where a clear numbering structure is provided within document, without the repetition of a number in a header.] [In 0.38 notation, you would map to the equivalent levels, the examples provided would map to the following new=A,B,C; break=1; num_top=1 [or newpage=A,B,C; breakpage=1; num_top=1] see headings]
243 @bold: [regular expression of words/phrases to be made bold] 244 @italics: [regular expression of words/phrases to italicise] 245 @vocabulary: name of taxonomy/vocabulary/wordlist to use against document 246 @skin: skin_doc_[name_of_desired_document_skin]
skins change default settings related to the appearance of documents generated, such as the urls of the home site, and the icon/logo for the document or site.
247 @links: { SiSU }http://www.jus.uio.no/sisu/;
{ FSF }http://www.fsf.org
248 @promo: sisu, ruby, search_libre_docs, open_society
[places content in right pane in html, makes use of list.yml and promo.yml, commented out sample in document sample: free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst]
249 11 11. Markup of Substantive Text 250 heading_levels 11.1 Heading Levels 251 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) 252 :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 253 :B~ [heading text] Second level heading [this is a heading level divider] 254 :C~ [heading text] Third level heading [this is a heading level divider] 255 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 256 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. 257 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 258      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)    
259 11.2 11.2 Font Attributes 260 markup example: 261      normal text !{emphasis}! *{bold text}* _{underscore}_ /{italics}/ "{citation}" ^{superscript}^ ,{subscript}, +{inserted text}+

     normal text

     !{emphasis}!

     *{bold text}*

     _{underscore}

     /{italics}/

     "{citation}"

     ^{superscript}^

     ,{subscript},

     +{inserted text}+

     -{strikethrough}-    
262 resulting output: 263 normal text emphasis bold text underscore italics citation superscript subscript inserted text strikethrough 264 normal text 265 emphasis 266 bold text 267 underscore 268 italics 269 citation 270 superscript 271 subscript 272 inserted text 273 strikethrough
274 11.3 11.3 Indentation and bullets 275 markup example: 276      ordinary paragraph

     _1 indent paragraph one step

     _2 indent paragraph two steps

     _9 indent paragraph nine steps    
277 resulting output: 278 ordinary paragraph 279 indent paragraph one step 280 indent paragraph two steps 281 indent paragraph nine steps 282 markup example: 283      _* bullet text

     _1* bullet text, first indent

     _2* bullet text, two step indent    
284 resulting output: 285 bullet text 286 bullet text, first indent 287 bullet text, two step indent 288 Numbered List (not to be confused with headings/titles, (document structure)) 289 markup example: 290      # numbered list                numbered list 1., 2., 3, etc.

     _# numbered list numbered list indented a., b., c., d., etc.    
291 11.4 11.4 Footnotes / Endnotes 292 Footnotes and endnotes not distinguished in markup. They are automatically numbered. Depending on the output file format (html, odf, pdf etc.), the document output selected will have either footnotes or endnotes. 293 markup example: 294      ~{ a footnote or endnote }~     295 resulting output: 296 17a footnote or endnote 297 markup example: 298      normal text~{ self contained endnote marker & endnote in one }~ continues     299 resulting output: 300 normal text18self contained endnote marker & endnote in one continues 301 markup example: 302      normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks if required }~ continues

     normal text ~{** another unnumbered asterisk footnote/endnote }~ continues    
303 resulting output: 304 normal text *unnumbered asterisk footnote/endnote, insert multiple asterisks if required continues 305 normal text **another unnumbered asterisk footnote/endnote continues 306 markup example: 307      normal text ~[* editors notes, numbered asterisk footnote/endnote series ]~ continues

     normal text ~[+ editors notes, numbered asterisk footnote/endnote series ]~ continues    
308 resulting output: 309 normal text *3editors notes, numbered asterisk footnote/endnote series continues 310 normal text +2editors notes, numbered asterisk footnote/endnote series continues 311 Alternative endnote pair notation for footnotes/endnotes: 312      % note the endnote marker "~^"

     normal text~^ continues

     ^~ endnote text following the paragraph in which the marker occurs    
313 the standard and pair notation cannot be mixed in the same document
314 11.5 11.5 Links 315 11.5.1 11.5.1 Naked URLs within text, dealing with urls 316 urls are found within text and 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). 317 markup example: 318      normal text http://www.jus.uio.no/sisu continues     319 resulting output: 320 normal text <http://www.jus.uio.no/sisu> continues 321 An escaped url without decoration 322 markup example: 323      normal text _http://www.jus.uio.no/sisu continues

     deb _http://www.jus.uio.no/sisu/archive unstable main non-free    
324 resulting output: 325 normal text http://www.jus.uio.no/sisu continues 326 deb http://www.jus.uio.no/sisu/archive unstable main non-free 327 where a code block is used there is neither decoration nor hyperlinking, code blocks are discussed later in this document 328 resulting output: 329      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    
330 To link text or an image to a url the markup is as follows 331 markup example: 332      about { SiSU }http://url.org markup    
333 11.5.2 11.5.2 Linking Text 334 resulting output: 335 about SiSU markup 336 A shortcut notation is available so the url link may also be provided automatically as a footnote 337 markup example: 338      about {~^ SiSU }http://url.org markup     339 resulting output: 340 about SiSU 19<http://www.jus.uio.no/sisu/> markup 341 11.5.3 11.5.3 Linking Images 342 markup example: 343      {tux.png 64x80 }image

     % various url linked images

     {tux.png 64x80 "a better way" }http://www.jus.uio.no/sisu/

     {GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian and Ruby" }http://www.jus.uio.no/sisu/

     {~^ ruby_logo.png "Ruby" }http://www.ruby-lang.org/en/

    
344 resulting output: 345 {tux.png 64x80 }image 346 [tux.png] "Gnu/Linux - a better way" 347 [ ruby_logo (png missing) ] 20<http://www.ruby-lang.org/en/> 348 [GnuDebianLinuxRubyBetterWay.png] "Way Better - with Gnu/Linux, Debian and Ruby" 349 linked url footnote shortcut 350      {~^ [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    
351      text marker *~name     352 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.
353 11.6 11.6 Grouped Text 354 11.6.1 11.6.1 Tables 355 Tables may be prepared in two either of two forms 356 markup example: 357      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    
358 resulting output:
This is a table this would become column two of row one column three of row one is here
And here begins another row column two of row two column three of row two, and so on
360 a second form may be easier to work with in cases where there is not much information in each column 361 markup example:21Table from the Wealth of Networks by Yochai Benkler
<http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler>
362      !_ 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.    
363 resulting output: 364 Table 3.1: Contributors to Wikipedia, January 2001 - June 2005
Jan. 2001 Jan. 2002 Jan. 2003 Jan. 2004 July 2004 June 2006
Contributors* 10 472 2,188 9,653 25,011 48,721
Active contributors** 9 212 846 3,228 8,442 16,945
Very active contributors*** 0 31 190 692 1,639 3,016
No. of English language articles 25 16,000 101,000 190,000 320,000 630,000
No. of articles, all languages 25 19,000 138,000 490,000 862,000 1,600,000
366 * Contributed at least ten times; ** at least 5 times in last month; *** more than 100 times in last month.
367 11.6.2 11.6.2 Poem 368 basic markup: 369      poem{

       Your poem here

     }poem

     Each verse in a poem is given a separate object number.    
370 markup example: 371      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    
372 resulting output: 373 '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."'
374 11.6.3 11.6.3 Group 375 basic markup: 376      group{

       Your grouped text here

     }group

     A group is treated as an object and given a single object number.    
377 markup example: 378      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    
379 resulting output: 380 '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."'
381 11.6.4 11.6.4 Code 382 Code tags 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. 383 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] 384 use of code tags instead of poem compared, resulting output: 385                          '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."'    
386 12 12. Composite documents markup 387 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 388 basic markup for importing a document into a master document 389      << |filename1.sst|@|^|

     << |filename2.ssi|@|^|    
390 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. 391      r{filename}

     {filename.ssi}require

     << {filename.ssi}

     % using textlink alternatives

     |filename.ssi|@|^|require

     << |filename.ssi|@|^|

     % using thlnk alternatives

     <url:filename.ssi>require

     << <url:filename.ssi>    
392 Markup Syntax History 393 13 13. Notes related to Files-types and Markup Syntax 394 0.38 is substantially current, depreciated 0.16 supported, though file names were changed at 0.37 395 0.52 (2007w14/6) declared document type identifier at start of text/document: 396 SiSU 0.52 397 or, backward compatible using the comment marker: 398 % SiSU 0.38 399 variations include 'SiSU (text|master|insert) [version]' and 'sisu-[version]' 400 0.51 (2007w13/6) skins changed (simplified), markup unchanged 401 0.42 (2006w27/4) * (asterisk) type endnotes, used e.g. in relation to author 402 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) 403 0.37 (2006w09/7) introduced new file naming convention, .sst (text), .ssm (master), .ssi (insert), markup syntax unchanged 404 0.35 (2005w52/3) sisupod, zipped content file introduced 405 0.23 (2005w36/2) utf-8 for markup file 406 0.22 (2005w35/3) image dimensions may be omitted if rmagick is available to be relied upon 407 0.20.4 (2005w33/4) header 0~links 408 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 409 filetypes 14. SiSU filetypes 410 SiSU has plaintext and binary filetypes, and can process either type of document. 411 14.1 14.1 .sst .ssm .ssi marked up plain text 412 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. 413 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. 414 SiSU source markup can be shared with the command: 415 sisu -s [filename] 416 14.1.1 14.1.1 sisu text - regular files (.sst) 417 The most common form of document in SiSU, see the section on SiSU markup. 418 <http://www.jus.uio.no/sisu/sisu_markup> 419 <http://www.jus.uio.no/sisu/sisu_manual> 420 14.1.2 14.1.2 sisu master files (.ssm) 421 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. 422 The mechanism by which master files incorporate other documents is described as one of the headings under under SiSU markup in the SiSU manual. 423 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. 424 Note: a secondary file of the composite document is built prior to processing with the same prefix and the suffix ._sst 22.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. 425 <http://www.jus.uio.no/sisu/sisu_markup> 426 <http://www.jus.uio.no/sisu/sisu_manual> 427 14.1.3 14.1.3 sisu insert files (.ssi) 428 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. 429 14.2 14.2 sisupod, zipped binary container (sisupod.zip, .ssp) 430 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) 431 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. 432 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. 433 The command to create a sisupod is: 434 sisu -S [filename] 435 Alternatively, make a pod of the contents of a whole directory: 436 sisu -S 437 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. 438 <http://www.jus.uio.no/sisu/sisu_commands> 439 <http://www.jus.uio.no/sisu/sisu_manual> 440 alt 15. Experimental Alternative Input Representations 441 15.1 15.1 Alternative XML 442 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. 443 convert from sst to simple xml representations (sax, dom and node): 444 sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard] 445 sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard] 446 sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard] 447 convert to sst from any sisu xml representation (sax, dom and node): 448 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 449 or the same: 450 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 451 15.1.1 15.1.1 XML SAX representation 452 To convert from sst to simple xml (sax) representation: 453 sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard] 454 To convert from any sisu xml representation back to sst 455 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 456 or the same: 457 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 458 15.1.2 15.1.2 XML DOM representation 459 To convert from sst to simple xml (dom) representation: 460 sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard] 461 To convert from any sisu xml representation back to sst 462 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 463 or the same: 464 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 465 15.1.3 15.1.3 XML Node representation 466 To convert from sst to simple xml (node) representation: 467 sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard] 468 To convert from any sisu xml representation back to sst 469 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 470 or the same: 471 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] 472 config 16. Configuration 473 16.1 16.1 Determining the Current Configuration 474 Information on the current configuration of SiSU should be available with the help command: 475 sisu -v 476 which is an alias for: 477 sisu --help env 478 Either of these should be executed from within a directory that contains sisu markup source documents. 479 16.2 16.2 Configuration files (config.yml) 480 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. 481 The SiSU configuration file is a yaml file, which means indentation is significant. 482 SiSU resource configuration is determined by looking at the following files if they exist: 483 ./_sisu/sisurc.yml 484 ~/.sisu/sisurc.yml 485 /etc/sisu/sisurc.yml 486 The search is in the order listed, and the first one found is used. 487 In the absence of instructions in any of these it falls back to the internal program defaults. 488 Configuration determines the output and processing directories and the database access details. 489 If SiSU is installed a sample sisurc.yml may be found in /etc/sisu/sisurc.yml 490 skins 17. Skins 491 Skins modify the default appearance of document output on a document, directory, or site wide basis. Skins are looked for in the following locations: 492 ./_sisu/skin 493 ~/.sisu/skin 494 /etc/sisu/skin 495 Within the skin directory are the following the default sub-directories for document skins: 496 ./skin/doc 497 ./skin/dir 498 ./skin/site 499 A skin is placed in the appropriate directory and the file named skin_[name].rb 500 The skin itself is a ruby file which modifies the default appearances set in the program. 501 17.1 17.1 Document Skin 502 Documents take on a document skin, if the header of the document specifies a skin to be used. 503      @skin: skin_united_nations     504 17.2 17.2 Directory Skin 505 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). 506 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. 507 17.3 17.3 Site Skin 508 A site skin, modifies the program default skin. 509 17.4 17.4 Sample Skins 510 With SiSU installed sample skins may be found in: 511 /etc/sisu/skin/doc and /usr/share/doc/sisu/sisu_markup_samples/dfsg/_sisu/skin/doc 512 (or equivalent directory) and if sisu-markup-samples is installed also under: 513 /usr/share/doc/sisu/sisu_markup_samples/non-free/_sisu/skin/doc 514 Samples of list.yml and promo.yml (which are used to create the right column list) may be found in: 515 /usr/share/doc/sisu/sisu_markup_samples/dfsg/_sisu/skin/yml (or equivalent directory) 516 css 18. CSS - Cascading Style Sheets (for html, XHTML and XML) 517 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. 518 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. 519 HTML: html.css 520 XML DOM: dom.css 521 XML SAX: sax.css 522 XHTML: xhtml.css 523 The default homepage may use homepage.css or html.css 524 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.23SiSU 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. 525 organising_content 19. Organising Content 526 19.1 19.1 Directory Structure and Mapping 527 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) 528 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. 529 19.2 19.2 Organising Content 530 home 20. Homepages 531 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: 532 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) 533 2. through providing what you want as the home page in a skin, 534 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. 535 20.1 20.1 Home page and other custom built pages in a sub-directory 536 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: 537 sisu -CC 538 20.2 20.2 Home page within a skin 539 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. 540 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 541        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    
542 examples 21. Markup and Output Examples 543 21.1 21.1 Markup examples 544 Current markup examples and document output samples are provided at <http://www.jus.uio.no/sisu/SiSU/2.html> 545 Some markup with syntax highlighting may be found under <http://www.jus.uio.no/sisu/sample/syntax> but is not as up to date. 546 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. 547 21.2 21.2 A few book (and other) examples 548 [aukio.png] "Aukio, by Leena Krohn" 24Reproduced 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> 549 wealth_of_networks "The Wealth of Networks", Yochai Benkler 550 "The Wealth of Networks", Yochai Benkler 551 document manifest 25<http://www.jus.uio.no/sisu/sisu_manual/the_wealth_of_networks.yochai_benkler/sisu_manifest.html> 552 html, segmented text 553 html, scroll, document in one 554 pdf, landscape 555 pdf, portrait 556 open document 557 xhtml scroll 558 xml, sax 559 xml, dom 560 plain text utf-8 561 concordance 562 dcc, document content certificate (digests) 563 markup source text 564 zipped markup source pod 565 freeculture "Free Culture", Lawrence Lessig 566 "Free Culture", Lawrence Lessig 567 document manifest 26<http://www.jus.uio.no/sisu/sisu_manual/free_culture.lawrence_lessig/sisu_manifest.html> 568 html, segmented text 569 html, scroll, document in one 570 pdf, landscape 571 pdf, portrait 572 open document 573 xhtml scroll 574 xml, sax 575 xml, dom 576 plain text utf-8 577 concordance 578 dcc, document content certificate (digests) 579 markup source text 580 zipped markup source pod 581 free_as_in_freedom "Free as in Freedom: Richard Stallman's Crusade for Free Software", by Sam Williams 582 "Free as in Freedom: Richard Stallman's Crusade for Free Software", by Sam Williams 583 document manifest 27<http://www.jus.uio.no/sisu/sisu_manual/free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams/sisu_manifest.html> 584 html, segmented text 585 html, scroll, document in one 586 pdf, landscape 587 pdf, portrait 588 open document 589 xhtml scroll 590 xml, sax 591 xml, dom 592 plain text utf-8 593 concordance 594 dcc, document content certificate (digests) 595 markup source text 596 zipped markup source pod 597 free_for_all "Free For All: How Linux and the Free Software Movement Undercut the High Tech Titans", by Peter Wayner 598 "Free For All: How Linux and the Free Software Movement Undercut the High Tech Titans", by Peter Wayner 599 document manifest 28<http://www.jus.uio.no/sisu/sisu_manual/free_for_all.peter_wayner/sisu_manifest.html> 600 html, segmented text 601 html, scroll, document in one 602 pdf, landscape 603 pdf, portrait 604 open document 605 xhtml scroll 606 xml, sax 607 xml, dom 608 plain text utf-8 609 concordance 610 dcc, document content certificate (digests) 611 markup source text 612 zipped markup source pod 613 catb "The Cathedral and the Bazaar", by Eric S. Raymond 614 "The Cathedral and the Bazaar", by Eric S. Raymond 615 document manifest 29<http://www.jus.uio.no/sisu/sisu_manual/the_cathedral_and_the_bazaar.eric_s_raymond/sisu_manifest.html> 616 html, segmented text 617 html, scroll, document in one 618 pdf, landscape 619 pdf, portrait 620 open document 621 xhtml scroll 622 xml, sax 623 xml, dom 624 plain text utf-8 625 concordance 626 dcc, document content certificate (digests) 627 markup source text 628 zipped markup source pod 629 accelerando "Accelerando", Charles Stross 630 "Accelerando", Charles Stross 631 document manifest 30<http://www.jus.uio.no/sisu/sisu_manual/accelerando.charles_stross/sisu_manifest.html> 632 html, segmented text 633 html, scroll, document in one 634 pdf, landscape 635 pdf, portrait 636 open document 637 xhtml scroll 638 xml, sax 639 xml, dom 640 plain text utf-8 641 concordance 642 dcc, document content certificate (digests) 643 markup source text 644 zipped markup source pod 645 tainaron "Tainaron", Leena Krohn 646 "Tainaron", Leena Krohn 647 document manifest 31<http://www.jus.uio.no/sisu/sisu_manual/tainaron.leena_krohn.1998/sisu_manifest.html> 648 html, segmented text 649 html, scroll, document in one 650 pdf, landscape 651 pdf, portrait 652 open document 653 xhtml scroll 654 xml, sax 655 xml, dom 656 plain text utf-8 657 concordance 658 dcc, document content certificate (digests) 659 markup source text 660 zipped markup source pod 661 sphinx "Sphinx or Robot", Leena Krohn 662 [i_sor.png] "Sphinx or Robot by Leena Krohn" 663 "Sphinx or Robot", Leena Krohn 664 document manifest 32<http://www.jus.uio.no/sisu/sisu_manual/sphinx_or_robot.leena_krohn.1996/sisu_manifest.html> 665 html, segmented text 666 html, scroll, document in one 667 pdf, landscape 668 pdf, portrait 669 open document 670 xhtml scroll 671 xml, sax 672 xml, dom 673 plain text utf-8 674 concordance 675 dcc, document content certificate (digests) 676 markup source text 677 zipped markup source pod 678 war_and_peace "War and Peace", Leo Tolstoy, PG Etext 2600 679 "War and Peace", Leo Tolstoy 33<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. 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 is possible to do a simple search and replace to make Project Gutenberg ascii presentations suitable for SiSU using the older endnote markup style. There is 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 the <:insert1> and <:insert2> markers and the legal notices are available for similar insertion into the next Project Gutenberg text prepared for SiSU, should there be one.
680 document manifest 34<http://www.jus.uio.no/sisu/sisu_manual/war_and_peace.leo_tolstoy/sisu_manifest.html> 681 html, segmented text 682 html, scroll, document in one 683 pdf, landscape 684 pdf, portrait 685 open document 686 xhtml scroll 687 xml, sax 688 xml, dom 689 plain text utf-8 690 concordance 691 dcc, document content certificate (digests) 692 markup source text 693 zipped markup source pod
694 quixote "Don Quixote", Miguel de Cervantes [Saavedra], translated by John Ormsby, PG Etext 996 695 "Don Quixote", Miguel de Cervantes [Saavedra] 696 document manifest 35<http://www.jus.uio.no/sisu/sisu_manual/don_quixote.miguel_de_cervantes/sisu_manifest.html> 697 html, segmented text 698 html, scroll, document in one 699 pdf, landscape 700 pdf, portrait 701 open document 702 xhtml scroll 703 xml, sax 704 xml, dom 705 plain text utf-8 706 concordance 707 dcc, document content certificate (digests) 708 markup source text 709 zipped markup source pod 710 gulliver "Gulliver's Travels", Jonathan Swift, transcribed from the 1892 George Bell and Sons edition by David Price, PG Etext 829 711 "Gulliver's Travels", Jonathan Swift 712 document manifest 36<http://www.jus.uio.no/sisu/sisu_manual/gullivers_travels.jonathan_swift/sisu_manifest.html> 713 html, segmented text 714 html, scroll, document in one 715 pdf, landscape 716 pdf, portrait 717 open document 718 xhtml scroll 719 xml, sax 720 xml, dom 721 plain text utf-8 722 concordance 723 dcc, document content certificate (digests) 724 markup source text 725 zipped markup source pod 726 alice "Alice's Adventures in Wonderland", Lewis Carroll, PG Etext 11 727 "Alice's Adventures in Wonderland", Lewis Carroll 728 document manifest 37<http://www.jus.uio.no/sisu/sisu_manual/alices_adventures_in_wonderland.lewis_carroll/sisu_manifest.html> 729 html, segmented text 730 html, scroll, document in one 731 pdf, landscape 732 pdf, portrait 733 open document 734 xhtml scroll 735 xml, sax 736 xml, dom 737 plain text utf-8 738 concordance 739 dcc, document content certificate (digests) 740 markup source text 741 zipped markup source pod 742 glass "Through The Looking-Glass", Lewis Carroll, PG Etext 12 743 "Through The Looking-Glass", Lewis Carroll 744 document manifest 38<http://www.jus.uio.no/sisu/sisu_manual/through_the_looking_glass.lewis_carroll/sisu_manifest.html> 745 html, segmented text 746 html, scroll, document in one 747 pdf, landscape 748 pdf, portrait 749 open document 750 xhtml scroll 751 xml, sax 752 xml, dom 753 plain text utf-8 754 concordance 755 dcc, document content certificate (digests) 756 markup source text 757 zipped markup source pod 758 alice "Alice's Adventures in Wonderland" and "Through The Looking-Glass", Lewis Carroll, PG Etexts 11 and 12 759 "Alice's Adventures in Wonderland" and "Through The Looking-Glass", Lewis Carroll 760 document manifest 39<http://www.jus.uio.no/sisu/sisu_manual/alices_adventures_in_wonderland_and_through_the_looking_glass.lewis_carroll/sisu_manifest.html> 761 html, segmented text 762 html, scroll, document in one 763 pdf, landscape 764 pdf, portrait 765 open document 766 xhtml scroll 767 xml, sax 768 xml, dom 769 plain text utf-8 770 concordance 771 dcc, document content certificate (digests) 772 markup source text 773 zipped markup source pod 774 gpl "Gnu Public License 2", (GPL 2) Free Software Foundation 775 "Gnu Public License 2", (GPL 2) Free Software Foundation 776 document manifest 40<http://www.jus.uio.no/sisu/sisu_manual/gpl2.fsf/sisu_manifest.html> 777 html, segmented text 778 html, scroll, document in one 779 pdf, landscape 780 pdf, portrait 781 open document 782 xhtml scroll 783 xml, sax 784 xml, dom 785 plain text utf-8 786 concordance 787 dcc, document content certificate (digests) 788 markup source text 789 zipped markup source pod 790 gpl "Gnu Public License v3 - Third discussion draft", (GPLv3) Free Software Foundation 791 "Gnu Public License 3 - Third discussion draft", (GPL v3 draft3) Free Software Foundation 792 document manifest 41<http://www.jus.uio.no/sisu/sisu_manual/gpl3_draft3.fsf/sisu_manifest.html> 793 html, segmented text 794 html, scroll, document in one 795 pdf, landscape 796 pdf, portrait 797 open document 798 xhtml scroll 799 xml, sax 800 xml, dom 801 plain text utf-8 802 concordance 803 dcc, document content certificate (digests) 804 markup source text 805 zipped markup source pod 806 dsc "Debian Social Contract" 807 "Debian Social Contract" 808 document manifest 42<http://www.jus.uio.no/sisu/sisu_manual/debian_social_contract_v1.1/sisu_manifest.html> 809 html, segmented text 810 html, scroll, document in one 811 pdf, landscape 812 pdf, portrait 813 open document 814 xhtml scroll 815 xml, sax 816 xml, dom 817 plain text utf-8 818 concordance 819 dcc, document content certificate (digests) 820 markup source text 821 zipped markup source pod 822 dc "Debian Constitution v1.3", (simple/default markup) 823 "Debian Constitution v1.3" 824 document manifest 43<http://www.jus.uio.no/sisu/sisu_manual/debian_constitution_v1.3/sisu_manifest.html> 825 html, segmented text 826 html, scroll, document in one 827 pdf, landscape 828 pdf, portrait 829 open document 830 xhtml scroll 831 xml, sax 832 xml, dom 833 plain text utf-8 834 concordance 835 dcc, document content certificate (digests) 836 markup source text 837 zipped markup source pod 838 dc "Debian Constitution v1.3", (markup adjusted for output to more closely match the original) 839 "Debian Constitution v1.3", (markup adjusted for output to more closely match the original) 840 document manifest 44<http://www.jus.uio.no/sisu/sisu_manual/debian_constitution_v1.3.adjusted/sisu_manifest.html> 841 html, segmented text 842 html, scroll, document in one 843 pdf, landscape 844 pdf, portrait 845 open document 846 xhtml scroll 847 xml, sax 848 xml, dom 849 plain text utf-8 850 concordance 851 dcc, document content certificate (digests) 852 markup source text 853 zipped markup source pod 854 dc "Debian Constitution v1.2", (simple/default markup) 855 "Debian Constitution v1.2 (more translations)" 856 document manifest 45<http://www.jus.uio.no/sisu/sisu_manual/debian_constitution_v1.2/sisu_manifest.html> 857 html, segmented text 858 html, scroll, document in one 859 pdf, landscape 860 pdf, portrait 861 open document 862 xhtml scroll 863 xml, sax 864 xml, dom 865 plain text utf-8 866 concordance 867 dcc, document content certificate (digests) 868 markup source text 869 zipped markup source pod 870 dc "Debian Constitution v1.2", (markup adjusted for output to more closely match the original) 871 "Debian Constitution (more translations)", (markup adjusted for output to more closely match the original) 872 document manifest 46<http://www.jus.uio.no/sisu/sisu_manual/debian_constitution_v1.2.adjusted/sisu_manifest.html> 873 html, segmented text 874 html, scroll, document in one 875 pdf, landscape 876 pdf, portrait 877 open document 878 xhtml scroll 879 xml, sax 880 xml, dom 881 plain text utf-8 882 concordance 883 dcc, document content certificate (digests) 884 markup source text 885 zipped markup source pod 886 terminology "A Uniform Sales Terminology", Vikki Rogers and Albert Kritzer 887 "A Uniform Sales Terminology", Vikki Rogers and Albert Kritzer 888 document manifest 47<http://www.jus.uio.no/sisu/sisu_manual/a_uniform_international_sales_terminology.vikki_rogers.and.albert_kritzer/sisu_manifest.html> 889 html, segmented text 890 html, scroll, document in one 891 pdf, landscape 892 pdf, portrait 893 open document 894 xhtml scroll 895 xml, sax 896 xml, dom 897 plain text utf-8 898 concordance 899 dcc, document content certificate (digests) 900 markup source text 901 zipped markup source pod 902 autonomous "The Autonomous Contract" 1997 - markup sample 903 "The Autonomous Contract" 1997 - markup sample 904 document manifest 48<http://www.jus.uio.no/sisu/sisu_manual/the_autonomous_contract.amissah.19970710/sisu_manifest.html> 905 html, segmented text 906 html, scroll, document in one 907 pdf, landscape 908 pdf, portrait 909 open document 910 xhtml scroll 911 xml, sax 912 xml, dom 913 plain text utf-8 914 concordance 915 dcc, document content certificate (digests) 916 markup source text 917 zipped markup source pod 918 autonomous "The Autonomous Contract Revisited" - markup sample 919 "The Autonomous Contract Revisited" - markup sample 49<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.
920 document manifest 50<http://www.jus.uio.no/sisu/sisu_manual/autonomy_markup0/sisu_manifest.html> 921 html, segmented text 922 html, scroll, document in one 923 pdf, landscape 924 pdf, portrait 925 open document 926 xhtml scroll 927 xml, sax 928 xml, dom 929 plain text utf-8 930 concordance 931 dcc, document content certificate (digests) 932 markup source text 933 zipped markup source pod
934 cisg "United Nations Convention on Contracts for the International Sale of Goods" 935 "United Nations Convention on Contracts for the International Sale of Goods" 51<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).
936 document manifest 52<http://www.jus.uio.no/sisu/sisu_manual/un_contracts_international_sale_of_goods_convention_1980/sisu_manifest.html> 937 html, segmented text 938 html, scroll, document in one 939 pdf, landscape 940 pdf, portrait 941 open document 942 xhtml scroll 943 xml, sax 944 xml, dom 945 plain text utf-8 946 concordance 947 dcc, document content certificate (digests) 948 markup source text 949 zipped markup source pod
950 pecl PECL the "Principles of European Contract Law" 951 "Principles of European Contract Law" 952 document manifest 53<http://www.jus.uio.no/sisu/sisu_manual/eu_contract_principles_parts_1_to_3_2002/sisu_manifest.html> 953 html, segmented text 954 html, scroll, document in one 955 pdf, landscape 956 pdf, portrait 957 open document 958 xhtml scroll 959 xml, sax 960 xml, dom 961 plain text utf-8 962 concordance 963 dcc, document content certificate (digests) 964 markup source text 965 zipped markup source pod
966 sql 21.3 SQL - PostgreSQL, SQLite 967 A Sample search form is available at <http://search.sisudoc.org> 968 A few canned searches, showing object numbers. Search for: 969 English documents matching Linux OR Debian 970 GPL OR Richard Stallman 971 invention OR innovation in English language 972 copyright in English language documents 973 Note that the searches done in this form are case sensitive. 974 Expand those same searches, showing the matching text in each document: 975 English documents matching Linux OR Debian 976 GPL OR Richard Stallman 977 invention OR innovation in English language 978 copyright in English language documents 979 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.54of 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. 980 21.4 21.4 Lex Mercatoria as an example 981 There is quite a bit to peruse if you explore the site Lex Mercatoria: 982 <http://www.lexmercatoria.org/> 55<http://www.jus.uio.no/lm/index> 983 or perhaps: 984 <http://lexmercatoria.org/treaties.and.organisations/lm.chronological> 56<http://www.jus.uio.no/lm/treaties.and.organisations/lm.chronological> 985 21.5 21.5 For good measure the markup for a document with lots of (simple) tables 986 SiSU is not optimised for table making, but does handle simple tables. 987 SiSU marked up file with tables 57<http://www.jus.uio.no/sisu/sample/syntax/un_conventions_membership_status.sst.html>
<http://www.jus.uio.no/sisu/sample/markup/un_conventions_membership_status.sst>
988 Output of table file example 58<http://www.jus.uio.no/lm/un_conventions_membership_status/toc.html>
989 21.6 21.6 And a link to the output of a reported case 990 <http://www.jus.uio.no/lm/england.fothergill.v.monarch.airlines.hl.1980/toc.html>
991 22 22. A Checklist of Output Features 992 This table gives an indication of the features that are available for various forms of output of SiSU. 59updated for sisu-0.36.6 on 2006-01-23
feature txt ltx/pdf HTML XHTML XML/s XML/d ODF SQLite pgSQL
headings * * * * * * * * *
footnotes * * * * * * * * *
bold, underscore, italics . * * * * * * * *
strikethrough . * * * * * *
superscript, subscript . * * * * * *
extended ascii set (utf-8) * * * * * * * *
indents * * * * * * *
bullets . * * * * * .
groups
* tables * * . . . . . .
* poem * * * . . . * . .
* code * * * . . . * . .
url * * * * * * * . .
links * * * * * * * . .
images - * * T T T * T T
image caption - * *
table of contents * * * * * .
page header/footer? - * * * * * t
line break * * * * * * *
page break * *
segments *
skins * * * * * *
ocn . * * * * * -? * *
auto-heading numbers * * * * * * * * *
minor list numbering * * * * * * * * *
special characters . . .
994 Done
* yes/done
. partial
- not available/appropriate
Not Done
T task todo
t lesser task/todo
not done
995 search_intro 23. SiSU Search - Introduction 996 SiSU output can easily and conveniently be indexed by a number of standalone indexing tools, such as Lucene, Hyperestraier. 997 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. 998 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. 999 search_sql 24. SQL 1000 24.1 24.1 populating SQL type databases 1001 SiSU feeds sisu markupd documents into sql type databases PostgreSQL60<http://www.postgresql.org/>
<http://advocacy.postgresql.org/>
<http://en.wikipedia.org/wiki/Postgresql>
and/or SQLite61<http://www.hwaci.com/sw/sqlite/>
<http://en.wikipedia.org/wiki/Sqlite>
database together with information related to document structure.
1002 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: 1003 one containing semantic (and other) headers, including, title, author, subject, (the Dublin Core...); 1004 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 1005 a third containing endnotes cross-referenced back to the paragraph from which they are referenced (both in formatted and clean text versions for searching). 1006 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. 1007 There is of course the possibility to add further structures. 1008 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. 1009 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).
1010 postgresql 25. Postgresql 1011 25.1 25.1 Name 1012 SiSU - Structured information, Serialized Units - a document publishing system, postgresql dependency package 1013 25.2 25.2 Description 1014 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). 1015 25.3 25.3 Synopsis 1016 sisu -D [instruction] [filename/wildcard if required] 1017 sisu -D --pg --[instruction] [filename/wildcard if required] 1018 25.4 25.4 Commands 1019 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 1020 -D or --pgsql may be used interchangeably. 1021 25.4.1 25.4.1 create and destroy database 1022 --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)
1023 sisu -D --createdb
creates database where no database existed before
1024 sisu -D --create
creates database tables where no database tables existed before
1025 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).
1026 sisu -D --recreate
destroys existing database and builds a new empty database structure
1027 25.4.2 25.4.2 import and remove documents 1028 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).
1029 sisu -D --update -v [filename/wildcard]
updates file contents in database
1030 sisu -D --remove -v [filename/wildcard]
removes specified document from postgresql database.
1031 sqlite 26. Sqlite 1032 26.1 26.1 Name 1033 SiSU - Structured information, Serialized Units - a document publishing system. 1034 26.2 26.2 Description 1035 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). 1036 26.3 26.3 Synopsis 1037 sisu -d [instruction] [filename/wildcard if required] 1038 sisu -d --(sqlite|pg) --[instruction] [filename/wildcard if required] 1039 26.4 26.4 Commands 1040 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 1041 -d or --sqlite may be used interchangeably. 1042 26.4.1 26.4.1 create and destroy database 1043 --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)
1044 sisu -d --createdb
creates database where no database existed before
1045 sisu -d --create
creates database tables where no database tables existed before
1046 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).
1047 sisu -d --recreate
destroys existing database and builds a new empty database structure
1048 26.4.2 26.4.2 import and remove documents 1049 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).
1050 sisu -d --update -v [filename/wildcard]
updates file contents in database
1051 sisu -d --remove -v [filename/wildcard]
removes specified document from sqlite database.
1052 search_cgi 27. Introduction 1053 27.1 27.1 Search - database frontend sample, utilising database and SiSU features, including object citation numbering (backend currently PostgreSQL) 1054 Sample search frontend 62<http://search.sisudoc.org> A small database and sample query front-end (search from) that makes use of the citation system, object citation numbering to demonstrates functionality.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. 1055 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, 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. 1056 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.64of 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. 1057 sisu -F --webserv-webrick
builds a cgi web search frontend for the database created
1058 The following is feedback on the setup on a machine provided by the help command: 1059 sisu --help sql 1060      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    
1061 Note on databases built 1062 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]
1063 27.2 27.2 Search Form 1064 sisu -F
generates a sample search form, which must be copied to the web-server cgi directory
1065 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
1066 sisu -Fv
as above, and provides some information on setting up hyperestraier
1067 sisu -W
starts the webrick server which should be available wherever sisu is properly installed
1068 The generated search form must be copied manually to the webserver directory as instructed
1069 search_hyperestraier 28. Hyperestraier 1070 See the documentation for hyperestraier: 1071 <http://hyperestraier.sourceforge.net/> 1072 /usr/share/doc/hyperestraier/index.html 1073 man estcmd 1074 on sisu_hyperestraier: 1075 man sisu_hyperestraier 1076 /usr/share/doc/sisu/sisu_markup/sisu_hyperestraier/index.html 1077 NOTE: the examples that follow assume that sisu output is placed in the directory /home/ralph/sisu_www 1078 (A) to generate the index within the webserver directory to be indexed: 1079 estcmd gather -sd [index name] [directory path to index] 1080 the following are examples that will need to be tailored according to your needs: 1081 cd /home/ralph/sisu_www 1082 estcmd gather -sd casket /home/ralph/sisu_www 1083 you may use the 'find' command together with 'egrep' to limit indexing to particular document collection directories within the web server directory: 1084 find /home/ralph/sisu_www -type f | egrep '/home/ralph/sisu_www/sisu/.+?.html$' |estcmd gather -sd casket - 1085 Check which directories in the webserver/output directory (~/sisu_www or elsewhere depending on configuration) you wish to include in the search index. 1086 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. 1087 find /home/ralph/sisu_www -type f | egrep '/sisu_www/(sisu|bookmarks)/.+?.html$' | egrep -v '(doc|concordance).html$' |estcmd gather -sd casket - 1088 from your current document preparation/markup directory, you would construct a rune along the following lines: 1089 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 - 1090 (B) to set up the search form 1091 (i) copy estseek.cgi to your cgi directory and set file permissions to 755: 1092 sudo cp -vi /usr/lib/estraier/estseek.cgi /usr/lib/cgi-bin 1093 sudo chmod -v 755 /usr/lib/cgi-bin/estseek.cgi 1094 sudo cp -v /usr/share/hyperestraier/estseek.* /usr/lib/cgi-bin 1095 [see estraier documentation for paths] 1096 (ii) edit estseek.conf, with attention to the lines starting 'indexname:' and 'replace:': 1097 indexname: /home/ralph/sisu_www/casket 1098 replace: ^file:///home/ralph/sisu_www{{!}}http://localhost 1099 replace: /index.html?${{!}}/ 1100 (C) to test using webrick, start webrick: 1101 sisu -W 1102 and try open the url: <http://localhost:8081/cgi-bin/estseek.cgi> 1103 webrick 29. sisu_webrick 1104 29.1 29.1 Name 1105 SiSU - Structured information, Serialized Units - a document publishing system 1106 29.2 29.2 Synopsis 1107 sisu_webrick [port] 1108 or 1109 sisu -W [port] 1110 29.3 29.3 Description 1111 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). 1112 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). 1113 29.4 29.4 Summary of man page 1114 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] 1115 where no port is given and settings are unchanged the default port is 8081 1116 29.5 29.5 Document processing command flags 1117 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 1118 29.6 29.6 Further information 1119 For more information on SiSU see: <http://www.jus.uio.no/sisu> 1120 or man sisu 1121 29.7 29.7 Author 1122 Ralph Amissah or 1123 29.8 29.8 SEE ALSO 1124 sisu(1) 1125 sisu_vim(7) 1126 sisu(8) 1127 remote_source 30. Remote Source Documents 1128 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 1129 .sst / .ssm - sisu text files 1130 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. 1131      sisu -3 http://[provide url to valid .sst or .ssm file]     1132 Any of the source documents in the sisu examples page can be used in this way, see <http://www.jus.uio.no/sisu/SiSU/2.html> and use the url for the desired document. 1133 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 1134 sisupod - zipped sisu files 1135 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. 1136 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. 1137      sisu -3 http://[provide url to valid sisupod.zip or .ssp file]     1138 Any of the source documents in the sisu examples page can be used in this way, see <http://www.jus.uio.no/sisu/SiSU/2.html> and use the url for the desired document.
1139 Remote Document Output 1140 remote_output 31. Remote Output 1141 Once properly configured SiSU output can be automatically posted once generated to a designated remote machine using either rsync, or scp. 1142 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. 1143      sisu -3R sisu_remote.sst     1144 31.1 31.1 commands 1145 -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
1146 -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
1147 31.2 31.2 configuration 1148 [expand on the setting up of an ssh-agent / keychain]
1149 remote_servers 32. Remote Servers 1150 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. 1151 download 33. Download SiSU - Linux/Unix 1152 current SiSU Current Version - Linux/Unix 1153 source Source (tarball tar.gz) 1154 Download the latest version of SiSU (and SiSU markup samples):65Breakage and Fixes Report
<http://www.jus.uio.no/sisu/SiSU/breakage_and_fixes.html>
1155 sisu_0.58.3.orig.tar.gz (of 2007-09-05:36/3) 66<http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu_0.58.3.orig.tar.gz>
e9a20a06ffee8d633b8ce525017d89ba 1278987
1156 cgi generated sample search form 1157 order results on files of the same title, in multiple files (with different filenames) 1158 postgresql, character case sensitivity, control, on/off 1159 tail decoration, gplv3 & sisu info 1160 texinfo/info (pinfo) module starts to do something vaguely useful again [not a much used module, testing required] 1161 print XML rendition of document structure to screen -T 1162 help on environment visited, sisu -V 1163 sisurc.yml default, color set to true [apologies if this causes anyone any inconvenience, it is configurable in sisurc.yml] 1164 help and man pages, some work man(8) related 1165 sisu-install (install ruby rant script renamed) and permissions set to executable 1166 sisu-markup-samples_1.0.8.orig.tar.gz (of 2007-08-19:33/7 ) 67<http://www.jus.uio.no/sisu/archive/pool/non-free/s/sisu-markup-samples/sisu-markup-samples_1.0.7.orig.tar.gz>
04ae2812617a4689666600a0fb32301f 3438571
1167 For installation notes see <http://www.jus.uio.no/sisu/SiSU/download.html> 1168 For changelogs see <http://www.jus.uio.no/sisu/SiSU/changelog.html> 1169 [tulva.png] "Tulva, by Leena Krohn" 68Reproduced 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/2.html#sample>
1170 git Git (source control management) 1171 Git repository currently at: 1172 git clone git://sisudoc.org/git/sisu/ 1173 <http://search.sisudoc.org/cgi-bin/gitweb.cgi?p=sisu;a=summary> 1174 debian Debian 1175 This section contains information on the latest SiSU release. For installation notes see <http://www.jus.uio.no/sisu/sisu_download/installation.html> 1176 SiSU is updated fairly regularly in Debian testing and unstable, and should be available therefrom. 1177 To add this archive, should you still choose to do so, add the following lines to your /etc/apt/sources.list 1178      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    
1179 Source 1180 sisu_0.58.3.orig.tar.gz 69<http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu_0.58.3.orig.tar.gz> 1181 sisu_0.58.3-1.diff.gz 70<http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu_0.58.3-1.diff.gz> 1182 sisu_0.58.3-1.dsc 71<http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu_0.58.3-1.dsc>
b8330f8b97a15e6eaecba8f2616acb10 606 sisu_0.58.3-1.dsc
1183 Debs 1184 sisu_0.58.3-1_all.deb 72<http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu_0.58.3-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
1185 sisu-complete_0.58.3-1_all.deb 73<http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu-complete_0.58.3-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
1186 sisu-pdf_0.58.3-1_all.deb 74<http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu-pdf_0.58.3-1_all.deb>
dependencies used by sisu to produce pdf from LaTeX generated
Depends: sisu, tetex-bin, tetex-extra, latex-ucs
Suggests: evince, xpdf
1187 sisu-postgresql_0.58.3-1_all.deb 75<http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu-postgresql_0.58.3-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
1188 sisu-sqlite_0.58.3-1_all.deb 76<http://www.jus.uio.no/sisu/archive/pool/main/s/sisu/sisu-sqlite_0.58.3-1_all.deb>
dependencies used by sisu to populate sqlite database
Depends: sisu, sqlite, libdbi-ruby, libdbm-ruby, libdbd-sqlite-ruby
Suggests: libdbd-sqlite
1189 For changelogs see: 1190 <http://www.jus.uio.no/sisu/SiSU/changelog.html> 1191 <http://www.jus.uio.no/sisu/sisu_changelog/changelog.html> 1192 non-free 1193 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. 1194 sisu-markup-samples_1.0.8-1_all.deb 77<http://www.jus.uio.no/sisu/archive/pool/non-free/s/sisu-markup-samples/sisu-markup-samples_1.0.8-1_all.deb>
marked up documents and other examples related to sisu, a larger package containing a number of texts
Depends: sisu
1195 sisu-markup-samples_1.0.8-1.dsc 78<http://www.jus.uio.no/sisu/archive/pool/non-free/s/sisu-markup-samples/sisu-markup-samples_1.0.8-1.dsc>
ca03c11467097d6049c43c54d0961ef5 606 sisu-markup-samples_1.0.8-1.dsc
1196 For changelogs see: 1197 <http://www.jus.uio.no/sisu/SiSU/changelog_markup_samples.html> 1198 <http://www.jus.uio.no/sisu/sisu_markup_samples_changelog/changelog_markup_samples.html>
1199 rpm RPM 1200 The RPM is generated from the source file using Alien.79<http://www.kitenet.net/programs/alien/> Dependencies are not handled, not even that of the essential Ruby. 1201 sisu_0.58.3.orig-1-2.noarch.rpm 80<http://www.jus.uio.no/sisu/pkg/rpm/sisu_0.58.3.orig-1-2.noarch.rpm>
31f5cd3e0e577b418e7c98492f71f0af
untested, created using: alien -r sisu_0.58.3.orig.tar.gz
1202 sisu-0.58.3-2.noarch.rpm 81<http://www.jus.uio.no/sisu/pkg/rpm/sisu-0.58.3-2.noarch.rpm>
8b6858f0117351ce441e8559bf5308be
untested, created using: alien -r sisu_0.58.3-1_all.deb
1203 sisu-markup-samples_1.0.8.orig-2.noarch.rpm 82<http://www.jus.uio.no/sisu/pkg/rpm/sisu-markup-samples_1.0.6.orig-2.noarch.rpm>
15eed830b4d004f011bafe831bb816da
untested, created using alien
1204 sudo rpm -i [package name]
1205 Installation 1206 installation 34. Installation 1207 See the download pages 83<http://www.jus.uio.no/sisu/SiSU/download>
<http://www.jus.uio.no/sisu/sisu_download>
for information related to installation.
1208 34.1 34.1 Debian 1209 SiSU is developed on Debian, and packages are available for Debian that take care of the dependencies encountered on installation. 1210 The package is divided into the following components: 1211 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 1212 sisu-complete, a dummy package that installs the whole of greater sisu as described below, apart from sisu-examples 1213 sisu-pdf, dependencies used by sisu to produce pdf from LaTeX generated 1214 sisu-postgresql, dependencies used by sisu to populate postgresql database (further configuration is necessary) 1215 sisu-remote, dependencies used to place sisu output on a remote server (further configuration is necessary) 1216 sisu-sqlite, dependencies used by sisu to populate sqlite database 1217 sisu-markup-samples, sisu markup samples and other miscellany (under Debian Free Software Guidelines non-free) 1218 SiSU is available off Debian Unstable and Testing 84<http://packages.qa.debian.org/s/sisu.html> install it using apt-get, aptitude or alternative Debian install tools. SiSU is currently comprised of eight packages. 1219 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: 1220      #/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    
1221 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. 1222 On Debian there is little more to know beyond how to install software on Debian using apt, aptitude or synaptic. 1223      #Using aptitude:

       aptitude update

       aptitude install sisu-complete sisu-markup-samples    
1224      Using apt-get

       apt-get update

       apt get install sisu-complete sisu-examples    
1225 34.2 34.2 Other Unix / Linux 1226 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. 85Notes on dependencies are provided in the section that follows Information on dependencies configured for Debian is provided as this may be of assistance. 1227 34.2.1 34.2.1 source tarball 1228 installation with provided install script 1229 To install SiSU, in the root directory of the unpacked SiSU as root type:86This 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. 1230 ruby install 1231 Once installed see man 8 sisu for information on additional programs that sisu makes use of. 1232 Further notes on install script. 1233 The install script is prepared using Rant, and a Rantfile is provided,87a Rantfile has been configured to do post installation setup with more comprehensive install options, and post install and setup configuration and generation of first test file, if you have installed Stefan Lang's Rant 88<http://make.rubyforge.org/> <http://make.rubyforge.org/>
<http://rubyforge.org/frs/?group_id=615>
installed. While in the package directory, type: rant help, or rant -T, or to install SiSU as root, type:
1234 install is an install script prepared using Stefan Lang's Rant 89<http://make.rubyforge.org/> <http://make.rubyforge.org/>
<http://rubyforge.org/frs/?group_id=615>
It should work whether you have previously installed Rant or not. It has fairly comprehensive install options, and can do some post install and setup configuration and generation of first test file. For options type:
1235 ruby install -T 1236 To install as root type: 1237 ruby install 1238 For a minimal install type: 1239 ruby install base 1240 installation with setup.rb 1241 setup.rb 90<http://i.loveruby.net/en/projects/setup/> is provided the package and will install SiSU91Minero Aoki
<http://i.loveruby.net/en/projects/setup/doc/>
installation is a 3 step process92Installation instructions
<http://i.loveruby.net/en/projects/setup/doc/usage.html>
the following string assumes you are in the package directory and that you have root as sudo:
1242 ruby setup.rb config && ruby setup.rb setup && sudo ruby setup.rb install 1243 installation of rpm 1244 The RPM is generated from the source file using Alien.93<http://www.kitenet.net/programs/alien/> Dependencies are not handled, not even that of the essential Ruby.
1245 install_dependencies_and_notes 35. SiSU Components, Dependencies and Notes 1246 The dependency lists are from the Debian control file for SiSU version 0.36, and may assist in building SiSU on other distributions. 1247 35.1 35.1 sisu 1248 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 1249 Depends: on ruby (>=1.8.2), libwebrick-ruby 1250 Recommends: sisu-pdf, sisu-sqlite, sisu-postgresql, sisu-examples, librmagick-ruby, trang, tidy, libtidy, librexml-ruby, zip, unzip, openssl 1251 initialise directory 1252 sisu -CC 1253 html 1254 sisu -hv [filename/wildcard] 1255 sisu -Hv [filename/wildcard] 1256 LaTeX (but sisu-pdf dependencies required to convert that to pdf) 1257 sisu -pv [filename/wildcard] 1258 plain text Unix with footnotes 1259 sisu -av [filename/wildcard] 1260 plain text Dos with footnotes 1261 sisu -Av [filename/wildcard] 1262 plain text Unix with endnotes 1263 sisu -ev [filename/wildcard] 1264 plain text Dos with endnotes 1265 sisu -Ev [filename/wildcard] 1266 openoffice odt 1267 sisu -ov [filename/wildcard] 1268 xhtml 1269 sisu -bv [filename/wildcard] 1270 XML SAX 1271 sisu -xv [filename/wildcard] 1272 XML DOM 1273 sisu -Xv [filename/wildcard] 1274 wordmap (a rudimentary index of content) 1275 sisu -wv [filename/wildcard] 1276 document content certificate 1277 sisu -Nv [filename/wildcard] 1278 placement of sourcefile in output directory 1279 sisu -sv [filename/wildcard] 1280 creation of source tarball with images, and placement of source tarball in ouput directory 1281 sisu -Sv [filename/wildcard] 1282 manifest of output produced (polls output directory and provides links to existing output) 1283 sisu -yv [filename/wildcard] 1284 url for output files -u -U 1285 sisu -uv[and other flags] [filename/wildcard] 1286 sisu -Uv [filename/wildcard] 1287 toggle screen colour 1288 sisu -cv[and processing flags] [filename/wildcard] 1289 verbose mode 1290 sisu -v[and processing flags] [filename/wildcard] 1291 sisu -V[and processing flags] [filename/wildcard] 1292 quiet mode 1293 sisu -q[and processing flags] [filename/wildcard] 1294 maintenance mode, intermediate files kept -M 1295 sisu -Mv[and other flags] [filename/wildcard] 1296 [the -v is for verbose] 1297 start the webrick server 1298 sisu -W 1299 35.2 35.2 sisu-complete 1300 a dummy package that installs the whole SiSU, apart from sisu-examples 1301 Depends: ruby (>=1.8.2), sisu, sisu-pdf, sisu-postgresql, sisu-remote, sisu-sqlite 1302 Recommends: sisu-examples 1303 35.3 35.3 sisu-examples 1304 installs sisu markup samples and other miscelleny 1305 Depends: sisu 1306 35.4 35.4 sisu-pdf 1307 dependencies used by sisu to produce pdf from LaTeX generated 1308 Depends: sisu, tetex-bin, tetex-extra, latex-ucs 1309 Suggests: evince, xpdf 1310 converts sisu LaTeX produced to pdf 1311 sisu -pv [filename/wildcard] 1312 [the -v is for verbose] 1313 35.5 35.5 sisu-postgresql 1314 dependencies used by sisu to populate postgresql database (further configuration is necessary) 1315 Depends: sisu, postgresql-8.1, libdbi-ruby, libdbm-ruby, libdbd-pg-ruby 1316 Suggests: pgaccess, libdbd-pgsql, postgresql-contrib-8.1 1317 installs dependencies for sisu to work with and populate postgresql database 1318 create database 1319 sisu -Dv createall 1320 drop database 1321 sisu -Dv dropall 1322 import content 1323 sisu -Div [filename/wildcard] 1324 sisu -Dv import [filename/wildcard] 1325 update content 1326 sisu -Duv [filename/wildcard] 1327 sisu -Dv update [filename/wildcard] 1328 [the -v is for verbose] 1329 The following are available without installation of the sisu-postgresql component, but are of interest in this context 1330 generate a sample database query form for use with webserver on port 80 1331 sisu -F 1332 or for use with webrick server 1333 sisu -F webrick 1334 to start webrick server 1335 sisu -W 1336 35.6 35.6 sisu-remote 1337 dependencies used to place sisu output on a remote server (further configuration is necessary) 1338 scp 1339 sisu -vr[and processing flags] [filename/wildcard] 1340 rsync 1341 sisu -vR[and processing flags] [filename/wildcard] 1342 [the -v is for verbose] 1343 Depends: sisu, rsync, openssh-client|lsh-client, keychain 1344 35.7 35.7 sisu-sqlite 1345 dependencies used by sisu to populate sqlite database 1346 Depends: sisu, sqlite, libdbi-ruby, libdbm-ruby, libdbd-sqlite-ruby 1347 Suggests: libdbd-sqlite 1348 installs dependencies for sisu to work with and populate sqlite database 1349 create database 1350 sisu -dv createall 1351 drop database 1352 sisu -dv dropall 1353 update content 1354 sisu -div [filename/wildcard] 1355 sisu -dv import [filename/wildcard] 1356 update content 1357 sisu -duv [filename/wildcard] 1358 sisu -dv update [filename/wildcard] 1359 [the -v is for verbose] 1360 The following are available without installation of the sisu-sqlite component, but are of interest in this context 1361 generate a sample database query form for use with webserver on port 80 1362 sisu -F 1363 or for use with webrick server 1364 sisu -F webrick 1365 to start webrick server 1366 sisu -W 1367 36 36. Quickstart - Getting Started Howto 1368 36.1 36.1 Installation 1369 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. 1370 36.1.1 36.1.1 Debian Installation 1371 SiSU is available directly from the Debian Sid and testing archives (and possibly Ubuntu), assuming your /etc/apt/sources.list is set accordingly: 1372        aptitude update
       aptitude install sisu-complete    
1373 The following /etc/apt/sources.list setting permits the download of additional markup samples: 1374      #/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
     d    
1375 The aptitude commands become: 1376        aptitude update
       aptitude install sisu-complete sisu-markup-samples    
1377 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 1378      #/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    
1379 repeat the aptitude commands 1380        aptitude update
       aptitude install sisu-complete sisu-markup-samples    
1381 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.
1382 36.1.2 36.1.2 RPM Installation 1383 RPMs are provided though untested, they are prepared by running alien against the source package, and against the debs. 1384 They may be downloaded from: 1385 <http://www.jus.uio.no/sisu/SiSU/download.html#rpm> 1386 as root type: 1387 rpm -i [rpm package name] 1388 36.1.3 36.1.3 Installation from source 1389 To install SiSU from source check information at: 1390 <http://www.jus.uio.no/sisu/SiSU/download.html#current> 1391 download the source package 1392 Unpack the source 1393 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: 1394 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, 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)94There is nothing to stop MySQL support being added in future. or converting LaTeX to pdf. 1395 setup.rb 1396 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: 1397          ruby setup.rb config
         ruby setup.rb setup
         #[and as root:]
         ruby setup.rb install    
1398 further information on setup.rb is available from: 1399 <http://i.loveruby.net/en/projects/setup/> 1400 <http://i.loveruby.net/en/projects/setup/doc/usage.html> 1401 "install" 1402 The "install" file provided is an installer prepared using "rant". In the root directory of the unpacked SiSU as root type: 1403 ruby install base 1404 or for a more complete installation: 1405 ruby install 1406 or 1407 ruby install base 1408 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. 1409 Further information on "rant" is available from: 1410 <http://make.rubyforge.org/> 1411 <http://rubyforge.org/frs/?group_id=615> 1412 For a list of alternative actions you may type: 1413 ruby install help 1414 ruby install -T
1415 36.2 36.2 Testing SiSU, generating output 1416 To check which version of sisu is installed: 1417 sisu -v 1418 Depending on your mode of installation one or a number of markup sample files may be found either in the directory: 1419 ... 1420 or 1421 ... 1422 change directory to the appropriate one: 1423 cd /usr/share/doc/sisu/sisu_markup_samples/dfsg 1424 36.2.1 36.2.1 basic text, plaintext, html, XML, ODF 1425 Having moved to the directory that contains the markup samples (see instructions above if necessary), choose a file and run sisu against it 1426 sisu -NhwoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst 1427 this will generate html including a concordance file, opendocument text format, plaintext, XHTML and various forms of XML, and OpenDocument text 1428 36.2.2 36.2.2 LaTeX / pdf 1429 Assuming a LaTeX engine such as tetex or texlive is installed with the required modules (done automatically on selection of sisu-pdf in Debian) 1430 Having moved to the directory that contains the markup samples (see instructions above if necessary), choose a file and run sisu against it 1431 sisu -pv free_as_in_freedom.rms_and_free_software.sam_williams.sst 1432 sisu -3 free_as_in_freedom.rms_and_free_software.sam_williams.sst 1433 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 1434 36.2.3 36.2.3 relational database - postgresql, sqlite 1435 Relational databases need some setting up - you must have permission to create the database and write to it when you run sisu. 1436 Assuming you have the database installed and the requisite permissions 1437 sisu --sqlite --recreate 1438 sisu --sqlite -v --import free_as_in_freedom.rms_and_free_software.sam_williams.sst 1439 sisu --pgsql --recreate 1440 sisu --pgsql -v --import free_as_in_freedom.rms_and_free_software.sam_williams.sst 1441 36.3 36.3 Getting Help 1442 36.3.1 36.3.1 The man pages 1443 Type: 1444 man sisu 1445 The man pages are also available online, though not always kept as up to date as within the package itself: 1446 sisu.1 95<http://www.jus.uio.no/sisu/man/sisu.1> 1447 sisu.8 96<http://www.jus.uio.no/sisu/man/sisu.8> 1448 man directory 97<http://www.jus.uio.no/sisu/man> 1449 36.3.2 36.3.2 Built in help 1450 sisu --help 1451 sisu --help --env 1452 sisu --help --commands 1453 sisu --help --markup 1454 36.3.3 36.3.3 The home page 1455 <http://www.jus.uio.no/sisu> 1456 <http://www.jus.uio.no/sisu/SiSU> 1457 36.4 36.4 Markup Samples 1458 A number of markup samples (along with output) are available off: 1459 <http://www.jus.uio.no/sisu/SiSU/2.html> 1460 Additional markup samples are packaged separately in the file: 1461 * 1462 On Debian they are available in non-free98the Debian Free Software guidelines require that everything distributed within Debian can be changed - and the documents are authors' works that while freely distributable are not freely changeable. to include them it is necessary to include non-free in your /etc/apt/source.list or obtain them from the sisu home site.
1463 HowTo 1464 howto_help 37. Getting Help 1465 An online manual of sorts should be available at: 1466 <http://www.jus.uio.no/sisu_manual/> 1467 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. 1468 37.1 37.1 SiSU "man" pages 1469 If SiSU is installed on your system usual man commands should be available, try: 1470 man sisu 1471 The SiSU man pages can be viewed online at:99generated 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>
1472 An online version of the sisu man page is available here: 1473 various sisu man pages 100<http://www.jus.uio.no/sisu/man/> 1474 sisu.1 101<http://www.jus.uio.no/sisu/man/sisu.1.html> 1475 sisu.8 102<http://www.jus.uio.no/sisu/man/sisu.8.html> 1476 sisu_examples.1 103<http://www.jus.uio.no/sisu/man/sisu_examples.1.html> 1477 sisu_webrick.1 104<http://www.jus.uio.no/sisu/man/sisu_webrick.1.html>
1478 37.2 37.2 SiSU built-in help 1479 sisu --help 1480 sisu --help [subject] 1481 sisu --help env [for feedback on the way your system is setup with regard to sisu] 1482 sisu -V [same as above command] 1483 sisu --help commands 1484 sisu --help markup 1485 37.3 37.3 Command Line with Flags - Batch Processing 1486 Running sisu (alone without any flags, filenames or wildcards) brings up the interactive help, as does any sisu command that is not recognised. 1487 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.
1488 howto_setup 38. Setup, initialisation 1489 38.1 38.1 initialise output directory 1490 Images, css files for a document directory are copied to their respective locations in the output directory. 1491 while within your document markup/preparation directory, issue the following command 1492 sisu -CC 1493 38.1.1 38.1.1 Use of search functionality, an example using sqlite 1494 SiSU can populate PostgreSQL and Sqlite databases and provides a sample search form for querying these databases. 1495 This note provides an example to get you started and will use sqlite 1496 It is necessary to: 1497 (1) make sure the required dependencies have been installed 1498 (2) have a directory with sisu markup samples that is writable 1499 (3) use sisu to create a database 1500 (4) use sisu tp populate a database 1501 (5) use sisu to start the webrick (httpd) server 1502 (6) use sisu to create a search form 1503 (7) copy the search form to the cgi directory 1504 (8) open up the form in your browser 1505 (9) query the database using the search form 1506 (1) make sure the required dependencies have been installed 1507 if you use Debian, the following command will install the required dependencies 1508 aptitude install sisu-sqlite 1509 (2) have a directory with sisu markup samples that is writable 1510 ideally copy the sisu-examples directory to your home directory (because the directory in which you run this example should be writable) 1511 cp -rv /usr/share/sisu-examples/sample/document_samples_sisu_markup ~/. 1512 (3) use sisu to create an sqlite database 1513 within the sisu-examples directory 1514 sisu -dv createall 1515 (4) use sisu tp populate a database with some text 1516 within the sisu-examples directory 1517 sisu -div free_*.sst 1518 or 1519 sisu -dv import free_*.sst debian_constitution_v1.2.sst debian_social_contract_v1.1.sst gpl2.fsf.sst 1520 (5) use sisu to start the webrick (httpd) server (if it has not already been started): 1521 sisu -W 1522 (6) use sisu to create a search form (for use with the webrick server, and your sample documents) 1523 within the sisu-examples directory 1524 sisu -F webrick 1525 #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 1526 #now this should be possible: sisu -F webrick 1527 (7) copy the search form to the cgi directory 1528 the string should be provided as output from the previous command 1529 sudo cp -vi /usr/share/sisu-examples/sample/document_samples_sisu_markup/sisu_sqlite.cgi /usr/lib/cgi-bin 1530 sudo chmod -v 755 /usr/lib/cgi-bin/sisu_sqlite.cgi 1531 (8) open up the form in your browser and query it 1532 url: 1533 <http://localhost:8081/cgi-bin/sisu_sqlite.cgi> 1534 or as instructed by command sisu -F webrick 1535 (9) query the database using the search form 1536 if there are other options in the dropdown menu select 1537 document_samples_sisu_markup 1538 and search for some text, e.g.: 1539 aim OR project 1540 selecting the index radio button gives an index of results using the object numbers 1541 selecting the text radio button gives the content of the matched paragraphs with the match highlighted 1542 (10) to start again with a new database 1543 to start from scratch you can drop the database with the command 1544 sisu -dv dropall 1545 and go to step 3 1546 to get to step 3 in one step with a single command 1547 sisu -dv recreate 1548 continue subsequent steps 1549 38.2 38.2 misc 1550 38.2.1 38.2.1 url for output files -u -U 1551 sisu -uv[and other flags] [filename/wildcard] 1552 sisu -Uv [filename/wildcard] 1553 38.2.2 38.2.2 toggle screen color 1554 sisu -cv[and processing flags] [filename/wildcard] 1555 38.2.3 38.2.3 verbose mode 1556 sisu -v[and processing flags] [filename/wildcard] 1557 sisu -V[and processing flags] [filename/wildcard] 1558 38.2.4 38.2.4 quiet mode 1559 sisu -q[and processing flags] [filename/wildcard] 1560 38.2.5 38.2.5 maintenance mode intermediate files kept -M 1561 sisu -Mv[and other flags] [filename/wildcard] 1562 38.2.6 38.2.6 start the webrick server 1563 sisu -W 1564 38.3 38.3 remote placement of output 1565 configuration is necessary 1566 scp 1567 sisu -vr[and processing flags] [filename/wildcard] 1568 rsync 1569 sisu -vR[and processing flags] [filename/wildcard] 1570 howto_config 39. Configuration Files 1571 Sample provided, on untarring the source tarball: 1572 conf/sisu/sisurc.yaml 1573 and on installation under: 1574 /etc/sisu/sisurc.yaml 1575 The following paths are searched: 1576 ./_sisu/sisurc.yaml 1577 ~/.sisu/sisurc.yaml 1578 ./etc/sisu/sisurc.yaml 1579 howto_markup 40. Markup 1580 See sample markup provided on 1581 <http://www.jus.uio.no/sisu> 1582 <http://www.jus.uio.no/sisu_markup> 1583 <http://www.jus.uio.no/sisu/SiSU> 1584 in particular for each of the document output samples provided, the source document is provided as well 1585 <http://www.jus.uio.no/sisu/SiSU/2#books> 1586 on untarring the source tarball: 1587 data/sisu-examples/sample/document_samples_sisu_markup/ 1588 or the same once source is installed (or sisu-examples) under: 1589 /usr/share/sisu-examples/sample/document_samples_sisu_markup/ 1590 Some notes are contained within the man page, man sisu and within sisu help via the commands sisu help markup and sisu help headers 1591 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: 1592 40.1 40.1 Headers 1593 Headers @headername: provide information related to the document, this may relate to 1594 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 1595 2. semantic information about the document including the dublin core 1596 40.2 40.2 Font Face 1597 Defaults are set. You may change the face to: bold, italics, underscore, strikethrough, ... 1598 40.2.1 40.2.1 Bold 1599 \@bold: [list of words that should be made bold within document] 1600 bold line 1601 !_ bold line 1602 bold word or sentence 1603 !{ bold word or sentence }! 1604 *{ bold word or sentence }* 1605 boldword or boldword 1606 *boldword* or !boldword! 1607 40.2.2 40.2.2 Italics 1608 \@italics: [list of words that should be italicised within document] 1609 italicise word or sentence 1610 /{ italicise word or sentence }/ 1611 italicisedword 1612 /italicisedword/ 1613 40.2.3 40.2.3 Underscore 1614 underscore word or sentence 1615 _{ underscore word or sentence }_ 1616 underscoreword 1617 40.2.4 40.2.4 Strikethrough 1618 strikethrough word or sentence 1619 -{ strikethrough word or sentence }- 1620 strikeword 1621 -strikeword- 1622 40.3 40.3 Endnotes 1623 There are two forms of markup for endnotes, they cannot be mixed within the same document 1624 here105this is an endnote 1625 1. preferred endnote markup 1626 here~{ this is an endnote }~ 1627 2. alternative markup equivalent, kept because it is possible to search and replace to get markup in existing texts such as Project Gutenberg 1628 here~^ 1629 ^~ this is an endote 1630 40.4 40.4 Links 1631 SiSU 1632 { SiSU }http://sisudoc.org 1633 sisu.png 1634 {sisu.png }http://sisudoc.org 1635 {tux.png 64x80 }image 1636 { tux.png 64x80 }image 1637 SiSU 106<http://sisudoc.org> 1638 { SiSU }http://sisudoc.org 1639 is equivalent to: 1640 { SiSU }http://sisudoc.org ~{ <http://sisudoc.org> }~ 1641 the same can be done with an image: 1642 [sisu.png] "SiSU" 108<http://sisudoc.org> 1643 { sisu.png "SiSU" }http://sisudoc.org 1644 40.5 40.5 Number Titles 1645 Set with the header @markup: 1646 40.6 40.6 Line operations 1647 Line Operations (marker placed at start of line) 1648 !_ bold line 1649 bold line 1650 _1 indent paragraph one level 1651 indent paragraph one level 1652 _2 indent paragraph two steps 1653 indent paragraph two steps 1654 _* bullet paragraph 1655 bullet paragraph 1656 # number paragraph (see headers for numbering document headings) 1657 1. number paragraph (see headers for numbering document headings) 1658 _# number paragraph level 2 (see headers for numbering document headings) 1659 a. number paragraph level 2 (see headers for numbering document headings) 1660 40.7 40.7 Tables 1661 Table markup sample 1662 table{~h c3; 26; 32; 32;
1663 This is a table, column1
this would become row one of column two
column three of row one is here
1664 column one row 2
column two of row two
column three of row two, and so on
1665 column one row three
and so on
here
1666 }table
1667 Alternative form of table markup 1668      {t\~h}
          |Mon|Tue|Wed|Thu|Fri|Sat|Sun
     0    | * | * | * | * | * | * | *
     1    | * | * | * | * |   |   |  
     2    | - | * | * | * | * | * |  
     3    | - | * | * | * | * | * | *
     4    | - |   |   | * | * | * |  
     5    | * | * | * | * | * | * | *    
1669 40.8 40.8 Grouped Text 1670        5.times { puts 'Ruby' }     1671 code{ 1672        5.times { puts 'Ruby' }     1673 }code 1674 A Limerick
1675 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.
1676 poem{
1677 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.
1678 }\poem
1679 40.9 40.9 Composite Document 1680 To import another document, the master document or importing document should be named filename.r3 (r for require) 1681 << { filename.sst } 1682 << { filename.ssi }
1683 howto_appearance 41. Change Appearance 1684 41.1 41.1 Skins 1685 "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. 1686 There are a few examples provided, on untarring the source tarball: 1687 conf/sisu/skin/doc/ 1688 data/sisu-examples/sample/document_samples_sisu_markup/_sisu/skin/doc 1689 and on installation under: 1690 /etc/sisu/skin/doc/ 1691 /usr/share/sisu-examples/sample/document_samples_sisu_markup/_sisu/skin/doc 1692 The following paths are searched: 1693 ./_sisu/skin 1694 ~/.sisu/skin 1695 /etc/sisu/skin 1696 Skins under the searched paths in a per document directory, a per directory directory, or a site directory, named: 1697 doc [may be specified individually in each document] 1698 dir [used if identifier part of name matches markup directory name] 1699 site 1700 It is usual to place all skins in the document directory, with symbolic links as required from dir or site directories. 1701 41.2 41.2 CSS 1702 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: 1703 _./_sisu/css 1704 ~/.sisu/css 1705 and 1706 /etc/sisu/css 1707 The contents of the first directory found in the search path are copied to the corresponding sisu output directory with the commnd: 1708 sisu -CC 1709 The SiSU standard css files for SiSU output are: 1710 dom.css html.css html_tables.css index.css sax.css xhtml.css 1711 A document may specify its own/bespoke css file using the css header. 1712 \@css: 1713 [expand]
1714 Extracts from the README 1715 howto_readme 42. README 1716 SiSU 0.55 2007w27/6 2007-07-07 1717 Homepage: <http://www.jus.uio.no/sisu> 1718 Description 1719 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. 1720 With minimal preparation of a plain-text (UTF-8) file using its native markup-syntax, SiSU produces: plain-text, HTML, XHTML, 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. 1721 Outputs share a common citation numbering system, and any semantic meta-data provided about the document. 1722 SiSU also provides concordance files, document content certificates and manifests of generated output. 1723 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). 1724 A vim syntax highlighting file and an ftplugin with folds for sisu markup is provided. Vim 7 includes syntax highlighting for SiSU. 1725 man pages, and interactive help are provided. 1726 Dependencies for various features are taken care of in sisu related packages. The package sisu-complete installs the whole of SiSU. 1727 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. 1728 Homepage: <http://www.jus.uio.no/sisu> 1729 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. 1730 SiSU can be used for Internet, Intranet, local filesystem or cd publishing. 1731 SiSU can be used directly off the filesystem, or from a database. 1732 SiSU's scalability, is be dependent on your hardware, and filesystem (in my case Reiserfs), and/or database Postgresql. 1733 Amongst it's characteristics are: 1734 simple mnemonoic markup style, 1735 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, 1736 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. 1737 it is command line driven, and can be set up on a remote server 1738 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. 1739 Input files should be UTF-8 1740 Once set up it is simple to use. 1741 42.1 42.1 Online Information, places to look 1742 <http://www.jus.uio.no/sisu> 1743 Download Sources: 1744 <http://www.jus.uio.no/sisu/SiSU/download.html#current> 1745 <http://www.jus.uio.no/sisu/SiSU/download.html#debian> 1746 42.2 42.2 Installation 1747 NB. Platform is Unix / Linux. 1748 42.2.1 42.2.1 Debian 1749 If you use Debian use the Debian packages, check the information at: 1750 <http://www.jus.uio.no/sisu/SiSU/download.html#debian> 1751 (A) SiSU is available directly off the Debian archives for Sid and testing. It should necessary only to run as root: 1752 aptitude update 1753 aptitude install sisu-complete 1754 (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 1755 deb <http://www.jus.uio.no/sisu/archive> unstable main non-free 1756 deb-src <http://www.jus.uio.no/sisu/archive> unstable main non-free 1757 [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] 1758 Then as root run: 1759 aptitude update 1760 aptitude install sisu-complete 1761 42.2.2 42.2.2 RPM 1762 RPMs are provided though untested, they are prepared by running alien against the source package, and against the debs. 1763 They may be downloaded from: 1764 <http://www.jus.uio.no/sisu/SiSU/download.html#rpm> 1765 42.2.3 42.2.3 Source package .tgz 1766 Otherwise to install SiSU from source, check information at: 1767 <http://www.jus.uio.no/sisu/SiSU/download.html#current> 1768 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, 1769 Ruby is the essential dependency for the basic operation of SiSU 1770 1. Download the latest source (information available) from: 1771 <http://www.jus.uio.no/sisu/SiSU/download.html#current> 1772 2. Unpack the source 1773 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. 1774 42.2.4 42.2.4 to use setup.rb 1775 this is a three step process, in the root directory of the unpacked SiSU as root type: 1776 ruby setup.rb config 1777 ruby setup.rb setup 1778 as root: 1779 ruby setup.rb install 1780 further information: 1781 <http://i.loveruby.net/en/projects/setup/> 1782 <http://i.loveruby.net/en/projects/setup/doc/usage.html> 1783 42.2.5 42.2.5 to use install (prapared with "Rake") 1784 Rake must be installed on your system: 1785 <http://rake.rubyforge.org/> 1786 <http://rubyforge.org/frs/?group_id=50> 1787 in the root directory of the unpacked SiSU as root type: 1788 rake 1789 or 1790 rake base 1791 This makes use of Rake (by Jim Weirich) and the provided Rakefile 1792 For a list of alternative actions you may type: 1793 rake help 1794 rake -T 1795 42.2.6 42.2.6 to use install (prapared with "Rant") 1796 (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:) 1797 in the root directory of the unpacked SiSU as root type: 1798 ruby ./sisu-install 1799 or 1800 ruby ./sisu-install base 1801 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. 1802 further information: 1803 <http://make.rubyforge.org/> 1804 <http://rubyforge.org/frs/?group_id=615> 1805 For a list of alternative actions you may type: 1806 ruby ./sisu-install help 1807 ruby ./sisu-install -T 1808 42.3 42.3 Dependencies 1809 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. 1810 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). 1811 The following is from the debian/control file of sisu-0.58.2, which amongst other things provides the dependencies of sisu within Debian. 1812      Package: sisu
     Architecture: all
     Depends: ruby (>= 1.8.2), libwebrick-ruby, unzip, zip
     Conflicts: vim-sisu, sisu-vim, sisu-remote
     Replaces: vim-sisu, sisu-vim
     Recommends: sisu-pdf, sisu-sqlite, sisu-postgresql, librmagick-ruby, trang,
     tidy, librexml-ruby, openssl, rsync, openssh-client | lsh-client, keychain,
     hyperestraier, kdissert, vim-addon-manager
     Suggests: rcs | cvs, lv, texinfo, pinfo

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

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

     Package: sisu-postgresql
     Depends: sisu, postgresql-8.1, libdbi-ruby, libdbm-ruby, libdbd-pg-ruby
     Suggests: pgaccess, libdbd-pgsql, postgresql-contrib-8.1

     Package: sisu-sqlite
     Depends: sisu, sqlite, libdbi-ruby, libdbm-ruby, libdbd-sqlite-ruby
     Suggests: libdbd-sqlite

     Package: sisu-markup-samples
     Depends: sisu    
1813      Source: sisu
     Section: text
     Priority: optional
     Maintainer: Ralph Amissah <ralph@amissah.com>
     Build-Depends: debhelper (>= 5)
     Standards-Version: 3.7.2

     Package: sisu
     Architecture: all
     Depends: ruby (>= 1.8.2), libwebrick-ruby, unzip, zip
     Conflicts: vim-sisu, sisu-vim, sisu-remote
     Replaces: vim-sisu, sisu-vim
     Recommends: sisu-pdf, sisu-sqlite, sisu-postgresql, hyperestraier, keychain, librmagick-ruby, librexml-ruby, openssl, openssh-client | lsh-client, rsync, tidy, vim-addon-manager
     Suggests: kdissert, lv, rcs | cvs, pinfo, texinfo, trang
     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, 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.
      .
       Homepage: <http://www.jus.uio.no/sisu>

    
1814      Package: sisu-complete
     Architecture: all
     Depends: ruby (>= 1.8.2), sisu, sisu-pdf, sisu-postgresql, sisu-sqlite
     Recommends: hyperestraier
     Description: installs all SiSU related packages
      This package installs SiSU and related packages that enable sisu to produce
      pdf and to populate postgresql and sqlite databases.
      .
      SiSU is a lightweight markup based document publishing framework.
      .
      See sisu for a description of the package.
      .
       Homepage: <http://www.jus.uio.no/sisu>

    
1815      Package: sisu-pdf
     Architecture: all
     Depends: sisu, texlive-latex-base, texlive-fonts-recommended, texlive-latex-recommended, texlive-latex-extra
     #Suggests: evince, xpdf
     Description: dependencies to convert SiSU LaTeX output to pdf
      This package enables the conversion of SiSU LaTeX output to pdf.
      .
      SiSU is a lightweight markup based document publishing framework.
      .
       Homepage: <http://www.jus.uio.no/sisu>

    
1816      Package: sisu-postgresql
     Architecture: all
     Depends: sisu, libdbd-pg-ruby, libdbi-ruby, libdbm-ruby, postgresql
     Recommends: libfcgi-ruby
     Suggests: postgresql-contrib
     Description: SiSU dependencies for use with postgresql database
      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.
      .
      SiSU is a lightweight markup based document publishing framework.
      .
       Homepage: <http://www.jus.uio.no/sisu>

    
1817      Package: sisu-sqlite
     Architecture: all
     Depends: sisu, sqlite, libdbd-sqlite-ruby, libdbi-ruby, libdbm-ruby
     Recommends: libfcgi-ruby
     Description: SiSU dependencies for use with sqlite database
      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.
      .
      SiSU is a lightweight markup based document publishing framework.
      .
       Homepage: <http://www.jus.uio.no/sisu>

    
1818 42.4 42.4 Quick start 1819 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). 1820 After installation of sisu-complete, move to the document samples directory 1821 cd /usr/share/doc/sisu/sisu_markup_samples/dfsg 1822 and run 1823 sisu -3 free_as_in_freedom.rms_and_free_software.sam_williams.sst 1824 or the same: 1825 sisu -NhwpoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst 1826 look at output results, see the "sisu_manifest" page created for the document 1827 or to generate an online document move to a writable directory, as the file will be downloaded there and e.g. 1828 sisu -3 <http://www.jus.uio.no/sisu/free_culture.lawrence_lessig/free_culture.lawrence_lessig.sst> 1829 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 1830 examine source document, vim has syntax support 1831 gvim free_as_in_freedom.rms_and_free_software.sam_williams.sst 1832 additional markup samples in 1833 <http://www.jus.uio.no/sisu/SiSU/2.html> 1834 For help 1835 man sisu 1836 or 1837 sisu --help 1838 e.g. 1839 for the way sisu "sees/maps" your system 1840 sisu --help env 1841 for list of commands and so on 1842 sisu --help commands 1843 42.5 42.5 Configuration files 1844 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 1845 configuration file - a yaml file 1846 /etc/sisu/[sisu version]/sisurc.yml 1847 ~/.sisu/sisurc.yml 1848 directory structure - setting up of output and working directory. 1849 * skins - changing the appearance of a project, directory or individual documents within ~/.sisu/skin 1850 ~/.sisu/skin/doc contains individual skins, with symbolic links from 1851 ~/.sisu/skin/dir if the contents of a directory are to take a particular document skin. 1852 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. 1853 if you use Vim as editor there is a syntax highlighter and fold resource config file for SiSU. I hope more syntax highlighters follow. 1854 There are post installation steps (which are really part of the overall installation) 1855 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). 1856 42.6 42.6 Use General Overview 1857 Documents are marked up in SiSU syntax and kept in an ordinary text editable file, named with the suffix .sst, or .ssm 1858 Marked up SiSU documents are usually kept in a sub-directory of your choosing 1859 use the interactive help and man pages 1860 sisu --help 1861 man sisu 1862 42.7 42.7 Help 1863 interactive help described below, or man page: 1864 man sisu 1865 man 8 sisu 1866 'man sisu_markup-samples' [if the sisu-markup-samples package is also installed] 1867 Once installed an interactive help is available typing 'sisu' (without) any flags, and select an option: 1868 sisu 1869 alternatively, you could type e.g. 1870 sisu --help commands 1871 sisu --help env 1872 sisu --help headers 1873 sisu --help markup 1874 sisu --help headings 1875 etc. 1876 for questions about mappings, output paths etc. 1877 sisu --help env 1878 sisu --help path 1879 sisu --help directory 1880 42.8 42.8 Directory Structure 1881 Once installed, type: 1882 sisu --help env 1883 or 1884 sisu -V 1885 42.9 42.9 Configuration File 1886 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) 1887 42.10 42.10 Markup 1888 See man pages. 1889 man sisu 1890 man 8 sisu 1891 Once installed there is some information on SiSU Markup in its help: 1892 sisu --help markup 1893 and 1894 sisu --help headers 1895 Sample marked up document are provided with the download tarball in the directory: 1896 ./data/doc/sisu/sisu_markup_samples/dfsg 1897 These are installed on the system usually at: 1898 /usr/share/doc/sisu/sisu_markup_samples/dfsg 1899 More markup samples are available in the package sisu-markup-samples 1900 <http://www.jus.uio.no/sisu/SiSU/download.html#sisu-markup-samples> 1901 Many more are available online off: 1902 <http://www.jus.uio.no/sisu/SiSU/2.html> 1903 42.11 42.11 Additional Things 1904 There is syntax support for some editors provided (together with a README file) in 1905 ./data/sisu/conf/syntax 1906 usually installed to: 1907 /usr/share/sisu/conf/syntax 1908 42.12 42.12 License 1909 License: GPL 3 or later see the copyright file in 1910 ./data/doc/sisu 1911 usually installed to: 1912 /usr/share/doc/sisu 1913 42.13 42.13 SiSU Standard 1914 SiSU uses: 1915 Standard SiSU markup syntax, 1916 Standard SiSU meta-markup syntax, and the 1917 Standard SiSU object citation numbering and system 1918 © Ralph Amissah 1997, current 2006 All Rights Reserved. 1919 however note the License section 1920 CHANGELOG 1921 ./CHANGELOG 1922 and see 1923 <http://www.jus.uio.no/sisu/SiSU/changelog.html> 1924 <http://www.jus.uio.no/sisu/SiSU/changelog_markup_samples.html>
1925 Extracts from man 8 sisu 1926 howto_setup_post_installation 43. Post Installation Setup 1927 43.1 43.1 Post Installation Setup - Quick start 1928 After installation of sisu-complete, move to the document samples directory, 1929 cd /usr/share/doc/sisu/sisu_markup_samples/dfsg 1930 [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] 1931 and in that directory, initialise the output directory with the command 1932 sisu -CC 1933 then run: 1934 sisu -1 free_as_in_freedom.rms_and_free_software.sam_williams.sst 1935 or the same: 1936 sisu -NhwpoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst 1937 look at output results, see the "sisu_manifest" page created for the document 1938 for an overview of your current sisu setup, type: 1939 sisu --help env 1940 or 1941 sisu -V 1942 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. 1943 sisu -1 <http://www.jus.uio.no/sisu/gpl3.fsf/gpl3.fsf.sst> 1944 sisu -3 <http://www.jus.uio.no/sisu/free_culture.lawrence_lessig/free_culture.lawrence_lessig.sst> 1945 examine source document, vim has syntax highlighting support 1946 gvim free_as_in_freedom.rms_and_free_software.sam_williams.sst 1947 additional markup samples in 1948 <http://www.jus.uio.no/sisu/SiSU/2.html> 1949 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. 1950 sisu -3 <http://www.jus.uio.no/sisu/free_culture.lawrence_lessig/sisupod.zip> 1951 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: 1952 sisu -3 --trust <http://www.jus.uio.no/sisu/free_culture.lawrence_lessig/sisupod.zip> 1953 For help 1954 man sisu 1955 sisu --help 1956 sisu --help env for the way sisu "sees/maps" your system 1957 sisu --help commands for list of commands and so on 1958 43.2 43.2 Document markup directory 1959 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: 1960 mkdir ~/sisu_test 1961 cd ~/sisu_test 1962 cp -a /usr/share/doc/sisu/sisu_markup_samples/dfsg/* ~/sisu_test/. 1963 Tip: the markup syntax examples may be of interest 1964 <http://www.jus.uio.no/sisu/sample/> 1965 Tip: 1966 sisu -U [sisu markup filename] 1967 should printout the different possible outputs and where sisu would place them. 1968 Tip: if you want to toggle ansi color add 1969 c 1970 to your flags. 1971 43.2.1 43.2.1 Configuration files 1972 SiSU configuration file search path is: 1973 ./_sisu/sisurc.yaml 1974 ~/.sisu/sisurc.yaml 1975 /etc/sisu/sisurc.yaml 1976 .\"%% Debian Installation Note 1977 43.2.2 43.2.2 Debian INSTALLATION Note 1978 It is best you see 1979 <http://www.jus.uio.no/sisu/SiSU/download.html#debian> 1980 for up the most up to date information. 1981 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): 1982 Package: sisu 1983 SiSU is a lightweight markup based, command line oriented, document structuring, publishing and search framework for document collections. 1984 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), 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. 1985 SiSU also provides concordance files, document content certificates and manifests of generated output. 1986 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. 1987 man pages, and interactive help are provided. 1988 Dependencies for various features are taken care of in sisu related packages. The package sisu-complete installs the whole of SiSU. 1989 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. 1990 Homepage: <http://www.jus.uio.no/sisu> 1991 43.2.3 43.2.3 Document Resource Configuration 1992 sisu resource configuration information is obtained from sources (where they exist): 1993 ~/.sisu/sisurc.yaml 1994 /etc/sisu/[sisu version]/sisurc.yaml 1995 sisu program defaults 1996 43.2.4 43.2.4 Skins 1997 Skins default document appearance may be modified using skins contained in sub-directories located at the following paths: 1998 ./_sisu/skin 1999 ~/.sisu/skin 2000 /etc/sisu/skin 2001 more specifically, the following locations (or their /etc/sisu equivalent) should be used: 2002 ~/.sisu/skin/doc 2003 skins for individual documents; 2004 ~/.sisu/skin/dir 2005 skins for directories of matching names; 2006 ~/.sisu/skin/site 2007 site-wide skin modifying the site-wide appearance of documents. 2008 Usually all skin files are placed in the document skin directory: 2009 ~/.sisu/skin/doc 2010 with softlinks being made to the skins contained there from other skin directories as required. 2011 faq 44. FAQ - Frequently Asked/Answered Questions 2012 44.1 44.1 Why are urls produced with the -v (and -u) flag that point to a web server on port 8081? 2013 Try the following rune: 2014 sisu -W 2015 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. 2016 44.2 44.2 I cannot find my output, where is it? 2017 The following should provide help on output paths: 2018 sisu --help env 2019 sisu -V [same as the previous command] 2020 sisu --help directory 2021 sisu --help path 2022 sisu -U [filename] 2023 man sisu 2024 44.3 44.3 I do not get any pdf output, why? 2025 SiSU produces LaTeX and pdflatex is run against that to generate pdf files. 2026 If you use Debian the following will install the required dependencies 2027 aptitude install sisu-pdf 2028 the following packages are required: tetex-bin, tetex-extra, latex-ucs 2029 44.4 44.4 Where is the latex (or some other interim) output? 2030 Try adding -M (for maintenance) to your command flags, e.g.: 2031 sisu -HpMv [filename] 2032 this should result in the interim processing output being retained, and information being provided on where to find it. 2033 sisu --help directory 2034 sisu --help path 2035 should also provide some relevant information as to where it is placed. 2036 44.5 44.5 Why isn't SiSU markup XML 2037 I worked with text and (though I find XML immensely valuable) disliked noise ... better to sidestep the question and say: 2038 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 2039 sisu --to-sax [filename/wildcard] 2040 sisu --to-dom [filename/wildcard] 2041 sisu --to-node [filename/wildcard] 2042 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]. 2043 sisu --from-xml2sst [filename/wildcard] 2044 44.6 44.6 LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU? 2045 SiSU is not really about type-setting. 2046 LaTeX is the ultimate computer instruction type-setting language for paper based publication. 2047 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. 2048 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. 2049 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. 2050 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. 2051 Where there are large document sets, it provides consistency in appearance in each output format for the documents. 2052 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. 2053 44.7 44.7 How do I create GIN or GiST index in Postgresql for use in SiSU 2054 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: 2055 "I have tsearch2 slides which introduces tsearch2 <http://www.sai.msu.su/~megera/wiki/tsearch2slides> 2056 FTS in PostgreSQL is provided by tsearch2, which should works without any indices (GiST or GIN) ! Indices provide performance, not functionality. 2057 In your example I'd do ( simple way, just for demo): 2058 0. compile, install tsearch2 and load tsearch2 into your database 2059 cd contrib/tsearch2; make&&make&&install&&make installcheck; psql DB < tsearch2.sql 2060 1. Add column fts, which holds tsvector 2061 alter table documents add column fts tsvector; 2062 2. Fill fts column 2063 update document set fts = to_tsvector(clean); 2064 3. create index - just for performance ! 2065 create index fts_gin_idx on document using gin(fts); 2066 4. Run vacuum 2067 vacuum analyze document; 2068 That's all. 2069 Now you can search: 2070 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; 2071 44.8 44.8 Where is version 1.0? 2072 SiSU works pretty well as it is supposed to. Version 1.0 will have the current markup, and directory structure. At this point it is largely a matter of choice as to when the name change is made. 2073 The feature set for html,110html w3c compliance has been largely met. LaTeX/pdf and opendocument is in place. XML, and plaintext are in order. 2074 html and LaTeX/pdf may be regarded as reference copy outputs 2075 With regard to the populating of sql databases (postgresql and sqlite), there is a bit to be done. 2076 We are still almost there. 2077 45 45. Editor Files, Syntax Highlighting 2078 The directory: 2079 ./data/sisu/conf/editor-syntax-etc/ 2080 /usr/share/sisu/conf/editor-syntax-etc 2081 contains rudimentary sisu syntax highlighting files for: 2082 (g)vim <http://www.vim.org> 2083 package: sisu-vim 2084 status: largely done 2085 there is a vim syntax highlighting and folds component 2086 gedit <http://www.gnome.org/projects/gedit> 2087 gobby <http://gobby.0x539.de/> 2088 file: sisu.lang 2089 place in: 2090 /usr/share/gtksourceview-1.0/language-specs 2091 or 2092 ~/.gnome2/gtksourceview-1.0/language-specs 2093 status: very basic syntax highlighting 2094 comments: this editor features display line wrap and is used by Goby! 2095 nano <http://www.nano-editor.org> 2096 file: nanorc 2097 save as: 2098 ~/.nanorc 2099 status: basic syntax highlighting 2100 comments: assumes dark background; no display line-wrap; does line breaks 2101 diakonos (an editor written in ruby) <http://purepistos.net/diakonos> 2102 file: diakonos.conf 2103 save as: 2104 ~/.diakonos/diakonos.conf 2105 includes: 2106 status: basic syntax highlighting 2107 comments: assumes dark background; no display line-wrap 2108 kate & kwrite <http://kate.kde.org> 2109 file: sisu.xml 2110 place in: 2111 /usr/share/apps/katepart/syntax 2112 or 2113 ~/.kde/share/apps/katepart/syntax 2114 [settings::configure kate::{highlighting,filetypes}] 2115 [tools::highlighting::{markup,scripts}::SiSU] 2116 nedit <http://www.nedit.org> 2117 file: sisu_nedit.pats 2118 nedit -import sisu_nedit.pats 2119 status: a very clumsy first attempt [not really done] 2120 comments: this editor features display line wrap 2121 emacs <http://www.gnu.org/software/emacs/emacs.html> 2122 files: sisu-mode.el 2123 to file ~/.emacs add the following 2 lines: 2124 (add-to-list 'load-path "/usr/share/sisu-examples/config/syntax_hi") 2125 (require 'sisu-mode.el) 2126 [not done / not yet included] 2127 vim & gvim <http://www.vim.org> 2128 files: 2129 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) 2130 status: this includes: syntax highlighting; vim folds; some error checking 2131 comments: this editor features display line wrap 2132 NOTE: 2133 [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] 2134 help_sources 46. Help Sources 2135 For a summary of alternative ways to get help on SiSU try one of the following: 2136 man page 2137 man sisu_help 2138 man2html 2139 <file:///usr/share/doc/sisu/html/sisu_help.1.html> 2140 <http://www.jus.uio.no/sisu/man/sisu_help.1.html> 2141 sisu generated output - links to html 2142 <file:///usr/share/doc/sisu/sisu_manual/sisu_help/index.html> 2143 <http://sisudoc.org/sisu_manual/sisu_help/index.html> 2144 <http://www.jus.uio.no/sisu/sisu_manual/sisu_help/index.html> 2145 help sources lists 2146 Alternative sources for this help sources page listed here: 2147 man sisu_help_sources 2148 <file:///usr/share/doc/sisu/sisu_manual/sisu_help_sources/index.html> 2149 <file:///usr/share/doc/sisu/html/sisu_help_sources/index.html> 2150 <http://sisudoc.org/sisu_manual/sisu_help_sources/index.html> 2151 <http://www.jus.uio.no/sisu/sisu_manual/sisu_help_sources/index.html> 2152 46.1 46.1 man pages 2153 46.1.1 46.1.1 man 2154 man sisu 2155 man sisu_commands 2156 man 7 sisu_complete 2157 man sisu_configuration 2158 man 8 sisu_faq 2159 man sisu_filetypes 2160 man sisu_help 2161 man sisu_help_sources 2162 man 8 sisu_howto 2163 man sisu_introduction 2164 man sisu_markup 2165 man sisu_output_overview 2166 man 7 sisu_pdf 2167 man 7 sisu_postgresql 2168 man 8 sisu_quickstart 2169 man 8 sisu_remote 2170 man 8 sisu_search 2171 man sisu_skin 2172 man 7 sisu_sqlite 2173 man 8 sisu_syntax_highlighting 2174 man 7 sisu_vim 2175 man sisu_webrick 2176 46.2 46.2 sisu generated output - links to html 2177 Note SiSU documentation is prepared in SiSU and output is available in multiple formats including amongst others html, pdf, and odf which may be also be accessed via the html pages111named index.html or more extensively through sisu_manifest.html 2178 46.2.1 46.2.1 locally installed 2179 <file:///usr/share/doc/sisu/sisu_manual/sisu_manual/index.html> 2180 <file:///usr/share/doc/sisu/sisu_manual/sisu_help/index.html> 2181 <file:///usr/share/doc/sisu/sisu_manual/sisu_help_sources/index.html> 2182 /usr/share/doc/sisu/sisu_manual/sisu/index.html 2183 /usr/share/doc/sisu/sisu_manual/sisu_commands/index.html 2184 /usr/share/doc/sisu/sisu_manual/sisu_complete/index.html 2185 /usr/share/doc/sisu/sisu_manual/sisu_configuration/index.html 2186 /usr/share/doc/sisu/sisu_manual/sisu_description/index.html 2187 /usr/share/doc/sisu/sisu_manual/sisu_examples/index.html 2188 /usr/share/doc/sisu/sisu_manual/sisu_faq/index.html 2189 /usr/share/doc/sisu/sisu_manual/sisu_filetypes/index.html 2190 /usr/share/doc/sisu/sisu_manual/sisu_help/index.html 2191 /usr/share/doc/sisu/sisu_manual/sisu_help_sources/index.html 2192 /usr/share/doc/sisu/sisu_manual/sisu_howto/index.html 2193 /usr/share/doc/sisu/sisu_manual/sisu_introduction/index.html 2194 /usr/share/doc/sisu/sisu_manual/sisu_manual/index.html 2195 /usr/share/doc/sisu/sisu_manual/sisu_markup/index.html 2196 /usr/share/doc/sisu/sisu_manual/sisu_output_overview/index.html 2197 /usr/share/doc/sisu/sisu_manual/sisu_pdf/index.html 2198 /usr/share/doc/sisu/sisu_manual/sisu_postgresql/index.html 2199 /usr/share/doc/sisu/sisu_manual/sisu_quickstart/index.html 2200 /usr/share/doc/sisu/sisu_manual/sisu_remote/index.html 2201 /usr/share/doc/sisu/sisu_manual/sisu_search/index.html 2202 /usr/share/doc/sisu/sisu_manual/sisu_skin/index.html 2203 /usr/share/doc/sisu/sisu_manual/sisu_sqlite/index.html 2204 /usr/share/doc/sisu/sisu_manual/sisu_syntax_highlighting/index.html 2205 /usr/share/doc/sisu/sisu_manual/sisu_vim/index.html 2206 /usr/share/doc/sisu/sisu_manual/sisu_webrick/index.html 2207 46.2.2 46.2.2 www.sisudoc.org 2208 <http://sisudoc.org/sisu_manual/sisu_manual/index.html> 2209 <http://sisudoc.org/sisu_manual/sisu/index.html> 2210 <http://sisudoc.org/sisu_manual/sisu_commands/index.html> 2211 <http://sisudoc.org/sisu_manual/sisu_complete/index.html> 2212 <http://sisudoc.org/sisu_manual/sisu_configuration/index.html> 2213 <http://sisudoc.org/sisu_manual/sisu_description/index.html> 2214 <http://sisudoc.org/sisu_manual/sisu_examples/index.html> 2215 <http://sisudoc.org/sisu_manual/sisu_faq/index.html> 2216 <http://sisudoc.org/sisu_manual/sisu_filetypes/index.html> 2217 <http://sisudoc.org/sisu_manual/sisu_help/index.html> 2218 <http://sisudoc.org/sisu_manual/sisu_help_sources/index.html> 2219 <http://sisudoc.org/sisu_manual/sisu_howto/index.html> 2220 <http://sisudoc.org/sisu_manual/sisu_introduction/index.html> 2221 <http://sisudoc.org/sisu_manual/sisu_manual/index.html> 2222 <http://sisudoc.org/sisu_manual/sisu_markup/index.html> 2223 <http://sisudoc.org/sisu_manual/sisu_output_overview/index.html> 2224 <http://sisudoc.org/sisu_manual/sisu_pdf/index.html> 2225 <http://sisudoc.org/sisu_manual/sisu_postgresql/index.html> 2226 <http://sisudoc.org/sisu_manual/sisu_quickstart/index.html> 2227 <http://sisudoc.org/sisu_manual/sisu_remote/index.html> 2228 <http://sisudoc.org/sisu_manual/sisu_search/index.html> 2229 <http://sisudoc.org/sisu_manual/sisu_skin/index.html> 2230 <http://sisudoc.org/sisu_manual/sisu_sqlite/index.html> 2231 <http://sisudoc.org/sisu_manual/sisu_syntax_highlighting/index.html> 2232 <http://sisudoc.org/sisu_manual/sisu_vim/index.html> 2233 <http://sisudoc.org/sisu_manual/sisu_webrick/index.html> 2234 46.2.3 46.2.3 www.jus.uio.no/sisu 2235 <http://www.jus.uio.no/sisu/sisu_manual/sisu_manual/index.html> 2236 <http://www.jus.uio.no/sisu/sisu_manual/sisu/index.html> 2237 <http://www.jus.uio.no/sisu/sisu_manual/sisu_commands/index.html> 2238 <http://www.jus.uio.no/sisu/sisu_manual/sisu_complete/index.html> 2239 <http://www.jus.uio.no/sisu/sisu_manual/sisu_configuration/index.html> 2240 <http://www.jus.uio.no/sisu/sisu_manual/sisu_description/index.html> 2241 <http://www.jus.uio.no/sisu/sisu_manual/sisu_examples/index.html> 2242 <http://www.jus.uio.no/sisu/sisu_manual/sisu_faq/index.html> 2243 <http://www.jus.uio.no/sisu/sisu_manual/sisu_filetypes/index.html> 2244 <http://www.jus.uio.no/sisu/sisu_manual/sisu_help/index.html> 2245 <http://www.jus.uio.no/sisu/sisu_manual/sisu_help_sources/index.html> 2246 <http://www.jus.uio.no/sisu/sisu_manual/sisu_howto/index.html> 2247 <http://www.jus.uio.no/sisu/sisu_manual/sisu_introduction/index.html> 2248 <http://www.jus.uio.no/sisu/sisu_manual/sisu_manual/index.html> 2249 <http://www.jus.uio.no/sisu/sisu_manual/sisu_markup/index.html> 2250 <http://www.jus.uio.no/sisu/sisu_manual/sisu_output_overview/index.html> 2251 <http://www.jus.uio.no/sisu/sisu_manual/sisu_pdf/index.html> 2252 <http://www.jus.uio.no/sisu/sisu_manual/sisu_postgresql/index.html> 2253 <http://www.jus.uio.no/sisu/sisu_manual/sisu_quickstart/index.html> 2254 <http://www.jus.uio.no/sisu/sisu_manual/sisu_remote/index.html> 2255 <http://www.jus.uio.no/sisu/sisu_manual/sisu_search/index.html> 2256 <http://www.jus.uio.no/sisu/sisu_manual/sisu_skin/index.html> 2257 <http://www.jus.uio.no/sisu/sisu_manual/sisu_sqlite/index.html> 2258 <http://www.jus.uio.no/sisu/sisu_manual/sisu_syntax_highlighting/index.html> 2259 <http://www.jus.uio.no/sisu/sisu_manual/sisu_vim/index.html> 2260 <http://www.jus.uio.no/sisu/sisu_manual/sisu_webrick/index.html> 2261 46.2.4 46.2.4 man2html 2262 46.2.5 46.2.5 locally installed 2263 <file:///usr/share/doc/sisu/html/sisu_manual.1.html> 2264 <file:///usr/share/doc/sisu/html/sisu_help.1.html> 2265 <file:///usr/share/doc/sisu/html/sisu_help_sources.1.html> 2266 /usr/share/doc/sisu/html/sisu.1.html 2267 /usr/share/doc/sisu/html/sisu_commands.1.html 2268 /usr/share/doc/sisu/html/sisu_complete.7.html 2269 /usr/share/doc/sisu/html/sisu_configuration.1.html 2270 /usr/share/doc/sisu/html/sisu_faq.8.html 2271 /usr/share/doc/sisu/html/sisu_help.1.html 2272 /usr/share/doc/sisu/html/sisu_help_sources.1.html 2273 /usr/share/doc/sisu/html/sisu_howto.8.html 2274 /usr/share/doc/sisu/html/sisu_markup.1.html 2275 /usr/share/doc/sisu/html/sisu_pdf.7.html 2276 /usr/share/doc/sisu/html/sisu_postgresql.7.html 2277 /usr/share/doc/sisu/html/sisu_quickstart.8.html 2278 /usr/share/doc/sisu/html/sisu_remote.8.html 2279 /usr/share/doc/sisu/html/sisu_search.8.html 2280 /usr/share/doc/sisu/html/sisu_skin.1.html 2281 /usr/share/doc/sisu/html/sisu_sqlite.7.html 2282 /usr/share/doc/sisu/html/sisu_syntax_highlighting.8.html 2283 /usr/share/doc/sisu/html/sisu_vim.7.html 2284 /usr/share/doc/sisu/html/sisu_webrick.1.html 2285 46.2.6 46.2.6 www.sisudoc.org 2286 <http:///sisudoc.org/man/sisu_manual.1.html> 2287 <http:///sisudoc.org/man/sisu_help.1.html> 2288 <http:///sisudoc.org/man/sisu_help_sources.1.html> 2289 <http://sisudoc.org/man/sisu.1.html> 2290 <http://sisudoc.org/man/sisu_commands.1.html> 2291 <http://sisudoc.org/man/sisu_complete.7.html> 2292 <http://sisudoc.org/man/sisu_configuration.1.html> 2293 <http://sisudoc.org/man/sisu_faq.8.html> 2294 <http://sisudoc.org/man/sisu_help.1.html> 2295 <http://sisudoc.org/man/sisu_help_sources.1.html> 2296 <http://sisudoc.org/man/sisu_howto.8.html> 2297 <http://sisudoc.org/man/sisu_markup.1.html> 2298 <http://sisudoc.org/man/sisu_pdf.7.html> 2299 <http://sisudoc.org/man/sisu_postgresql.7.html> 2300 <http://sisudoc.org/man/sisu_quickstart.8.html> 2301 <http://sisudoc.org/man/sisu_remote.8.html> 2302 <http://sisudoc.org/man/sisu_search.8.html> 2303 <http://sisudoc.org/man/sisu_skin.1.html> 2304 <http://sisudoc.org/man/sisu_sqlite.7.html> 2305 <http://sisudoc.org/man/sisu_syntax_highlighting.8.html> 2306 <http://sisudoc.org/man/sisu_vim.7.html> 2307 <http://sisudoc.org/man/sisu_webrick.1.html> 2308 46.2.7 46.2.7 www.jus.uio.no/sisu 2309 <http://www.jus.uio.no/sisu/man/sisu_manual.1.html> 2310 <http://www.jus.uio.no/sisu/man/sisu_help.1.html> 2311 <http://www.jus.uio.no/sisu/man/sisu_help_sources.1.html> 2312 <http://www.jus.uio.no/sisu/man/sisu.1.html> 2313 <http://www.jus.uio.no/sisu/man/sisu_commands.1.html> 2314 <http://www.jus.uio.no/sisu/man/sisu_complete.7.html> 2315 <http://www.jus.uio.no/sisu/man/sisu_configuration.1.html> 2316 <http://www.jus.uio.no/sisu/man/sisu_faq.8.html> 2317 <http://www.jus.uio.no/sisu/man/sisu_help.1.html> 2318 <http://www.jus.uio.no/sisu/man/sisu_help_sources.1.html> 2319 <http://www.jus.uio.no/sisu/man/sisu_howto.8.html> 2320 <http://www.jus.uio.no/sisu/man/sisu_markup.1.html> 2321 <http://www.jus.uio.no/sisu/man/sisu_pdf.7.html> 2322 <http://www.jus.uio.no/sisu/man/sisu_postgresql.7.html> 2323 <http://www.jus.uio.no/sisu/man/sisu_quickstart.8.html> 2324 <http://www.jus.uio.no/sisu/man/sisu_remote.8.html> 2325 <http://www.jus.uio.no/sisu/man/sisu_search.8.html> 2326 <http://www.jus.uio.no/sisu/man/sisu_skin.1.html> 2327 <http://www.jus.uio.no/sisu/man/sisu_sqlite.7.html> 2328 <http://www.jus.uio.no/sisu/man/sisu_syntax_highlighting.8.html> 2329 <http://www.jus.uio.no/sisu/man/sisu_vim.7.html> 2330 <http://www.jus.uio.no/sisu/man/sisu_webrick.1.html> 0 endnotes Endnotes