diff options
| author | Ralph Amissah <ralph@amissah.com> | 2012-11-18 21:50:04 -0500 |
|---|---|---|
| committer | Ralph Amissah <ralph@amissah.com> | 2012-12-12 09:44:37 -0500 |
| commit | eae9bb93fdd2e677c8882bcc96d42b804ac2bafe (patch) | |
| tree | 5b5b33598ba30847c07888f6eb8cc644a8133876 /data/doc | |
| parent | v4: vim syntax, sisu.vim, make, new headers (diff) | |
v4: documentation; markup samples & help
Diffstat (limited to 'data/doc')
36 files changed, 7457 insertions, 6915 deletions
diff --git a/data/doc/sisu/CHANGELOG_v4 b/data/doc/sisu/CHANGELOG_v4 index 61c1f555..c3461a6c 100644 --- a/data/doc/sisu/CHANGELOG_v4 +++ b/data/doc/sisu/CHANGELOG_v4 @@ -66,3 +66,5 @@ http://www.jus.uio.no/sisu/pkg/src/sisu_4.0.0.orig.tar.xz * v4: document headers, metadata rearranged, wide-ranging effect * v4: vim syntax, sisu.vim, make new headers + +* v4: documentation; markup samples & help diff --git a/data/doc/sisu/html/sisu.1.html b/data/doc/sisu/html/sisu.1.html index 61535580..345e574b 100644 --- a/data/doc/sisu/html/sisu.1.html +++ b/data/doc/sisu/html/sisu.1.html @@ -1,2150 +1,1750 @@ -Content-type: text/html - -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> -<HTML><HEAD><TITLE>Man page of sisu</TITLE> -</HEAD><BODY> -<H1>sisu</H1> -Section: SiSU (1)<BR>Updated: 2012-05-25<BR><A HREF="#index">Index</A> -<A HREF="/cgi-bin/man/man2html">Return to Main Contents</A><HR> - -<BR> - -<A NAME="lbAB"> </A> -<H2>NAME</H2> - -<BR> - -sisu - documents: markup, structuring, publishing in multiple standard formats, and search -<BR> - -<A NAME="lbAC"> </A> -<H2>SYNOPSIS</H2> - -<BR> - +<!-- manual page source format generated by PolyglotMan v3.2, --> +<!-- available at http://polyglotman.sourceforge.net/ --> + +<html> +<head> +<title>"sisu"("1") manual page</title> +</head> +<body bgcolor='white'> +<a href='#toc'>Table of Contents</a><p> +<br> + +<h2><a name='sect0' href='#toc0'>Name</a></h2> +<br> +sisu - documents: markup, structuring, publishing in multiple standard formats, +and search <br> + +<h2><a name='sect1' href='#toc1'>Synopsis</a></h2> +<br> +sisu [-short-options|--long-options] [filename/wildcard] +<p> <br> sisu [-abCcDdeFGghIikLMmNnoPpQqRrSsTtUuVvWwXxYyZ_0-9] [filename/wildcard] -<BR> +<p> <br> +sisu --txt --html --epub --odt --pdf --wordmap --sqlite --manpage --texinfo --sisupod --source +--qrcode [filename/wildcard] +<p> <br> sisu [-Ddcv] [instruction] [filename/wildcard] -<P> <BR> - -sisu [-CcFLSVvW] -<P> <BR> - +<p> <br> +sisu --pg (--createdb|update [filename/wildcard]|--dropall) +<p> <br> sisu [operations] -<P> <BR> - -sisu --v3 [operations] -<P> <BR> - -sisu --v2 [operations] -<P> <BR> - -sisu2 [operations] -<A NAME="lbAD"> </A> -<H2>SISU - MANUAL,</H2> - -RALPH AMISSAH -<BR> - -<P> -<A NAME="lbAE"> </A> -<H2>WHAT IS SISU?</H2> - -<BR> -<P> -<A NAME="lbAF"> </A> -<H2>1. INTRODUCTION - WHAT IS SISU?</H2> - -<BR> <P> <BR> - -<B>SiSU</B> - -is a framework for document structuring, publishing (in multiple open standard -formats) and search, comprising of: (a) a lightweight document structure and -presentation markup syntax; and (b) an accompanying engine for generating -standard document format outputs from documents prepared in sisu markup syntax, -which is able to produce multiple standard outputs (including the population of -sql databases) that (can) share a common numbering system for the citation of -text within a document. -<P> <BR> - -<B>SiSU</B> is developed under an open source, software libre license (GPL3). -Its use case for development is work with medium to large document sets and -cope with evolving document formats/ representation technologies. Documents are -prepared once, and generated as need be to update the technical presentation or -add additional output formats. Various output formats (including search related -output) share a common mechanism for cross-output-format citation. -<P> <BR> - -<B>SiSU</B> -both defines a markup syntax and provides an engine that produces open -standards format outputs from documents prepared with -<B>SiSU</B> -markup. From a single lightly prepared document sisu custom builds several -standard output formats which share a common (text object) numbering system for +<p> <br> +sisu [-CcFLSVvW] +<p> <br> +sisu (--configure|--webrick|--sample-search-form) +<h2><a name='sect2' href='#toc2'>Sisu - Manual,</a></h2> +RALPH AMISSAH <br> + +<p> +<h2><a name='sect3' href='#toc3'>What is Sisu?</a></h2> +<br> + +<p> +<h2><a name='sect4' href='#toc4'>Introduction - What is Sisu?</a></h2> +<br> + +<p> <br> +<b>SiSU</b> is a framework for document structuring, publishing (in multiple open +standard formats) and search, comprising of: (a) a lightweight document +structure and presentation markup syntax; and (b) an accompanying engine +for generating standard document format outputs from documents prepared +in sisu markup syntax, which is able to produce multiple standard outputs +(including the population of sql databases) that (can) share a common numbering +system for the citation of text within a document. +<p> <br> +<b>SiSU</b> is developed under an open source, software libre license ( <i>GPLv3</i> +). Its use case for development is work with medium to large document sets +and cope with evolving document formats/ representation technologies. Documents +are prepared once, and generated as need be to update the technical presentation +or add additional output formats. Various output formats (including search +related output) share a common mechanism for cross-output-format citation. + +<p> <br> +<b>SiSU</b> both defines a markup syntax and provides an engine that produces +open standards format outputs from documents prepared with <b>SiSU</b> markup. +From a single lightly prepared document sisu custom builds several standard +output formats which share a common (text object) numbering system for citation of content within a document (that also has implications for search). -The sisu engine works with an abstraction of the document's structure and +The sisu engine works with an abstraction of the document’s structure and content from which it is possible to generate different forms of representation -of the document. Significantly -<B>SiSU</B> -markup is more sparse than html and outputs which include html, EPUB, LaTeX, -landscape and portrait pdfs, Open Document Format (ODF), all of which can be -added to and updated. -<B>SiSU</B> -is also able to populate SQL type databases at an object level, which means +of the document. Significantly <b>SiSU</b> markup is more sparse than html and +outputs which include <i>HTML,</i> <i>EPUB,</i> <i>ODT</i> (Open Document Format text), <i>LaTeX,</i> +landscape and portrait <i>PDF,</i> all of which can be added to and updated. <b>SiSU</b> +is also able to populate <i>SQL</i> type databases at an object level, which means that searches can be made with that degree of granularity. -<P> <BR> - -Source document preparation and output generation is a two step process: (i) -document source is prepared, that is, marked up in sisu markup syntax and (ii) -the desired output subsequently generated by running the sisu engine against -document source. Output representations if updated (in the sisu engine) can be -generated by re-running the engine against the prepared source. Using -<B>SiSU</B> markup applied to a document, <B>SiSU</B> custom builds (to take -advantage of the strengths of different ways of representing documents) various -standard open output formats including plain text, HTML, XHTML, XML, EPUB, -OpenDocument, LaTeX or PDF files, and populate an SQL database with objects[^1] -(equating generally to paragraph-sized chunks) so searches may be performed and -matches returned with that degree of granularity ( e.g. your search criteria is -met by these documents and at these locations within each document). Document -output formats share a common object numbering system for locating content. -This is particularly suitable for "published" works (finalized texts -as opposed to works that are frequently changed or updated) for which it -provides a fixed means of reference of content. - -<P> <BR> - -In preparing a <B>SiSU</B> document you optionally provide semantic information +<p> <br> +Source document preparation and output generation is a two step process: +(i) document source is prepared, that is, marked up in sisu markup syntax +and (ii) the desired output subsequently generated by running the sisu +engine against document source. Output representations if updated (in the +sisu engine) can be generated by re-running the engine against the prepared +source. Using <b>SiSU</b> markup applied to a document, <b>SiSU</b> custom builds (to +take advantage of the strengths of different ways of representing documents) +various standard open output formats including plain text, <i>HTML,</i> <i>XHTML,</i> +<i>XML,</i> <i>EPUB,</i> <i>ODT,</i> <i>LaTeX</i> or <i>PDF</i> files, and populate an <i>SQL</i> database with objects[^1] +(equating generally to paragraph-sized chunks) so searches may be performed +and matches returned with that degree of granularity ( e.g. your search criteria +is met by these documents and at these locations within each document). +Document output formats share a common object numbering system for locating +content. This is particularly suitable for "published" works (finalized +texts as opposed to works that are frequently changed or updated) for which +it provides a fixed means of reference of content. +<p> <br> +In preparing a <b>SiSU</b> document you optionally provide semantic information related to the document in a document header, and in marking up the substantive text provide information on the structure of the document, primarily indicating heading levels and footnotes. You also provide information on basic text -attributes where used. The rest is automatic, sisu from this information +attributes where used. The rest is automatic, sisu from this information custom builds[^2] the different forms of output requested. - -<P> <BR> - -<B>SiSU</B> works with an abstraction of the document based on its structure -which is comprised of its headings[^3] and objects[^4], which enables -<B>SiSU</B> to represent the document in many different ways, and to take -advantage of the strengths of different ways of presenting documents. The -objects are numbered, and these numbers can be used to provide a common basis -for citing material within a document across the different output format types. -This is significant as page numbers are not well suited to the digital age, in -web publishing, changing a browser's default font or using a different browser -can mean that text will appear on a different page; and publishing in different +<p> <br> +<b>SiSU</b> works with an abstraction of the document based on its structure which +is comprised of its headings[^3] and objects[^4], which enables <b>SiSU</b> to represent +the document in many different ways, and to take advantage of the strengths +of different ways of presenting documents. The objects are numbered, and +these numbers can be used to provide a common basis for citing material +within a document across the different output format types. This is significant +as page numbers are not well suited to the digital age, in web publishing, +changing a browser’s default font or using a different browser can mean +that text will appear on a different page; and publishing in different formats, html, landscape and portrait pdf etc. again page numbers are not -useful to cite text. Dealing with documents at an object level together with -object numbering also has implications for search that <B>SiSU</B> is able to -take advantage of. - -<P> <BR> - -One of the challenges of maintaining documents is to keep them in a format that -allows use of them independently of proprietary platforms. Consider issues -related to dealing with legacy proprietary formats today and what guarantee you -have that old proprietary formats will remain (or can be read without -proprietary software/equipment) in 15 years time, or the way the way in which -html has evolved over its relatively short span of existence. <B>SiSU</B> -provides the flexibility of producing documents in multiple non-proprietary -open formats including html, pdf[^5] ODF,[^6] and EPUB.[^7] Whilst <B>SiSU</B> -relies on software, the markup is uncomplicated and minimalistic which +useful to cite text. Dealing with documents at an object level together +with object numbering also has implications for search that <b>SiSU</b> is able +to take advantage of. +<p> <br> +One of the challenges of maintaining documents is to keep them in a format +that allows use of them independently of proprietary platforms. Consider +issues related to dealing with legacy proprietary formats today and what +guarantee you have that old proprietary formats will remain (or can be +read without proprietary software/equipment) in 15 years time, or the way +the way in which html has evolved over its relatively short span of existence. +<b>SiSU</b> provides the flexibility of producing documents in multiple non-proprietary +open formats including <i>HTML,</i> <i>EPUB,</i> [^5] <i>ODT,</i> [^6] <i>PDF</i> [^7] <i>ODF,</i> [^8]. Whilst +<b>SiSU</b> relies on software, the markup is uncomplicated and minimalistic which guarantees that future engines can be written to run against it. It is also -easily converted to other formats, which means documents prepared in -<B>SiSU</B> can be migrated to other document formats. Further security is -provided by the fact that the software itself, <B>SiSU</B> is available under -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. <B>SiSU</B> permits new forms of -output to be added as they become important, (Open Document Format text was -added in 2006 when it became an ISO standard for office applications and the -archival of documents), EPUB was introduced in 2009; and allows the technical -representations existing output to be updated (html has evolved and the related -module has been updated repeatedly over the years, presumably when the World -Wide Web Consortium (w3c) finalises html 5 which is currently under -development, the html module will again be updated allowing all existing -documents to be regenerated as html 5). - -<P> <BR> - +easily converted to other formats, which means documents prepared in <b>SiSU</b> +can be migrated to other document formats. Further security is provided +by the fact that the software itself, <b>SiSU</b> is available under <i>GPLv3</i> a licence +that guarantees that the source code will always be open, and free as in +libre, which means that that code base can be used, updated and further +developed as required under the terms of its license. Another challenge +is to keep up with a moving target. <b>SiSU</b> permits new forms of output to +be added as they become important, (Open Document Format text was added +in 2006 when it became an ISO standard for office applications and the +archival of documents), <i>EPUB</i> was introduced in 2009; and allows the technical +representations existing output to be updated ( <i>HTML</i> has evolved and the +related module has been updated repeatedly over the years, presumably when +the World Wide Web Consortium (w3c) finalises <i>HTML</i> 5 which is currently +under development, the <i>HTML</i> module will again be updated allowing all existing +documents to be regenerated as <i>HTML</i> 5). +<p> <br> The document formats are written to the file-system and available for indexing -by independent indexing tools, whether off the web like Google and Yahoo or on -the site like Lucene and Hyperestraier. - -<P> <BR> - -<B>SiSU</B> also provides other features such as concordance files and document +by independent indexing tools, whether off the web like Google and Yahoo +or on the site like Lucene and Hyperestraier. +<p> <br> +<b>SiSU</b> also provides other features such as concordance files and document content certificates, and the working against an abstraction of document -structure has further possibilities for the research and development of other -document representations, the availability of objects is useful for example for -topic maps and thesauri, together with the flexibility of <B>SiSU</B> offers -great possibilities. - -<P> <BR> - -<B>SiSU</B> is primarily for published works, which can take advantage of the -citation system to reliably reference its documents. <B>SiSU</B> works well in -a complementary manner with such collaborative technologies as Wikis, which can -take advantage of and be used to discuss the substance of content prepared in -<B>SiSU.</B> - -<P> <BR> - -<<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A>> - -<P> <BR> - -<<A HREF="http://www.jus.uio.no/sisu">http://www.jus.uio.no/sisu</A>> - -<P> -<A NAME="lbAG"> </A> -<H2>2. COMMANDS SUMMARY</H2> - -<BR> <P> - -<A NAME="lbAH"> </A> -<H2>2.1 DESCRIPTION</H2> - -<P> <BR> - -<B>SiSU</B> is a document publishing system, that from a simple single -marked-up document, produces multiple output formats including: plaintext, -html, xhtml, XML, epub, odt (odf text), LaTeX, pdf, info, and SQL (PostgreSQL -and SQLite), which share text object numbers ("object citation -numbering") and the same document structure information. For more see: -<<A HREF="http://www.jus.uio.no/sisu">http://www.jus.uio.no/sisu</A>> - -<P> -<A NAME="lbAI"> </A> -<H2>2.2 DOCUMENT PROCESSING COMMAND FLAGS</H2> - -<P> -<DL COMPACT> -<DT><B>-a [filename/wildcard]</B> - -<DD> -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) -<P> - -<DT><B>-b [filename/wildcard]</B> - -<DD> -see --xhtml -<P> -<DT><B>--by-*</B> - -<DD> -see --output-by-* -<P> -<DT><B>-C</B> - -<DD> -configure/initialise shared output directory files initialize shared output -directory (config files such as css and dtd files are not updated if they -already exist unless modifier is used). -C --init-site configure/initialise -site more extensive than -C on its own, shared output directory files/force -update, existing shared output config files such as css and dtd files are -updated if this modifier is used. -<P> -<DT><B>-CC</B> - -<DD> -see --configure -<P> -<DT><B>-c [filename/wildcard]</B> - -<DD> -see --color-toggle -<P> -<DT><B>--color-toggle [filename/wildcard]</B> - -<DD> -screen toggle ansi screen colour on or off depending on default set (unless -c -flag is used: if sisurc colour default is set to 'true', output to screen will -be with colour, if sisurc colour default is set to 'false' or is undefined -screen output will be without colour). Alias -c -<P> -<DT><B>--configure</B> - -<DD> -configure/initialise shared output directory files initialize shared output -directory (config files such as css and dtd files are not updated if they -already exist unless modifier is used). The equivalent of: -C --init-site -configure/initialise site, more extensive than -C on its own, shared output -directory files/force update, existing shared output config files such as css -and dtd files are updated if -CC is used. -<P> -<DT><B>--concordance [filename/wildcard]</B> - -<DD> -produces concordance (wordmap) a rudimentary index of all the words in a -document. (Concordance files are not generated for documents of over 260,000 -words unless this limit is increased in the file sisurc.yml). Alias -w -<P> -<DT><B>-D [instruction] [filename]</B> - -<DD> -see --pg -<P> -<DT><B>-d [--db-[database type (sqlite|pg)]] --[instruction] [filename]</B> - -<DD> -see --sqlite -<P> -<DT><B>--dal [filename/wildcard/url]</B> - -<DD> -assumed for most other flags, creates new intermediate files for processing +structure has further possibilities for the research and development of +other document representations, the availability of objects is useful for +example for topic maps and thesauri, together with the flexibility of <b>SiSU</b> +offers great possibilities. +<p> <br> +<b>SiSU</b> is primarily for published works, which can take advantage of the +citation system to reliably reference its documents. <b>SiSU</b> works well in +a complementary manner with such collaborative technologies as Wikis, which +can take advantage of and be used to discuss the substance of content prepared +in <b>SiSU.</b> +<p> <br> +<<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> +<p> <br> +<<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> +> +<p> +<h2><a name='sect5' href='#toc5'>Commands Summary</a></h2> +<br> + +<p> +<h2><a name='sect6' href='#toc6'>Description</a></h2> + +<p> <br> +<b>SiSU</b> is a document publishing system, that from a simple single marked-up +document, produces multiple output formats including: <i>plaintext,</i> <i>HTML,</i> +<i>XHTML,</i> <i>XML,</i> <i>EPUB,</i> <i>ODT</i> ( <i>OpenDocument</i> ( <i>ODF</i> ) text), <i>LaTeX,</i> <i>PDF,</i> info, and +<i>SQL</i> ( <i>PostgreSQL</i> and <i>SQLite</i> ) , which share text object numbers ("object +citation numbering") and the same document structure information. For more +see: <<a href='http://sisudoc.org'>http://sisudoc.org</a> +> or <<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> +> +<p> +<h2><a name='sect7' href='#toc7'>Document Processing +Command Flags</a></h2> + +<p> +<dl> + +<dt><b>-a [filename/wildcard]</b> </dt> +<dd>produces <i>plaintext</i> with Unix linefeeds +and without markup, (object numbers are omitted), has footnotes at end +of each paragraph that contains them [ -A for output file] [see -e for endnotes]. +(Options include: --endnotes for endnotes --footnotes for footnotes at the +end of each paragraph --unix for unix linefeed (default) --msdos for msdos +linefeed) +<p> </dd> + +<dt><b>-b [filename/wildcard]</b> </dt> +<dd>see --xhtml +<p> </dd> + +<dt><b>--by-*</b> </dt> +<dd>see --output-by-* +<p> </dd> + +<dt><b>-C</b> </dt> +<dd>configure/initialise +shared output directory files initialize shared output directory (config +files such as css and dtd files are not updated if they already exist unless +modifier is used). -C --init-site configure/initialise site more extensive than +-C on its own, shared output directory files/force update, existing shared +output config files such as css and dtd files are updated if this modifier +is used. +<p> </dd> + +<dt><b>-CC</b> </dt> +<dd>see --configure +<p> </dd> + +<dt><b>-c [filename/wildcard]</b> </dt> +<dd>see --color-toggle +<p> </dd> + +<dt><b>--color-toggle +[filename/wildcard]</b> </dt> +<dd>screen toggle ansi screen colour on or off depending +on default set (unless -c flag is used: if sisurc colour default is set +to ’true’, output to screen will be with colour, if sisurc colour default +is set to ’false’ or is undefined screen output will be without colour). Alias + +<p>- +<p>c +<p> </dd> + +<dt><b>--configure</b> </dt> +<dd>configure/initialise shared output directory files initialize +shared output directory (config files such as css and dtd files are not +updated if they already exist unless modifier is used). The equivalent of: +-C --init-site configure/initialise site, more extensive than -C on its own, +shared output directory files/force update, existing shared output config +files such as css and dtd files are updated if -CC is used. +<p> </dd> + +<dt><b>--concordance +[filename/wildcard]</b> </dt> +<dd>produces concordance (wordmap) a rudimentary index +of all the words in a document. (Concordance files are not generated for +documents of over 260,000 words unless this limit is increased in the file +sisurc.yml). Alias -w +<p> </dd> + +<dt><b>-D [instruction] [filename]</b> </dt> +<dd>see --pg +<p> </dd> + +<dt><b>-d [--db-[database type + (sqlite|pg)]] --[instruction] [filename]</b> </dt> +<dd>see --sqlite +<p> </dd> + +<dt><b>--dal [filename/wildcard/url]</b> +</dt> +<dd>assumed for most other flags, creates new intermediate files for processing (document abstraction) that is used in all subsequent processing of other output. This step is assumed for most processing flags. To skip it see -n. -Alias -m -<P> -<DT><B>--delete [filename/wildcard]</B> -<DD> -see --zap -<P> -<DT><B>--dump[=directory_path] [filename/wildcard]</B> +<p>Alias -m +<p> </dd> + +<dt><b>--delete [filename/wildcard]</b> </dt> +<dd>see --zap +<p> </dd> -<DD> -places output in directory specified, if none is specified in the current +<dt><b>--dump[=directory_path] [filename/wildcard]</b> +</dt> +<dd>places output in directory specified, if none is specified in the current directory (pwd). Compare --redirect -<P> -<DT><B>-e [filename/wildcard]</B> - -<DD> -see --epub -<P> -<DT><B>--epub [filename/wildcard]</B> - -<DD> -produces an epub document, [sisu version >=2 ] (filename.epub). Alias -e -<P> -<DT><B>--exc-*</B> - -<DD> -exclude output feature, overrides configuration settings --exc-ocn, (exclude -object citation numbering, (switches off object citation numbering), affects -html (seg, scroll), epub, xhtml, xml, pdf); --exc-toc, (exclude table of -contents, affects html (scroll), epub, pdf); --exc-links-to-manifest, ---exc-manifest-links, (exclude links to manifest, affects html (seg, -scroll)); --exc-search-form, (exclude search form, affects html (seg, -scroll), manifest); --exc-minitoc, (exclude mini table of contents, affects -html (seg), concordance, manifest); --exc-manifest-minitoc, (exclude mini -table of contents, affects manifest); --exc-html-minitoc, (exclude mini -table of contents, affects html (seg), concordance); --exc-html-navigation, -(exclude navigation, affects html (seg)); --exc-html-navigation-bar, -(exclude navigation bar, affects html (seg)); --exc-html-search-form, -(exclude search form, affects html (seg, scroll)); --exc-html-right-pane, -(exclude right pane/column, affects html (seg, scroll)); ---exc-html-top-band, (exclude top band, affects html (seg, scroll), -concordance (minitoc forced on to provide seg navigation)); --exc-segsubtoc -(exclude sub table of contents, affects html (seg), epub); see also --inc-* -<P> -<DT><B>-F [--webserv=webrick]</B> - -<DD> -see --sample-search-form -<P> -<DT><B>-f [optional string part of filename]</B> - -<DD> -see --find -<P> -<DT><B>--find [optional string part of filename]</B> - -<DD> -without match string, glob all .sst .ssm files in directory (including -language subdirectories). With match string, find files that match given string -in directory (including language subdirectories). Alias -f, --glob, -G -<P> -<DT><B>-G [optional string part of filename]</B> - -<DD> -see --find -<P> -<DT><B>-g [filename/wildcard]</B> - -<DD> -see --git -<P> -<DT><B>--git [filename/wildcard]</B> - -<DD> -produces or updates markup source file structure in a git repo (experimental -and subject to change). Alias -g -<P> -<DT><B>--glob [optional string part of filename]</B> - -<DD> -see --find -<P> -<DT><B>-h [filename/wildcard]</B> - -<DD> -see --html -<P> -<DT><B>--harvest *.ss[tm]</B> - -<DD> -makes two lists of sisu output based on the sisu markup documents in a -directory: list of author and authors works (year and titles), and; list by -topic with titles and author. Makes use of header metadata fields (author, -title, date, topic_register). Can be used with maintenance (-M) and remote -placement (-R) flags. -<P> -<DT><B>--help [topic]</B> - -<DD> -provides help on the selected topic, where topics (keywords) include: list, -(com)mands, short(cuts), (mod)ifiers, (env)ironment, markup, syntax, headers, -headings, endnotes, tables, example, customise, skin, (dir)ectories, path, -(lang)uage, db, install, setup, (conf)igure, convert, termsheet, search, sql, -features, license. -<P> -<DT><B>--html [filename/wildcard]</B> - -<DD> -produces html output, segmented text with table of contents (toc.html and -index.html) and the document in a single file (scroll.html). Alias -h -<P> -<DT><B>-I [filename/wildcard]</B> - -<DD> -see --texinfo -<P> -<DT><B>-i [filename/wildcard]</B> - -<DD> -see --manpage -<P> -<DT><B>--inc-*</B> - -<DD> -include output feature, overrides configuration settings, (usually the default -if none set), has precedence over --exc-* (exclude output feature). Some -detail provided under --exc-*, see --exc-* -<P> -<DT><B>-j [filename/wildcard]</B> - -<DD> -copies images associated with a file for use by html, xhtml & xml outputs +<p> </dd> + +<dt><b>-e [filename/wildcard]</b> </dt> +<dd>see --epub +<p> </dd> + +<dt><b>--epub +[filename/wildcard]</b> </dt> +<dd>produces an epub document, [sisu version >=2 ] (filename.epub). + +<p>Alias -e +<p> </dd> + +<dt><b>--exc-*</b> </dt> +<dd>exclude output feature, overrides configuration settings +--exc- <i>ocn,</i> (exclude <i>object</i> citation numbering, (switches off <i>object</i> citation +numbering ) , affects html (seg, scroll), epub, xhtml, xml, pdf) ; --exc-toc, +(exclude table of contents, affects html (scroll), epub, pdf) ; --exc-links-to-manifest, +--exc-manifest-links, (exclude links to manifest, affects html (seg, scroll)); +--exc-search-form, (exclude search form, affects html (seg, scroll), manifest); +--exc-minitoc, (exclude mini table of contents, affects html (seg), concordance, +manifest); --exc-manifest-minitoc, (exclude mini table of contents, affects +manifest); --exc-html-minitoc, (exclude mini table of contents, affects html +(seg), concordance); --exc-html-navigation, (exclude navigation, affects html +(seg)); --exc-html-navigation-bar, (exclude navigation bar, affects html (seg)); +--exc-html-search-form, (exclude search form, affects html (seg, scroll)); --exc-html-right-pane, +(exclude right pane/column, affects html (seg, scroll)); --exc-html-top-band, +(exclude top band, affects html (seg, scroll), concordance (minitoc forced +on to provide seg navigation)); --exc-segsubtoc (exclude sub table of contents, +affects html (seg), epub) ; see also --inc-* +<p> </dd> + +<dt><b>-F [--webserv=webrick]</b> </dt> +<dd>see --sample-search-form + +<p> </dd> + +<dt><b>-f [optional string part of filename]</b> </dt> +<dd>see --find +<p> </dd> + +<dt><b>--find [optional string part + of filename]</b> </dt> +<dd>without match string, glob all .sst .ssm files in directory +(including language subdirectories). With match string, find files that +match given string in directory (including language subdirectories). Alias +-f, --glob, -G +<p> </dd> + +<dt><b>-G [optional string part of filename]</b> </dt> +<dd>see --find +<p> </dd> + +<dt><b>-g [filename/wildcard]</b> +</dt> +<dd> +<p>see --git +<p> </dd> + +<dt><b>--git [filename/wildcard]</b> </dt> +<dd>produces or updates markup source file +structure in a git repo (experimental and subject to change). Alias -g +<p> </dd> + +<dt><b>--glob +[optional string part of filename]</b> </dt> +<dd>see --find +<p> </dd> + +<dt><b>-h [filename/wildcard]</b> </dt> +<dd>see + +<p>- +<p>- +<p>html +<p> </dd> + +<dt><b>--harvest *.ss[tm]</b> </dt> +<dd>makes two lists of sisu output based on the sisu +markup documents in a directory: list of author and authors works (year +and titles), and; list by topic with titles and author. Makes use of header +metadata fields (author, title, date, topic_register). Can be used with +maintenance (-M) and remote placement (-R) flags. +<p> </dd> + +<dt><b>--help [topic]</b> </dt> +<dd>provides help +on the selected topic, where topics (keywords) include: list, (com)mands, +short(cuts), (mod)ifiers, (env)ironment, markup, syntax, headers, headings, +endnotes, tables, example, customise, skin, (dir)ectories, path, (lang)uage, +db, install, setup, (conf)igure, convert, termsheet, search, sql, features, +license. +<p> </dd> + +<dt><b>--html [filename/wildcard]</b> </dt> +<dd>produces html output, segmented text +with table of contents (toc.html and index.html) and the document in a single +file (scroll.html). Alias -h +<p> </dd> + +<dt><b>-I [filename/wildcard]</b> </dt> +<dd>see --texinfo +<p> </dd> + +<dt><b>-i [filename/wildcard]</b> +</dt> +<dd> +<p>see --manpage +<p> </dd> + +<dt><b>--inc-*</b> </dt> +<dd>include output feature, overrides configuration settings, +(usually the default if none set), has precedence over --exc-* (exclude output +feature). Some detail provided under --exc-*, see --exc-* +<p> </dd> + +<dt><b>-j [filename/wildcard]</b> +</dt> +<dd>copies images associated with a file for use by html, xhtml & xml outputs (automatically invoked by --dump & redirect). -<P> -<DT><B>--keep-processing-files [filename/wildcard/url]</B> - -<DD> -see --maintenance -<P> -<DT><B>-L</B> - -<DD> -prints license information. -<P> -<DT><B>-M [filename/wildcard/url]</B> - -<DD> -see --maintenance -<P> -<DT><B>-m [filename/wildcard/url]</B> - -<DD> -see --dal (document abstraction level/layer) -<P> -<DT><B>--machine [filename/wildcard/url]</B> - -<DD> -see --dal (document abstraction level/layer) -<P> -<DT><B>--maintenance [filename/wildcard/url]</B> - -<DD> -maintenance mode, interim processing files are preserved and their locations -indicated. (also see -V). Aliases -M and --keep-processing-files. -<P> -<DT><B>--manpage [filename/wildcard]</B> - -<DD> -produces man page of file, not suitable for all outputs. Alias -i -<P> -<DT><B>-N [filename/wildcard/url]</B> - -<DD> -document digest or document content certificate ( DCC ) as md5 digest tree of -the document: the digest for the document, and digests for each object +<p> </dd> + +<dt><b>--keep-processing-files [filename/wildcard/url]</b> +</dt> +<dd> +<p>see --maintenance +<p> </dd> + +<dt><b>-L</b> </dt> +<dd>prints license information. +<p> </dd> + +<dt><b>-M [filename/wildcard/url]</b> +</dt> +<dd> +<p>see --maintenance +<p> </dd> + +<dt><b>-m [filename/wildcard/url]</b> </dt> +<dd>see --dal (document abstraction +level/layer) +<p> </dd> + +<dt><b>--machine [filename/wildcard/url]</b> </dt> +<dd>see --dal (document abstraction +level/layer) +<p> </dd> + +<dt><b>--maintenance [filename/wildcard/url]</b> </dt> +<dd>maintenance mode, interim +processing files are preserved and their locations indicated. (also see +-V). Aliases -M and --keep-processing-files. +<p> </dd> + +<dt><b>--manpage [filename/wildcard]</b> </dt> +<dd>produces +man page of file, not suitable for all outputs. Alias -i +<p> </dd> + +<dt><b>-N [filename/wildcard/url]</b> +</dt> +<dd>document digest or document content certificate ( DCC ) as md5 digest tree +of the document: the digest for the document, and digests for each object contained within the document (together with information on software versions that produced it) (digest.txt). -NV for verbose digest output to screen. -<P> -<DT><B>-n [filename/wildcard/url]</B> - -<DD> -skip the creation of intermediate processing files (document abstraction) if -they already exist, this skips the equivalent of -m which is otherwise assumed -by most processing flags. -<P> -<DT><B>--no-*</B> - -<DD> -see --exc-* -<P> -<DT><B>-o [filename/wildcard/url]</B> - -<DD> -see --odt -<P> -<DT><B>--odf [filename/wildcard/url]</B> - -<DD> -see --odt -<P> -<DT><B>--odt [filename/wildcard/url]</B> - -<DD> -output basic document in opendocument file format (opendocument.odt). Alias -o -<P> -<DT><B>--output-by-*</B> - -<DD> -select output directory structure from 3 alternatives: ---output-by-language, (language directory (based on language code) with -filetype (html, epub, pdf etc.) subdirectories); --output-by-filetype, -(filetype directories with language code as part of filename); ---output-by-filename, (filename directories with language code as part of -filename). This is configurable. Alias --by-* -<P> -<DT><B>-P [language_directory/filename language_directory]</B> - -<DD> -see --po4a -<P> -<DT><B>-p [filename/wildcard]</B> - -<DD> -see --pdf -<P> -<DT><B>--pdf [filename/wildcard]</B> - -<DD> -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 - -<P> -<DT><B>--pg [instruction] [filename]</B> - -<DD> -database postgresql ( --pgsql may be used instead) possible instructions, -include: --createdb; --create; --dropall; --import [filename]; ---update [filename]; --remove [filename]; see database section below. Alias --D -<P> -<DT><B>--po [language_directory/filename language_directory]</B> - -<DD> -see --po4a -<P> -<DT><B>--po4a [language_directory/filename language_directory]</B> - -<DD> -produces .pot and po files for the file in the languages specified by the -language directory. -<B>SiSU</B> - -markup is placed in subdirectories named with the language code, e.g. en/ fr/ -es/. The sisu config file must set the output directory structure to -multilingual. v3, experimental -<P> -<DT><B>-Q [filename/wildcard]</B> - -<DD> -see --qrcode -<P> -<DT><B>-q [filename/wildcard]</B> - -<DD> -see --quiet -<P> -<DT><B>--qrcode [filename/wildcard]</B> - -<DD> -generate QR code image of metadata (used in manifest). v3 only. -<P> -<DT><B>--quiet [filename/wildcard]</B> - -<DD> -quiet less output to screen. -<P> -<DT><B>-R [filename/wildcard]</B> - -<DD> -see --rsync -<P> -<DT><B>-r [filename/wildcard]</B> - -<DD> -see --scp -<P> -<DT><B>--redirect[=directory_path] [filename/wildcard]</B> - -<DD> -places output in subdirectory under specified directory, subdirectory uses the -filename (without the suffix). If no output directory is specified places the -subdirectory under the current directory (pwd). Compare --dump -<P> -<DT><B>--rsync [filename/wildcard]</B> - -<DD> -copies sisu output files to remote host using rsync. This requires that -sisurc.yml has been provided with information on hostname and username, and -that you have your "keys" and ssh agent in place. Note the behavior of rsync -different if -R is used with other flags from if used alone. Alone the rsync ---delete parameter is sent, useful for cleaning the remote directory (when --R is used together with other flags, it is not). Also see --scp. Alias -R -<P> -<DT><B>-S</B> - -<DD> -see --sisupod -<P> -<DT><B>-S [filename/wildcard]</B> - -<DD> -see --sisupod -<P> -<DT><B>-s [filename/wildcard]</B> - -<DD> -see --source -<P> -<DT><B>--sample-search-form [--webserv=webrick]</B> - -<DD> -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 +<p> </dd> + +<dt><b>-n +[filename/wildcard/url]</b> </dt> +<dd>skip the creation of intermediate processing files +(document abstraction) if they already exist, this skips the equivalent +of -m which is otherwise assumed by most processing flags. +<p> </dd> + +<dt><b>--no-*</b> </dt> +<dd>see --exc-* + +<p> </dd> + +<dt><b>-o [filename/wildcard/url]</b> </dt> +<dd>see --odt +<p> </dd> + +<dt><b>--odf [filename/wildcard/url]</b> </dt> +<dd>see --odt + +<p> </dd> + +<dt><b>--odt [filename/wildcard/url]</b> </dt> +<dd>output basic document in opendocument file +format (opendocument.odt). Alias -o +<p> </dd> + +<dt><b>--output-by-*</b> </dt> +<dd>select output directory structure +from 3 alternatives: --output-by-language, (language directory (based on language +code) with filetype (html, epub, pdf etc.) subdirectories); --output-by-filetype, +(filetype directories with language code as part of filename); --output-by-filename, +(filename directories with language code as part of filename). This is configurable. +Alias --by-* +<p> </dd> + +<dt><b>-P [language_directory/filename language_directory]</b> </dt> +<dd>see --po4a + +<p> </dd> + +<dt><b>-p [filename/wildcard]</b> </dt> +<dd>see --pdf +<p> </dd> + +<dt><b>--pdf [filename/wildcard]</b> </dt> +<dd>produces <i>LaTeX</i> +pdf (portrait.pdf & landscape.pdf). Default paper size is set in config file, +or document header, or provided with additional command line parameter, +e.g. --papersize-a4 preset sizes include: ’A4’, U.S. ’letter’ and ’legal’ and book sizes +’A5’ and ’B5’ (system defaults to A4). Alias -p +<p> </dd> + +<dt><b>--pg [instruction] [filename]</b> +</dt> +<dd>database <i>PostgreSQL</i> ( --pgsql may be used instead) possible instructions, +include: --createdb; --create; --dropall; --import [filename]; --update [filename]; +--remove [filename]; see database section below. Alias -D +<p> </dd> + +<dt><b>--po [language_directory/filename + language_directory]</b> </dt> +<dd>see --po4a +<p> </dd> + +<dt><b>--po4a [language_directory/filename language_directory]</b> +</dt> +<dd>produces .pot and po files for the file in the languages specified by the +language directory. <b>SiSU</b> markup is placed in subdirectories named with the +language code, e.g. en/ fr/ es/. The sisu config file must set the output +directory structure to multilingual. v3, experimental +<p> </dd> + +<dt><b>-Q [filename/wildcard]</b> +</dt> +<dd> +<p>see --qrcode +<p> </dd> + +<dt><b>-q [filename/wildcard]</b> </dt> +<dd>see --quiet +<p> </dd> + +<dt><b>--qrcode [filename/wildcard]</b> +</dt> +<dd>generate QR code image of metadata (used in manifest). v3 only. +<p> </dd> + +<dt><b>--quiet [filename/wildcard]</b> +</dt> +<dd>quiet less output to screen. +<p> </dd> + +<dt><b>-R [filename/wildcard]</b> </dt> +<dd>see --rsync +<p> </dd> + +<dt><b>-r [filename/wildcard]</b> +</dt> +<dd> +<p>see --scp +<p> </dd> + +<dt><b>--redirect[=directory_path] [filename/wildcard]</b> </dt> +<dd>places output in +subdirectory under specified directory, subdirectory uses the filename +(without the suffix). If no output directory is specified places the subdirectory +under the current directory (pwd). Compare --dump +<p> </dd> + +<dt><b>--rsync [filename/wildcard]</b> +</dt> +<dd>copies sisu output files to remote host using rsync. This requires that +sisurc.yml has been provided with information on hostname and username, +and that you have your "keys" and ssh agent in place. Note the behavior +of rsync different if -R is used with other flags from if used alone. Alone +the rsync --delete parameter is sent, useful for cleaning the remote directory +(when -R is used together with other flags, it is not). Also see --scp. Alias + +<p>- +<p>R +<p> </dd> + +<dt><b>-S</b> </dt> +<dd>see --sisupod +<p> </dd> + +<dt><b>-S [filename/wildcard]</b> </dt> +<dd>see --sisupod +<p> </dd> + +<dt><b>-s [filename/wildcard]</b> +</dt> +<dd> +<p>see --source +<p> </dd> + +<dt><b>--sample-search-form [--webserv=webrick]</b> </dt> +<dd>generate examples of (naive) +cgi search form for <i>SQLite</i> and PgSQL depends on your already having used +sisu to populate an <i>SQLite</i> and/or PgSQL database, (the <i>SQLite</i> version scans +the output directories for existing sisu_sqlite databases, so it is first +necessary to create them, before generating the search form) see -d -D and +the database section below. If the optional parameter --webserv=webrick is +passed, the cgi examples created will be set up to use the default port +set for use by the webrick server, (otherwise the port is left blank and +the system setting used, usually 80). The samples are dumped in the present +work directory which must be writable, (with screen instructions given that they be copied to the cgi-bin directory). Alias -F -<P> -<DT><B>--scp [filename/wildcard]</B> - -<DD> -copies sisu output files to remote host using scp. This requires that -sisurc.yml has been provided with information on hostname and username, and -that you have your "keys" and ssh agent in place. Also see --rsync. Alias -r -<P> -<DT><B>--sqlite --[instruction] [filename]</B> - -<DD> -database type set to sqlite, this produces one of two possible databases, -without additional database related instructions it produces a discreet sqlite -file for the document processed; with additional instructions it produces a -common sqlite database of all processed documents that (come from the same -document preparation directory and as a result) share the same output directory -base path (possible instructions include: --createdb; --create; ---dropall; --import [filename]; --update [filename]; --remove +<p> </dd> + +<dt><b>--scp [filename/wildcard]</b> +</dt> +<dd>copies sisu output files to remote host using scp. This requires that sisurc.yml +has been provided with information on hostname and username, and that you +have your "keys" and ssh agent in place. Also see --rsync. Alias -r +<p> </dd> + +<dt><b>--sqlite +--[instruction] [filename]</b> </dt> +<dd>database type set to <i>SQLite,</i> this produces one +of two possible databases, without additional database related instructions +it produces a discreet <i>SQLite</i> file for the document processed; with additional +instructions it produces a common <i>SQLite</i> database of all processed documents +that (come from the same document preparation directory and as a result) +share the same output directory base path (possible instructions include: +--createdb; --create; --dropall; --import [filename]; --update [filename]; --remove [filename]); see database section below. Alias -d -<P> -<DT><B>--sisupod</B> - -<DD> -produces a sisupod a zipped sisu directory of markup files including sisu -markup source files and the directories local configuration file, images and -skins. Note: this only includes the configuration files or skins contained in -<BR> ./_sisu not those in ~/.sisu -S [filename/wildcard] option. Note: (this -option is tested only with zsh). Alias -S -<P> -<DT><B>--sisupod [filename/wildcard]</B> - -<DD> -produces a zipped file of the prepared document specified along with associated -images, by default named sisupod.zip they may alternatively be named with the -filename extension .ssp This provides a quick way of gathering the relevant +<p> </dd> + +<dt><b>--sisupod</b> </dt> +<dd>produces a sisupod +a zipped sisu directory of markup files including sisu markup source files +and the directories local configuration file, images and skins. Note: this +only includes the configuration files or skins contained in ./_sisu not +those in ~/.sisu -S [filename/wildcard] option. Note: (this<br> + option is tested only with zsh). Alias -S +<p> </dd> + +<dt><b>--sisupod [filename/wildcard]</b> </dt> +<dd>produces +a zipped file of the prepared document specified along with associated +images, by default named sisupod.zip they may alternatively be named with +the filename extension .ssp This provides a quick way of gathering the relevant parts of a sisu document which can then for example be emailed. A sisupod -includes sisu markup source file, (along with associated documents if a master -file, or available in multilingual versions), together with related images and -skin. -<B>SiSU</B> - -commands can be run directly against a sisupod contained in a local directory, -or provided as a url on a remote site. As there is a security issue with skins -provided by other users, they are not applied unless the flag --trust or ---trusted is added to the command instruction, it is recommended that file -that are not your own are treated as untrusted. The directory structure of the -unzipped file is understood by sisu, and sisu commands can be run within it. -Note: if you wish to send multiple files, it quickly becomes more space -efficient to zip the sisu markup directory, rather than the individual files -for sending). See the -S option without [filename/wildcard]. Alias -S -<P> -<DT><B>--source [filename/wildcard]</B> - -<DD> -copies sisu markup file to output directory. Alias -s -<P> -<DT><B>-T [filename/wildcard (*.termsheet.rb)]</B> - -<DD> -standard form document builder, preprocessing feature -<P> -<DT><B>-t [filename/wildcard]</B> - -<DD> -see --txt -<P> -<DT><B>--texinfo [filename/wildcard]</B> - -<DD> -produces texinfo and info file, (view with pinfo). Alias -I -<P> -<DT><B>--txt [filename/wildcard]</B> - -<DD> -produces plaintext with Unix linefeeds and without markup, (object numbers are -omitted), has footnotes at end of each paragraph that contains them [ -A for equivalent dos (linefeed) output file] [see -e for endnotes]. (Options include: --endnotes for endnotes --footnotes for -footnotes at the end of each paragraph --unix for unix linefeed (default) ---msdos for msdos linefeed). Alias -t -<P> -<DT><B>-U [filename/wildcard]</B> - -<DD> -see --urls -<P> -<DT><B>-u [filename/wildcard]</B> - -<DD> -provides url mapping of output files for the flags requested for processing, -also see -U -<P> -<DT><B>--urls [filename/wildcard]</B> - -<DD> -prints url output list/map for the available processing flags options and -resulting files that could be requested, (can be used to get a list of -processing options in relation to a file, together with information on the -output that would be produced), -u provides url output mapping for those flags -requested for processing. The default assumes sisu_webrick is running and -provides webrick url mappings where appropriate, but these can be switched to -file system paths in sisurc.yml. Alias -U -<P> -<DT><B>-V</B> - -<DD> -on its own, provides -<B>SiSU</B> - -version and environment information (sisu --help env) -<P> -<DT><B>-V [filename/wildcard]</B> - -<DD> -even more verbose than the -v flag. -<P> -<DT><B>-v</B> - -<DD> -on its own, provides -<B>SiSU</B> - -version information -<P> -<DT><B>-v [filename/wildcard]</B> - -<DD> -see --verbose -<P> -<DT><B>--v2 [filename/wildcard]</B> - -<DD> -invokes the sisu v2 document parser/generator. This is the default and is -normally omitted. -<P> -<DT><B>--v3 [filename/wildcard]</B> - -<DD> -invokes the sisu v3 document parser/generator. Currently under development and -incomplete, v3 requires >= ruby1.9.2p180. You may run sisu3 instead. -<P> -<DT><B>--verbose [filename/wildcard]</B> - -<DD> -provides verbose output of what is being generated, where output is placed (and -error messages if any), as with -u flag provides a url mapping of files +includes sisu markup source file, (along with associated documents if a +master file, or available in multilingual versions), together with related +images and skin. <b>SiSU</b> commands can be run directly against a sisupod contained +in a local directory, or provided as a url on a remote site. As there is +a security issue with skins provided by other users, they are not applied +unless the flag --trust or --trusted is added to the command instruction, it +is recommended that file that are not your own are treated as untrusted. +The directory structure of the unzipped file is understood by sisu, and +sisu commands can be run within it. Note: if you wish to send multiple files, +it quickly becomes more space efficient to zip the sisu markup directory, +rather than the individual files for sending). See the -S option without +[filename/wildcard]. Alias -S +<p> </dd> + +<dt><b>--source [filename/wildcard]</b> </dt> +<dd>copies sisu markup +file to output directory. Alias -s +<p> </dd> + +<dt><b>-T [filename/wildcard (*.termsheet.rb)]</b> +</dt> +<dd>standard form document builder, preprocessing feature +<p> </dd> + +<dt><b>-t [filename/wildcard]</b> +</dt> +<dd> +<p>see --txt +<p> </dd> + +<dt><b>--texinfo [filename/wildcard]</b> </dt> +<dd>produces texinfo and info file, (view +with pinfo). Alias -I +<p> </dd> + +<dt><b>--txt [filename/wildcard]</b> </dt> +<dd>produces <i>plaintext</i> with Unix +linefeeds and without markup, (object numbers are omitted), has footnotes +at end of each paragraph that contains them [ -A for output file] [see -e + for endnotes]. (Options include: --endnotes for endnotes --footnotes for footnotes +at the end of each paragraph --unix for unix linefeed (default) --msdos for +msdos linefeed). Alias -t +<p> </dd> + +<dt><b>-U [filename/wildcard]</b> </dt> +<dd>see --urls +<p> </dd> + +<dt><b>-u [filename/wildcard]</b> +</dt> +<dd>provides url mapping of output files for the flags requested for processing, + +<p>also see -U +<p> </dd> + +<dt><b>--urls [filename/wildcard]</b> </dt> +<dd>prints url output list/map for the +available processing flags options and resulting files that could be requested, +(can be used to get a list of processing options in relation to a file, +together with information on the output that would be produced), -u provides +url output mapping for those flags requested for processing. The default +assumes sisu_webrick is running and provides webrick url mappings where +appropriate, but these can be switched to file system paths in sisurc.yml. + +<p>Alias -U +<p> </dd> + +<dt><b>-V</b> </dt> +<dd>on its own, provides <b>SiSU</b> version and environment information +(sisu --help env) +<p> </dd> + +<dt><b>-V [filename/wildcard]</b> </dt> +<dd>even more verbose than the -v flag. + +<p> </dd> + +<dt><b>-v</b> </dt> +<dd>on its own, provides <b>SiSU</b> version information +<p> </dd> + +<dt><b>-v [filename/wildcard]</b> +</dt> +<dd> +<p>see --verbose +<p> </dd> + +<dt><b>--v3 [filename/wildcard]</b> </dt> +<dd>invokes the sisu v3 document parser/generator. +You may run sisu3 instead. +<p> </dd> + +<dt><b>--v4 [filename/wildcard]</b> </dt> +<dd>invokes the sisu v4 document +parser/generator. This is the default and is normally omitted. +<p> </dd> + +<dt><b>--verbose [filename/wildcard]</b> +</dt> +<dd>provides verbose output of what is being generated, where output is placed +(and error messages if any), as with -u flag provides a url mapping of files created for each of the processing flag requests. Alias -v -<P> -<DT><B>-W</B> - -<DD> -see --webrick -<P> -<DT><B>-w [filename/wildcard]</B> - -<DD> -see --concordance -<P> -<DT><B>--webrick</B> - -<DD> -starts ruby's webrick webserver points at sisu output directories, the default -port is set to 8081 and can be changed in the resource configuration files. -[tip: the webrick server requires link suffixes, so html output should be created using the -h option rather than -H ; also, note -F webrick ]. Alias -W -<P> -<DT><B>--wordmap [filename/wildcard]</B> - -<DD> -see --concordance -<P> -<DT><B>--xhtml [filename/wildcard]</B> - -<DD> -produces xhtml/XML output for browser viewing (sax parsing). Alias -b -<P> -<DT><B>--xml-dom [filename/wildcard]</B> - -<DD> -produces XML output with deep document structure, in the nature of dom. Alias --X -<P> -<DT><B>--xml-sax [filename/wildcard]</B> - -<DD> -produces XML output shallow structure (sax parsing). Alias -x -<P> -<DT><B>-X [filename/wildcard]</B> - -<DD> -see --xml-dom -<P> -<DT><B>-x [filename/wildcard]</B> - -<DD> -see --xml-sax -<P> -<DT><B>-Y [filename/wildcard]</B> - -<DD> -produces a short sitemap entry for the document, based on html output and the -sisu_manifest. --sitemaps generates/updates the sitemap index of existing -sitemaps. (Experimental, [g,y,m announcement this week]) -<P> -<DT><B>-y [filename/wildcard]</B> - -<DD> -produces an html summary of output generated (hyperlinked to content) and -document specific metadata (sisu_manifest.html). This step is assumed for most -processing flags. -<P> -<DT><B>-Z [filename/wildcard]</B> - -<DD> -see --zap -<P> -<DT><B>--zap [filename/wildcard]</B> - -<DD> -Zap, if used with other processing flags deletes output files of the type about -to be processed, prior to processing. If -Z is used as the lone processing -related flag (or in conjunction with a combination of -[mMvVq]), will remove -the related document output directory. Alias -Z -<P> -</DL> -<A NAME="lbAJ"> </A> -<H2>3. COMMAND LINE MODIFIERS</H2> - -<BR> - -<P> -<DL COMPACT> -<DT><B>--no-ocn</B> - -<DD> -[with --html --pdf or --epub] switches off object citation -numbering. Produce output without identifying numbers in margins of html or -LaTeX/pdf output. -<P> -<DT><B>--no-annotate</B> - -<DD> -strips output text of editor endnotes[^*1] denoted by asterisk or dagger/plus -sign -<P> -<DT><B>--no-asterisk</B> - -<DD> -strips output text of editor endnotes[^*2] denoted by asterisk sign -<P> -<DT><B>--no-dagger</B> - -<DD> -strips output text of editor endnotes[^+1] denoted by dagger/plus sign -<P> -</DL> -<A NAME="lbAK"> </A> -<H2>4. DATABASE COMMANDS</H2> - -<BR> - -<P> -<BR> - -dbi - database interface -<P> -<BR> - --D or --pgsql set for postgresql -d or --sqlite default set for sqlite --d is modifiable with --db=[database type (pgsql or sqlite)] -<P> -<DL COMPACT> -<DT><B>--pg -v --createall</B> - -<DD> -initial step, creates required relations (tables, indexes) in existing -postgresql database (a database should be created manually and given the same -name as working directory, as requested) (rb.dbi) [ -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. -<P> -<DT><B>--pg -v --import</B> - -<DD> -[filename/wildcard] imports data specified to postgresql db (rb.dbi) [ -dv --import sqlite equivalent] -<P> -<DT><B>--pg -v --update</B> - -<DD> -[filename/wildcard] updates/imports specified data to postgresql db (rb.dbi) [ - -dv --update sqlite equivalent] -<P> -<DT><B>--pg --remove</B> - -<DD> -[filename/wildcard] removes specified data to postgresql db (rb.dbi) [ -d --remove sqlite equivalent] -<P> -<DT><B>--pg --dropall</B> - -<DD> -kills data" and drops (postgresql or sqlite) db, tables & indexes [ -d --dropall sqlite equivalent] -<P> -<BR> - +<p> </dd> + +<dt><b>-W</b> </dt> +<dd>see --webrick + +<p> </dd> + +<dt><b>-w [filename/wildcard]</b> </dt> +<dd>see --concordance +<p> </dd> + +<dt><b>--webrick</b> </dt> +<dd>starts ruby’ s webrick webserver +points at sisu output directories, the default port is set to 8081 and +can be changed in the resource configuration files. [tip: the webrick server + requires link suffixes, so html output should be created using the -h option + rather than also, note -F webrick ]. Alias -W +<p> </dd> + +<dt><b>--wordmap [filename/wildcard]</b> +</dt> +<dd> +<p>see --concordance +<p> </dd> + +<dt><b>--xhtml [filename/wildcard]</b> </dt> +<dd>produces xhtml/ <i>XML</i> output for +browser viewing (sax parsing). Alias -b +<p> </dd> + +<dt><b>--xml-dom [filename/wildcard]</b> </dt> +<dd>produces +<i>XML</i> output with deep document structure, in the nature of dom. Alias -X +<p> +</dd> + +<dt><b>--xml-sax [filename/wildcard]</b> </dt> +<dd>produces <i>XML</i> output shallow structure (sax parsing). + +<p>Alias -x +<p> </dd> + +<dt><b>-X [filename/wildcard]</b> </dt> +<dd>see --xml-dom +<p> </dd> + +<dt><b>-x [filename/wildcard]</b> </dt> +<dd>see --xml-sax + +<p> </dd> + +<dt><b>-Y [filename/wildcard]</b> </dt> +<dd>produces a short sitemap entry for the document, +based on html output and the sisu_manifest. --sitemaps generates/updates the +sitemap index of existing sitemaps. (Experimental, [g,y,m announcement this + week]) +<p> </dd> + +<dt><b>-y [filename/wildcard]</b> </dt> +<dd>produces an html summary of output generated +(hyperlinked to content) and document specific metadata (sisu_manifest.html). +This step is assumed for most processing flags. +<p> </dd> + +<dt><b>-Z [filename/wildcard]</b> </dt> +<dd>see + +<p>- +<p>- +<p>zap +<p> </dd> + +<dt><b>--zap [filename/wildcard]</b> </dt> +<dd>Zap, if used with other processing flags deletes +output files of the type about to be processed, prior to processing. If +-Z is used as the lone processing related flag (or in conjunction with a +combination of -[mMvVq]), will remove the related document output directory. + +<p>Alias -Z +<p> </dd> +</dl> + +<h2><a name='sect8' href='#toc8'>Command Line Modifiers</a></h2> +<br> + +<p> +<dl> + +<dt><b>--no-</b> </dt> +<dd><i>ocn</i> [with --html --pdf or --epub] switches off <i>object</i> citation numbering. +Produce output without identifying numbers in margins of html or <i>LaTeX</i> +/pdf output. +<p> </dd> + +<dt><b>--no-annotate</b> </dt> +<dd>strips output text of editor endnotes[^*1] denoted + +<p>by asterisk or dagger/plus sign +<p> </dd> + +<dt><b>--no-asterisk</b> </dt> +<dd>strips output text of editor +endnotes[^*2] denoted by asterisk sign +<p> </dd> + +<dt><b>--no-dagger</b> </dt> +<dd>strips output text of editor +endnotes[^+1] denoted by dagger/plus sign +<p> </dd> +</dl> + +<h2><a name='sect9' href='#toc9'>Database Commands</a></h2> +<br> + +<p> <br> +<b>dbi - database interface</b> +<p> <br> +<b>-D or --pgsql</b> set for <i>PostgreSQL</i> <b>-d or --sqlite</b> default set for <i>SQLite</i> -d is modifiable +with --db=[database type (PgSQL or .I SQLite ) ] +<p> +<dl> + +<dt><b>--pg -v --createall</b> </dt> +<dd>initial step, +creates required relations (tables, indexes) in existing <i>PostgreSQL</i> database +(a database should be created manually and given the same name as working +directory, as requested) (rb.dbi) [ -dv --createall .I SQLite equivalent] it +may be necessary to run sisu -Dv --createdb initially NOTE: at the present +time for <i>PostgreSQL</i> it may be necessary to manually create the database. +The command would be working directory name (without path)]. Please use +only alphanumerics and underscores. +<p> </dd> + +<dt><b>--pg -v --import</b> </dt> +<dd>[filename/wildcard] imports +data specified to <i>PostgreSQL</i> db (rb.dbi) [ -dv --import .I SQLite equivalent] + +<p> </dd> + +<dt><b>--pg -v --update</b> </dt> +<dd>[filename/wildcard] updates/imports specified data to <i>PostgreSQL</i> +db (rb.dbi) [ -dv --update .I SQLite equivalent] +<p> </dd> + +<dt><b>--pg --remove</b> </dt> +<dd>[filename/wildcard] +removes specified data to <i>PostgreSQL</i> db (rb.dbi) [ -d --remove .I SQLite equivalent] + +<p> </dd> + +<dt><b>--pg --dropall</b> </dt> +<dd>kills data" and drops ( <i>PostgreSQL</i> or <i>SQLite</i> ) db, tables & +indexes [ -d --dropall .I SQLite equivalent] +<p> <br> The -v is for verbose output. -<P> -</DL> -<A NAME="lbAL"> </A> -<H2>5. SHORTCUTS, SHORTHAND FOR MULTIPLE FLAGS</H2> - -<BR> - -<P> -<DL COMPACT> -<DT><B>--update [filename/wildcard]</B> - -<DD> -Checks existing file output and runs the flags required to update this output. -This means that if only html and pdf output was requested on previous runs, -only the -hp files will be applied, and only these will be generated this -time, together with the summary. This can be very convenient, if you offer -different outputs of different files, and just want to do the same again. -<P> -<DT><B>-0 to -5 [filename or wildcard]</B> - -<DD> -Default shorthand mappings (for v3, note that the defaults can be -changed/configured in the sisurc.yml file): -<P> -<DT><B>-0</B> - -<DD> --NQhewpotbxXyYv [this is the default action run when no options are give, i.e. on 'sisu [filename]'] -<P> -<DT><B>-1</B> - -<DD> --Qhewpoty -<P> -<DT><B>-2</B> - -<DD> --NQhewpotbxXy -<P> -<DT><B>-3</B> - -<DD> --NQhewpotbxXyY -<P> -<DT><B>-4</B> - -<DD> --NQhewpotbxXDyY --update -<P> -<DT><B>-5</B> - -<DD> --NQhewpotbxXDyYv --update -<P> -<BR> - -add -v for verbose mode and -c to toggle color state, e.g. sisu -2vc -[filename or wildcard] -<P> -<BR> - -consider -u for appended url info or -v for verbose output -<P> -</DL> -<A NAME="lbAM"> </A> -<H2>5.1 COMMAND LINE WITH FLAGS - BATCH PROCESSING</H2> - -<P> -<BR> - -In the data directory run sisu -mh filename or wildcard eg. "sisu -h -cisg.sst" or "sisu -h *.{sst,ssm}" to produce html version of all documents. -<P> -<BR> - -Running sisu (alone without any flags, filenames or wildcards) brings up the -interactive help, as does any sisu command that is not recognised. Enter to -escape. -<P> -<A NAME="lbAN"> </A> -<H2>6. HELP</H2> - -<BR> - -<P> -<A NAME="lbAO"> </A> -<H2>6.1 SISU MANUAL</H2> - -<P> -<BR> - +<p> </dd> +</dl> + +<h2><a name='sect10' href='#toc10'>Shortcuts, Shorthand for Multiple Flags</a></h2> +<br> + +<p> +<dl> + +<dt><b>--update [filename/wildcard]</b> </dt> +<dd>Checks existing file output and runs the flags +required to update this output. This means that if only html and pdf output +was requested on previous runs, only the -hp files will be applied, and +only these will be generated this time, together with the summary. This +can be very convenient, if you offer different outputs of different files, +and just want to do the same again. +<p> </dd> + +<dt><b>-0 to -5 [filename or wildcard]</b> </dt> +<dd>Default +shorthand mappings (for v3, note that the defaults can be changed/configured +in the sisurc.yml file): +<p> </dd> + +<dt><b>-0</b> </dt> +<dd>-NQhewpotbxXyYv [this is the default action run + when no options are give, i.e. on ’sisu [filename]’] +<p> </dd> + +<dt><b>-1</b> </dt> +<dd>-Qhewpoty +<p> </dd> + +<dt><b>-2</b> </dt> +<dd>-NQhewpotbxXy + +<p> </dd> + +<dt><b>-3</b> </dt> +<dd>-NQhewpotbxXyY +<p> </dd> + +<dt><b>-4</b> </dt> +<dd>-NQhewpotbxXDyY --update +<p> </dd> + +<dt><b>-5</b> </dt> +<dd>-NQhewpotbxXDyYv --update +<p> <br> +add -v for verbose mode and -c to toggle color state, e.g. sisu -2vc [filename + or wildcard] +<p> <br> + +<p>consider -u for appended url info or -v for verbose output +<p> </dd> +</dl> + +<h2><a name='sect11' href='#toc11'>Command Line +with Flags - Batch Processing</a></h2> + +<p> <br> +In the data directory run sisu -mh filename or wildcard eg. "sisu -h cisg.sst" +or "sisu -h *.{sst,ssm}" to produce html version of all documents. +<p> <br> +Running sisu (alone without any flags, filenames or wildcards) brings up +the interactive help, as does any sisu command that is not recognised. Enter +to escape. +<p> +<h2><a name='sect12' href='#toc12'>Help</a></h2> +<br> + +<p> +<h2><a name='sect13' href='#toc13'>Sisu Manual</a></h2> + +<p> <br> The most up to date information on sisu should be contained in the sisu_manual, available at: -<P> -<BR> - -<BR> <<A HREF="http://sisudoc.org/sisu/sisu_manual/">http://sisudoc.org/sisu/sisu_manual/</A>> -<P> -<BR> +<p> <br> + <<a href='http://sisudoc.org/sisu/sisu_manual/'>http://sisudoc.org/sisu/sisu_manual/</a> +><br> -The manual can be generated from source, found respectively, either within the -<B>SiSU</B> +<p> <br> +The manual can be generated from source, found respectively, either within +the <b>SiSU</b> tarball or installed locally at: +<p> <br> + ./data/doc/sisu/markup-samples/sisu_manual<br> -tarball or installed locally at: -<P> -<BR> - -<BR> ./data/doc/sisu/markup-samples/sisu_manual -<P> -<BR> - -<BR> /usr/share/doc/sisu/markup-samples/sisu_manual -<P> -<BR> +<p> <br> + /usr/share/doc/sisu/markup-samples/sisu_manual<br> +<p> <br> move to the respective directory and type e.g.: -<P> -<BR> - -<BR> sisu sisu_manual.ssm -<P> -<A NAME="lbAP"> </A> -<H2>6.2 SISU MAN PAGES</H2> - -<P> -<BR> - -If -<B>SiSU</B> - -is installed on your system usual man commands should be available, try: -<P> -<BR> - -<BR> man sisu -<P> -<BR> - -Most -<B>SiSU</B> - -man pages are generated directly from sisu documents that are used to prepare -the sisu manual, the sources files for which are located within the -<B>SiSU</B> - -tarball at: -<P> -<BR> - -<BR> ./data/doc/sisu/markup-samples/sisu_manual -<P> -<BR> - +<p> <br> + sisu sisu_manual.ssm<br> + +<p> +<h2><a name='sect14' href='#toc14'>Sisu Man Pages</a></h2> + +<p> <br> +If <b>SiSU</b> is installed on your system usual man commands should be available, +try: +<p> <br> + man sisu<br> + +<p> <br> +Most <b>SiSU</b> man pages are generated directly from sisu documents that are +used to prepare the sisu manual, the sources files for which are located +within the <b>SiSU</b> tarball at: +<p> <br> + ./data/doc/sisu/markup-samples/sisu_manual<br> + +<p> <br> Once installed, directory equivalent to: -<P> -<BR> - -<BR> /usr/share/doc/sisu/markup-samples/sisu_manual -<P> -<BR> +<p> <br> + /usr/share/doc/sisu/markup-samples/sisu_manual<br> +<p> <br> Available man pages are converted back to html using man2html: -<P> -<BR> +<p> <br> + /usr/share/doc/sisu/html/<br> -<BR> /usr/share/doc/sisu/html/ -<P> -<BR> - -<BR> ./data/doc/sisu/html -<P> -<BR> +<p> <br> + ./data/doc/sisu/html<br> +<p> <br> An online version of the sisu man page is available here: -<P> -<BR> - -* various sisu man pages <<A HREF="http://www.jus.uio.no/sisu/man/">http://www.jus.uio.no/sisu/man/</A>> [^8] -<P> -<BR> - -* sisu.1 <<A HREF="http://www.jus.uio.no/sisu/man/sisu.1.html">http://www.jus.uio.no/sisu/man/sisu.1.html</A>> [^9] -<P> -<A NAME="lbAQ"> </A> -<H2>6.3 SISU BUILT-IN INTERACTIVE HELP</H2> - -<P> -<BR> - +<p> <br> +* various sisu man pages <<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a> +> [^9] +<p> <br> +* sisu.1 <<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a> +> [^10] +<p> +<h2><a name='sect15' href='#toc15'>Sisu Built-in Interactive +Help</a></h2> + +<p> <br> This is particularly useful for getting the current sisu setup/environment information: -<P> -<BR> - -<BR> sisu --help -<P> -<BR> +<p> <br> + sisu --help<br> -<BR> sisu --help [subject] -<P> -<BR> +<p> <br> + sisu --help [subject]<br> -<BR> sisu --help commands -<P> -<BR> +<p> <br> + sisu --help commands<br> -<BR> sisu --help markup -<P> -<BR> +<p> <br> + sisu --help markup<br> -<BR> sisu --help env [for feedback on the way your system is setup with regard to sisu] -<P> -<BR> +<p> <br> + sisu --help env [for feedback on the way your system is <br> + setup with regard to sisu ]<br> -<BR> sisu -V [environment information, same as above command] -<P> -<BR> +<p> <br> + sisu -V [environment information, same as above command]<br> -<BR> sisu (on its own provides version and some help information) -<P> -<BR> - -Apart from real-time information on your current configuration the -<B>SiSU</B> +<p> <br> + sisu (on its own provides version and some help information)<br> +<p> <br> +Apart from real-time information on your current configuration the <b>SiSU</b> manual and man pages are likely to contain more up-to-date information than the sisu interactive help (for example on commands and markup). -<P> -<BR> - -NOTE: Running the command sisu (alone without any flags, filenames or -wildcards) brings up the interactive help, as does any sisu command that is not -recognised. Enter to escape. -<P> -<A NAME="lbAR"> </A> -<H2>7. INTRODUCTION TO SISU MARKUP[^10]</H2> - -<BR> - -<P> -<A NAME="lbAS"> </A> -<H2>7.1 SUMMARY</H2> - -<P> -<BR> - -<B>SiSU</B> - -source documents are plaintext (UTF-8)[^11] files -<P> -<BR> - +<p> <br> +NOTE: Running the command sisu (alone without any flags, filenames or wildcards) +brings up the interactive help, as does any sisu command that is not recognised. +Enter to escape. +<p> +<h2><a name='sect16' href='#toc16'>Introduction to Sisu Markup[^11]</a></h2> +<br> + +<p> +<h2><a name='sect17' href='#toc17'>Summary</a></h2> + +<p> <br> +<b>SiSU</b> source documents are <i>plaintext</i> ( <i>UTF-8</i> )[^12] files +<p> <br> All paragraphs are separated by an empty line. -<P> -<BR> - +<p> <br> Markup is comprised of: -<P> -<BR> - +<p> <br> * at the top of a document, the document header made up of semantic meta-data -about the document and if desired additional processing instructions (such an -instruction to automatically number headings from a particular level down) -<P> -<BR> - -* followed by the prepared substantive text of which the most important single -characteristic is the markup of different heading levels, which define the -primary outline of the document structure. Markup of substantive text includes: -<P> -<BR> - -<BR> * heading levels defines document structure -<P> -<BR> - -<BR> * text basic attributes, italics, bold etc. -<P> -<BR> - -<BR> * grouped text (objects), which are to be treated differently, such as code -<BR> blocks or poems. -<P> -<BR> - -<BR> * footnotes/endnotes -<P> -<BR> - -<BR> * linked text and images -<P> -<BR> - -<BR> * paragraph actions, such as indent, bulleted, numbered-lists, etc. -<P> -<BR> - +about the document and if desired additional processing instructions (such +an instruction to automatically number headings from a particular level +down) +<p> <br> +* followed by the prepared substantive text of which the most important +single characteristic is the markup of different heading levels, which +define the primary outline of the document structure. Markup of substantive +text includes: +<p> <br> + * heading levels defines document structure<br> + +<p> <br> + * text basic attributes, italics, bold etc.<br> + +<p> <br> + * grouped text (objects), which are to be treated differently, such as +code<br> + blocks or poems.<br> + +<p> <br> + * footnotes/endnotes<br> + +<p> <br> + * linked text and images<br> + +<p> <br> + * paragraph actions, such as indent, bulleted, numbered-lists, etc.<br> + +<p> <br> Some interactive help on markup is available, by typing sisu and selecting -markup or sisu --help markup -<P> -<BR> +<p>markup or sisu --help markup +<p> <br> To check the markup in a file: -<P> -<BR> - -<BR> sisu --identify [filename].sst -<P> -<BR> +<p> <br> + sisu --identify [filename].sst<br> -For brief descriptive summary of markup history -<P> -<BR> +<p> <br> -<BR> sisu --query-history -<P> -<BR> +<p>For brief descriptive summary of markup history +<p> <br> + sisu --query-history<br> +<p> <br> or if for a particular version: -<P> -<BR> - -<BR> sisu --query-0.38 -<P> -<A NAME="lbAT"> </A> -<H2>7.2 MARKUP EXAMPLES</H2> +<p> <br> + sisu --query-0.38<br> -<P> -<A NAME="lbAU"> </A> -<H2>7.2.1 ONLINE</H2> +<p> +<h2><a name='sect18' href='#toc18'>Markup Examples</a></h2> -<P> -<BR> +<p> +<h2><a name='sect19' href='#toc19'>Online</a></h2> +<p> <br> Online markup examples are available together with the respective outputs -produced from <<A HREF="http://www.jus.uio.no/sisu/SiSU/examples.html">http://www.jus.uio.no/sisu/SiSU/examples.html</A>> or from -<<A HREF="http://www.jus.uio.no/sisu/sisu_examples/">http://www.jus.uio.no/sisu/sisu_examples/</A>> -<P> -<BR> - -There is of course this document, which provides a cursory overview of sisu -markup and the respective output produced: -<<A HREF="http://www.jus.uio.no/sisu/sisu_markup/">http://www.jus.uio.no/sisu/sisu_markup/</A>> -<P> -<BR> - -an alternative presentation of markup syntax: -/usr/share/doc/sisu/on_markup.txt.gz -<P> -<A NAME="lbAV"> </A> -<H2>7.2.2 INSTALLED</H2> - -<P> -<BR> - -With -<B>SiSU</B> - -installed sample skins may be found in: /usr/share/doc/sisu/markup-samples (or -equivalent directory) and if sisu-markup-samples is installed also under: -/usr/share/doc/sisu/markup-samples-non-free -<P> -<A NAME="lbAW"> </A> -<H2>8. MARKUP OF HEADERS</H2> - -<BR> - -<P> -<BR> - -Headers contain either: semantic meta-data about a document, which can be used -by any output module of the program, or; processing instructions. -<P> -<BR> - +produced from <<a href='http://www.jus.uio.no/sisu/SiSU/examples.html'>http://www.jus.uio.no/sisu/SiSU/examples.html</a> +> or from <<a href='http://www.jus.uio.no/sisu/sisu_examples/'>http://www.jus.uio.no/sisu/sisu_examples/</a> +> + +<p> <br> +There is of course this document, which provides a cursory overview of +sisu markup and the respective output produced: <<a href='http://www.jus.uio.no/sisu/sisu_markup/'>http://www.jus.uio.no/sisu/sisu_markup/</a> +> + +<p> <br> +an alternative presentation of markup syntax: /usr/share/doc/sisu/on_markup.txt.gz + +<p> +<h2><a name='sect20' href='#toc20'>Installed</a></h2> + +<p> <br> +With <b>SiSU</b> installed sample skins may be found in: /usr/share/doc/sisu/markup-samples +(or equivalent directory) and if sisu -markup-samples is installed also under: + +<p>/usr/share/doc/sisu/markup-samples-non-free +<p> +<h2><a name='sect21' href='#toc21'>Markup of Headers</a></h2> +<br> + +<p> <br> +Headers contain either: semantic meta-data about a document, which can be +used by any output module of the program, or; processing instructions. +<p> +<br> Note: the first line of a document may include information on the markup -version used in the form of a comment. Comments are a percentage mark at the -start of a paragraph (and as the first character in a line of text) followed by -a space and the comment: -<P> -<PRE> -% this would be a comment -</PRE> - -<P> -<A NAME="lbAX"> </A> -<H2>8.1 SAMPLE HEADER</H2> - -<P> -<BR> - -This current document is loaded by a master document that has a header similar -to this one: -<P> -<PRE> -% SiSU master 2.0 +version used in the form of a comment. Comments are a percentage mark at +the start of a paragraph (and as the first character in a line of text) +followed by a space and the comment: +<p> <br> +<pre>% this would be a comment +</pre> +<p> +<h2><a name='sect22' href='#toc22'>Sample Header</a></h2> + +<p> <br> +This current document is loaded by a master document that has a header +similar to this one: +<p> <br> +<pre>% SiSU master 2.0 @title: SiSU - :subtitle: Manual +:subtitle: Manual @creator: - :author: Amissah, Ralph -@publisher: [publisher name] -@rights: Copyright (C) Ralph Amissah 2007, License GPL 3 +:author: Amissah, Ralph +@publisher: [publisher name] +@rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, +License GPL 3 @classify: - :type: information - :topic_register: SiSU:manual;electronic documents:SiSU:manual - :subject: ebook, epublishing, electronic book, electronic publishing, +:type: information +:topic_register: SiSU:manual;electronic documents:SiSU:manual +:subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search % used_by: manual @date: - :published: 2008-05-22 - :created: 2002-08-28 - :issued: 2002-08-28 - :available: 2002-08-28 - :modified: 2010-03-03 +:published: 2008-05-22 +:created: 2002-08-28 +:issued: 2002-08-28 +:available: 2002-08-28 +:modified: 2010-03-03 @make: - :num_top: 1 - :breaks: new=C; break=1 - :skin: skin_sisu_manual - :bold: /Gnu|Debian|Ruby|SiSU/ - :manpage: name=sisu - documents: markup, structuring, publishing - in multiple standard formats, and search; - synopsis=sisu [-abcDdeFhIiMmNnopqRrSsTtUuVvwXxYyZz0-9] [filename/wildcard ] - . sisu [-Ddcv] [instruction] - . sisu [-CcFLSVvW] - . sisu --v2 [operations] - . sisu --v3 [operations] +:num_top: 1 +:breaks: new=C; break=1 +:bold: /Gnu|Debian|Ruby|SiSU/ +:home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org +:footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org +:manpage: name=sisu - documents: markup, structuring, publishing in multiple +standard formats, and search; + synopsis=sisu [-abcDdeFhIiMmNnopqRrSsTtUuVvwXxYyZz0-9] [filename/wildcard + ] + . sisu [-Ddcv] [instruction] + . sisu [-CcFLSVvW] + . sisu --v4 [operations] + . sisu --v3 [operations] @links: - { SiSU Homepage }<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A> - { SiSU Manual }<A HREF="http://www.sisudoc.org/sisu/sisu_manual/">http://www.sisudoc.org/sisu/sisu_manual/</A> - { Book Samples & Markup Examples }<A HREF="http://www.jus.uio.no/sisu/SiSU/examples.html">http://www.jus.uio.no/sisu/SiSU/examples.html</A> - { SiSU Download }<A HREF="http://www.jus.uio.no/sisu/SiSU/download.html">http://www.jus.uio.no/sisu/SiSU/download.html</A> - { SiSU Changelog }<A HREF="http://www.jus.uio.no/sisu/SiSU/changelog.html">http://www.jus.uio.no/sisu/SiSU/changelog.html</A> - { SiSU Git repo }<A HREF="http://git.sisudoc.org/?p=code/sisu.git;a=summary">http://git.sisudoc.org/?p=code/sisu.git;a=summary</A> - { SiSU List Archives }<A HREF="http://lists.sisudoc.org/pipermail/sisu/">http://lists.sisudoc.org/pipermail/sisu/</A> - { SiSU @ Debian }<A HREF="http://packages.qa.debian.org/s/sisu.html">http://packages.qa.debian.org/s/sisu.html</A> - { SiSU Project @ Debian }<A HREF="http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org">http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org</A> - { SiSU @ Wikipedia }<A HREF="http://en.wikipedia.org/wiki/SiSU">http://en.wikipedia.org/wiki/SiSU</A> -</PRE> - -<P> -<A NAME="lbAY"> </A> -<H2>8.2 AVAILABLE HEADERS</H2> - -<P> -<BR> - +{ SiSU Homepage }http://www.sisudoc.org/ +{ SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ +{ Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html +{ SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html +{ SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html +{ SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary +{ SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ +{ SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html +{ SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org +{ SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU +</pre> +<p> +<h2><a name='sect23' href='#toc23'>Available Headers</a></h2> + +<p> <br> Header tags appear at the beginning of a document and provide meta information -on the document (such as the Dublin Core), or information as to how the -document as a whole is to be processed. All header instructions take the form -@headername: or on the next line and indented by once space :subheadername: All -Dublin Core meta tags are available -<P> -<BR> - -<B>@indentifier:</B> - -information or instructions -<P> -<BR> - -where the "identifier" is a tag recognised by the program, and the -"information" or "instructions" belong to the tag/indentifier specified -<P> -<BR> - +on the document (such as the <i>Dublin</i> Core ) , or information as to how the +document as a whole is to be processed. All header instructions take the +form @headername: or on the next line and indented by once space :subheadername: + +<p>All <i>Dublin</i> Core meta tags are available +<p> <br> +<b>@indentifier:</b> information or instructions +<p> <br> +where the "identifier" is a tag recognised by the program, and the "information" +or "instructions" belong to the tag/indentifier specified +<p> <br> Note: a header where used should only be used once; all headers apart from @title: are optional; the @structure: header is used to describe document structure, and can be useful to know. -<P> -<BR> - -This is a sample header -<P> -<PRE> -% SiSU 2.0 [declared file-type identifier with markup version] -</PRE> - -<P> -<PRE> -@title: [title text] [this header is the only one that is mandatory] - :subtitle: [subtitle if any] +<p> <br> + +<p>This is a sample header +<p> <br> +<pre>% SiSU 2.0 [declared file-type identifier with markup version] +</pre> +<p> <br> +<pre>@title: [title text] [this header is the only one that is mandatory] + :subtitle: [subtitle if any] :language: English -</PRE> - -<P> -<PRE> -@creator: - :author: [Lastname, First names] - :illustrator: [Lastname, First names] - :translator: [Lastname, First names] - :prepared_by: [Lastname, First names] -</PRE> - -<P> -<PRE> -@date: - :published: [year or yyyy-mm-dd] - :created: [year or yyyy-mm-dd] - :issued: [year or yyyy-mm-dd] - :available: [year or yyyy-mm-dd] - :modified: [year or yyyy-mm-dd] - :valid: [year or yyyy-mm-dd] - :added_to_site: [year or yyyy-mm-dd] - :translated: [year or yyyy-mm-dd] -</PRE> - -<P> -<PRE> -@rights: - :copyright: Copyright (C) [Year and Holder] - :license: [Use License granted] - :text: [Year and Holder] - :translation: [Name, Year] - :illustrations: [Name, Year] -</PRE> - -<P> -<PRE> -@classify: - :topic_register: SiSU:markup sample:book;book:novel:fantasy - :type: - :subject: - :description: - :keywords: - :abstract: - :isbn: [ISBN] - :loc: [Library of Congress classification] - :dewey: [Dewey classification] - :pg: [Project Gutenberg text number] -</PRE> - -<P> -<PRE> -@links: { SiSU }<A HREF="http://www.sisudoc.org">http://www.sisudoc.org</A> - { FSF }<A HREF="http://www.fsf.org">http://www.fsf.org</A> -</PRE> - -<P> -<PRE> -@make: - :skin: skin_name - [skins change default settings related to the appearance of documents generated] - :num_top: 1 - :headings: [text to match for each level - (e.g. PART; Chapter; Section; Article; - or another: none; BOOK|FIRST|SECOND; none; CHAPTER;) - :breaks: new=:C; break=1 - :promo: sisu, ruby, sisu_search_libre, open_society - :bold: [regular expression of words/phrases to be made bold] - :italics: [regular expression of words/phrases to italicise] -</PRE> - -<P> -<PRE> -@original: - :language: [language] -</PRE> - -<P> -<PRE> -@notes: - :comment: - :prefix: [prefix is placed just after table of contents] -</PRE> - -<P> -<A NAME="lbAZ"> </A> -<H2>9. MARKUP OF SUBSTANTIVE TEXT</H2> - -<BR> - -<P> -<A NAME="lbBA"> </A> -<H2>9.1 HEADING LEVELS</H2> - -<P> -<BR> - +</pre> +<p> <br> +<pre>@creator: +:author: [Lastname, First names] +:illustrator: [Lastname, First names] +:translator: [Lastname, First names] +:prepared_by: [Lastname, First names] +</pre> +<p> <br> +<pre>@date: +:published: [year or yyyy-mm-dd] +:created: [year or yyyy-mm-dd] +:issued: [year or yyyy-mm-dd] +:available: [year or yyyy-mm-dd] +:modified: [year or yyyy-mm-dd] +:valid: [year or yyyy-mm-dd] +:added_to_site: [year or yyyy-mm-dd] +:translated: [year or yyyy-mm-dd] +</pre> +<p> <br> +<pre>@rights: +:copyright: Copyright (C) [Year and Holder] +:license: [Use License granted] +:text: [Year and Holder] +:translation: [Name, Year] +:illustrations: [Name, Year] +</pre> +<p> <br> +<pre>@classify: +:topic_register: SiSU:markup sample:book;book:novel:fantasy +:type: +:subject: +:description: +:keywords: +:abstract: +:loc: [Library of Congress classification] +:dewey: Dewey classification +</pre> +<p> <br> +<pre>@identify: +:isbn: [ISBN] +:oclc: +</pre> +<p> <br> +<pre>@links: { SiSU }http://www.sisudoc.org + { FSF }http://www.fsf.org +</pre> +<p> <br> +<pre>@make: +:num_top: 1 +:headings: [text to match for each level (e.g. PART; Chapter; Section; + Article; or another: none; BOOK|FIRST|SECOND; none; CHAPTER;) :breaks: new=:C; + break=1 :promo: sisu, ruby, sisu_search_libre, open_society :bold: [regular + expression of words/phrases to be made bold] +:italics: [regular expression of words/phrases to italicise] +:home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org +:footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org +</pre> +<p> <br> +<pre>@original: +:language: [language] +</pre> +<p> <br> +<pre>@notes: +:comment: +:prefix: [prefix is placed just after table of contents] +</pre> +<p> +<h2><a name='sect24' href='#toc24'>Markup of Substantive Text</a></h2> +<br> + +<p> +<h2><a name='sect25' href='#toc25'>Heading Levels</a></h2> + +<p> <br> Heading levels are :A~ ,:B~ ,:C~ ,1~ ,2~ ,3~ ... :A - :C being part / section headings, followed by other heading levels, and 1 -6 being headings followed by substantive text or sub-headings. :A~ usually the title :A~? conditional level 1 heading (used where a stand-alone document may be imported into another) -<P> -<BR> - -<B>:A~ [heading text]</B> - -Top level heading [this usually has similar content to the title - @title: ] NOTE: the heading levels described here are in 0.38 notation, see -heading -<P> -<BR> - -<B>:B~ [heading text]</B> - -Second level heading [this is a heading level divider] -<P> -<BR> - -<B>:C~ [heading text]</B> - -Third level heading [this is a heading level divider] -<P> -<BR> - -<B>1~ [heading text]</B> - -Top level heading preceding substantive text of document or sub-heading 2, the -heading level that would normally be marked 1. or 2. or 3. etc. in a document, -and the level on which sisu by default would break html output into named -segments, names are provided automatically if none are given (a number), -otherwise takes the form 1~my_filename_for_this_segment -<P> -<BR> - -<B>2~ [heading text]</B> - -Second level heading preceding substantive text of document or sub-heading 3, -the heading level that would normally be marked 1.1 or 1.2 or 1.3 or 2.1 etc. -in a document. -<P> -<BR> - -<B>3~ [heading text]</B> - -Third level heading preceding substantive text of document, that would normally -be marked 1.1.1 or 1.1.2 or 1.2.1 or 2.1.1 etc. in a document -<P> -<PRE> -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) -</PRE> - -<P> -<A NAME="lbBB"> </A> -<H2>9.2 FONT ATTRIBUTES</H2> - -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -normal text, *{emphasis}*, !{bold text}!, /{italics}/, _{underscore}_, "{citation}", +<p> <br> +<b>:A~ [heading text]</b> Top level heading [this usually has similar content + to the title @title: ] NOTE: the heading levels described here are in 0.38 +notation, see heading +<p> <br> +<b>:B~ [heading text]</b> Second level heading [this is a heading level divider] + +<p> <br> +<b>:C~ [heading text]</b> Third level heading [this is a heading level divider] + +<p> <br> +<b>1~ [heading text]</b> Top level heading preceding substantive text of document +or sub-heading 2, the heading level that would normally be marked 1. or 2. +or 3. etc. in a document, and the level on which sisu by default would break +html output into named segments, names are provided automatically if none +are given (a number), otherwise takes the form 1~my_filename_for_this_segment + +<p> <br> +<b>2~ [heading text]</b> Second level heading preceding substantive text of document +or sub-heading 3 , the heading level that would normally be marked 1.1 or +1.2 or 1.3 or 2.1 etc. in a document. +<p> <br> +<b>3~ [heading text]</b> Third level heading preceding substantive text of document, +that would normally be marked 1.1.1 or 1.1.2 or 1.2.1 or 2.1.1 etc. in a document + +<p> <br> +<pre>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) +</pre> +<p> +<h2><a name='sect26' href='#toc26'>Font Attributes</a></h2> + +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>normal text, *{emphasis}*, !{bold text}!, /{italics}/, _{underscore}_, +"{citation}", ^{superscript}^, ,{subscript},, +{inserted text}+, -{strikethrough}-, #{monospace}# normal text -<BR> -*{emphasis}* [note: can be configured to be represented by bold, italics or underscore] -<BR> +*{emphasis}* [note: can be configured to be represented by bold, italics + or underscore] !{bold text}! -<BR> -_{underscore}_ -<BR> /{italics}/ -<BR> -"{citation}" -<BR> +_{underscore}_ +"{citation}" ^{superscript}^ -<BR> ,{subscript}, -<BR> +{inserted text}+ -<BR> -{strikethrough}- -<BR> #{monospace}# -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - -normal text, -<B>emphasis,</B> - -<B>bold text,</B> - -<I>italics,</I> - -<I>underscore,</I> - -"citation", ^superscript^, [subscript], ++inserted text++, ---strikethrough--, monospace -<P> -<BR> - -normal text -<P> -<BR> - -<B>emphasis</B> - -[note: can be configured to be represented by bold, italics or underscore] -<P> -<BR> - -<B>bold text</B> - -<P> -<BR> - -<I>italics</I> - -<P> -<BR> - -<I>underscore</I> - -<P> -<BR> - -"citation" -<P> -<BR> - +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +normal text, <b>emphasis,</b> <b>bold text</b> , <i>italics,</i> <i>underscore,</i> "citation", ^superscript^, +[subscript], ++inserted text++, --strikethrough--, monospace +<p> <br> + +<p>normal text +<p> <br> +<b>emphasis</b> [note: can be configured to be represented by bold, italics italics + or underscore] or underscore] +<p> <br> + +<p><b>bold text</b> +<p> <br> + +<p><i>italics</i> +<p> <br> + +<p><i>underscore</i> +<p> <br> +"citation" +<p> <br> ^superscript^ -<P> -<BR> - +<p> <br> [subscript] -<P> -<BR> - +<p> <br> ++inserted text++ -<P> -<BR> - +<p> <br> --strikethrough-- -<P> -<BR> - -monospace -<P> -<A NAME="lbBC"> </A> -<H2>9.3 INDENTATION AND BULLETS</H2> +<p> <br> -<P> -<BR> +<p>monospace +<p> +<h2><a name='sect27' href='#toc27'>Indentation and Bullets</a></h2> -<B>markup example:</B> - -<P> -<PRE> -ordinary paragraph -<BR> +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>ordinary paragraph _1 indent paragraph one step -<BR> _2 indent paragraph two steps -<BR> _9 indent paragraph nine steps -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - -ordinary paragraph -<P> -<BR> +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> -<BR> indent paragraph one step -<P> -<BR> +<p>ordinary paragraph +<p> <br> + indent paragraph one step<br> -<BR> indent paragraph two steps -<P> -<BR> +<p> <br> + indent paragraph two steps<br> -<BR> indent paragraph nine steps -<P> -<BR> +<p> <br> + indent paragraph nine steps<br> -<B>markup example:</B> - -<P> -<PRE> -_* bullet text -<BR> +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>_* bullet text _1* bullet text, first indent -<BR> _2* bullet text, two step indent -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> * bullet text -<P> -<BR> - -<BR> * bullet text, first indent -<P> -<BR> +<p> <br> + * bullet text, first indent<br> -<BR> * bullet text, two step indent -<P> -<BR> +<p> <br> + * bullet text, two step indent<br> +<p> <br> Numbered List (not to be confused with headings/titles, (document structure)) -<P> -<BR> -<B>markup example:</B> - -<P> -<PRE> -# numbered list numbered list 1., 2., 3, etc. -<BR> +<p> <br> +<b>markup example:</b> +<p> <br> +<pre># numbered list numbered list 1., 2., 3, etc. _# numbered list numbered list indented a., b., c., d., etc. -</PRE> - -<P> -<A NAME="lbBD"> </A> -<H2>9.4 HANGING INDENTS</H2> - -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -_0_1 first line no indent, +</pre> +<p> +<h2><a name='sect28' href='#toc28'>Hanging Indents</a></h2> + +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>_0_1 first line no indent, rest of paragraph indented one step _1_0 first line indented, rest of paragraph no indent in each case level may be 0-9 -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - -<BR> first line no indent, rest of paragraph indented one step -<P> -<BR> +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> + first line no indent, rest of paragraph indented one step<br> +<p> <br> first line indented, rest of paragraph no indent -<P> -<BR> - -in each case level may be 0-9 -<P> -<A NAME="lbBE"> </A> -<H2>9.5 FOOTNOTES / ENDNOTES</H2> +<p> <br> -<P> -<BR> +<p>in each case level may be 0-9 +<p> +<h2><a name='sect29' href='#toc29'>Footnotes / Endnotes</a></h2> +<p> <br> Footnotes and endnotes are marked up at the location where they would be indicated within a text. They are automatically numbered. The output type -determines whether footnotes or endnotes will be produced -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -~{ a footnote or endnote }~ -</PRE> -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - -[^12] -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -normal text~{ self contained endnote marker & endnote in one }~ continues -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - -normal text[^13] continues -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks if required }~ continues -<BR> +<p>determines whether footnotes or endnotes will be produced +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>~{ a footnote or endnote }~ +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +[^13] +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>normal text~{ self contained endnote marker & endnote in one }~ continues +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +normal text[^14] continues +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks +if required }~ continues normal text ~{** another unnumbered asterisk footnote/endnote }~ continues -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> normal text [^*] continues -<P> -<BR> - +<p> <br> normal text [^**] continues -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -normal text ~[* editors notes, numbered asterisk footnote/endnote series ]~ continues -<BR> -normal text ~[+ editors notes, numbered asterisk footnote/endnote series ]~ continues -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>normal text ~[* editors notes, numbered asterisk footnote/endnote series + ]~ continues +normal text ~[+ editors notes, numbered asterisk footnote/endnote series + ]~ continues +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> normal text [^*3] continues -<P> -<BR> - +<p> <br> normal text [^+2] continues -<P> -<BR> - -<B>Alternative endnote pair notation for footnotes/endnotes:</B> - -<P> -<PRE> -% note the endnote marker "~^" +<p> <br> +<b>Alternative endnote pair notation for footnotes/endnotes:</b> +<p> <br> +<pre>% note the endnote marker "~^" normal text~^ continues -<BR> ^~ endnote text following the paragraph in which the marker occurs -</PRE> - -<P> -<BR> +</pre> +<p> <br> -the standard and pair notation cannot be mixed in the same document -<P> -<A NAME="lbBF"> </A> -<H2>9.6 LINKS</H2> +<p>the standard and pair notation cannot be mixed in the same document +<p> +<h2><a name='sect30' href='#toc30'>Links</a></h2> -<P> -<A NAME="lbBG"> </A> -<H2>9.6.1 NAKED URLS WITHIN TEXT, DEALING WITH URLS</H2> +<p> -<P> -<BR> +<h2><a name='sect31' href='#toc31'>Naked Urls Within Text, Dealing with Urls</a></h2> +<p> <br> urls found within text are marked up automatically. A url within text is automatically hyperlinked to itself and by default decorated with angled -braces, unless they are contained within a code block (in which case they are -passed as normal text), or escaped by a preceding underscore (in which case the -decoration is omitted). -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -normal text <A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A> continues -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - -normal text <<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A>> continues -<P> -<BR> - -An escaped url without decoration -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -normal text _<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A> continues -deb _<A HREF="http://www.jus.uio.no/sisu/archive">http://www.jus.uio.no/sisu/archive</A> unstable main non-free -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - -normal text <_<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A>> continues -<P> -<BR> - -deb <_<A HREF="http://www.jus.uio.no/sisu/archive">http://www.jus.uio.no/sisu/archive</A>> unstable main non-free -<P> -<BR> - -where a code block is used there is neither decoration nor hyperlinking, code -blocks are discussed later in this document -<P> -<BR> - -<B>resulting output:</B> - -<P> -<PRE> -deb <A HREF="http://www.jus.uio.no/sisu/archive">http://www.jus.uio.no/sisu/archive</A> unstable main non-free -<BR> -deb-src <A HREF="http://www.jus.uio.no/sisu/archive">http://www.jus.uio.no/sisu/archive</A> unstable main non-free -</PRE> - -<P> -<A NAME="lbBH"> </A> -<H2>9.6.2 LINKING TEXT</H2> - -<P> -<BR> - -To link text or an image to a url the markup is as follows -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -about { SiSU }<A HREF="http://url.org">http://url.org</A> markup -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - -aboutSiSU <<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A>> markup -<P> -<BR> - -A shortcut notation is available so the url link may also be provided -automatically as a footnote -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -about {~^ SiSU }<A HREF="http://url.org">http://url.org</A> markup -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - -about SiSU <<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A>> [^14] markup -<P> -<BR> - -Internal document links to a tagged location, including an ocn -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> - { tux.png 64x80 }image -<BR> - % various url linked images -<BR> - {tux.png 64x80 "a better way" }<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A> -<BR> -<BR> - {GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian and Ruby" }<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A> -<BR> -<BR> - {~^ ruby_logo.png "Ruby" }<A HREF="http://www.ruby-lang.org/en/">http://www.ruby-lang.org/en/</A> -<BR> -<BR> -<B>markup example:</B> - -{ tux.png 64x80 }image +braces, unless they are contained within a code block (in which case they +are passed as normal text), or escaped by a preceding underscore (in which +case the decoration is omitted). +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>normal text http://www.sisudoc.org/ continues +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +normal text <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> continues +<p> <br> + +<p>An escaped url without decoration +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>normal text _http://www.sisudoc.org/ continues +deb _http://www.jus.uio.no/sisu/archive unstable main non-free +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +normal text <_<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> continues +<p> <br> +deb <_<a href='http://www.jus.uio.no/sisu/archive'>http://www.jus.uio.no/sisu/archive</a> +> unstable main non-free +<p> <br> +where a code block is used there is neither decoration nor hyperlinking, + +<p>code blocks are discussed later in this document +<p> <br> +<b>resulting output:</b> +<p> <br> +<pre>deb http://www.jus.uio.no/sisu/archive unstable main non-free +deb-src http://www.jus.uio.no/sisu/archive unstable main non-free +</pre> +<p> +<h2><a name='sect32' href='#toc32'>Linking Text</a></h2> + +<p> <br> + +<p>To link text or an image to a url the markup is as follows +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>about { SiSU }http://url.org markup +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +aboutSiSU <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> markup +<p> <br> + +<p>A shortcut notation is available so the url link may also be provided automatically + +<p>as a footnote +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>about {~^ SiSU }http://url.org markup +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +aboutSiSU <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> [^15] markup +<p> <br> +Internal document links to a tagged location, including an <i>ocn</i> +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>about { text links }#link_text +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +about ⌠text links⌡⌈link_text⌋ +<p> <br> + +<p>Shared document collection link +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>about { SiSU book markup examples }:SiSU/examples.html +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +about ⌠ <b>SiSU</b> book markup examples⌡⌈:SiSU/examples.html⌋ +<p> +<h2><a name='sect33' href='#toc33'>Linking +Images</a></h2> + +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>{ tux.png 64x80 }image % various url linked images -{tux.png 64x80 "a better way" }<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A> -{GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian and Ruby" }<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A> -{~^ ruby_logo.png "Ruby" }<A HREF="http://www.ruby-lang.org/en/">http://www.ruby-lang.org/en/</A> -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - +{tux.png 64x80 "a better way" }http://www.sisudoc.org/ +{GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian +and Ruby" }http://www.sisudoc.org/ +{~^ ruby_logo.png "Ruby" }http://www.ruby-lang.org/en/ +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> [ tux.png ] -<P> -<BR> - -tux.png 64x80 "Gnu/Linux - a better way" <<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A>> -<P> -<BR> - -GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian -and Ruby" <<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A>> -<P> -<BR> - -[ ruby_logo (png missing) ] [^15] -<P> -<BR> - -<B>linked url footnote shortcut</B> - -<P> -<PRE> -{~^ [text to link] }<A HREF="http://url.org">http://url.org</A> -% maps to: { [text to link] }<A HREF="http://url.org">http://url.org</A> ~{ <A HREF="http://url.org">http://url.org</A> }~ -% which produces hyper-linked text within a document/paragraph, -% with an endnote providing the url for the text location used in the hyperlink -</PRE> - -<P> -<PRE> -text marker *~name -</PRE> - -<P> -<BR> - -note at a heading level the same is automatically achieved by providing names -to headings 1, 2 and 3 i.e. 2~[name] and 3~[name] or in the case of +<p> <br> +tux.png 64x80 "Gnu/Linux - a better way" <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> +<p> <br> +GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian +and Ruby" <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> +<p> <br> +ruby_logo.png 70x90 "Ruby" <<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a> +> [^16] +<p> <br> + +<p><b>linked url footnote shortcut</b> +<p> <br> +<pre>{~^ [text to link] }http://url.org +% maps to: { [text to link] }http://url.org ~{ http://url.org }~ +% which produces hyper-linked text within a document/paragraph, with an +endnote providing the url for the text location used in the hyperlink +</pre> +<p> <br> +<pre>text marker *~name +</pre> +<p> <br> +note at a heading level the same is automatically achieved by providing +names to headings 1, 2 and 3 i.e. 2~[name] and 3~[name] or in the case of auto-heading numbering, without further intervention. -<P> -<A NAME="lbBI"> </A> -<H2>9.7 GROUPED TEXT</H2> - -<P> -<A NAME="lbBJ"> </A> -<H2>9.7.1 TABLES</H2> - -<P> -<BR> - -Tables may be prepared in two either of two forms -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -table{ c3; 40; 30; 30; +<p> +<h2><a name='sect34' href='#toc34'>Link Shortcut for +Multiple Versions of a Sisu Document in the Same Directory</a></h2> +TREE +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>!_ /{"Viral Spiral"}/, David Bollier +{ "Viral Spiral", David Bollier [3sS]}viral_spiral.david_bollier.sst +</pre> +<p> <br> +<b></b> <i>Viral Spiral</i>, David Bollier +<p> "Viral Spiral", David Bollier <<a href='http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html'>http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html</a> +> + document manifest <<a href='http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html'>http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html</a> +><br> + ⌠html, segmented text⌡「<a href='http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」'>http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」</a> +<br> + ⌠html, scroll, document in one⌡「<a href='http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」'>http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」</a> +<br> + ⌠epub⌡「<a href='http://corundum/sisu_manual/en/epub/viral_spiral.david_bollier.epub」'>http://corundum/sisu_manual/en/epub/viral_spiral.david_bollier.epub」</a> +<br> + ⌠pdf, landscape⌡「<a href='http://corundum/sisu_manual/en/pdf/viral_spiral.david_bollier.pdf」'>http://corundum/sisu_manual/en/pdf/viral_spiral.david_bollier.pdf」</a> +<br> + ⌠pdf, portrait⌡「<a href='http://corundum/sisu_manual/en/pdf/viral_spiral.david_bollier.pdf」'>http://corundum/sisu_manual/en/pdf/viral_spiral.david_bollier.pdf」</a> +<br> + ⌠odf: odt, open document text⌡「<a href='http://corundum/sisu_manual/en/odt/viral_spiral.david_bollier.odt」'>http://corundum/sisu_manual/en/odt/viral_spiral.david_bollier.odt」</a> +<br> + ⌠xhtml scroll⌡「<a href='http://corundum/sisu_manual/en/xhtml/viral_spiral.david_bollier.xhtml」'>http://corundum/sisu_manual/en/xhtml/viral_spiral.david_bollier.xhtml」</a> +<br> + ⌠xml, sax⌡「<a href='http://corundum/sisu_manual/en/xml/viral_spiral.david_bollier.xml」'>http://corundum/sisu_manual/en/xml/viral_spiral.david_bollier.xml」</a> +<br> + ⌠xml, dom⌡「<a href='http://corundum/sisu_manual/en/xml/viral_spiral.david_bollier.xml」'>http://corundum/sisu_manual/en/xml/viral_spiral.david_bollier.xml」</a> +<br> + ⌠concordance⌡「<a href='http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」'>http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」</a> +<br> + ⌠dcc, document content certificate (digests)⌡「<a href='http://corundum/sisu_manual/en/digest/viral_spiral.david_bollier.txt」'>http://corundum/sisu_manual/en/digest/viral_spiral.david_bollier.txt」</a> +<br> + ⌠markup source text⌡「<a href='http://corundum/sisu_manual/en/src/viral_spiral.david_bollier.sst」'>http://corundum/sisu_manual/en/src/viral_spiral.david_bollier.sst」</a> +<br> + ⌠markup source (zipped) pod⌡「<a href='http://corundum/sisu_manual/en/pod/viral_spiral.david_bollier.sst.zip」'>http://corundum/sisu_manual/en/pod/viral_spiral.david_bollier.sst.zip」</a> +<br> + +<p> +<h2><a name='sect35' href='#toc35'>Grouped Text</a></h2> + +<p> +<h2><a name='sect36' href='#toc36'>Tables</a></h2> + +<p> <br> + +<p>Tables may be prepared in two either of two forms +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>table{ c3; 40; 30; 30; This is a table this would become column two of row one column three of row one is here @@ -2152,101 +1752,83 @@ And here begins another row column two of row two column three of row two, and so on }table -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> [table omitted, see other document formats] -<P> -<BR> - -a second form may be easier to work with in cases where there is not much -information in each column -<P> -<BR> - -<B>markup example:</B> - -[^17] -<P> -<PRE> -!_ Table 3.1: Contributors to Wikipedia, January 2001 - June 2005 +</pre> +<p> <br> +<b>resulting output:</b> +<p> This is a table|this would become column two of row one|column +three of row one is here』And here begins another row|column two of row +two|column three of row two, and so on』 +<p> <br> + +<p>a second form may be easier to work with in cases where there is not much + +<p>information in each column +<p> <br> +<b>markup example:</b> [^18] +<p> <br> +<pre>!_ Table 3.1: Contributors to Wikipedia, January 2001 - June 2005 {table~h 24; 12; 12; 12; 12; 12; 12;} - |Jan. 2001|Jan. 2002|Jan. 2003|Jan. 2004|July 2004|June 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 + |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. -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> - -<B>Table 3.1: Contributors to Wikipedia, January 2001 - June 2005</B> - -<P> -<BR> [table omitted, see other document formats] -<P> -<BR> - -* Contributed at least ten times; ** at least 5 times in last month; *** more -than 100 times in last month. -<P> -<A NAME="lbBK"> </A> -<H2>9.7.2 POEM</H2> - -<P> -<BR> - -<B>basic markup:</B> - -<P> -<PRE> -poem{ +* Contributed at least ten times; ** at least 5 times in last month; *** +more than 100 times in last month. +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +<b>Table 3.1: Contributors to Wikipedia, January 2001 - June 2005</b> +<p> |Jan. 2001|Jan. +2002|Jan. 2003|Jan. 2004|July 2004|June 2006』Contributors*|10|472|2,188|9,653|25,011|48,721』Active +contributors**|9|212|846|3,228|8,442|16,945』Very active contributors***|0|31|190|692|1,639|3,016』No. +of English language articles|25|16,000|101,000|190,000|320,000|630,000』No. of +articles, all languages|25|19,000|138,000|490,000|862,000|1,600,000』 +<p> <br> +* Contributed at least ten times; ** at least 5 times in last month; *** +more than 100 times in last month. +<p> +<h2><a name='sect37' href='#toc37'>Poem</a></h2> + +<p> <br> +<b>basic markup:</b> +<p> <br> +<pre>poem{ Your poem here }poem Each verse in a poem is given an object number. -</PRE> - -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -poem{ - `Fury said to a +</pre> +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>poem{ + ‘Fury said to a mouse, That he met in the house, - "Let us + "Let us both go to law: I will prosecute YOU. --Come, - I'll take no + I’ll take no denial; We must have a trial: For really this - morning I've + morning I’ve nothing - to do." + to do." Said the mouse to the - cur, "Such + cur, "Such a trial, dear Sir, With @@ -2255,14 +1837,14 @@ poem{ would be wasting our - breath." - "I'll be - judge, I'll - be jury," + breath." + "I’ll be + judge, I’ll + be jury," Said cunning old Fury: - "I'll + "I’ll try the whole cause, @@ -2270,196 +1852,91 @@ poem{ condemn you to - death."' + death."’ }poem -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> `Fury said to a -<BR> - -<BR> mouse, That he -<BR> - -<BR> met in the -<BR> - -<BR> house, -<BR> - -<BR> "Let us -<BR> - -<BR> both go to -<BR> - -<BR> law: I will -<BR> - -<BR> prosecute -<BR> - -<BR> YOU. --Come, -<BR> - -<BR> I'll take no -<BR> - -<BR> denial; We -<BR> - -<BR> must have a -<BR> - -<BR> trial: For -<BR> - -<BR> really this -<BR> - -<BR> morning I've -<BR> - -<BR> nothing -<BR> - -<BR> to do." -<BR> - -<BR> Said the -<BR> - -<BR> mouse to the -<BR> - -<BR> cur, "Such -<BR> - -<BR> a trial, -<BR> - -<BR> dear Sir, -<BR> - -<BR> With -<BR> - -<BR> no jury -<BR> - -<BR> or judge, -<BR> - -<BR> would be -<BR> - -<BR> wasting -<BR> - -<BR> our -<BR> - -<BR> breath." -<BR> - -<BR> "I'll be -<BR> - -<BR> judge, I'll -<BR> - -<BR> be jury," -<BR> - -<BR> Said -<BR> - -<BR> cunning -<BR> - -<BR> old Fury: -<BR> - -<BR> "I'll -<BR> - -<BR> try the -<BR> - -<BR> whole -<BR> - -<BR> cause, -<BR> - -<BR> and -<BR> - -<BR> condemn -<BR> - -<BR> you -<BR> - -<BR> to -<BR> - -<BR> death."' -<BR> - -<P> -<A NAME="lbBL"> </A> -<H2>9.7.3 GROUP</H2> - -<P> -<BR> - -<B>basic markup:</B> - -<P> -<PRE> -group{ -<BR> +</pre> +<p> <br> +<b>resulting output:</b> +<p> ‘Fury said to a<br> + mouse, That he<br> + met in the<br> + house,<br> + "Let us<br> + both go to<br> + law: I will<br> + prosecute<br> + YOU. --Come,<br> + I’ll take no<br> + denial; We<br> + must have a<br> + trial: For<br> + really this<br> + morning I’ve<br> + nothing<br> + to do."<br> + Said the<br> + mouse to the<br> + cur, "Such<br> + a trial,<br> + dear Sir,<br> + With<br> + no jury<br> + or judge,<br> + would be<br> + wasting<br> + our<br> + breath."<br> + "I’ll be<br> + judge, I’ll<br> + be jury,"<br> + Said<br> + cunning<br> + old Fury:<br> + "I’ll<br> + try the<br> + whole<br> + cause,<br> + and<br> + condemn<br> + you<br> + to<br> + death."’<br> + +<p> +<h2><a name='sect38' href='#toc38'>Group</a></h2> + +<p> <br> +<b>basic markup:</b> +<p> <br> +<pre>group{ Your grouped text here -<BR> }group -<BR> A group is treated as an object and given a single object number. -</PRE> - -<P> -<BR> - -<B>markup example:</B> - -<P> -<PRE> -group{ - 'Fury said to a +</pre> +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>group{ + ‘Fury said to a mouse, That he met in the house, - "Let us + "Let us both go to law: I will prosecute YOU. --Come, - I'll take no + I’ll take no denial; We must have a trial: For really this - morning I've + morning I’ve nothing - to do." + to do." Said the mouse to the - cur, "Such + cur, "Such a trial, dear Sir, With @@ -2468,14 +1945,14 @@ group{ would be wasting our - breath." - "I'll be - judge, I'll - be jury," + breath." + "I’ll be + judge, I’ll + be jury," Said cunning old Fury: - "I'll + "I’ll try the whole cause, @@ -2483,193 +1960,92 @@ group{ condemn you to - death."' + death."’ }group -</PRE> - -<P> -<BR> - -<B>resulting output:</B> - -<P> -<BR> `Fury said to a -<BR> - -<BR> mouse, That he -<BR> - -<BR> met in the -<BR> - -<BR> house, -<BR> - -<BR> "Let us -<BR> - -<BR> both go to -<BR> - -<BR> law: I will -<BR> - -<BR> prosecute -<BR> - -<BR> YOU. --Come, -<BR> - -<BR> I'll take no -<BR> - -<BR> denial; We -<BR> - -<BR> must have a -<BR> - -<BR> trial: For -<BR> - -<BR> really this -<BR> - -<BR> morning I've -<BR> - -<BR> nothing -<BR> - -<BR> to do." -<BR> - -<BR> Said the -<BR> - -<BR> mouse to the -<BR> - -<BR> cur, "Such -<BR> - -<BR> a trial, -<BR> - -<BR> dear Sir, -<BR> - -<BR> With -<BR> - -<BR> no jury -<BR> - -<BR> or judge, -<BR> - -<BR> would be -<BR> - -<BR> wasting -<BR> - -<BR> our -<BR> - -<BR> breath." -<BR> - -<BR> "I'll be -<BR> - -<BR> judge, I'll -<BR> - -<BR> be jury," -<BR> - -<BR> Said -<BR> - -<BR> cunning -<BR> - -<BR> old Fury: -<BR> - -<BR> "I'll -<BR> - -<BR> try the -<BR> - -<BR> whole -<BR> - -<BR> cause, -<BR> - -<BR> and -<BR> - -<BR> condemn -<BR> - -<BR> you -<BR> - -<BR> to -<BR> - -<BR> death."' -<BR> - -<P> -<A NAME="lbBM"> </A> -<H2>9.7.4 CODE</H2> - -<P> -<BR> - -Code tags code{ ... }code (used as with other group tags described above) are -used to escape regular sisu markup, and have been used extensively within this -document to provide examples of -<B>SiSU</B> - -markup. You cannot however use code tags to escape code tags. They are however -used in the same way as group or poem tags. -<P> -<BR> - -A code-block is treated as an object and given a single object number. [an option to number each line of code may be considered at some later time] -<P> -<BR> - -<B>use of code tags instead of poem compared, resulting output:</B> - -<P> -<PRE> - `Fury said to a +</pre> +<p> <br> +<b>resulting output:</b> +<p> ‘Fury said to a<br> + mouse, That he<br> + met in the<br> + house,<br> + "Let us<br> + both go to<br> + law: I will<br> + prosecute<br> + YOU. --Come,<br> + I’ll take no<br> + denial; We<br> + must have a<br> + trial: For<br> + really this<br> + morning I’ve<br> + nothing<br> + to do."<br> + Said the<br> + mouse to the<br> + cur, "Such<br> + a trial,<br> + dear Sir,<br> + With<br> + no jury<br> + or judge,<br> + would be<br> + wasting<br> + our<br> + breath."<br> + "I’ll be<br> + judge, I’ll<br> + be jury,"<br> + Said<br> + cunning<br> + old Fury:<br> + "I’ll<br> + try the<br> + whole<br> + cause,<br> + and<br> + condemn<br> + you<br> + to<br> + death."’<br> + +<p> +<h2><a name='sect39' href='#toc39'>Code</a></h2> + +<p> <br> +Code tags code{ ... }code (used as with other group tags described above) +are used to escape regular sisu markup, and have been used extensively +within this document to provide examples of <b>SiSU</b> markup. You cannot however +use code tags to escape code tags. They are however used in the same way +as group or poem tags. +<p> <br> +A code-block is treated as an object and given a single object number. [an +option to number each line of code may be considered at some later time] + +<p> <br> +<b>use of code tags instead of poem compared, resulting output:</b> +<p> <br> +<pre> ‘Fury said to a mouse, That he met in the house, - "Let us + "Let us both go to law: I will prosecute YOU. --Come, - I'll take no + I’ll take no denial; We must have a trial: For really this - morning I've + morning I’ve nothing - to do." + to do." Said the mouse to the - cur, "Such + cur, "Such a trial, dear Sir, With @@ -2678,14 +2054,14 @@ A code-block is treated as an object and given a single object number. [an optio would be wasting our - breath." - "I'll be - judge, I'll - be jury," + breath." + "I’ll be + judge, I’ll + be jury," Said cunning old Fury: - "I'll + "I’ll try the whole cause, @@ -2693,39 +2069,32 @@ A code-block is treated as an object and given a single object number. [an optio condemn you to - death."' -</PRE> - -<P> -<BR> - -From -<B>SiSU</B> - -2.7.7 on you can number codeblocks by placing a hash after the opening code tag -code{# as demonstrated here: -<P> -<PRE> -1 | `Fury said to a + death."’ +</pre> +<p> <br> +From <b>SiSU</b> 2.7.7 on you can number codeblocks by placing a hash after the +opening code tag code{# as demonstrated here: +<p> <br> +<pre>1 | ‘Fury said to a 2 | mouse, That he 3 | met in the 4 | house, -5 | "Let us +5 | "Let us 6 | both go to 7 | law: I will 8 | prosecute 9 | YOU. --Come, -10 | I'll take no +10 | I’ll take no 11 | denial; We 12 | must have a 13 | trial: For 14 | really this -15 | morning I've +15 | morning I’ve 16 | nothing -17 | to do." +17 | to do." 18 | Said the 19 | mouse to the -20 | cur, "Such +20 | cur, "Such 21 | a trial, 22 | dear Sir, 23 | With @@ -2734,14 +2103,14 @@ code{# as demonstrated here: 26 | would be 27 | wasting 28 | our -29 | breath." -30 | "I'll be -31 | judge, I'll -32 | be jury," +29 | breath." +30 | "I’ll be +31 | judge, I’ll +32 | be jury," 33 | Said 34 | cunning 35 | old Fury: -36 | "I'll +36 | "I’ll 37 | try the 38 | whole 39 | cause, @@ -2749,1284 +2118,454 @@ code{# as demonstrated here: 41 | condemn 42 | you 43 | to -44 | death."' -</PRE> - -<P> -<A NAME="lbBN"> </A> -<H2>9.8 ADDITIONAL BREAKS - LINEBREAKS WITHIN OBJECTS, COLUMN AND PAGE-BREAKS</H2> - -<P> -<A NAME="lbBO"> </A> -<H2>9.8.1 LINE-BREAKS</H2> - -<P> -<BR> - -To break a line within a "paragraph object", two backslashes \\ -with a space before and a space or newline after them -may be used. -<P> -<PRE> -To break a line within a "paragraph object", +44 | death."’ +</pre> +<p> +<h2><a name='sect40' href='#toc40'>Additional Breaks - Linebreaks Within Objects, Column and Page-breaks</a></h2> + +<p> +<h2><a name='sect41' href='#toc41'>Line-breaks</a></h2> + +<p> +<br> +To break a line within a "paragraph object", two backslashes \\ with a space +before and a space or newline after them may be used. +<p> <br> +<pre>To break a line within a "paragraph object", two backslashes \\ with a space before and a space or newline after them \\ may be used. -</PRE> - -<P> -<BR> - +</pre> +<p> <br> The html break br enclosed in angle brackets (though undocumented) is available in versions prior to 3.0.13 and 2.9.7 (it remains available for the time being, but is depreciated). -<P> -<A NAME="lbBP"> </A> -<H2>9.8.2 PAGE BREAKS</H2> - -<P> -<BR> - -Page breaks are only relevant and honored in some output formats. A page break -or a new page may be inserted manually using the following markup on a line on -its own: -<P> -<PRE> +<p> +<h2><a name='sect42' href='#toc42'>Page Breaks</a></h2> + +<p> <br> +Page breaks are only relevant and honored in some output formats. A page +break or a new page may be inserted manually using the following markup +on a line on its own: +<p> <br> +page new =\= or breaks the page, starts a new page. +<p> <br> +page break -\- or breaks a column, starts a new column, if using columns, +else breaks the page, starts a new page. +<p> <br> +<pre>-\\- +or <:pb> -</PRE> - -<P> -<BR> +</pre> +<p> <br> +<p>or +<p> <br> +<pre>=\\= or -<P> -<PRE> <:pn> -</PRE> - -<P> -<BR> - -page new <:pn> breaks the page, starts a new page. -<P> -<BR> - -page break <:pb> breaks a column, starts a new column, if using columns, else -breaks the page, starts a new page. -<P> -<A NAME="lbBQ"> </A> -<H2>9.9 BOOK INDEX</H2> - -<P> -<BR> - -To make an index append to paragraph the book index term relates to it, using -an equal sign and curly braces. -<P> -<BR> - +</pre> +<p> +<h2><a name='sect43' href='#toc43'>Book Index</a></h2> + +<p> <br> +To make an index append to paragraph the book index term relates to it, +using an equal sign and curly braces. +<p> <br> Currently two levels are provided, a main term and if needed a sub-term. Sub-terms are separated from the main term by a colon. -<P> -<PRE> - Paragraph containing main term and sub-term. +<p> <br> +<pre> Paragraph containing main term and sub-term. ={Main term:sub-term} -</PRE> - -<P> -<BR> - -The index syntax starts on a new line, but there should not be an empty line -between paragraph and index markup. -<P> -<BR> - +</pre> +<p> <br> +The index syntax starts on a new line, but there should not be an empty +line between paragraph and index markup. +<p> <br> The structure of the resulting index would be: -<P> -<PRE> - Main term, 1 +<p> <br> +<pre> Main term, 1 sub-term, 1 -</PRE> +</pre> +<p> <br> +Several terms may relate to a paragraph, they are separated by a semicolon. +If the term refers to more than one paragraph, indicate the number of paragraphs. -<P> -<BR> - -Several terms may relate to a paragraph, they are separated by a semicolon. If -the term refers to more than one paragraph, indicate the number of paragraphs. -<P> -<PRE> - Paragraph containing main term, second term and sub-term. +<p> <br> +<pre> Paragraph containing main term, second term and sub-term. ={first term; second term: sub-term} -</PRE> - -<P> -<BR> - +</pre> +<p> <br> The structure of the resulting index would be: -<P> -<PRE> - First term, 1, +<p> <br> +<pre> First term, 1, Second term, 1, sub-term, 1 -</PRE> - -<P> -<BR> - -If multiple sub-terms appear under one paragraph, they are separated under the -main term heading from each other by a pipe symbol. -<P> -<PRE> - Paragraph containing main term, second term and sub-term. +</pre> +<p> <br> +If multiple sub-terms appear under one paragraph, they are separated under +the main term heading from each other by a pipe symbol. +<p> <br> +<pre> Paragraph containing main term, second term and sub-term. ={Main term:sub-term+1|second sub-term} A paragraph that continues discussion of the first sub-term -</PRE> - -<P> -<BR> - -The plus one in the example provided indicates the first sub-term spans one -additional paragraph. The logical structure of the resulting index would be: -<P> -<PRE> - Main term, 1, +</pre> +<p> <br> +The plus one in the example provided indicates the first sub-term spans +one additional paragraph. The logical structure of the resulting index would +be: +<p> <br> +<pre> Main term, 1, sub-term, 1-3, second sub-term, 1, -</PRE> - -<P> -<A NAME="lbBR"> </A> -<H2>10. COMPOSITE DOCUMENTS MARKUP</H2> - -<BR> - -<P> -<BR> +</pre> +<p> +<h2><a name='sect44' href='#toc44'>Composite Documents Markup</a></h2> +<br> +<p> <br> It is possible to build a document by creating a master document that requires -other documents. The documents required may be complete documents that could be -generated independently, or they could be markup snippets, prepared so as to be -easily available to be placed within another text. If the calling document is a -master document (built from other documents), it should be named with the -suffix -<B>.ssm</B> - -Within this document you would provide information on the other documents that -should be included within the text. These may be other documents that would be -processed in a regular way, or markup bits prepared only for inclusion within a -master document -<B>.sst</B> - -regular markup file, or -<B>.ssi</B> - -(insert/information) A secondary file of the composite document is built prior -to processing with the same prefix and the suffix -<B>._sst</B> - -<P> -<BR> - -basic markup for importing a document into a master document -<P> -<PRE> -<< filename1.sst +other documents. The documents required may be complete documents that could +be generated independently, or they could be markup snippets, prepared +so as to be easily available to be placed within another text. If the calling +document is a master document (built from other documents), it should be +named with the suffix <b>.ssm</b> Within this document you would provide information +on the other documents that should be included within the text. These may +be other documents that would be processed in a regular way, or markup +bits prepared only for inclusion within a master document <b>.sst</b> regular markup +file, or <b>.ssi</b> (insert/information) A secondary file of the composite document + +<p>is built prior to processing with the same prefix and the suffix <b>._sst</b> +<p> +<br> + +<p>basic markup for importing a document into a master document +<p> <br> +<pre><< filename1.sst << filename2.ssi -</PRE> - -<P> -<BR> - -The form described above should be relied on. Within the 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. -<P> -<PRE> -<< filename.ssi -<<{filename.ssi} -% using textlink alternatives -<< |filename.ssi|@|^| -</PRE> - -<P> -<A NAME="lbBS"> </A> -<H2>11. MARKUP SYNTAX HISTORY</H2> - -<BR> - -<P> -<A NAME="lbBT"> </A> -<H2>11.1 NOTES RELATED TO FILES-TYPES AND MARKUP SYNTAX</H2> - -<BR> - -<P> -2.0 introduced new headers and is therefore incompatible with 1.0 though -otherwise the same with the addition of a couple of tags (i.e. a superset) -<P> -<BR> - -0.38 is substantially current for version 1.0 -<P> -<BR> - -depreciated 0.16 supported, though file names were changed at 0.37 -<P> -<BR> - -* sisu --query=[sisu version [0.38] or 'history] -<P> -<BR> - -provides a short history of changes to -<B>SiSU</B> - -markup -<P> -<BR> - -<B>SiSU 2.0</B> - -(2010-03-06:09/6) same as 1.0, apart from the changing of headers and the -addition of a monospace tag related headers now grouped, e.g. -<P> -<PRE> -@title: - :subtitle: - -@creator: - :author: - :translator: - :illustrator: - -@rights: - :text: - :illustrations: -</PRE> - -<P> -<BR> - -see document markup samples, and sisu --help headers -<P> -<BR> - -the monospace tag takes the form of a hash '#' -<P> -<PRE> -#{ this enclosed text would be monospaced }# -</PRE> - -<P> -<BR> - -<B>1.0</B> - -(2009-12-19:50/6) same as 0.69 -<P> -<BR> - -<B>0.69</B> - -(2008-09-16:37/2) (same as 1.0) and as previous (0.57) with the addition of -book index tags -<P> -<PRE> -/^={.+?}$/ -</PRE> - -<P> -<BR> - -e.g. appended to a paragraph, on a new-line (without a blank line in between) -logical structure produced assuming this is the first text "object" -<P> -<PRE> -={GNU/Linux community distribution:Debian+2|Fedora|Gentoo;Free Software Foundation+5} -</PRE> - -<P> -<PRE> -Free Software Foundation, 1-6 -GNU/Linux community distribution, 1 - Debian, 1-3 - Fedora, 1 - Gentoo, -</PRE> - -<P> -<BR> - -<B>0.66</B> - -(2008-02-24:07/7) same as previous, adds semantic tags, [experimental and not-used] -<P> -<PRE> -/[:;]{.+?}[:;][a-z+]/ -</PRE> - -<P> -<BR> - -<B>0.57</B> - -(2007w34/4) -<B>SiSU</B> - -0.57 is the same as 0.42 with the introduction of some a shortcut to use the -headers @title and @creator in the first heading [expanded using the contents of the headers @title: and @author:] -<P> -<PRE> -:A~ @title by @author -</PRE> - -<P> -<BR> - -<B>0.52</B> - -(2007w14/6) declared document type identifier at start of text/document: -<P> -<BR> - -<BR> .B SiSU -0.52 -<P> -<BR> - -or, backward compatible using the comment marker: -<P> -<BR> - -<BR> % -<B>SiSU</B> - -0.38 -<P> -<BR> - -variations include ' -<B>SiSU</B> - -(text|master|insert) [version]' and 'sisu-[version]' -<P> -<BR> - -<B>0.51</B> - -(2007w13/6) skins changed (simplified), markup unchanged -<P> -<BR> - -<B>0.42</B> - -(2006w27/4) * (asterisk) type endnotes, used e.g. in relation to author -<P> -<BR> - -<B>SiSU</B> - -0.42 is the same as 0.38 with the introduction of some additional endnote -types, -<P> -<BR> - -Introduces some variations on endnotes, in particular the use of the asterisk -<P> -<PRE> -~{* for example for describing an author }~ and ~{** for describing a second author }~ -</PRE> - -<P> -<BR> - -* for example for describing an author -<P> -<BR> - -** for describing a second author -<P> -<BR> - -and -<P> -<PRE> -~[* my note ]~ or ~[+ another note ]~ -</PRE> - -<P> -<BR> - -which numerically increments an asterisk and plus respectively -<P> -<BR> - -*1 my note +1 another note -<P> -<BR> - -<B>0.38</B> - -(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) -<P> -<BR> - -<B>SiSU</B> - -0.38 introduced alternative experimental header and heading/structure markers, -<P> -<PRE> -@headername: and headers :A~ :B~ :C~ 1~ 2~ 3~ -</PRE> - -<P> -<BR> - -as the equivalent of: -<P> -<PRE> -0~headername and headers 1~ 2~ 3~ 4~ 5~ 6~ -</PRE> - -<P> -<BR> - -The internal document markup of -<B>SiSU</B> - -0.16 remains valid and standard Though note that -<B>SiSU</B> - -0.37 introduced a new file naming convention -<P> -<BR> - -<B>SiSU</B> - -has in effect two sets of levels to be considered, using 0.38 notation A-C -headings/levels, pre-ordinary paragraphs /pre-substantive text, and 1-3 -headings/levels, levels which are followed by ordinary text. This may be -conceptualised as levels A,B,C, 1,2,3, and using such letter number notation, -in effect: A must exist, optional B and C may follow in sequence (not strict) 1 -must exist, optional 2 and 3 may follow in sequence i.e. there are two -independent heading level sequences A,B,C and 1,2,3 (using the 0.16 standard -notation 1,2,3 and 4,5,6) on the positive side: the 0.38 A,B,C,1,2,3 -alternative makes explicit an aspect of structuring documents in -<B>SiSU</B> - -that is not otherwise obvious to the newcomer (though it appears more -complicated, is more in your face and likely to be understood fairly quickly); -the substantive text follows levels 1,2,3 and it is 'nice' to do most work in -those levels -<P> -<BR> - -<B>0.37</B> - -(2006w09/7) introduced new file naming convention, .sst (text), .ssm -(master), .ssi (insert), markup syntax unchanged -<P> -<BR> - -<B>SiSU</B> - -0.37 introduced new file naming convention, using the file extensions .sst -<BR> .ssm and .ssi to replace .s1 .s2 .s3 .r1 .r2 .r3 and .si -<P> -<BR> - -this is captured by the following file 'rename' instruction: -<P> -<PRE> -rename 's/\.s[123]$/\.sst/' *.s{1,2,3} -rename 's/\.r[123]$/\.ssm/' *.r{1,2,3} -rename 's/\.si$/\.ssi/' *.si -</PRE> - -<P> -<BR> - -The internal document markup remains unchanged, from -<B>SiSU</B> - -0.16 -<P> -<BR> - -<B>0.35</B> - -(2005w52/3) sisupod, zipped content file introduced -<P> -<BR> - -<B>0.23</B> - -(2005w36/2) utf-8 for markup file -<P> -<BR> - -<B>0.22</B> - -(2005w35/3) image dimensions may be omitted if rmagick is available to be -relied upon -<P> -<BR> - -<B>0.20.4</B> - -(2005w33/4) header 0~links -<P> -<BR> - -<B>0.16</B> - -(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 -<P> -<BR> - -<B>SiSU</B> - -0.16 (0.15 development branch) introduced the use of -<P> -<BR> - -the header 0~ and headings/structure 1~ 2~ 3~ 4~ 5~ 6~ -<P> -<BR> - -in place of the 0.1 header, heading/structure notation -<P> -<BR> - -<B>SiSU</B> - -0.1 headers and headings structure represented by header 0{~ and -headings/structure 1{ 2{ 3{ 4{~ 5{ 6{ -<P> -<A NAME="lbBU"> </A> -<H2>12. SISU FILETYPES</H2> - -<BR> - -<P> -<BR> - -<B>SiSU</B> - -has plaintext and binary filetypes, and can process either type of document. -<P> -<A NAME="lbBV"> </A> -<H2>12.1 .SST .SSM .SSI MARKED UP PLAIN TEXT</H2> - -<P> -<BR> - -<B>SiSU</B> - -documents are prepared as plain-text (utf-8) files with -<B>SiSU</B> - -markup. They may make reference to and contain images (for example), which are -stored in the directory beneath them _sisu/image. -<B>SiSU</B> - -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 -<BR> .ssi and are not processed. -<P> -<BR> - -<B>SiSU</B> - -processing can be done directly against a sisu documents; which may be located -locally or on a remote server for which a url is provided. -<P> -<BR> - -<B>SiSU</B> - -source markup can be shared with the command: -<P> -<BR> - -<BR> sisu -s [filename] -<P> -<A NAME="lbBW"> </A> -<H2>12.1.1 SISU TEXT - REGULAR FILES (.SST)</H2> - -<P> -<BR> - -The most common form of document in -<B>SiSU,</B> - -see the section on -<B>SiSU</B> - -markup. -<P> -<BR> - -<<A HREF="http://www.sisudoc.org/sisu/sisu_markup">http://www.sisudoc.org/sisu/sisu_markup</A>> -<P> -<BR> - -<<A HREF="http://www.sisudoc.org/sisu/sisu_manual">http://www.sisudoc.org/sisu/sisu_manual</A>> -<P> -<A NAME="lbBX"> </A> -<H2>12.1.2 SISU MASTER FILES (.SSM)</H2> - -<P> -<BR> - -Composite documents which incorporate other -<B>SiSU</B> - -documents which may be either regular -<B>SiSU</B> - -text .sst which may be generated independently, or inserts prepared solely for -the purpose of being incorporated into one or more master documents. -<P> -<BR> - -The mechanism by which master files incorporate other documents is described as -one of the headings under under -<B>SiSU</B> - -markup in the -<B>SiSU</B> - -manual. -<P> -<BR> - +</pre> +<p> <br> +The form described above should be relied on. Within the <i>Vim</i> editor it results +in the text thus linked becoming hyperlinked to the document it is calling +in which is convenient for editing. +<p> +<h2><a name='sect45' href='#toc45'>Sisu Filetypes</a></h2> +<br> + +<p> <br> +<b>SiSU</b> has <i>plaintext</i> and binary filetypes, and can process either type of +document. +<p> +<h2><a name='sect46' href='#toc46'>.sst .ssm .ssi Marked Up Plain Text</a></h2> + +<p> +<dl> + +<dt><b>SiSU¤b〕 documents are prepared +as plain-text (utf-8) files with</b> </dt> +<dd><b>SiSU</b> markup. They may make reference to and +contain images (for example), which are stored in the directory beneath +them _sisu/image. 〔b¤SiSU <i>plaintext</i> markup files are of three types that +may be distinguished by the file extension used: regular text .sst; master +documents, composite documents that incorporate other text, which can be +any regular text or text insert; and inserts the contents of which are +like regular text except these are marked .ssi and are not processed.<br> + +<p> <br> +<b>SiSU</b> processing can be done directly against a sisu documents; which may +be located locally or on a remote server for which a url is provided. +<p> <br> +<b>SiSU</b> source markup can be shared with the command: +<p> <br> + sisu -s [filename]<br> + +<p> </dd> +</dl> + +<h2><a name='sect47' href='#toc47'>Sisu Text - Regular Files (.sst)</a></h2> + +<p> <br> +The most common form of document in <b>SiSU,</b> see the section on <b>SiSU</b> markup. + +<p> +<h2><a name='sect48' href='#toc48'>Sisu Master Files (.ssm)</a></h2> + +<p> <br> +Composite documents which incorporate other <b>SiSU</b> documents which may be +either regular <b>SiSU</b> text .sst which may be generated independently, or inserts +prepared solely for the purpose of being incorporated into one or more +master documents. +<p> <br> +The mechanism by which master files incorporate other documents is described +as one of the headings under under <b>SiSU</b> markup in the <b>SiSU</b> manual. +<p> <br> Note: Master documents may be prepared in a similar way to regular documents, and processing will occur normally if a .sst file is renamed .ssm without requiring any other documents; the .ssm marker flags that the document may contain other documents. -<P> -<BR> - +<p> <br> Note: a secondary file of the composite document is built prior to processing -with the same prefix and the suffix ._sst [^18] -<P> -<BR> - -<<A HREF="http://www.sisudoc.org/sisu/sisu_markup">http://www.sisudoc.org/sisu/sisu_markup</A>> -<P> -<BR> - -<<A HREF="http://www.sisudoc.org/sisu/sisu_manual">http://www.sisudoc.org/sisu/sisu_manual</A>> -<P> -<A NAME="lbBY"> </A> -<H2>12.1.3 SISU INSERT FILES (.SSI)</H2> - -<P> -<BR> +with the same prefix and the suffix ._sst [^19] +<p> +<h2><a name='sect49' href='#toc49'>Sisu Insert Files (.ssi)</a></h2> +<p> +<br> Inserts are documents prepared solely for the purpose of being incorporated -into one or more master documents. They resemble regular -<B>SiSU</B> - -text files except they are ignored by the -<B>SiSU</B> - -processor. Making a file a .ssi file is a quick and convenient way of flagging -that it is not intended that the file should be processed on its own. -<P> -<A NAME="lbBZ"> </A> -<H2>12.2 SISUPOD, ZIPPED BINARY CONTAINER (SISUPOD.ZIP, .SSP)</H2> - -<P> -<BR> - -A sisupod is a zipped -<B>SiSU</B> - -text file or set of -<B>SiSU</B> - -text files and any associated images that they contain (this will be extended -to include sound and multimedia-files) -<P> -<BR> - -<B>SiSU</B> - -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. -<P> -<BR> - -The structure of the sisupod is such that it may for example contain a single -document and its associated images; a master document and its associated -documents and anything else; or the zipped contents of a whole directory of -prepared -<B>SiSU</B> - -documents. -<P> -<BR> - +into one or more master documents. They resemble regular <b>SiSU</b> text files +except they are ignored by the <b>SiSU</b> processor. Making a file a .ssi file +is a quick and convenient way of flagging that it is not intended that +the file should be processed on its own. +<p> +<h2><a name='sect50' href='#toc50'>Sisupod, Zipped Binary Container +(sisupod.zip, .ssp)</a></h2> + +<p> <br> +A sisupod is a zipped <b>SiSU</b> text file or set of <b>SiSU</b> text files and any +associated images that they contain (this will be extended to include sound +and multimedia-files) +<p> +<dl> + +<dt><b>SiSU</b> </dt> +<dd><i>plaintext</i> files rely on a recognised directory +structure to find contents such as images associated with documents, but +all images for example for all documents contained in a directory are located +in the sub-directory _sisu/image. Without the ability to create a sisupod +it can be inconvenient to manually identify all other files associated +with a document. A sisupod automatically bundles all associated files with +the document that is turned into a pod. +<p> <br> +The structure of the sisupod is such that it may for example contain a +single document and its associated images; a master document and its associated +documents and anything else; or the zipped contents of a whole directory +of prepared <b>SiSU</b> documents. +<p> <br> The command to create a sisupod is: -<P> -<BR> - -<BR> sisu -S [filename] -<P> -<BR> +<p> <br> + sisu -S [filename]<br> +<p> <br> Alternatively, make a pod of the contents of a whole directory: -<P> -<BR> - -<BR> sisu -S -<P> -<BR> - -<B>SiSU</B> - -processing can be done directly against a sisupod; which may be located locally -or on a remote server for which a url is provided. -<P> -<BR> - -<<A HREF="http://www.sisudoc.org/sisu/sisu_commands">http://www.sisudoc.org/sisu/sisu_commands</A>> -<P> -<BR> - -<<A HREF="http://www.sisudoc.org/sisu/sisu_manual">http://www.sisudoc.org/sisu/sisu_manual</A>> -<P> -<A NAME="lbCA"> </A> -<H2>13. EXPERIMENTAL ALTERNATIVE INPUT REPRESENTATIONS</H2> - -<BR> - -<P> -<A NAME="lbCB"> </A> -<H2>13.1 ALTERNATIVE XML</H2> - -<P> -<BR> - -<B>SiSU</B> - -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. -<P> -<BR> - -<B>convert from sst to simple xml representations (sax, dom and node):</B> - -<P> -<BR> - -<BR> sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard] -<P> -<BR> - -<BR> sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard] -<P> -<BR> - -<BR> sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard] -<P> -<BR> - -<B>convert to sst from any sisu xml representation (sax, dom and node):</B> - -<P> -<BR> - -<BR> sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] -<P> -<BR> - -or the same: -<P> -<BR> - -<BR> sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] -<P> -<A NAME="lbCC"> </A> -<H2>13.1.1 XML SAX REPRESENTATION</H2> - -<P> -<BR> - -To convert from sst to simple xml (sax) representation: -<P> -<BR> - -<BR> sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard] -<P> -<BR> - -To convert from any sisu xml representation back to sst -<P> -<BR> - -<BR> sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] -<P> -<BR> - -or the same: -<P> -<BR> - -<BR> sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] -<P> -<A NAME="lbCD"> </A> -<H2>13.1.2 XML DOM REPRESENTATION</H2> - -<P> -<BR> - -To convert from sst to simple xml (dom) representation: -<P> -<BR> - -<BR> sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard] -<P> -<BR> - -To convert from any sisu xml representation back to sst -<P> -<BR> - -<BR> sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] -<P> -<BR> - -or the same: -<P> -<BR> - -<BR> sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] -<P> -<A NAME="lbCE"> </A> -<H2>13.1.3 XML NODE REPRESENTATION</H2> - -<P> -<BR> - -To convert from sst to simple xml (node) representation: -<P> -<BR> - -<BR> sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard] -<P> -<BR> - -To convert from any sisu xml representation back to sst -<P> -<BR> - -<BR> sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] -<P> -<BR> - -or the same: -<P> -<BR> - -<BR> sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] -<P> -<A NAME="lbCF"> </A> -<H2>14. CONFIGURATION</H2> - -<BR> - -<P> -<A NAME="lbCG"> </A> -<H2>14.1 DETERMINING THE CURRENT CONFIGURATION</H2> - -<P> -<BR> - -Information on the current configuration of -<B>SiSU</B> - -should be available with the help command: -<P> -<BR> - -<BR> sisu -v -<P> -<BR> - -which is an alias for: -<P> -<BR> - -<BR> sisu --help env -<P> -<BR> - -Either of these should be executed from within a directory that contains sisu -markup source documents. -<P> -<A NAME="lbCH"> </A> -<H2>14.2 CONFIGURATION FILES (CONFIG.YML)</H2> - -<P> -<BR> - -<B>SiSU</B> - -configration parameters are adjusted in the configuration file, which can be -used to override the defaults set. This includes such things as which directory -interim processing should be done in and where the generated output should be -placed. -<P> -<BR> - -The -<B>SiSU</B> - -configuration file is a yaml file, which means indentation is significant. -<P> -<BR> - -<B>SiSU</B> - -resource configuration is determined by looking at the following files if they -exist: -<P> -<BR> - -<BR> ./_sisu/sisurc.yml -<P> -<BR> - -<BR> ~/.sisu/sisurc.yml -<P> -<BR> - -<BR> /etc/sisu/sisurc.yml -<P> -<BR> +<p> <br> + sisu -S<br> +<p> <br> +<b>SiSU</b> processing can be done directly against a sisupod; which may be located +locally or on a remote server for which a url is provided. +<p> <br> +<<a href='http://www.sisudoc.org/sisu/sisu_commands'>http://www.sisudoc.org/sisu/sisu_commands</a> +> +<p> <br> +<<a href='http://www.sisudoc.org/sisu/sisu_manual'>http://www.sisudoc.org/sisu/sisu_manual</a> +> +<p> </dd> +</dl> + +<h2><a name='sect51' href='#toc51'>Configuration</a></h2> +<br> + +<p> +<h2><a name='sect52' href='#toc52'>Configuration Files</a></h2> + +<p> +<h2><a name='sect53' href='#toc53'>Config.yml</a></h2> + +<p> <br> +<b>SiSU</b> configration parameters are adjusted in the configuration file, which +can be used to override the defaults set. This includes such things as which +directory interim processing should be done in and where the generated +output should be placed. +<p> <br> +The <b>SiSU</b> configuration file is a yaml file, which means indentation is +significant. +<p> <br> +<b>SiSU</b> resource configuration is determined by looking at the following files +if they exist: +<p> <br> + ./_sisu/v4/sisurc.yml<br> + +<p> <br> + ./_sisu/sisurc.yml<br> + +<p> <br> + ~/.sisu/v4/sisurc.yml<br> + +<p> <br> + ~/.sisu/sisurc.yml<br> + +<p> <br> + /etc/sisu/v4/sisurc.yml<br> + +<p> <br> + /etc/sisu/sisurc.yml<br> + +<p> <br> The search is in the order listed, and the first one found is used. -<P> -<BR> - +<p> <br> In the absence of instructions in any of these it falls back to the internal program defaults. -<P> -<BR> - -Configuration determines the output and processing directories and the database -access details. -<P> -<BR> - -If -<B>SiSU</B> - -is installed a sample sisurc.yml may be found in /etc/sisu/sisurc.yml -<P> -<A NAME="lbCI"> </A> -<H2>15. SKINS</H2> - -<BR> - -<P> -<BR> - -Skins modify the default appearance of document output on a document, -directory, or site wide basis. Skins are looked for in the following locations: -<P> -<BR> - -<BR> ./_sisu/skin -<P> -<BR> - -<BR> ~/.sisu/skin -<P> -<BR> - -<BR> /etc/sisu/skin -<P> -<BR> - -<B>Within the skin directory</B> - -are the following the default sub-directories for document skins: -<P> -<BR> - -<BR> ./skin/doc -<P> -<BR> - -<BR> ./skin/dir -<P> -<BR> - -<BR> ./skin/site -<P> -<BR> - -A skin is placed in the appropriate directory and the file named skin_[name].rb -<P> -<BR> - -The skin itself is a ruby file which modifies the default appearances set in -the program. -<P> -<A NAME="lbCJ"> </A> -<H2>15.1 DOCUMENT SKIN</H2> - -<P> -<BR> - -Documents take on a document skin, if the header of the document specifies a -skin to be used. -<P> -<PRE> -@skin: skin_united_nations -</PRE> - -<P> -<A NAME="lbCK"> </A> -<H2>15.2 DIRECTORY SKIN</H2> - -<P> -<BR> - -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). -<P> -<BR> - -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. -<P> -<A NAME="lbCL"> </A> -<H2>15.3 SITE SKIN</H2> - -<P> -<BR> - -A site skin, modifies the program default skin. -<P> -<A NAME="lbCM"> </A> -<H2>15.4 SAMPLE SKINS</H2> - -<P> -<BR> - -With -<B>SiSU</B> - -installed sample skins may be found in: -<P> -<BR> - -<BR> /etc/sisu/skin/doc and -<BR> /usr/share/doc/sisu/markup-samples/samples/_sisu/skin/doc -<P> -<BR> - -(or equivalent directory) and if sisu-markup-samples is installed also under: -<P> -<BR> - -<BR> /usr/share/doc/sisu/markup-samples-non-free/samples/_sisu/skin/doc -<P> -<BR> - -Samples of list.yml and promo.yml (which are used to create the right column -list) may be found in: -<P> -<BR> - -<BR> /usr/share/doc/sisu/markup-samples-non-free/samples/_sisu/skin/yml (or -<BR> equivalent directory) -<P> -<A NAME="lbCN"> </A> -<H2>16. CSS - CASCADING STYLE SHEETS (FOR HTML, XHTML AND XML)</H2> - -<BR> - -<P> -<BR> - -CSS files to modify the appearance of -<B>SiSU</B> - -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. -<P> -<BR> - -The basic CSS file for html output is html.css, placing a file of that name in -directory _sisu/css or equivalent will result in the default file of that name -being overwritten. -<P> -<BR> - -HTML: html.css -<P> -<BR> - -XML DOM: dom.css -<P> -<BR> - -XML SAX: sax.css -<P> -<BR> - -XHTML: xhtml.css -<P> -<BR> - -The default homepage may use homepage.css or html.css -<P> -<BR> - +<p> <br> +Configuration determines the output and processing directories and the +database access details. +<p> <br> + +<p>If <b>SiSU</b> is installed a sample sisurc.yml may be found in /etc/sisu/sisurc.yml + +<p> +<h2><a name='sect54' href='#toc54'>Sisu_document_make</a></h2> + +<p> <br> +Most sisu document headers relate to metadata, the exception is the @make: +header which provides processing related information. The default contents +of the @make header may be set by placing them in a file sisu_document_make. + +<p> <br> +The search order is as for resource configuration: +<p> <br> + ./_sisu/v4/sisu_document_make<br> + +<p> <br> + ./_sisu/sisu_document_make<br> + +<p> <br> + ~/.sisu/v4/sisu_document_make<br> + +<p> <br> + ~/.sisu/sisu_document_make<br> + +<p> <br> + /etc/sisu/v4/sisu_document_make<br> + +<p> <br> + /etc/sisu/sisu_document_make<br> + +<p> <br> +A sample sisu_document_make can be found in the _sisu/ directory under +along with the provided sisu markup samples. +<p> +<h2><a name='sect55' href='#toc55'>Css - Cascading Style Sheets +(for Html, Xhtml and Xml)</a></h2> +<br> + +<p> <br> +CSS files to modify the appearance of <b>SiSU</b> html, <i>XHTML</i> or <i>XML</i> may be placed +in the configuration directory: ./_sisu/css ; ~/.sisu/css or; /etc/sisu/css +and these will be copied to the output directories with the command sisu +-CC. +<p> <br> +The basic CSS file for html output is html. css, placing a file of that +name in directory _sisu/css or equivalent will result in the default file +of that name being overwritten. +<p> <br> +<i>HTML:</i> html. css +<p> <br> +<i>XML</i> DOM: dom.css +<p> <br> +<i>XML</i> SAX: sax.css +<p> <br> +<i>XHTML:</i> xhtml. css +<p> <br> +The default homepage may use homepage.css or html. css +<p> <br> Under consideration is to permit the placement of a CSS file with a different -name in directory _sisu/css directory or equivalent, and change the default CSS -file that is looked for in a skin.[^19] -<P> -<A NAME="lbCO"> </A> -<H2>17. ORGANISING CONTENT - DIRECTORY STRUCTURE AND MAPPING</H2> - -<BR> - -<P> -<BR> - -<B>SiSU</B> - -v3 has new options for the source directory tree, and output directory +name in directory _sisu/css directory or equivalent.[^20] +<p> +<h2><a name='sect56' href='#toc56'>Organising Content +- Directory Structure and Mapping</a></h2> +<br> + +<p> <br> +<b>SiSU</b> v3 has new options for the source directory tree, and output directory structures of which there are 3 alternatives. -<P> -<A NAME="lbCP"> </A> -<H2>17.1 DOCUMENT SOURCE DIRECTORY</H2> - -<P> -<BR> +<p> +<h2><a name='sect57' href='#toc57'>Document Source Directory</a></h2> +<p> +<br> The document source directory is the directory in which sisu processing commands are given. It contains the sisu source files (.sst .ssm .ssi), or -(for sisu v3 may contain) subdirectories with language codes which contain the -sisu source files, so all English files would go in subdirectory en/, French in -fr/, Spanish in es/ and so on. ISO 639-1 codes are used (as varied by po4a). A -list of available languages (and possible sub-directory names) can be obtained -with the command "sisu --help lang" The list of languages is limited to -langagues supported by XeTeX polyglosia. -<P> -<A NAME="lbCQ"> </A> -<H2>17.1.1 GENERAL DIRECTORIES</H2> - -<P> -<PRE> -% files stored at this level e.g. sisu_manual.sst or +(for sisu v3 may contain) subdirectories with language codes which contain +the sisu source files, so all English files would go in subdirectory en/, +French in fr/, Spanish in es/ and so on. ISO 639-1 codes are used (as varied +by po4a). A list of available languages (and possible sub-directory names) +can be obtained with the command "sisu --help lang" The list of languages +is limited to langagues supported by XeTeX polyglosia. +<p> +<h2><a name='sect58' href='#toc58'>General Directories</a></h2> + +<p> +<br> +<pre>% files stored at this level e.g. sisu_manual.sst or % for sisu v3 may be under language sub-directories % e.g. -% configuration file e.g. sisurc.yml -% skins in various skin directories doc, dir, site, yml -</PRE> - -<P> -<A NAME="lbCR"> </A> -<H2>17.2 DOCUMENT OUTPUT DIRECTORY STRUCTURES</H2> - -<P> -<A NAME="lbCS"> </A> -<H2>17.2.1 OUTPUT DIRECTORY ROOT</H2> + ./subject_name/en + ./subject_name/fr + ./subject_name/es + ./subject_name/_sisu + ./subject_name/_sisu/css + ./subject_name/_sisu/image +</pre> +<p> +<h2><a name='sect59' href='#toc59'>Document Output Directory Structures</a></h2> -<P> -<BR> +<p> +<h2><a name='sect60' href='#toc60'>Output Directory Root</a></h2> +<p> <br> The output directory root can be set in the sisurc.yml file. Under the root, -subdirectories are made for each directory in which a document set resides. If -you have a directory named poems or conventions, that directory will be created -under the output directory root and the output for all documents contained in -the directory of a particular name will be generated to subdirectories 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 +subdirectories are made for each directory in which a document set resides. +If you have a directory named poems or conventions, that directory will +be created under the output directory root and the output for all documents +contained in the directory of a particular name will be generated to subdirectories +beneath that directory (poem or conventions). A document will be placed +in a subdirectory of the same name as the document with the filetype identifier stripped (.sst .ssm) -<P> -<BR> - -The last part of a directory path, representing the sub-directory in which a -document set resides, is the directory name that will be used for the output -directory. This has implications for the organisation of document collections -as it could make sense to place documents of a particular subject, or type -within a directory identifying them. This grouping as suggested could be by -subject (sales_law, english_literature); or just as conveniently by some other -classification (X University). The mapping means it is also possible to place -in the same output directory documents that are for organisational purposes -kept separately, for example documents on a given subject of two different -institutions may be kept in two different directories of the same name, under a -directory named after each institution, and these would be output to the same -output directory. Skins could be associated with each institution on a -directory basis and resulting documents will take on the appropriate different -appearance. -<P> -<A NAME="lbCT"> </A> -<H2>17.2.2 ALTERNATIVE OUTPUT STRUCTURES</H2> - -<P> -<BR> - -There are 3 possibile output structures described as being, by language, by -filetype or by filename, the selection is made in sisurc.yml -<P> -<PRE> -#% output_dir_structure_by: language; filetype; or filename +<p> <br> +The last part of a directory path, representing the sub-directory in which +a document set resides, is the directory name that will be used for the +output directory. This has implications for the organisation of document +collections as it could make sense to place documents of a particular subject, +or type within a directory identifying them. This grouping as suggested +could be by subject (sales_law, english_literature); or just as conveniently +by some other classification (X University). The mapping means it is also +possible to place in the same output directory documents that are for organisational +purposes kept separately, for example documents on a given subject of two +different institutions may be kept in two different directories of the +same name, under a directory named after each institution, and these would +be output to the same output directory. Skins could be associated with each +institution on a directory basis and resulting documents will take on the +appropriate different appearance. +<p> +<h2><a name='sect61' href='#toc61'>Alternative Output Structures</a></h2> + +<p> <br> +There are 3 possibile output structures described as being, by language, +by filetype or by filename, the selection is made in sisurc.yml +<p> <br> +<pre>#% output_dir_structure_by: language; filetype; or filename output_dir_structure_by: language #(language & filetype, preferred?) #output_dir_structure_by: filetype -#output_dir_structure_by: filename #(default, closest to original v1 & v2) -</PRE> - -<P> -<A NAME="lbCU"> </A> -<H2>17.2.3 BY LANGUAGE</H2> - -<P> -<BR> - -The by language directory structure places output files -<P> -<BR> - -The by language directory structure separates output files by language code -(all files of a given language), and within the language directory by filetype. -<P> -<BR> - -Its selection is configured in sisurc.yml -<P> -<BR> - +#output_dir_structure_by: filename #(default, closest to original v1 & +v2) +</pre> +<p> +<h2><a name='sect62' href='#toc62'>by Language</a></h2> + +<p> <br> + +<p>The by language directory structure places output files +<p> <br> +The by language directory structure separates output files by language +code (all files of a given language), and within the language directory +by filetype. +<p> <br> + +<p>Its selection is configured in sisurc.yml +<p> <br> output_dir_structure_by: language -<P> -<PRE> - |-- en +<p> <br> +<pre> |-- en |-- epub |-- hashes |-- html @@ -4038,47 +2577,37 @@ output_dir_structure_by: language | |-- sitemaps | |-- txt | |-- xhtml - | `-- xml + | ‘-- xml |-- po4a - | `-- live-manual + | ‘-- live-manual | |-- po | |-- fr - | `-- pot - `-- _sisu + | ‘-- pot + ‘-- _sisu |-- css |-- image |-- image_sys -> ../../_sisu/image_sys - `-- xml + ‘-- xml |-- rnc |-- rng - `-- xsd -</PRE> - -<P> -<BR> - + ‘-- xsd +</pre> +<p> <br> #by: language subject_dir/en/manifest/filename.html -<P> -<A NAME="lbCV"> </A> -<H2>17.2.4 BY FILETYPE</H2> +<p> +<h2><a name='sect63' href='#toc63'>by Filetype</a></h2> -<P> -<BR> - -The by filetype directory structure separates output files by filetype, all -html files in one directory pdfs in another and so on. Filenames are given a -language extension. -<P> -<BR> - -Its selection is configured in sisurc.yml -<P> -<BR> +<p> <br> +The by filetype directory structure separates output files by filetype, +all html files in one directory pdfs in another and so on. Filenames are +given a language extension. +<p> <br> +<p>Its selection is configured in sisurc.yml +<p> <br> output_dir_structure_by: filetype -<P> -<PRE> - |-- epub +<p> <br> +<pre> |-- epub |-- hashes |-- html |-- viral_spiral.david_bollier @@ -4090,76 +2619,61 @@ output_dir_structure_by: filetype |-- live-manual | |-- po | |-- fr - | `-- pot + | ‘-- pot |-- _sisu | |-- css | |-- image | |-- image_sys -> ../../_sisu/image_sys - | `-- xml + | ‘-- xml | |-- rnc | |-- rng - | `-- xsd + | ‘-- xsd |-- sitemaps |-- txt |-- xhtml - `-- xml -</PRE> - -<P> -<BR> - + ‘-- xml +</pre> +<p> <br> #by: filetype subject_dir/html/filename/manifest.en.html -<P> -<A NAME="lbCW"> </A> -<H2>17.2.5 BY FILENAME</H2> - -<P> -<BR> +<p> +<h2><a name='sect64' href='#toc64'>by Filename</a></h2> -The by filename directory structure places most output of a particular file -(the different filetypes) in a common directory. -<P> -<BR> - -Its selection is configured in sisurc.yml -<P> -<BR> +<p> <br> +The by filename directory structure places most output of a particular +file (the different filetypes) in a common directory. +<p> <br> +<p>Its selection is configured in sisurc.yml +<p> <br> output_dir_structure_by: filename -<P> -<PRE> - |-- epub +<p> <br> +<pre> |-- epub |-- po4a |-- live-manual | |-- po | |-- fr - | `-- pot + | ‘-- pot |-- _sisu | |-- css | |-- image | |-- image_sys -> ../../_sisu/image_sys - | `-- xml + | ‘-- xml | |-- rnc | |-- rng - | `-- xsd + | ‘-- xsd |-- sitemaps |-- src |-- pod - `-- viral_spiral.david_bollier -</PRE> - -<P> -<BR> - + ‘-- viral_spiral.david_bollier +</pre> +<p> <br> #by: filename subject_dir/filename/manifest.en.html -<P> -<A NAME="lbCX"> </A> -<H2>17.2.6 REMOTE DIRECTORIES</H2> - -<P> -<PRE> -./subject_name/ -% containing sub_directories named after the generated files from which they are made +<p> +<h2><a name='sect65' href='#toc65'>Remote Directories</a></h2> + +<p> <br> +<pre>% containing sub_directories named after the generated files from which +they are made ./subject_name/src % contains shared source files text and binary e.g. sisu_manual.sst and sisu_manual.sst.zip ./subject_name/_sisu @@ -4170,16 +2684,12 @@ output_dir_structure_by: filename ./subject_name/_sisu/image % images for documents contained in this directory ./subject_name/_sisu/mm -</PRE> - -<P> -<A NAME="lbCY"> </A> -<H2>17.2.7 SISUPOD</H2> +</pre> +<p> +<h2><a name='sect66' href='#toc66'>Sisupod</a></h2> -<P> -<PRE> -./sisupod/ -% files stored at this level e.g. sisu_manual.sst +<p> <br> +<pre>% files stored at this level e.g. sisu_manual.sst ./sisupod/_sisu % configuration file e.g. sisurc.yml ./sisupod/_sisu/skin @@ -4188,528 +2698,460 @@ output_dir_structure_by: filename ./sisupod/_sisu/image % images for documents contained in this directory ./sisupod/_sisu/mm -</PRE> - -<P> -<A NAME="lbCZ"> </A> -<H2>17.3 ORGANISING CONTENT</H2> +</pre> +<p> +<h2><a name='sect67' href='#toc67'>Organising Content</a></h2> -<P> -<A NAME="lbDA"> </A> -<H2>18. HOMEPAGES</H2> - -<BR> - -<P> -<BR> - -<B>SiSU</B> - -is about the ability to auto-generate documents. Home pages are regarded as -custom built items, and are not created by -<B>SiSU.</B> - -More accurately, -<B>SiSU</B> +<p> +<h2><a name='sect68' href='#toc68'>Homepages</a></h2> +<br> +<p> <br> +<b>SiSU</b> is about the ability to auto-generate documents. Home pages are regarded +as custom built items, and are not created by <b>SiSU.</b> More accurately, <b>SiSU</b> has a default home page, which will not be appropriate for use with other -sites, and the means to provide your own home page instead in one of two ways -as part of a site's configuration, these being: -<P> -<BR> - +sites, and the means to provide your own home page instead in one of two +ways as part of a site’s configuration, these being: +<p> <br> 1. through placing your home page and other custom built documents in the subdirectory _sisu/home/ (this probably being the easier and more convenient option) -<P> -<BR> - +<p> <br> 2. through providing what you want as the home page in a skin, -<P> -<BR> - +<p> <br> Document sets are contained in directories, usually organised by site or -subject. Each directory can/should have its own homepage. See the section on -directory structure and organisation of content. -<P> -<A NAME="lbDB"> </A> -<H2>18.1 HOME PAGE AND OTHER CUSTOM BUILT PAGES IN A SUB-DIRECTORY</H2> - -<P> -<BR> - -Custom built pages, including the home page index.html may be placed within the -configuration directory _sisu/home/ in any of the locations that is searched -for the configuration directory, namely ./_sisu ; ~/_sisu ; /etc/sisu From -there they are copied to the root of the output directory with the command: -<P> -<BR> - -<BR> sisu -CC -<P> -<A NAME="lbDC"> </A> -<H2>18.2 HOME PAGE WITHIN A SKIN</H2> - -<P> -<BR> - -Skins are described in a separate section, but basically are a file written in -the programming language -<B>Ruby</B> - -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. -<P> -<BR> - -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 -<P> -<PRE> - 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 -</PRE> - -<P> -<A NAME="lbDD"> </A> -<H2>19. MARKUP AND OUTPUT EXAMPLES</H2> - -<BR> - -<P> -<A NAME="lbDE"> </A> -<H2>19.1 MARKUP EXAMPLES</H2> - -<P> -<BR> - -Current markup examples and document output samples are provided at -<<A HREF="http://www.jus.uio.no/sisu/SiSU/examples.html">http://www.jus.uio.no/sisu/SiSU/examples.html</A>> -<P> -<BR> - -For some documents hardly any markup at all is required at all, other than a -header, and an indication that the levels to be taken into account by the -program in generating its output are. -<P> -<A NAME="lbDF"> </A> -<H2>20. SISU SEARCH - INTRODUCTION</H2> - -<BR> - -<P> -<BR> - -<B>SiSU</B> - -output can easily and conveniently be indexed by a number of standalone +subject. Each directory can/should have its own homepage. See the section +on directory structure and organisation of content. +<p> +<h2><a name='sect69' href='#toc69'>Home Page and Other +Custom Built Pages in a Sub-directory</a></h2> + +<p> <br> +Custom built pages, including the home page index.html may be placed within +the configuration directory _sisu/home/ in any of the locations that is +searched for the configuration directory, namely ./_sisu ; ~/_sisu ; /etc/sisu +From there they are copied to the root of the output directory with the +command: +<p> <br> + sisu -CC<br> + +<p> +<h2><a name='sect70' href='#toc70'>Markup and Output Examples</a></h2> +<br> + +<p> +<h2><a name='sect71' href='#toc71'>Markup Examples</a></h2> + +<p> <br> +Current markup examples and document output samples are provided off <<a href='http://sisudoc.org'>http://sisudoc.org</a> +> +or <<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> +> and in the sisu -markup-sample package available +off <<a href='http://sources.sisudoc.org'>http://sources.sisudoc.org</a> +> +<p> <br> +For some documents hardly any markup at all is required at all, other than +a header, and an indication that the levels to be taken into account by +the program in generating its output are. +<p> +<h2><a name='sect72' href='#toc72'>Sisu Markup Samples</a></h2> + +<p> <br> +A few additional sample books prepared as sisu markup samples, output formats +to be generated using <b>SiSU</b> are contained in a separate package sisu -markup-samples. +sisu -markup-samples contains books (prepared using sisu markup), that were +released by their authors various licenses mostly different Creative Commons +licences that do not permit inclusion in the <b>Debian</b> Project as they have +requirements that do not meet the <b>Debian</b> Free Software Guidelines for various +reasons, most commonly that they require that the original substantive +text remain unchanged, and sometimes that the works be used only non-commercially. + +<p> <br> +<i>Accelerando,</i> Charles Stross (2005) accelerando.charles_stross.sst +<p> <br> +<i>Alice’s</i> Adventures in Wonderland, Lewis Carroll (1865) alices_adventures_in_wonderland.lewis_carroll.sst + +<p> <br> +<i>CONTENT,</i> Cory Doctorow (2008) content.cory_doctorow.sst +<p> <br> +<i>Democratizing</i> Innovation, Eric von Hippel (2005) democratizing_innovation.eric_von_hippel.sst + +<p> <br> +<i>Down</i> and Out in the Magic Kingdom, Cory Doctorow (2003) down_and_out_in_the_magic_kingdom.cory_doctorow.sst + +<p> <br> +<i>For</i> the Win, Cory Doctorow (2010) for_the_win.cory_doctorow.sst +<p> <br> +<i>Free</i> as in Freedom - Richard Stallman’s Crusade for Free Software, Sam Williams +(2002) free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst + +<p> <br> +<i>Free</i> as in Freedom 2.0 - Richard Stallman and the Free Software Revolution, +Sam Williams (2002), Richard M. Stallman (2010) free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst + +<p> <br> +<i>Free</i> Culture - How Big Media Uses Technology and the Law to Lock Down Culture +and Control Creativity, Lawrence Lessig (2004) free_culture.lawrence_lessig.sst + +<p> <br> +<i>Free</i> For All - How Linux and the Free Software Movement Undercut the High +Tech Titans, Peter Wayner (2002) free_for_all.peter_wayner.sst +<p> <br> +<i>GNU</i> GENERAL PUBLIC LICENSE v2, Free Software Foundation (1991) gpl2.fsf.sst + +<p> <br> +<i>GNU</i> GENERAL PUBLIC LICENSE v3, Free Software Foundation (2007) gpl3.fsf.sst + +<p> <br> +<i>Gulliver’s</i> Travels, Jonathan Swift (1726 / 1735) gullivers_travels.jonathan_swift.sst + +<p> <br> +<i>Little</i> Brother, Cory Doctorow (2008) little_brother.cory_doctorow.sst +<p> <br> +<i>The</i> Cathederal and the Bazaar, Eric Raymond (2000) the_cathedral_and_the_bazaar.eric_s_raymond.sst + +<p> <br> +<i>The</i> Public Domain - Enclosing the Commons of the Mind, James Boyle (2008) + +<p>the_public_domain.james_boyle.sst +<p> <br> +<i>The</i> Wealth of Networks - How Social Production Transforms Markets and Freedom, +Yochai Benkler (2006) the_wealth_of_networks.yochai_benkler.sst +<p> <br> +<i>Through</i> the Looking Glass, Lewis Carroll (1871) through_the_looking_glass.lewis_carroll.sst + +<p> <br> +<i>Two</i> Bits - The Cultural Significance of Free Software, Christopher Kelty +(2008) two_bits.christopher_kelty.sst +<p> <br> +<i>UN</i> Contracts for International Sale of Goods, UN (1980) un_contracts_international_sale_of_goods_convention_1980.sst + +<p> <br> +<i>Viral</i> Spiral, David Bollier (2008) viral_spiral.david_bollier.sst +<p> +<h2><a name='sect73' href='#toc73'>Sisu Search +- Introduction</a></h2> +<br> + +<p> <br> +<b>SiSU</b> output can easily and conveniently be indexed by a number of standalone indexing tools, such as Lucene, Hyperestraier. -<P> -<BR> - -Because the document structure of sites created is clearly defined, and 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. -<P> -<BR> - -In addition to this -<B>SiSU</B> - -has the ability to populate a relational sql type database with documents at an -object level, with objects numbers that are shared across different output -types, which make them searchable with that degree of granularity. Basically, -your match criteria is met by these documents and at these locations within -each document, which can be viewed within the database directly or in various -output formats. -<P> -<A NAME="lbDG"> </A> -<H2>21. SQL</H2> - -<BR> - -<P> -<A NAME="lbDH"> </A> -<H2>21.1 POPULATING SQL TYPE DATABASES</H2> - -<P> -<BR> - -<B>SiSU</B> - -feeds sisu markupd documents into sql type databases PostgreSQL[^20] and/or -SQLite[^21] database together with information related to document structure. -<P> -<BR> - -This is one of the more interesting output forms, as all the structural data of -the documents are retained (though can be ignored by the user of the database -should they so choose). All site texts/documents are (currently) streamed to -four tables: -<P> -<BR> - -<BR> * one containing semantic (and other) headers, including, title, author, -<BR> subject, (the Dublin Core...); -<P> -<BR> - -<BR> * another the substantive texts by individual "paragraph" (or object) - -<BR> along with structural information, each paragraph being identifiable by its -<BR> paragraph number (if it has one which almost all of them do), and the -<BR> substantive text of each paragraph quite naturally being searchable (both in -<BR> formatted and clean text versions for searching); and -<P> -<BR> - -<BR> * a third containing endnotes cross-referenced back to the paragraph from -<BR> which they are referenced (both in formatted and clean text versions for -<BR> searching). -<P> -<BR> - -<BR> * a fourth table with a one to one relation with the headers table contains -<BR> full text versions of output, eg. pdf, html, xml, and ascii. -<P> -<BR> - +<p> <br> +Because the document structure of sites created is clearly defined, and +the text <i>object</i> citation system is available hypothetically at least, for +all forms of output, it is possible to search the sql database, and either +read results from that database, or just as simply map the results to the +html output, which has richer text markup. +<p> <br> +In addition to this <b>SiSU</b> has the ability to populate a relational sql type +database with documents at an object level, with objects numbers that are +shared across different output types, which make them searchable with that +degree of granularity. Basically, your match criteria is met by these documents +and at these locations within each document, which can be viewed within +the database directly or in various output formats. +<p> +<h2><a name='sect74' href='#toc74'>Sql</a></h2> +<br> + +<p> +<h2><a name='sect75' href='#toc75'>Populating Sql Type Databases</a></h2> + +<p> <br> +<b>SiSU</b> feeds sisu markupd documents into sql type databases <i>PostgreSQL</i> [^21] +and/or <i>SQLite</i> [^22] database together with information related to document +structure. +<p> <br> +This is one of the more interesting output forms, as all the structural +data of the documents are retained (though can be ignored by the user of +the database should they so choose). All site texts/documents are (currently) +streamed to four tables: +<p> <br> + * one containing semantic (and other) headers, including, title, author,<br> + subject, (the<br> + .I Dublin Core.<br> + ..);<br> + +<p> <br> + * another the substantive texts by individual "paragraph" (or object) +-<br> + along with structural information, each paragraph being identifiable +by its<br> + paragraph number (if it has one which almost all of them do), and the<br> + substantive text of each paragraph quite naturally being searchable +(both in<br> + formatted and clean text versions for searching); and<br> + +<p> <br> + * a third containing endnotes cross-referenced back to the paragraph from<br> + which they are referenced (both in formatted and clean text versions +for<br> + searching).<br> + +<p> <br> + * a fourth table with a one to one relation with the headers table contains<br> + full text versions of output, eg. pdf, html, xml, and<br> + .I ascii.<br> + +<p> <br> There is of course the possibility to add further structures. -<P> -<BR> - -At this level -<B>SiSU</B> - -loads a relational database with documents chunked into objects, their smallest -logical structurally constituent parts, as text objects, with their object -citation number and all other structural information needed to construct the -document. Text is stored (at this text object level) with and without -elementary markup tagging, the stripped version being so as to facilitate ease -of searching. -<P> -<BR> - +<p> <br> +At this level <b>SiSU</b> loads a relational database with documents chunked into +objects, their smallest logical structurally constituent parts, as text +objects, with their object citation number and all other structural information +needed to construct the document. Text is stored (at this text object level) +with and without elementary markup tagging, the stripped version being +so as to facilitate ease of searching. +<p> <br> Being able to search a relational database at an object level with the -<B>SiSU</B> - -citation system is an effective way of locating content generated by -<B>SiSU.</B> - -As individual text objects of a document stored (and indexed) together with -object numbers, and all versions of the document have the same numbering, +<b>SiSU</b> citation system is an effective way of locating content generated +by <b>SiSU.</b> As individual text objects of a document stored (and indexed) together +with object numbers, and all versions of the document have the same numbering, complex searches can be tailored to return just the locations of the search results relevant for all available output formats, with live links to the precise locations in the database or in html/xml documents; or, the structural information provided makes it possible to search the full contents of the -database and have headings in which search content appears, or to search only -headings etc. (as the Dublin Core is incorporated it is easy to make use of -that as well). -<P> -<A NAME="lbDI"> </A> -<H2>22. POSTGRESQL</H2> - -<BR> - -<P> -<A NAME="lbDJ"> </A> -<H2>22.1 NAME</H2> - -<P> -<BR> - -<B>SiSU</B> - -- Structured information, Serialized Units - a document publishing system, -postgresql dependency package -<P> -<A NAME="lbDK"> </A> -<H2>22.2 DESCRIPTION</H2> - -<P> -<BR> - -Information related to using postgresql with sisu (and related to the -sisu_postgresql dependency package, which is a dummy package to install -dependencies needed for -<B>SiSU</B> - -to populate a postgresql database, this being part of -<B>SiSU</B> - -- man sisu). -<P> -<A NAME="lbDL"> </A> -<H2>22.3 SYNOPSIS</H2> - -<P> -<BR> - -<BR> sisu -D [instruction] [filename/wildcard if required] -<P> -<BR> - -<BR> sisu -D --pg --[instruction] [filename/wildcard if required] -<P> -<A NAME="lbDM"> </A> -<H2>22.4 COMMANDS</H2> - -<P> -<BR> - -Mappings to two databases are provided by default, postgresql and sqlite, the -same commands are used within sisu to construct and populate databases however --d (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, -alternatively --sqlite or --pgsql may be used -<P> -<BR> - -<B>-D or --pgsql</B> - -may be used interchangeably. -<P> -<A NAME="lbDN"> </A> -<H2>22.4.1 CREATE AND DESTROY DATABASE</H2> - -<P> -<DL COMPACT> -<DT><B>--pgsql --createall</B> - -<DD> -initial step, creates required relations (tables, indexes) in existing -(postgresql) database (a database should be created manually and given the same -name as working directory, as requested) (rb.dbi) -<P> -<DT><B>sisu -D --createdb</B> - -<DD> -creates database where no database existed before -<P> -<DT><B>sisu -D --create</B> - -<DD> -creates database tables where no database tables existed before -<P> -<DT><B>sisu -D --Dropall</B> - -<DD> -destroys database (including all its content)! kills data and drops tables, -indexes and database associated with a given directory (and directories of the -same name). -<P> -<DT><B>sisu -D --recreate</B> - -<DD> -destroys existing database and builds a new empty database structure -<P> -</DL> -<A NAME="lbDO"> </A> -<H2>22.4.2 IMPORT AND REMOVE DOCUMENTS</H2> - -<P> -<DL COMPACT> -<DT><B>sisu -D --import -v [filename/wildcard]</B> - -<DD> -populates database with the contents of the file. Imports documents(s) -specified to a postgresql database (at an object level). -<P> -<DT><B>sisu -D --update -v [filename/wildcard]</B> - -<DD> -updates file contents in database -<P> -<DT><B>sisu -D --remove -v [filename/wildcard]</B> - -<DD> -removes specified document from postgresql database. -<P> -</DL> -<A NAME="lbDP"> </A> -<H2>23. SQLITE</H2> - -<BR> - -<P> -<A NAME="lbDQ"> </A> -<H2>23.1 NAME</H2> - -<P> -<BR> - -<B>SiSU</B> - -- Structured information, Serialized Units - a document publishing system. -<P> -<A NAME="lbDR"> </A> -<H2>23.2 DESCRIPTION</H2> - -<P> -<BR> +database and have headings in which search content appears, or to search +only headings etc. (as the <i>Dublin</i> Core is incorporated it is easy to make +use of that as well). +<p> +<h2><a name='sect76' href='#toc76'>Postgresql</a></h2> +<br> + +<p> +<h2><a name='sect77' href='#toc77'>Name</a></h2> + +<p> <br> +<b>SiSU</b> - Structured information, Serialized Units - a document publishing system, + +<p>postgresql dependency package +<p> +<h2><a name='sect78' href='#toc78'>Description</a></h2> + +<p> <br> +Information related to using postgresql with sisu (and related to the sisu_postgresql +dependency package, which is a dummy package to install dependencies needed +for <b>SiSU</b> to populate a postgresql database, this being part of <b>SiSU</b> - man +sisu) . +<p> +<h2><a name='sect79' href='#toc79'>Synopsis</a></h2> + +<p> <br> + sisu -D [instruction] [filename/wildcard if required]<br> + +<p> <br> + sisu -D --pg --[instruction] [filename/wildcard if required]<br> + +<p> +<h2><a name='sect80' href='#toc80'>Commands</a></h2> + +<p> <br> +Mappings to two databases are provided by default, postgresql and sqlite, +the same commands are used within sisu to construct and populate databases +however -d (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, + +<p>alternatively --sqlite or --pgsql may be used +<p> <br> +<b>-D or --pgsql</b> may be used interchangeably. +<p> +<h2><a name='sect81' href='#toc81'>Create and Destroy Database</a></h2> + +<p> +<dl> + +<dt><b>--pgsql +--createall</b> </dt> +<dd>initial step, creates required relations (tables, indexes) in +existing (postgresql) database (a database should be created manually and +given the same name as working directory, as requested) (rb.dbi) +<p> </dd> + +<dt><b>sisu -D +--createdb</b> </dt> +<dd>creates database where no database existed before +<p> </dd> + +<dt><b>sisu -D --create</b> +</dt> +<dd> +<p>creates database tables where no database tables existed before +<p> </dd> + +<dt><b>sisu -D +--Dropall</b> </dt> +<dd>destroys database (including all its content)! kills data and drops +tables, indexes and database associated with a given directory (and directories +of the same name). +<p> </dd> + +<dt><b>sisu -D --recreate</b> </dt> +<dd>destroys existing database and builds + +<p>a new empty database structure +<p> </dd> +</dl> + +<h2><a name='sect82' href='#toc82'>Import and Remove Documents</a></h2> + +<p> +<dl> + +<dt><b>sisu -D --import +-v [filename/wildcard]</b> </dt> +<dd>populates database with the contents of the file. +Imports documents(s) specified to a postgresql database (at an object level). + +<p> </dd> + +<dt><b>sisu -D --update -v [filename/wildcard]</b> </dt> +<dd>updates file contents in database + +<p> </dd> + +<dt><b>sisu -D --remove -v [filename/wildcard]</b> </dt> +<dd>removes specified document from postgresql +database. +<p> </dd> +</dl> -Information related to using sqlite with sisu (and related to the sisu_sqlite -dependency package, which is a dummy package to install dependencies needed for -<B>SiSU</B> - -to populate an sqlite database, this being part of -<B>SiSU</B> - -- man sisu). -<P> -<A NAME="lbDS"> </A> -<H2>23.3 SYNOPSIS</H2> - -<P> -<BR> - -<BR> sisu -d [instruction] [filename/wildcard if required] -<P> -<BR> - -<BR> sisu -d --(sqlite|pg) --[instruction] [filename/wildcard if required] -<P> -<A NAME="lbDT"> </A> -<H2>23.4 COMMANDS</H2> - -<P> -<BR> - -Mappings to two databases are provided by default, postgresql and sqlite, the -same commands are used within sisu to construct and populate databases however --d (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, -alternatively --sqlite or --pgsql may be used -<P> -<BR> - -<B>-d or --sqlite</B> - -may be used interchangeably. -<P> -<A NAME="lbDU"> </A> -<H2>23.4.1 CREATE AND DESTROY DATABASE</H2> - -<P> -<DL COMPACT> -<DT><B>--sqlite --createall</B> - -<DD> -initial step, creates required relations (tables, indexes) in existing (sqlite) -database (a database should be created manually and given the same name as -working directory, as requested) (rb.dbi) -<P> -<DT><B>sisu -d --createdb</B> - -<DD> -creates database where no database existed before -<P> -<DT><B>sisu -d --create</B> - -<DD> -creates database tables where no database tables existed before -<P> -<DT><B>sisu -d --dropall</B> - -<DD> -destroys database (including all its content)! kills data and drops tables, -indexes and database associated with a given directory (and directories of the -same name). -<P> -<DT><B>sisu -d --recreate</B> - -<DD> -destroys existing database and builds a new empty database structure -<P> -</DL> -<A NAME="lbDV"> </A> -<H2>23.4.2 IMPORT AND REMOVE DOCUMENTS</H2> - -<P> -<DL COMPACT> -<DT><B>sisu -d --import -v [filename/wildcard]</B> - -<DD> -populates database with the contents of the file. Imports documents(s) -specified to an sqlite database (at an object level). -<P> -<DT><B>sisu -d --update -v [filename/wildcard]</B> - -<DD> -updates file contents in database -<P> -<DT><B>sisu -d --remove -v [filename/wildcard]</B> - -<DD> -removes specified document from sqlite database. -<P> -</DL> -<A NAME="lbDW"> </A> -<H2>24. INTRODUCTION</H2> - -<BR> - -<P> -<A NAME="lbDX"> </A> -<H2>24.1 SEARCH - DATABASE FRONTEND SAMPLE, UTILISING DATABASE AND SISU FEATURES,</H2> - -INCLUDING OBJECT CITATION NUMBERING (BACKEND CURRENTLY POSTGRESQL) -<P> -<BR> - -Sample search frontend <<A HREF="http://search.sisudoc.org">http://search.sisudoc.org</A>> [^22] A small database and -sample query front-end (search from) that makes use of the citation system, -<I>object citation numbering</I> +<h2><a name='sect83' href='#toc83'>Sqlite</a></h2> +<br> -to demonstrates functionality.[^23] -<P> -<BR> +<p> +<h2><a name='sect84' href='#toc84'>Name</a></h2> -<B>SiSU</B> +<p> <br> +<b>SiSU</b> - Structured information, Serialized Units - a document publishing system. -can provide information on which documents are matched and at what locations -within each document the matches are found. These results are relevant across -all outputs using object citation numbering, which includes html, XML, EPUB, -LaTeX, PDF and indeed the SQL database. You can then refer to one of the other -outputs or in the SQL database expand the text within the matched objects -(paragraphs) in the documents matched. -<P> -<BR> +<p> +<h2><a name='sect85' href='#toc85'>Description</a></h2> +<p> <br> +Information related to using sqlite with sisu (and related to the sisu_sqlite +dependency package, which is a dummy package to install dependencies needed +for <b>SiSU</b> to populate an sqlite database, this being part of <b>SiSU</b> - man sisu) +. +<p> +<h2><a name='sect86' href='#toc86'>Synopsis</a></h2> + +<p> <br> + sisu -d [instruction] [filename/wildcard if required]<br> + +<p> <br> + sisu -d --(sqlite|pg) --[instruction] [filename/wildcard if <br> + required]<br> + +<p> +<h2><a name='sect87' href='#toc87'>Commands</a></h2> + +<p> <br> +Mappings to two databases are provided by default, postgresql and sqlite, +the same commands are used within sisu to construct and populate databases +however -d (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, + +<p>alternatively --sqlite or --pgsql may be used +<p> <br> +<b>-d or --sqlite</b> may be used interchangeably. +<p> +<h2><a name='sect88' href='#toc88'>Create and Destroy Database</a></h2> + +<p> +<dl> + +<dt><b>--sqlite +--createall</b> </dt> +<dd>initial step, creates required relations (tables, indexes) in +existing (sqlite) database (a database should be created manually and given +the same name as working directory, as requested) (rb.dbi) +<p> </dd> + +<dt><b>sisu -d --createdb</b> +</dt> +<dd> +<p>creates database where no database existed before +<p> </dd> + +<dt><b>sisu -d --create</b> </dt> +<dd>creates + +<p>database tables where no database tables existed before +<p> </dd> + +<dt><b>sisu -d --dropall</b> +</dt> +<dd>destroys database (including all its content)! kills data and drops tables, +indexes and database associated with a given directory (and directories +of the same name). +<p> </dd> + +<dt><b>sisu -d --recreate</b> </dt> +<dd>destroys existing database and builds + +<p>a new empty database structure +<p> </dd> +</dl> + +<h2><a name='sect89' href='#toc89'>Import and Remove Documents</a></h2> + +<p> +<dl> + +<dt><b>sisu -d --import +-v [filename/wildcard]</b> </dt> +<dd>populates database with the contents of the file. +Imports documents(s) specified to an sqlite database (at an object level). + +<p> </dd> + +<dt><b>sisu -d --update -v [filename/wildcard]</b> </dt> +<dd>updates file contents in database + +<p> </dd> + +<dt><b>sisu -d --remove -v [filename/wildcard]</b> </dt> +<dd>removes specified document from sqlite +database. +<p> </dd> +</dl> + +<h2><a name='sect90' href='#toc90'>Introduction</a></h2> +<br> + +<p> +<h2><a name='sect91' href='#toc91'>Search - Database Frontend Sample, Utilising Database and Sisu Features,</a></h2> +INCLUDING +OBJECT CITATION NUMBERING (BACKEND CURRENTLY POSTGRESQL) +<p> <br> +Sample search frontend <<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a> +> [^23] A small database and +sample query front-end (search from) that makes use of the citation system, +<i>object</i> citation numbering to demonstrates functionality.[^24] +<p> <br> +<b>SiSU</b> can provide information on which documents are matched and at what +locations within each document the matches are found. These results are +relevant across all outputs using <i>object</i> citation numbering, which includes +html, <i>XML,</i> <i>EPUB,</i> <i>LaTeX,</i> <i>PDF</i> and indeed the <i>SQL</i> database. You can then refer +to one of the other outputs or in the <i>SQL</i> database expand the text within +the matched objects (paragraphs) in the documents matched. +<p> <br> Note you may set results either for documents matched and object number -locations within each matched document meeting the search criteria; or display -the names of the documents matched along with the objects (paragraphs) that -meet the search criteria.[^24] -<P> -<DL COMPACT> -<DT><B>sisu -F --webserv-webrick</B> - -<DD> -builds a cgi web search frontend for the database created -<P> -<BR> +locations within each matched document meeting the search criteria; or +display the names of the documents matched along with the objects (paragraphs) +that meet the search criteria.[^25] +<p> +<dl> +<dt><b>sisu -F --webserv-webrick</b> </dt> +<dd>builds a cgi web + +<p>search frontend for the database created +<p> <br> The following is feedback on the setup on a machine provided by the help command: -<P> -<BR> +<p> <br> + sisu --help sql<br> -<BR> sisu --help sql -<P> -<PRE> -Postgresql +<p> <br> +<pre>Postgresql user: ralph current db set: SiSU_sisu port: 5432 @@ -4717,1937 +3159,535 @@ Postgresql sqlite current db set: /home/ralph/sisu_www/sisu/sisu_sqlite.db dbi connect DBI:SQLite:/home/ralph/sisu_www/sisu/sisu_sqlite.db -</PRE> - -<P> -<BR> - -Note on databases built -<P> -<BR> +</pre> +<p> <br> +<p>Note on databases built +<p> <br> By default, [unless otherwise specified] databases are built on a directory -basis, from collections of documents within that directory. The name of the -directory you choose to work from is used as the database name, i.e. if you are -working in a directory called /home/ralph/ebook the database SiSU_ebook is -used. [otherwise a manual mapping for the collection is necessary] -<P> -</DL> -<A NAME="lbDY"> </A> -<H2>24.2 SEARCH FORM</H2> - -<P> -<DL COMPACT> -<DT><B>sisu -F</B> - -<DD> -generates a sample search form, which must be copied to the web-server cgi -directory -<P> -<DT><B>sisu -F --webserv-webrick</B> - -<DD> -generates a sample search form for use with the webrick server, which must be -copied to the web-server cgi directory -<P> -<DT><B>sisu -Fv</B> - -<DD> -as above, and provides some information on setting up hyperestraier -<P> -<DT><B>sisu -W</B> - -<DD> -starts the webrick server which should be available wherever sisu is properly -installed -<P> -<BR> - -The generated search form must be copied manually to the webserver directory as -instructed -<P> -</DL> -<A NAME="lbDZ"> </A> -<H2>25. SISU_WEBRICK</H2> - -<BR> - -<P> -<A NAME="lbEA"> </A> -<H2>25.1 NAME</H2> - -<P> -<BR> - -<B>SiSU</B> - -- Structured information, Serialized Units - a document publishing system -<P> -<A NAME="lbEB"> </A> -<H2>25.2 SYNOPSIS</H2> - -<P> -<BR> - -sisu_webrick [port] -<P> -<BR> - -or -<P> -<BR> - -sisu -W [port] -<P> -<A NAME="lbEC"> </A> -<H2>25.3 DESCRIPTION</H2> - -<P> -<BR> - -sisu_webrick is part of -<B>SiSU</B> - -(man sisu) sisu_webrick starts -<B>Ruby</B> - - -<B>SiSU</B> - -output is written, providing a list of these directories (assuming -<B>SiSU</B> - -is in use and they exist). -<P> -<BR> - -The default port for sisu_webrick is set to 8081, this may be modified in the -yaml file: ~/.sisu/sisurc.yml a sample of which is provided as -/etc/sisu/sisurc.yml (or in the equivalent directory on your system). -<P> -<A NAME="lbED"> </A> -<H2>25.4 SUMMARY OF MAN PAGE</H2> - -<P> -<BR> - -sisu_webrick, may be started on it's own with the command: sisu_webrick [port] -or using the sisu command with the -W flag: sisu -W [port] -<P> -<BR> - -where no port is given and settings are unchanged the default port is 8081 -<P> -<A NAME="lbEE"> </A> -<H2>25.5 DOCUMENT PROCESSING COMMAND FLAGS</H2> - -<P> -<BR> - -sisu -W [port] starts -<B>Ruby</B> - -Webrick web-server, serving -<B>SiSU</B> - -output directories, on the port provided, or if no port is provided and the -defaults have not been changed in ~/.sisu/sisurc.yaml then on port 8081 -<P> -<A NAME="lbEF"> </A> -<H2>25.6 FURTHER INFORMATION</H2> +basis, from collections of documents within that directory. The name of +the directory you choose to work from is used as the database name, i.e. +if you are working in a directory called /home/ralph/ebook the database +SiSU_ebook is used. [otherwise a manual mapping for the collection is +<p> </dd> +</dl> -<P> -<BR> +<h2><a name='sect92' href='#toc92'>Search +Form</a></h2> -For more information on -<B>SiSU</B> +<p> +<dl> -see: <<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A>> or <<A HREF="http://www.jus.uio.no/sisu">http://www.jus.uio.no/sisu</A>> -<P> -<BR> +<dt><b>sisu -F</b> </dt> +<dd>generates a sample search form, which must be copied to the -or man sisu -<P> -<A NAME="lbEG"> </A> -<H2>25.7 AUTHOR</H2> +<p>web-server cgi directory +<p> </dd> -<P> -<BR> +<dt><b>sisu -F --webserv-webrick</b> </dt> +<dd>generates a sample search +form for use with the webrick server, which must be copied to the web-server -Ralph Amissah <<A HREF="mailto:ralph@amissah.com">ralph@amissah.com</A>> or <<A HREF="mailto:ralph.amissah@gmail.com">ralph.amissah@gmail.com</A>> -<P> -<A NAME="lbEH"> </A> -<H2>25.8 SEE ALSO</H2> +<p>cgi directory +<p> </dd> -<P> -<BR> +<dt><b>sisu -W</b> </dt> +<dd>starts the webrick server which should be available -<BR> <A HREF="/cgi-bin/man/man2html?1+sisu">sisu</A>(1) -<P> -<BR> +<p>wherever sisu is properly installed +<p> <br> -<BR> <A HREF="/cgi-bin/man/man2html?7+sisu_vim">sisu_vim</A>(7) -<P> -<A NAME="lbEI"> </A> -<H2>26. REMOTE SOURCE DOCUMENTS</H2> +<p>The generated search form must be copied manually to the webserver directory -<BR> +<p>as instructed +<p> </dd> +</dl> -<P> -<BR> +<h2><a name='sect93' href='#toc93'>Sisu_webrick</a></h2> +<br> -<B>SiSU</B> +<p> +<h2><a name='sect94' href='#toc94'>Name</a></h2> -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 -<B>SiSU</B> +<p> <br> +<b>SiSU</b> - Structured information, Serialized Units - a document publishing system -documents can either be sisu marked up files in plaintext .sst or .ssm or; -zipped sisu files, sisupod.zip or filename.ssp -<P> -<BR> +<p> +<h2><a name='sect95' href='#toc95'>Synopsis</a></h2> -<B>.sst / .ssm - sisu text files</B> - -<P> -<BR> - -<B>SiSU</B> - -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. -<P> -<PRE> -sisu -3 <A HREF="http://[provide">http://[provide</A> url to valid .sst or .ssm file] -</PRE> - -<P> -<BR> - -Any of the source documents in the sisu examples page can be used in this way, -see <<A HREF="http://www.jus.uio.no/sisu/SiSU/examples.html">http://www.jus.uio.no/sisu/SiSU/examples.html</A>> and use the url to the -<BR> .sst for the desired document. -<P> -<BR> - -NOTE: to set up a remote machine to serve -<B>SiSU</B> - -documents in this way, images should be in the directory relative to the -document source ../_sisu/image -<P> -<BR> - -<B>sisupod - zipped sisu files</B> - -<P> -<BR> - -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. -<P> -<BR> - -<B>SiSU</B> - -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. -<P> -<PRE> -sisu -3 <A HREF="http://[provide">http://[provide</A> url to valid sisupod.zip or .ssp file] -</PRE> - -<P> -<BR> - -Any of the source documents in the sisu examples page can be used in this way, -see <<A HREF="http://www.jus.uio.no/sisu/SiSU/examples.html">http://www.jus.uio.no/sisu/SiSU/examples.html</A>> and use the url for the -desired document. -<P> -<A NAME="lbEJ"> </A> -<H2>REMOTE DOCUMENT OUTPUT</H2> - -<BR> - -<P> -<A NAME="lbEK"> </A> -<H2>27. REMOTE OUTPUT</H2> - -<BR> - -<P> -<BR> - -Once properly configured -<B>SiSU</B> - -output can be automatically posted once generated to a designated remote -machine using either rsync, or scp. -<P> -<BR> - -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. -<P> -<PRE> -sisu -3R sisu_remote.sst -</PRE> - -<P> -<A NAME="lbEL"> </A> -<H2>27.1 COMMANDS</H2> - -<P> -<DL COMPACT> -<DT><B>-R [filename/wildcard]</B> - -<DD> -copies sisu output files to remote host using rsync. This requires that -sisurc.yml has been provided with information on hostname and username, and -that you have your "keys" and ssh agent in place. Note the behavior of rsync -different if -R is used with other flags from if used alone. Alone the rsync ---delete parameter is sent, useful for cleaning the remote directory (when --R is used together with other flags, it is not). Also see -r -<P> -<DT><B>-r [filename/wildcard]</B> - -<DD> -copies sisu output files to remote host using scp. This requires that -sisurc.yml has been provided with information on hostname and username, and -that you have your "keys" and ssh agent in place. Also see -R -<P> -</DL> -<A NAME="lbEM"> </A> -<H2>27.2 CONFIGURATION</H2> - -<P> -<BR> - -[expand on the setting up of an ssh-agent / keychain] -<P> -<A NAME="lbEN"> </A> -<H2>28. REMOTE SERVERS</H2> - -<BR> - -<P> -<BR> - -As -<B>SiSU</B> - -is generally operated using the command line, and works within a Unix type -environment, -<B>SiSU</B> - -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. -<P> -<A NAME="lbEO"> </A> -<H2>29. QUICKSTART - GETTING STARTED HOWTO</H2> - -<BR> - -<P> -<A NAME="lbEP"> </A> -<H2>29.1 INSTALLATION</H2> - -<P> -<BR> - -Installation is currently most straightforward and tested on the -<B>Debian</B> - -platform, as there are packages for the installation of sisu and all -requirements for what it does. -<P> -<A NAME="lbEQ"> </A> -<H2>29.1.1 DEBIAN INSTALLATION</H2> - -<P> -<BR> - -<B>SiSU</B> - -is available directly from the -<B>Debian</B> - -Sid and testing archives (and possibly Ubuntu), assuming your -/etc/apt/sources.list is set accordingly: -<P> -<PRE> - aptitude update - aptitude install sisu-complete -</PRE> - -<P> -<BR> - -The following /etc/apt/sources.list setting permits the download of additional -markup samples: -<P> -<PRE> - #/etc/apt/sources.list -<BR> - deb <A HREF="http://ftp.fi.debian.org/debian/">http://ftp.fi.debian.org/debian/</A> unstable main non-free contrib -<BR> - deb-src <A HREF="http://ftp.fi.debian.org/debian/">http://ftp.fi.debian.org/debian/</A> unstable main non-free contrib -<BR> - -</PRE> - -<P> -<BR> - -The aptitude commands become: -<P> -<PRE> - aptitude update -<BR> - aptitude install sisu-complete sisu-markup-samples -</PRE> - -<P> -<BR> - -If there are newer versions of -<B>SiSU</B> - -upstream of the -<B>Debian</B> - -archives, they will be available by adding the following to your -/etc/apt/sources.list -<P> -<PRE> -#/etc/apt/sources.list - deb <A HREF="http://www.jus.uio.no/sisu/archive">http://www.jus.uio.no/sisu/archive</A> unstable main non-free - deb-src <A HREF="http://www.jus.uio.no/sisu/archive">http://www.jus.uio.no/sisu/archive</A> unstable main non-free -</PRE> - -<P> -<BR> - -repeat the aptitude commands -<P> -<PRE> - aptitude update - aptitude install sisu-complete sisu-markup-samples -</PRE> - -<P> -<BR> - -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. -<P> -<A NAME="lbER"> </A> -<H2>29.1.2 RPM INSTALLATION</H2> - -<P> -<BR> - -RPMs are provided though untested, they are prepared by running alien against -the source package, and against the debs. -<P> -<BR> - -They may be downloaded from: -<P> -<BR> - -<BR> <<A HREF="http://www.jus.uio.no/sisu/SiSU/download.html#rpm">http://www.jus.uio.no/sisu/SiSU/download.html#rpm</A>> -<P> -<BR> - -as root type: -<P> -<BR> - -<BR> rpm -i [rpm package name] -<P> -<A NAME="lbES"> </A> -<H2>29.1.3 INSTALLATION FROM SOURCE</H2> - -<P> -<BR> - -To install -<B>SiSU</B> - -from source check information at: -<P> -<BR> - -<BR> <<A HREF="http://www.jus.uio.no/sisu/SiSU/download.html#current">http://www.jus.uio.no/sisu/SiSU/download.html#current</A>> -<P> -<BR> - -* download the source package -<P> -<BR> - -* Unpack the source -<P> -<BR> - -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: -<P> -<BR> - -For basic use -<B>SiSU</B> - -is only dependent on the programming language in which it is written -<B>Ruby,</B> - -and -<B>SiSU</B> - -will be able to generate html, EPUB, various XMLs, including ODF (and will also -produce LaTeX). Dependencies required for further actions, though it relies on -the installation of additional dependencies which the source tarball does not -take care of, for things like using a database (postgresql or sqlite)[^25] or -converting LaTeX to pdf. -<P> -<BR> - -<B>setup.rb</B> - -<P> -<BR> - -This is a standard ruby installer, using setup.rb is a three step process. In -the root directory of the unpacked -<B>SiSU</B> - -as root type: -<P> -<PRE> - ruby setup.rb config - ruby setup.rb setup - #[and as root:] - ruby setup.rb install -</PRE> - -<P> -<BR> - -further information on setup.rb is available from: -<P> -<BR> - -<BR> <<A HREF="http://i.loveruby.net/en/projects/setup/">http://i.loveruby.net/en/projects/setup/</A>> -<P> -<BR> - -<BR> <<A HREF="http://i.loveruby.net/en/projects/setup/doc/usage.html">http://i.loveruby.net/en/projects/setup/doc/usage.html</A>> -<P> -<BR> - -<B>install</B> - -<P> -<BR> - -The "install" file provided is an installer prepared using "rant". In the root -directory of the unpacked -<B>SiSU</B> - -as root type: -<P> -<BR> - -<BR> ruby install base -<P> -<BR> - -or for a more complete installation: -<P> -<BR> - -<BR> ruby install -<P> -<BR> - -or -<P> -<BR> - -<BR> ruby install base -<P> -<BR> - -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. -<P> -<BR> - -Further information on "rant" is available from: -<P> -<BR> - -<BR> <<A HREF="http://make.rubyforge.org/">http://make.rubyforge.org/</A>> -<P> -<BR> - -<BR> <<A HREF="http://rubyforge.org/frs/?group_id=615">http://rubyforge.org/frs/?group_id=615</A>> -<P> -<BR> - -For a list of alternative actions you may type: -<P> -<BR> - -<BR> ruby install help -<P> -<BR> - -<BR> ruby install -T -<P> -<A NAME="lbET"> </A> -<H2>29.2 TESTING SISU, GENERATING OUTPUT</H2> - -<P> -<BR> - -To check which version of sisu is installed: -<P> -<BR> - -sisu -v -<P> -<BR> - -Depending on your mode of installation one or a number of markup sample files -may be found either in the directory: -<P> -<BR> - - -<P> -<BR> - -or -<P> -<BR> - - -<P> -<BR> - -change directory to the appropriate one: -<P> -<BR> - -cd /usr/share/doc/sisu/markup-samples/samples -<P> -<A NAME="lbEU"> </A> -<H2>29.2.1 BASIC TEXT, PLAINTEXT, HTML, XML, ODF, EPUB</H2> - -<P> -<BR> - -Having moved to the directory that contains the markup samples (see -instructions above if necessary), choose a file and run sisu against it -<P> -<BR> - -sisu -NhwoabxXyv free_as_in_freedom.rms_and_free_software.sam_williams.sst -<P> -<BR> - -this will generate html including a concordance file, opendocument text format, -plaintext, XHTML and various forms of XML, and OpenDocument text -<P> -<A NAME="lbEV"> </A> -<H2>29.2.2 LATEX / PDF</H2> - -<P> -<BR> - -Assuming a LaTeX engine such as tetex or texlive is installed with the required -modules (done automatically on selection of sisu-pdf in -<B>Debian</B> - -) -<P> -<BR> - -Having moved to the directory that contains the markup samples (see -instructions above if necessary), choose a file and run sisu against it -<P> -<BR> - -sisu -pv free_as_in_freedom.rms_and_free_software.sam_williams.sst -<P> -<BR> - -sisu -3 free_as_in_freedom.rms_and_free_software.sam_williams.sst -<P> -<BR> - -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 -<P> -<A NAME="lbEW"> </A> -<H2>29.2.3 RELATIONAL DATABASE - POSTGRESQL, SQLITE</H2> - -<P> -<BR> - -Relational databases need some setting up - you must have permission to create -the database and write to it when you run sisu. -<P> -<BR> - -Assuming you have the database installed and the requisite permissions -<P> -<BR> - -sisu --sqlite --recreate -<P> -<BR> - -sisu --sqlite -v --import -free_as_in_freedom.rms_and_free_software.sam_williams.sst -<P> -<BR> - -sisu --pgsql --recreate -<P> -<BR> - -sisu --pgsql -v --import -free_as_in_freedom.rms_and_free_software.sam_williams.sst -<P> -<A NAME="lbEX"> </A> -<H2>29.3 GETTING HELP</H2> - -<P> -<A NAME="lbEY"> </A> -<H2>29.3.1 THE MAN PAGES</H2> - -<P> -<BR> - -Type: -<P> -<BR> - -<BR> man sisu -<P> -<BR> - -The man pages are also available online, though not always kept as up to date -as within the package itself: -<P> -<BR> - -* sisu.1 <<A HREF="http://www.jus.uio.no/sisu/man/sisu.1.html">http://www.jus.uio.no/sisu/man/sisu.1.html</A>> [^26] -<P> -<BR> - -* sisu.8 <<A HREF="http://www.jus.uio.no/sisu/man/sisu.8.html">http://www.jus.uio.no/sisu/man/sisu.8.html</A>> [^27] -<P> -<BR> - -* man directory <<A HREF="http://www.jus.uio.no/sisu/man">http://www.jus.uio.no/sisu/man</A>> [^28] -<P> -<A NAME="lbEZ"> </A> -<H2>29.3.2 BUILT IN HELP</H2> - -<P> -<BR> - -sisu --help -<P> -<BR> - -sisu --help --env -<P> -<BR> - -sisu --help --commands -<P> -<BR> - -sisu --help --markup -<P> -<A NAME="lbFA"> </A> -<H2>29.3.3 THE HOME PAGE</H2> - -<P> -<BR> - -<<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A>> -<P> -<BR> - -<<A HREF="http://www.jus.uio.no/sisu">http://www.jus.uio.no/sisu</A>> -<P> -<BR> - -<<A HREF="http://www.jus.uio.no/sisu/SiSU">http://www.jus.uio.no/sisu/SiSU</A>> -<P> -<A NAME="lbFB"> </A> -<H2>29.4 MARKUP SAMPLES</H2> - -<P> -<BR> - -A number of markup samples (along with output) are available off: -<P> -<BR> - -<<A HREF="http://www.jus.uio.no/sisu/SiSU/examples.html">http://www.jus.uio.no/sisu/SiSU/examples.html</A>> -<P> -<BR> - -Additional markup samples are packaged separately in the file: -<P> -<BR> - -*** -<P> -<BR> - -On -<B>Debian</B> - -they are available in non-free[^29] to include them it is necessary to include -non-free in your /etc/apt/source.list or obtain them from the sisu home site. -<P> -<A NAME="lbFC"> </A> -<H2>30. EDITOR FILES, SYNTAX HIGHLIGHTING</H2> - -<BR> - -<P> -<BR> - -The directory: -<P> -<BR> - -<BR> ./data/sisu/v2/conf/editor-syntax-etc/ -<P> -<BR> - -<BR> ./data/sisu/v3/conf/editor-syntax-etc/ -<P> -<BR> - -<BR> /usr/share/sisu/v2/conf/editor-syntax-etc -<P> -<BR> - -<BR> /usr/share/sisu/v3/conf/editor-syntax-etc -<P> -<BR> - -contains rudimentary sisu syntax highlighting files for: -<P> -<BR> - -* (g)vim <<A HREF="http://www.vim.org">http://www.vim.org</A>> -<P> -<BR> - -<BR> package: sisu-vim -<P> -<BR> - -status: largely done -<P> -<BR> - -<BR> there is a vim syntax highlighting and folds component -<P> -<BR> - -* gedit <<A HREF="http://www.gnome.org/projects/gedit">http://www.gnome.org/projects/gedit</A>> -<P> -<BR> - -* gobby <<A HREF="http://gobby.0x539.de/">http://gobby.0x539.de/</A>> -<P> -<BR> - -<BR> file: sisu.lang -<P> -<BR> - -place in: -<P> -<BR> - -<BR> /usr/share/gtksourceview-1.0/language-specs -<P> -<BR> - -or -<P> -<BR> - -<BR> ~/.gnome2/gtksourceview-1.0/language-specs -<P> -<BR> - -<BR> status: very basic syntax highlighting -<P> -<BR> - -<BR> comments: this editor features display line wrap and is used by Goby! -<P> -<BR> - -* nano <<A HREF="http://www.nano-editor.org">http://www.nano-editor.org</A>> -<P> -<BR> - -<BR> file: nanorc -<P> -<BR> - -save as: -<P> -<BR> - -<BR> ~/.nanorc -<P> -<BR> - -<BR> status: basic syntax highlighting -<P> -<BR> - -<BR> comments: assumes dark background; no display line-wrap; does line breaks -<P> -<BR> - -* diakonos (an editor written in ruby) <<A HREF="http://purepistos.net/diakonos">http://purepistos.net/diakonos</A>> -<P> -<BR> - -file: diakonos.conf -<P> -<BR> - -save as: -<P> -<BR> - -<BR> ~/.diakonos/diakonos.conf -<P> -<BR> - -includes: -<P> -<BR> - -<BR> status: basic syntax highlighting -<P> -<BR> - -comments: assumes dark background; no display line-wrap -<P> -<BR> - -* kate & kwrite <<A HREF="http://kate.kde.org">http://kate.kde.org</A>> -<P> -<BR> - -<BR> file: sisu.xml -<P> -<BR> - -<BR> place in: -<P> -<BR> - -<BR> /usr/share/apps/katepart/syntax -<P> -<BR> - -<BR> or -<P> -<BR> +<p> <br> +sisu_webrick [port] +<p> <br> -<BR> ~/.kde/share/apps/katepart/syntax -<P> -<BR> +<p>or +<p> <br> +sisu -W [port] +<p> +<h2><a name='sect96' href='#toc96'>Description</a></h2> -<BR> [settings::configure kate::{highlighting,filetypes}] -<P> -<BR> - -<BR> [tools::highlighting::{markup,scripts}:: .B SiSU ] -<P> -<BR> - -* nedit <<A HREF="http://www.nedit.org">http://www.nedit.org</A>> -<P> -<BR> - -<BR> file: sisu_nedit.pats -<P> -<BR> - -<BR> nedit -import sisu_nedit.pats -<P> -<BR> - -<BR> status: a very clumsy first attempt [not really done] -<P> -<BR> - -<BR> comments: this editor features display line wrap -<P> -<BR> - -* emacs <<A HREF="http://www.gnu.org/software/emacs/emacs.html">http://www.gnu.org/software/emacs/emacs.html</A>> -<P> -<BR> - -<BR> files: sisu-mode.el -<P> -<BR> - -<BR> to file ~/.emacs add the following 2 lines: -<P> -<BR> - -<BR> (add-to-list 'load-path -<BR> "/usr/share/sisu/v2/conf/editor-syntax-etc/emacs") -<P> -<BR> - -<BR> (require 'sisu-mode.el) -<P> -<BR> - -<BR> [not done / not yet included] -<P> -<BR> - -* vim & gvim <<A HREF="http://www.vim.org">http://www.vim.org</A>> -<P> -<BR> - -<BR> files: -<P> -<BR> - -<BR> package is the most comprehensive sisu syntax highlighting and editor -<BR> environment provided to date (is for vim/ gvim, and is separate from the -<BR> contents of this directory) -<P> -<BR> - -<BR> status: this includes: syntax highlighting; vim folds; some error checking -<P> -<BR> - -<BR> comments: this editor features display line wrap -<P> -<BR> - -NOTE: -<P> -<BR> - -[ .B 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] -<P> -<A NAME="lbFD"> </A> -<H2>31. HOW DOES SISU WORK?</H2> - -<BR> - -<P> -<BR> - -<B>SiSU</B> - -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. -<B>SiSU</B> - -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). -<P> -<A NAME="lbFE"> </A> -<H2>32. SUMMARY OF FEATURES</H2> - -<BR> - -<P> -<BR> - -* 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 +<p> <br> +sisu_webrick is part of <b>SiSU</b> (man sisu) sisu_webrick starts <b>Ruby</b> <b>SiSU</b> +output is written, providing a list of these directories (assuming <b>SiSU</b> +is in use and they exist). +<p> <br> +The default port for sisu_webrick is set to 8081, this may be modified +in the yaml file: ~/.sisu/sisurc.yml a sample of which is provided as /etc/sisu/sisurc.yml +(or in the equivalent directory on your system). +<p> +<h2><a name='sect97' href='#toc97'>Summary of Man Page</a></h2> + +<p> <br> +sisu_webrick, may be started on it’s own with the command: sisu_webrick +[port] or using the sisu command with the -W flag: sisu -W [port] +<p> <br> + +<p>where no port is given and settings are unchanged the default port is 8081 + +<p> +<h2><a name='sect98' href='#toc98'>Document Processing Command Flags</a></h2> + +<p> <br> +sisu -W [port] starts <b>Ruby</b> Webrick web-server, serving <b>SiSU</b> output directories, +on the port provided, or if no port is provided and the defaults have not + +<p>been changed in ~/.sisu/sisurc.yaml then on port 8081 +<p> +<h2><a name='sect99' href='#toc99'>Summary of Features</a></h2> +<br> + +<p> <br> +* sparse/minimal markup (clean utf-8 source texts). Documents are prepared +in a single <i>UTF-8</i> file using a minimalistic mnemonic syntax. Typical literature, +documents like "War and Peace" require almost no markup, and most of the headers are optional. -<P> -<BR> - -* markup is easily readable/parsable by the human eye, (basic markup is simpler -and more sparse than the most basic HTML), [this may also be converted - to XML representations of the same input/source document]. -<P> -<BR> - +<p> <br> +* markup is easily readable/parsable by the human eye, (basic markup is +simpler and more sparse than the most basic <i>HTML</i> ) , [this may also be + converted to .I XML representations of the same input/source document]. +<p> +<br> * markup defines document structure (this may be done once in a header pattern-match description, or for heading levels individually); basic text -attributes (bold, italics, underscore, strike-through etc.) as required; and -semantic information related to the document (header information, extended +attributes (bold, italics, underscore, strike-through etc.) as required; +and semantic information related to the document (header information, extended beyond the Dublin core and easily further extended as required); the headers -may also contain processing instructions. -<B>SiSU</B> - -markup is primarily an abstraction of document structure and document metadata -to permit taking advantage of the basic strengths of existing alternative -practical standard ways of representing documents [be that browser viewing, paper publication, sql search etc.] (html, epub, xml, odf, -latex, pdf, sql) -<P> -<BR> - -* for output produces reasonably elegant output of established industry and -institutionally accepted open standard formats.[3] takes advantage of the -different strengths of various standard formats for representing documents, +may also contain processing instructions. <b>SiSU</b> markup is primarily an abstraction +of document structure and document metadata to permit taking advantage +of the basic strengths of existing alternative practical standard ways +of representing documents [be that browser viewing, paper publication, + sql search etc.] (html, epub, xml, odf, latex, pdf, sql) +<p> <br> +* for output produces reasonably elegant output of established industry +and institutionally accepted open standard formats.[3] takes advantage of +the different strengths of various standard formats for representing documents, amongst the output formats currently supported are: -<P> -<BR> - -<BR> * html - both as a single scrollable text and a segmented document -<P> -<BR> - -<BR> * xhtml -<P> -<BR> - -<BR> * epub -<P> -<BR> - -<BR> * XML - both in sax and dom style xml structures for further development as -<BR> required -<P> -<BR> - -<BR> * ODF - open document format, the iso standard for document storage -<P> -<BR> - -<BR> * LaTeX - used to generate pdf -<P> -<BR> - -<BR> * pdf (via LaTeX) -<P> -<BR> - -<BR> * sql - population of an sql database, (at the same object level that is -<BR> used to cite text within a document) -<P> -<BR> - -Also produces: concordance files; document content certificates (md5 or sha256 -digests of headings, paragraphs, images etc.) and html manifests (and sitemaps -of content). (b) takes advantage of the strengths implicit in these very -different output types, (e.g. PDFs produced using typesetting of LaTeX, -databases populated with documents at an individual object/paragraph level, -making possible granular search (and related possibilities)) -<P> -<BR> - +<p> <br> +* <i>HTML</i> - both as a single scrollable text and a segmented document +<p> <br> +* <i>XHTML</i> +<p> <br> +* <i>EPUB</i> +<p> <br> +* <i>XML</i> - both in sax and dom style xml structures for further development + +<p>as required +<p> <br> +* <i>ODT</i> - Open Document Format text, the iso standard for document storage + +<p> <br> +* <i>LaTeX</i> - used to generate pdf +<p> <br> +* <i>PDF</i> (via <i>LaTeX</i> ) +<p> <br> +* <i>SQL</i> - population of an sql database ( <i>PostgreSQL</i> or <i>SQLite</i> ) , (at the +same object level that is used to cite text within a document) +<p> <br> +Also produces: concordance files; document content certificates (md5 or +sha256 digests of headings, paragraphs, images etc.) and html manifests +(and sitemaps of content). (b) takes advantage of the strengths implicit +in these very different output types, (e.g. PDFs produced using typesetting +of <i>LaTeX,</i> databases populated with documents at an individual object/paragraph +level, making possible <i>granular</i> search (and related possibilities)) +<p> <br> * ensuring content can be cited in a meaningful way regardless of selected output format. Online publishing (and publishing in multiple document formats) -lacks a useful way of citing text internally within documents (important to -academics generally and to lawyers) as page numbers are meaningless across -browsers and formats. sisu seeks to provide a common way of pinpoint the text -within a document, (which can be utilized for citation and by search engines). -The outputs share a common numbering system that is meaningful (to man and -machine) across all digital outputs whether paper, screen, or database -oriented, (pdf, HTML, EPUB, xml, sqlite, postgresql), this numbering system can -be used to reference content. -<P> -<BR> - -* 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]. -<P> -<BR> - +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, <i>HTML,</i> <i>EPUB,</i> xml, sqlite, postgresql) , this +numbering system can be used to reference content. +<p> <br> +* Granular search within documents. <i>SQL</i> databases are populated at an object +level (roughly headings, paragraphs, verse, tables) and become searchable +with that degree of granularity, the output information provides the object/paragraph +numbers which are relevant across all generated outputs; it is also possible +to look at just the matching paragraphs of the documents in the database; +[output indexing also work +<p> <br> * long term maintainability of document collections in a world of changing -formats, having a very sparsely marked-up source document base. there is a -considerable degree of future-proofing, output representations are -"upgradeable", and new document formats may be added. e.g. addition of odf -(open document text) module in 2006, epub in 2009 and in future html5 output -sometime in future, without modification of existing prepared texts -<P> -<BR> - -* SQL search aside, documents are generated as required and static once +formats, having a very sparsely marked-up source document base. there is +a considerable degree of future-proofing, output representations are "upgradeable", +and new document formats may be added. e.g. addition of odf (open document +text) module in 2006, epub in 2009 and in future html5 output sometime +in future, without modification of existing prepared texts +<p> <br> +* <i>SQL</i> search aside, documents are generated as required and static once generated. -<P> -<BR> - -* documents produced are static files, and may be batch processed, this needs -to be done only once but may be repeated for various reasons as desired +<p> <br> +* documents produced are static files, and may be batch processed, this +needs to be done only once but may be repeated for various reasons as desired (updated content, addition of new output formats, updated technology document presentations/representations) -<P> -<BR> - -* document source (plaintext utf-8) if shared on the net may be used as input -and processed locally to produce the different document outputs -<P> -<BR> +<p> <br> +* document source ( <i>plaintext</i> utf-8) if shared on the net may be used as +<p>input and processed locally to produce the different document outputs +<p> +<br> * document source may be bundled together (automatically) with associated -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 -<P> -<BR> - -* generated document outputs may automatically be posted to remote sites. -<P> -<BR> +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 -* for basic document generation, the only software dependency is -<B>Ruby,</B> +<p>these too may be processed locally to produce the desired document outputs -and a few standard Unix tools (this covers plaintext, HTML, EPUB, XML, ODF, -LaTeX). To use a database you of course need that, and to convert the LaTeX -generated to pdf, a latex processor like tetex or texlive. -<P> -<BR> +<p> <br> +* generated document outputs may automatically be posted to remote sites. +<p> <br> +* for basic document generation, the only software dependency is <b>Ruby,</b> +and a few standard Unix tools (this covers <i>plaintext,</i> <i>HTML,</i> <i>EPUB,</i> <i>XML,</i> +<i>ODF,</i> <i>LaTeX</i> ) . To use a database you of course need that, and to convert +the <i>LaTeX</i> generated to pdf, a latex processor like tetex or texlive. +<p> <br> * as a developers tool it is flexible and extensible -<P> -<BR> - -Syntax highlighting for -<B>SiSU</B> - -markup is available for a number of text editors. -<P> -<BR> - -<B>SiSU</B> - -is less about document layout than about finding a way with little markup to be -able to construct an abstract representation of a document that makes it -possible to produce multiple representations of it which may be rather -different from each other and used for different purposes, whether layout and -publishing, or search of content -<P> -<BR> - -i.e. to be able to take advantage from this minimal preparation starting point -of some of the strengths of rather different established ways of representing -documents for different purposes, whether for search (relational database, or -indexed flat files generated for that purpose whether of complete documents, or -say of files made up of objects), online viewing (e.g. html, xml, pdf), or -paper publication (e.g. pdf)... -<P> -<BR> - +<p> <br> +Syntax highlighting for <b>SiSU</b> markup is available for a number of text editors. + +<p> <br> +<b>SiSU</b> is less about document layout than about finding a way with little +markup to be able to construct an abstract representation of a document +that makes it possible to produce multiple representations of it which +may be rather different from each other and used for different purposes, +whether layout and publishing, or search of content +<p> <br> +i.e. to be able to take advantage from this minimal preparation starting +point of some of the strengths of rather different established ways of +representing documents for different purposes, whether for search (relational +database, or indexed flat files generated for that purpose whether of complete +documents, or say of files made up of objects), online viewing (e.g. html, +xml, pdf) , or paper publication (e.g. pdf) ... +<p> <br> the solution arrived at is by extracting structural information about the document (about headings within the document) and by tracking objects (which are serialized and also given hash values) in the manner described. It makes possible representations that are quite different from those offered at -present. For example objects could be saved individually and identified by -their hashes, with an index of how the objects relate to each other to form a -document. -<P> -<A NAME="lbFF"> </A> -<H2>33. HELP SOURCES</H2> - -<BR> - -<P> -<A NAME="lbFG"> </A> -<H2>33.1 MAN PAGES</H2> - -<P> -<BR> - -<BR> man sisu -<P> -<BR> - -<BR> man sisu-concordance -<P> -<BR> - -<BR> man sisu-epub -<P> -<BR> - -<BR> man sisu-git -<P> -<BR> - -<BR> man sisu-harvest -<P> -<BR> - -<BR> man sisu-html -<P> -<BR> - -<BR> man sisu-odf -<P> -<BR> - -<BR> man sisu-pdf -<P> -<BR> - -<BR> man sisu-pg -<P> -<BR> - -<BR> man sisu-po -<P> -<BR> - -<BR> man sisu-sqlite -<P> -<BR> - -<BR> man sisu-txt -<P> -<BR> - -<BR> man 7 sisu_complete -<P> -<BR> - -<BR> man 7 sisu_pdf -<P> -<BR> - -<BR> man 7 sisu_postgresql -<P> -<BR> - -<BR> man 7 sisu_sqlite -<P> -<BR> - -<BR> man sisu_termsheet -<P> -<BR> - -<BR> man sisu_webrick -<P> -<A NAME="lbFH"> </A> -<H2>33.2 SISU GENERATED OUTPUT - LINKS TO HTML</H2> - -<P> -<BR> - -Note -<B>SiSU</B> - -documentation is prepared in -<B>SiSU</B> - -and output is available in multiple formats including amongst others html, pdf, -odf and epub, which may be also be accessed via the html pages[^30] -<P> -<A NAME="lbFI"> </A> -<H2>33.2.1 WWW.SISUDOC.ORG</H2> - -<P> -<BR> - -<<A HREF="http://sisudoc.org/sisu/sisu_manual/index.html">http://sisudoc.org/sisu/sisu_manual/index.html</A>> -<P> -<BR> - -<BR> <<A HREF="http://sisudoc.org/sisu/sisu_manual/index.html">http://sisudoc.org/sisu/sisu_manual/index.html</A>> -<P> -<A NAME="lbFJ"> </A> -<H2>33.3 MAN2HTML</H2> - -<P> -<A NAME="lbFK"> </A> -<H2>33.3.1 LOCALLY INSTALLED</H2> - -<P> -<BR> - -<A HREF="file:///usr/share/doc/sisu/html/sisu.1.html">file:///usr/share/doc/sisu/html/sisu.1.html</A> -<P> -<BR> - -<BR> <A HREF="file:///usr/share/doc/sisu/html/sisu.1.html">file:///usr/share/doc/sisu/html/sisu.1.html</A> -<P> -<BR> - -<BR> /usr/share/doc/sisu/html/sisu_pdf.7.html -<P> -<BR> - -<BR> /usr/share/doc/sisu/html/sisu_postgresql.7.html -<P> -<BR> - -<BR> /usr/share/doc/sisu/html/sisu_sqlite.7.html -<P> -<BR> - -<BR> /usr/share/doc/sisu/html/sisu_webrick.1.html -<P> -<A NAME="lbFL"> </A> -<H2>33.3.2 WWW.JUS.UIO.NO/SISU</H2> - -<P> -<BR> - -<<A HREF="http://www.jus.uio.no/sisu/man/sisu.1.html">http://www.jus.uio.no/sisu/man/sisu.1.html</A>> -<P> -<BR> - -<BR> <<A HREF="http://www.jus.uio.no/sisu/man/sisu.1.html">http://www.jus.uio.no/sisu/man/sisu.1.html</A>> -<P> -<BR> - -<BR> <<A HREF="http://www.jus.uio.no/sisu/man/sisu_complete.7.html">http://www.jus.uio.no/sisu/man/sisu_complete.7.html</A>> -<P> -<BR> - -<BR> <<A HREF="http://www.jus.uio.no/sisu/man/sisu_pdf.7.html">http://www.jus.uio.no/sisu/man/sisu_pdf.7.html</A>> -<P> -<BR> - -<BR> <<A HREF="http://www.jus.uio.no/sisu/man/sisu_postgresql.7.html">http://www.jus.uio.no/sisu/man/sisu_postgresql.7.html</A>> -<P> -<BR> - -<BR> <<A HREF="http://www.jus.uio.no/sisu/man/sisu_sqlite.7.html">http://www.jus.uio.no/sisu/man/sisu_sqlite.7.html</A>> -<P> -<BR> - -<BR> <<A HREF="http://www.jus.uio.no/sisu/man/sisu_webrick.1.html">http://www.jus.uio.no/sisu/man/sisu_webrick.1.html</A>> -<P> -<DL COMPACT> -<DT><B>1.</B> - -<DD> -objects include: headings, paragraphs, verse, tables, images, but not -footnotes/endnotes which are numbered separately and tied to the object from -which they are referenced. -<P> -<BR> - -<DT><B>2.</B> - -<DD> -i.e. the html, pdf, epub, odf outputs are each built individually and -optimised for that form of presentation, rather than for example the html being -a saved version of the odf, or the pdf being a saved version of the html. -<P> -<BR> - -<DT><B>3.</B> - -<DD> -the different heading levels -<P> -<BR> - -<DT><B>4.</B> - -<DD> -units of text, primarily paragraphs and headings, also any tables, poems, -code-blocks -<P> -<BR> - -<DT><B>5.</B> - -<DD> -Specification submitted by Adobe to ISO to become a full open ISO -specification -<P> -<BR> - -<<A HREF="http://www.linux-watch.com/news/NS7542722606.html">http://www.linux-watch.com/news/NS7542722606.html</A>> -<P> -<BR> - -<DT><B>6.</B> - -<DD> -ISO standard ISO/IEC 26300:2006 -<P> -<BR> - -<DT><B>7.</B> - -<DD> -An open standard format for e-books -<P> -<BR> - -<DT><B>*1.</B> - -<DD> -square brackets -<P> -<BR> - -<DT><B>*2.</B> - -<DD> -square brackets -<P> -<BR> - -<DT><B>+1.</B> - -<DD> -square brackets -<P> -<BR> - -<DT><B>8.</B> - -<DD> -<<A HREF="http://www.jus.uio.no/sisu/man/">http://www.jus.uio.no/sisu/man/</A>> -<P> -<BR> - -<DT><B>9.</B> - -<DD> -<<A HREF="http://www.jus.uio.no/sisu/man/sisu.1.html">http://www.jus.uio.no/sisu/man/sisu.1.html</A>> -<P> -<BR> - -<DT><B>10.</B> - -<DD> -From sometime after SiSU 0.58 it should be possible to describe SiSU markup +present. For example objects could be saved individually and identified +by their hashes, with an index of how the objects relate to each other +to form a document. +<p> +<ol> +<b>.</b><li>objects include: headings, paragraphs, verse, tables, +images, but not footnotes/endnotes which are numbered separately and tied +to the object from which they are referenced. +<p> <br> +</li><b>.</b><li>i.e. the +<p> <br> +<i>HTML,</i> +<p> <br> +<i>PDF,</i> +<p> <br> +<i>EPUB,</i> +<p> <br> + +<p><i>ODT</i> +<p> <br> +outputs are each built individually and optimised for that form of presentation, +rather than for example the html being a saved version of the odf, or the +pdf being a saved version of the html. +<p> <br> +</li><b>.</b><li> +<p>the different heading levels +<p> <br> +</li><b>.</b><li>units of text, primarily paragraphs and headings, also any tables, poems, + +<p>code-blocks +<p> <br> +</li><b>.</b><li> +<p>An open standard format for e-books +<p> <br> +</li><b>.</b><li>Open Document Format ( +<p> <br> + +<p><i>ODF</i> +<p> <br> +) text +<p> <br> +</li><b>.</b><li> +<p>Specification submitted by Adobe to ISO to become a full open ISO specification + +<p> <br> +<<a href='http://www.linux-watch.com/news/NS7542722606.html'>http://www.linux-watch.com/news/NS7542722606.html</a> +> +<p> <br> +</li><b>.</b><li> +<p>ISO standard ISO/IEC 26300:2006 +<p> <br> +</dd> + +<dt><b>*1.</b> </dt> +<dd>square brackets +<p> <br> +</dd> + +<dt><b>*2.</b> </dt> +<dd>square brackets +<p> <br> +</dd> + +<dt><b>+1.</b> </dt> +<dd>square brackets +<p> <br> +</li><b>.</b><li><<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a> +> +<p> <br> +</li><b>.</b><li><<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a> +> +<p> <br> +</li><b>.</b><li>From sometime after SiSU 0.58 it should be possible to describe SiSU markup using SiSU, which though not an original design goal is useful. -<P> -<BR> - -<DT><B>11.</B> - -<DD> -files should be prepared using UTF-8 character encoding -<P> -<BR> - -<DT><B>12.</B> - -<DD> -a footnote or endnote -<P> -<BR> - -<DT><B>13.</B> - -<DD> -self contained endnote marker & endnote in one -<P> -<BR> - -<DT><B>*.</B> - -<DD> -unnumbered asterisk footnote/endnote, insert multiple asterisks if required -<P> -<BR> - -<DT><B>**.</B> - -<DD> -another unnumbered asterisk footnote/endnote -<P> -<BR> - -<DT><B>*3.</B> - -<DD> -editors notes, numbered asterisk footnote/endnote series -<P> -<BR> - -<DT><B>+2.</B> - -<DD> -editors notes, numbered asterisk footnote/endnote series -<P> -<BR> - -<DT><B>14.</B> - -<DD> -<<A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A>> -<P> -<BR> - -<DT><B>15.</B> - -<DD> -<<A HREF="http://www.ruby-lang.org/en/">http://www.ruby-lang.org/en/</A>> -<P> -<BR> - -<DT><B>17.</B> - -<DD> -Table from the Wealth of Networks by Yochai Benkler -<P> -<BR> - -<<A HREF="http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler">http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler</A>> -<P> -<BR> - -<DT><B>18.</B> - -<DD> -.ssc (for composite) is under consideration but ._sst makes clear that this -is not a regular file to be worked on, and thus less likely that people will -have "accidents", working on a .ssc file that is overwritten by subsequent -processing. It may be however that when the resulting file is shared .ssc is an -appropriate suffix to use. -<P> -<BR> - -<DT><B>20.</B> - -<DD> -<<A HREF="http://www.postgresql.org/">http://www.postgresql.org/</A>> -<P> -<BR> - -<<A HREF="http://advocacy.postgresql.org/">http://advocacy.postgresql.org/</A>> -<BR> - -<<A HREF="http://en.wikipedia.org/wiki/Postgresql">http://en.wikipedia.org/wiki/Postgresql</A>> -<BR> - -<DT><B>21.</B> - -<DD> -<<A HREF="http://www.hwaci.com/sw/sqlite/">http://www.hwaci.com/sw/sqlite/</A>> -<P> -<BR> - -<<A HREF="http://en.wikipedia.org/wiki/Sqlite">http://en.wikipedia.org/wiki/Sqlite</A>> -<BR> - -<DT><B>22.</B> - -<DD> -<<A HREF="http://search.sisudoc.org">http://search.sisudoc.org</A>> -<P> -<BR> - -<DT><B>23.</B> - -<DD> -(which could be extended further with current back-end). As regards scaling +<p> <br> +</li><b>.</b><li> +<p>files should be prepared using +<p> <br> + +<p><i>UTF-8</i> +<p> <br> + +<p>character encoding +<p> <br> +</li><b>.</b><li> +<p>a footnote or endnote +<p> <br> +</li><b>.</b><li>self contained endnote marker & endnote in one +<p> <br> +</dd> + +<dt><b>*.</b> </dt> +<dd>unnumbered asterisk footnote/endnote, insert multiple asterisks if required + +<p> <br> +</dd> + +<dt><b>**.</b> </dt> +<dd>another unnumbered asterisk footnote/endnote +<p> <br> +</dd> + +<dt><b>*3.</b> </dt> +<dd>editors notes, numbered asterisk footnote/endnote series +<p> <br> +</dd> + +<dt><b>+2.</b> </dt> +<dd>editors notes, numbered asterisk footnote/endnote series +<p> <br> +</li><b>.</b><li><<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> +<p> <br> +</li><b>.</b><li><<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a> +> +<p> <br> +</li><b>.</b><li> +<p>Table from the Wealth of Networks by Yochai Benkler +<p> <br> +<<a href='http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler'>http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler</a> +> +<p> <br> +</li><b>.</b><li>.ssc (for composite) is under consideration but ._sst makes clear that this +is not a regular file to be worked on, and thus less likely that people +will have "accidents", working on a .ssc file that is overwritten by subsequent +processing. It may be however that when the resulting file is shared .ssc +is an appropriate suffix to use. +<p> <br> +</li><b>.</b><li><<a href='http://www.postgresql.org/'>http://www.postgresql.org/</a> +> +<p> <br> +<<a href='http://advocacy.postgresql.org/'>http://advocacy.postgresql.org/</a> +> +<p> <br> +<<a href='http://en.wikipedia.org/wiki/Postgresql'>http://en.wikipedia.org/wiki/Postgresql</a> +> +<p> <br> +</li><b>.</b><li><<a href='http://www.hwaci.com/sw/sqlite/'>http://www.hwaci.com/sw/sqlite/</a> +> +<p> <br> +<<a href='http://en.wikipedia.org/wiki/Sqlite'>http://en.wikipedia.org/wiki/Sqlite</a> +> +<p> <br> +</li><b>.</b><li><<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a> +> +<p> <br> +</li><b>.</b><li>(which could be extended further with current back-end). As regards scaling of the database, it is as scalable as the database (here Postgresql) and hardware allow. -<P> -<BR> - -<DT><B>24.</B> - -<DD> -of this feature when demonstrated to an IBM software innovations evaluator -in 2004 he said to paraphrase: this could be of interest to us. We have large -document management systems, you can search hundreds of thousands of documents -and we can tell you which documents meet your search criteria, but there is no -way we can tell you without opening each document where within each your -matches are found. -<P> -<BR> - -<DT><B>25.</B> - -<DD> -There is nothing to stop MySQL support being added in future. -<P> -<BR> - -<DT><B>26.</B> - -<DD> -<<A HREF="http://www.jus.uio.no/sisu/man/sisu.1.html">http://www.jus.uio.no/sisu/man/sisu.1.html</A>> -<P> -<BR> - -<DT><B>27.</B> - -<DD> -<<A HREF="http://www.jus.uio.no/sisu/man/sisu.8.html">http://www.jus.uio.no/sisu/man/sisu.8.html</A>> -<P> -<BR> - -<DT><B>28.</B> - -<DD> -<<A HREF="http://www.jus.uio.no/sisu/man">http://www.jus.uio.no/sisu/man</A>> -<P> -<BR> - -29. the -<B>Debian</B> - -Free Software guidelines require that everything distributed within -<B>Debian</B> - -can be changed - and the documents are authors' works that while freely -distributable are not freely changeable. -<P> -<BR> - -30. named index.html or more extensively through sisu_manifest.html -<BR> - -<P> -</DL> -<A NAME="lbFM"> </A> -<H2>SEE ALSO</H2> - -<BR> - -<I><A HREF="/cgi-bin/man/man2html?1+sisu">sisu</A></I>(1), -<BR> - -<I><A HREF="/cgi-bin/man/man2html?1+sisu-epub">sisu-epub</A></I>(1), -<BR> - -<I><A HREF="/cgi-bin/man/man2html?1+sisu-harvest">sisu-harvest</A></I>(1), -<BR> - -<I><A HREF="/cgi-bin/man/man2html?1+sisu-html">sisu-html</A></I>(1), -<BR> - -<I><A HREF="/cgi-bin/man/man2html?1+sisu-odf">sisu-odf</A></I>(1), -<BR> - -<I><A HREF="/cgi-bin/man/man2html?1+sisu-pdf">sisu-pdf</A></I>(1), -<BR> - -<I><A HREF="/cgi-bin/man/man2html?1+sisu-pg">sisu-pg</A></I>(1), -<BR> - -<I><A HREF="/cgi-bin/man/man2html?1+sisu-sqlite">sisu-sqlite</A></I>(1), -<BR> - -<I><A HREF="/cgi-bin/man/man2html?1+sisu-txt">sisu-txt</A></I>(1). -<BR> - -<I><A HREF="/cgi-bin/man/man2html?7+sisu_vim">sisu_vim</A></I>(7) -<P> -<A NAME="lbFN"> </A> -<H2>HOMEPAGE</H2> - -<BR> - -More information about <B>SiSU</B> can be found at <<I><A HREF="http://www.sisudoc.org/">http://www.sisudoc.org/</A></I>> or <<I><A HREF="http://www.jus.uio.no/sisu/">http://www.jus.uio.no/sisu/</A></I>>. -<P> -<A NAME="lbFO"> </A> -<H2>AUTHOR</H2> - -<B>SiSU</B> is written by Ralph Amissah <<I><A HREF="mailto:ralph@amissah.com">ralph@amissah.com</A></I>>. -<P> - -<HR> -<A NAME="index"> </A><H2>Index</H2> -<DL> -<DT><A HREF="#lbAB">NAME</A><DD> -<DT><A HREF="#lbAC">SYNOPSIS</A><DD> -<DT><A HREF="#lbAD">SISU - MANUAL,</A><DD> -<DT><A HREF="#lbAE">WHAT IS SISU?</A><DD> -<DT><A HREF="#lbAF">1. INTRODUCTION - WHAT IS SISU?</A><DD> -<DT><A HREF="#lbAG">2. COMMANDS SUMMARY</A><DD> -<DT><A HREF="#lbAH">2.1 DESCRIPTION</A><DD> -<DT><A HREF="#lbAI">2.2 DOCUMENT PROCESSING COMMAND FLAGS</A><DD> -<DT><A HREF="#lbAJ">3. COMMAND LINE MODIFIERS</A><DD> -<DT><A HREF="#lbAK">4. DATABASE COMMANDS</A><DD> -<DT><A HREF="#lbAL">5. SHORTCUTS, SHORTHAND FOR MULTIPLE FLAGS</A><DD> -<DT><A HREF="#lbAM">5.1 COMMAND LINE WITH FLAGS - BATCH PROCESSING</A><DD> -<DT><A HREF="#lbAN">6. HELP</A><DD> -<DT><A HREF="#lbAO">6.1 SISU MANUAL</A><DD> -<DT><A HREF="#lbAP">6.2 SISU MAN PAGES</A><DD> -<DT><A HREF="#lbAQ">6.3 SISU BUILT-IN INTERACTIVE HELP</A><DD> -<DT><A HREF="#lbAR">7. INTRODUCTION TO SISU MARKUP[^10]</A><DD> -<DT><A HREF="#lbAS">7.1 SUMMARY</A><DD> -<DT><A HREF="#lbAT">7.2 MARKUP EXAMPLES</A><DD> -<DT><A HREF="#lbAU">7.2.1 ONLINE</A><DD> -<DT><A HREF="#lbAV">7.2.2 INSTALLED</A><DD> -<DT><A HREF="#lbAW">8. MARKUP OF HEADERS</A><DD> -<DT><A HREF="#lbAX">8.1 SAMPLE HEADER</A><DD> -<DT><A HREF="#lbAY">8.2 AVAILABLE HEADERS</A><DD> -<DT><A HREF="#lbAZ">9. MARKUP OF SUBSTANTIVE TEXT</A><DD> -<DT><A HREF="#lbBA">9.1 HEADING LEVELS</A><DD> -<DT><A HREF="#lbBB">9.2 FONT ATTRIBUTES</A><DD> -<DT><A HREF="#lbBC">9.3 INDENTATION AND BULLETS</A><DD> -<DT><A HREF="#lbBD">9.4 HANGING INDENTS</A><DD> -<DT><A HREF="#lbBE">9.5 FOOTNOTES / ENDNOTES</A><DD> -<DT><A HREF="#lbBF">9.6 LINKS</A><DD> -<DT><A HREF="#lbBG">9.6.1 NAKED URLS WITHIN TEXT, DEALING WITH URLS</A><DD> -<DT><A HREF="#lbBH">9.6.2 LINKING TEXT</A><DD> -<DT><A HREF="#lbBI">9.7 GROUPED TEXT</A><DD> -<DT><A HREF="#lbBJ">9.7.1 TABLES</A><DD> -<DT><A HREF="#lbBK">9.7.2 POEM</A><DD> -<DT><A HREF="#lbBL">9.7.3 GROUP</A><DD> -<DT><A HREF="#lbBM">9.7.4 CODE</A><DD> -<DT><A HREF="#lbBN">9.8 ADDITIONAL BREAKS - LINEBREAKS WITHIN OBJECTS, COLUMN AND PAGE-BREAKS</A><DD> -<DT><A HREF="#lbBO">9.8.1 LINE-BREAKS</A><DD> -<DT><A HREF="#lbBP">9.8.2 PAGE BREAKS</A><DD> -<DT><A HREF="#lbBQ">9.9 BOOK INDEX</A><DD> -<DT><A HREF="#lbBR">10. COMPOSITE DOCUMENTS MARKUP</A><DD> -<DT><A HREF="#lbBS">11. MARKUP SYNTAX HISTORY</A><DD> -<DT><A HREF="#lbBT">11.1 NOTES RELATED TO FILES-TYPES AND MARKUP SYNTAX</A><DD> -<DT><A HREF="#lbBU">12. SISU FILETYPES</A><DD> -<DT><A HREF="#lbBV">12.1 .SST .SSM .SSI MARKED UP PLAIN TEXT</A><DD> -<DT><A HREF="#lbBW">12.1.1 SISU TEXT - REGULAR FILES (.SST)</A><DD> -<DT><A HREF="#lbBX">12.1.2 SISU MASTER FILES (.SSM)</A><DD> -<DT><A HREF="#lbBY">12.1.3 SISU INSERT FILES (.SSI)</A><DD> -<DT><A HREF="#lbBZ">12.2 SISUPOD, ZIPPED BINARY CONTAINER (SISUPOD.ZIP, .SSP)</A><DD> -<DT><A HREF="#lbCA">13. EXPERIMENTAL ALTERNATIVE INPUT REPRESENTATIONS</A><DD> -<DT><A HREF="#lbCB">13.1 ALTERNATIVE XML</A><DD> -<DT><A HREF="#lbCC">13.1.1 XML SAX REPRESENTATION</A><DD> -<DT><A HREF="#lbCD">13.1.2 XML DOM REPRESENTATION</A><DD> -<DT><A HREF="#lbCE">13.1.3 XML NODE REPRESENTATION</A><DD> -<DT><A HREF="#lbCF">14. CONFIGURATION</A><DD> -<DT><A HREF="#lbCG">14.1 DETERMINING THE CURRENT CONFIGURATION</A><DD> -<DT><A HREF="#lbCH">14.2 CONFIGURATION FILES (CONFIG.YML)</A><DD> -<DT><A HREF="#lbCI">15. SKINS</A><DD> -<DT><A HREF="#lbCJ">15.1 DOCUMENT SKIN</A><DD> -<DT><A HREF="#lbCK">15.2 DIRECTORY SKIN</A><DD> -<DT><A HREF="#lbCL">15.3 SITE SKIN</A><DD> -<DT><A HREF="#lbCM">15.4 SAMPLE SKINS</A><DD> -<DT><A HREF="#lbCN">16. CSS - CASCADING STYLE SHEETS (FOR HTML, XHTML AND XML)</A><DD> -<DT><A HREF="#lbCO">17. ORGANISING CONTENT - DIRECTORY STRUCTURE AND MAPPING</A><DD> -<DT><A HREF="#lbCP">17.1 DOCUMENT SOURCE DIRECTORY</A><DD> -<DT><A HREF="#lbCQ">17.1.1 GENERAL DIRECTORIES</A><DD> -<DT><A HREF="#lbCR">17.2 DOCUMENT OUTPUT DIRECTORY STRUCTURES</A><DD> -<DT><A HREF="#lbCS">17.2.1 OUTPUT DIRECTORY ROOT</A><DD> -<DT><A HREF="#lbCT">17.2.2 ALTERNATIVE OUTPUT STRUCTURES</A><DD> -<DT><A HREF="#lbCU">17.2.3 BY LANGUAGE</A><DD> -<DT><A HREF="#lbCV">17.2.4 BY FILETYPE</A><DD> -<DT><A HREF="#lbCW">17.2.5 BY FILENAME</A><DD> -<DT><A HREF="#lbCX">17.2.6 REMOTE DIRECTORIES</A><DD> -<DT><A HREF="#lbCY">17.2.7 SISUPOD</A><DD> -<DT><A HREF="#lbCZ">17.3 ORGANISING CONTENT</A><DD> -<DT><A HREF="#lbDA">18. HOMEPAGES</A><DD> -<DT><A HREF="#lbDB">18.1 HOME PAGE AND OTHER CUSTOM BUILT PAGES IN A SUB-DIRECTORY</A><DD> -<DT><A HREF="#lbDC">18.2 HOME PAGE WITHIN A SKIN</A><DD> -<DT><A HREF="#lbDD">19. MARKUP AND OUTPUT EXAMPLES</A><DD> -<DT><A HREF="#lbDE">19.1 MARKUP EXAMPLES</A><DD> -<DT><A HREF="#lbDF">20. SISU SEARCH - INTRODUCTION</A><DD> -<DT><A HREF="#lbDG">21. SQL</A><DD> -<DT><A HREF="#lbDH">21.1 POPULATING SQL TYPE DATABASES</A><DD> -<DT><A HREF="#lbDI">22. POSTGRESQL</A><DD> -<DT><A HREF="#lbDJ">22.1 NAME</A><DD> -<DT><A HREF="#lbDK">22.2 DESCRIPTION</A><DD> -<DT><A HREF="#lbDL">22.3 SYNOPSIS</A><DD> -<DT><A HREF="#lbDM">22.4 COMMANDS</A><DD> -<DT><A HREF="#lbDN">22.4.1 CREATE AND DESTROY DATABASE</A><DD> -<DT><A HREF="#lbDO">22.4.2 IMPORT AND REMOVE DOCUMENTS</A><DD> -<DT><A HREF="#lbDP">23. SQLITE</A><DD> -<DT><A HREF="#lbDQ">23.1 NAME</A><DD> -<DT><A HREF="#lbDR">23.2 DESCRIPTION</A><DD> -<DT><A HREF="#lbDS">23.3 SYNOPSIS</A><DD> -<DT><A HREF="#lbDT">23.4 COMMANDS</A><DD> -<DT><A HREF="#lbDU">23.4.1 CREATE AND DESTROY DATABASE</A><DD> -<DT><A HREF="#lbDV">23.4.2 IMPORT AND REMOVE DOCUMENTS</A><DD> -<DT><A HREF="#lbDW">24. INTRODUCTION</A><DD> -<DT><A HREF="#lbDX">24.1 SEARCH - DATABASE FRONTEND SAMPLE, UTILISING DATABASE AND SISU FEATURES,</A><DD> -<DT><A HREF="#lbDY">24.2 SEARCH FORM</A><DD> -<DT><A HREF="#lbDZ">25. SISU_WEBRICK</A><DD> -<DT><A HREF="#lbEA">25.1 NAME</A><DD> -<DT><A HREF="#lbEB">25.2 SYNOPSIS</A><DD> -<DT><A HREF="#lbEC">25.3 DESCRIPTION</A><DD> -<DT><A HREF="#lbED">25.4 SUMMARY OF MAN PAGE</A><DD> -<DT><A HREF="#lbEE">25.5 DOCUMENT PROCESSING COMMAND FLAGS</A><DD> -<DT><A HREF="#lbEF">25.6 FURTHER INFORMATION</A><DD> -<DT><A HREF="#lbEG">25.7 AUTHOR</A><DD> -<DT><A HREF="#lbEH">25.8 SEE ALSO</A><DD> -<DT><A HREF="#lbEI">26. REMOTE SOURCE DOCUMENTS</A><DD> -<DT><A HREF="#lbEJ">REMOTE DOCUMENT OUTPUT</A><DD> -<DT><A HREF="#lbEK">27. REMOTE OUTPUT</A><DD> -<DT><A HREF="#lbEL">27.1 COMMANDS</A><DD> -<DT><A HREF="#lbEM">27.2 CONFIGURATION</A><DD> -<DT><A HREF="#lbEN">28. REMOTE SERVERS</A><DD> -<DT><A HREF="#lbEO">29. QUICKSTART - GETTING STARTED HOWTO</A><DD> -<DT><A HREF="#lbEP">29.1 INSTALLATION</A><DD> -<DT><A HREF="#lbEQ">29.1.1 DEBIAN INSTALLATION</A><DD> -<DT><A HREF="#lbER">29.1.2 RPM INSTALLATION</A><DD> -<DT><A HREF="#lbES">29.1.3 INSTALLATION FROM SOURCE</A><DD> -<DT><A HREF="#lbET">29.2 TESTING SISU, GENERATING OUTPUT</A><DD> -<DT><A HREF="#lbEU">29.2.1 BASIC TEXT, PLAINTEXT, HTML, XML, ODF, EPUB</A><DD> -<DT><A HREF="#lbEV">29.2.2 LATEX / PDF</A><DD> -<DT><A HREF="#lbEW">29.2.3 RELATIONAL DATABASE - POSTGRESQL, SQLITE</A><DD> -<DT><A HREF="#lbEX">29.3 GETTING HELP</A><DD> -<DT><A HREF="#lbEY">29.3.1 THE MAN PAGES</A><DD> -<DT><A HREF="#lbEZ">29.3.2 BUILT IN HELP</A><DD> -<DT><A HREF="#lbFA">29.3.3 THE HOME PAGE</A><DD> -<DT><A HREF="#lbFB">29.4 MARKUP SAMPLES</A><DD> -<DT><A HREF="#lbFC">30. EDITOR FILES, SYNTAX HIGHLIGHTING</A><DD> -<DT><A HREF="#lbFD">31. HOW DOES SISU WORK?</A><DD> -<DT><A HREF="#lbFE">32. SUMMARY OF FEATURES</A><DD> -<DT><A HREF="#lbFF">33. HELP SOURCES</A><DD> -<DT><A HREF="#lbFG">33.1 MAN PAGES</A><DD> -<DT><A HREF="#lbFH">33.2 SISU GENERATED OUTPUT - LINKS TO HTML</A><DD> -<DT><A HREF="#lbFI">33.2.1 WWW.SISUDOC.ORG</A><DD> -<DT><A HREF="#lbFJ">33.3 MAN2HTML</A><DD> -<DT><A HREF="#lbFK">33.3.1 LOCALLY INSTALLED</A><DD> -<DT><A HREF="#lbFL">33.3.2 WWW.JUS.UIO.NO/SISU</A><DD> -<DT><A HREF="#lbFM">SEE ALSO</A><DD> -<DT><A HREF="#lbFN">HOMEPAGE</A><DD> -<DT><A HREF="#lbFO">AUTHOR</A><DD> -</DL> -<HR> -This document was created by -<A HREF="/cgi-bin/man/man2html">man2html</A>, -using the manual pages.<BR> -Time: 04:10:50 GMT, May 26, 2012 -</BODY> -</HTML> +<p> <br> +</li><b>.</b><li>of this feature when demonstrated to an IBM software innovations evaluator +in 2004 he said to paraphrase: this could be of interest to us. We have +large document management systems, you can search hundreds of thousands +of documents and we can tell you which documents meet your search criteria, +but there is no way we can tell you without opening each document where +within each your matches are found. +<p> <br> + +<p> </li> +</ol> + +<h2><a name='sect100' href='#toc100'>See Also</a></h2> + <a href='http:~/bin/man2html?sisu:1'>sisu(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-epub:1'>sisu-epub(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-harvest:1'>sisu-harvest(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-html:1'>sisu-html(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-odf:1'>sisu-odf(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-pdf:1'>sisu-pdf(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-pg:1'>sisu-pg(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-sqlite:1'>sisu-sqlite(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-txt:1'>sisu-txt(1)</a> +.<br> + <a href='http:~/bin/man2html?sisu_vim:7'>sisu_vim(7)</a> +<br> + +<h2><a name='sect101' href='#toc101'>Homepage</a></h2> + More information about SiSU can be found at <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> +or <<a href='http://www.jus.uio.no/sisu/'>http://www.jus.uio.no/sisu/</a> +><br> + +<h2><a name='sect102' href='#toc102'>Source</a></h2> + <<a href='http://sources.sisudoc.org/'>http://sources.sisudoc.org/</a> +><br> + +<h2><a name='sect103' href='#toc103'>Author</a></h2> + SiSU is written by Ralph Amissah <ralph@amissah.com><br> + <p> + +<hr><p> +<a name='toc'><b>Table of Contents</b></a><p> +<ul> +<li><a name='toc0' href='#sect0'>Name</a></li> +<li><a name='toc1' href='#sect1'>Synopsis</a></li> +<li><a name='toc2' href='#sect2'>Sisu - Manual,</a></li> +<li><a name='toc3' href='#sect3'>What is Sisu?</a></li> +<li><a name='toc4' href='#sect4'>Introduction - What is Sisu?</a></li> +<li><a name='toc5' href='#sect5'>Commands Summary</a></li> +<li><a name='toc6' href='#sect6'>Description</a></li> +<li><a name='toc7' href='#sect7'>Document Processing Command Flags</a></li> +<li><a name='toc8' href='#sect8'>Command Line Modifiers</a></li> +<li><a name='toc9' href='#sect9'>Database Commands</a></li> +<li><a name='toc10' href='#sect10'>Shortcuts, Shorthand for Multiple Flags</a></li> +<li><a name='toc11' href='#sect11'>Command Line with Flags - Batch Processing</a></li> +<li><a name='toc12' href='#sect12'>Help</a></li> +<li><a name='toc13' href='#sect13'>Sisu Manual</a></li> +<li><a name='toc14' href='#sect14'>Sisu Man Pages</a></li> +<li><a name='toc15' href='#sect15'>Sisu Built-in Interactive Help</a></li> +<li><a name='toc16' href='#sect16'>Introduction to Sisu Markup[^11]</a></li> +<li><a name='toc17' href='#sect17'>Summary</a></li> +<li><a name='toc18' href='#sect18'>Markup Examples</a></li> +<li><a name='toc19' href='#sect19'>Online</a></li> +<li><a name='toc20' href='#sect20'>Installed</a></li> +<li><a name='toc21' href='#sect21'>Markup of Headers</a></li> +<li><a name='toc22' href='#sect22'>Sample Header</a></li> +<li><a name='toc23' href='#sect23'>Available Headers</a></li> +<li><a name='toc24' href='#sect24'>Markup of Substantive Text</a></li> +<li><a name='toc25' href='#sect25'>Heading Levels</a></li> +<li><a name='toc26' href='#sect26'>Font Attributes</a></li> +<li><a name='toc27' href='#sect27'>Indentation and Bullets</a></li> +<li><a name='toc28' href='#sect28'>Hanging Indents</a></li> +<li><a name='toc29' href='#sect29'>Footnotes / Endnotes</a></li> +<li><a name='toc30' href='#sect30'>Links</a></li> +<li><a name='toc31' href='#sect31'>Naked Urls Within Text, Dealing with Urls</a></li> +<li><a name='toc32' href='#sect32'>Linking Text</a></li> +<li><a name='toc33' href='#sect33'>Linking Images</a></li> +<li><a name='toc34' href='#sect34'>Link Shortcut for Multiple Versions of a Sisu Document in the Same Directory</a></li> +<li><a name='toc35' href='#sect35'>Grouped Text</a></li> +<li><a name='toc36' href='#sect36'>Tables</a></li> +<li><a name='toc37' href='#sect37'>Poem</a></li> +<li><a name='toc38' href='#sect38'>Group</a></li> +<li><a name='toc39' href='#sect39'>Code</a></li> +<li><a name='toc40' href='#sect40'>Additional Breaks - Linebreaks Within Objects, Column and Page-breaks</a></li> +<li><a name='toc41' href='#sect41'>Line-breaks</a></li> +<li><a name='toc42' href='#sect42'>Page Breaks</a></li> +<li><a name='toc43' href='#sect43'>Book Index</a></li> +<li><a name='toc44' href='#sect44'>Composite Documents Markup</a></li> +<li><a name='toc45' href='#sect45'>Sisu Filetypes</a></li> +<li><a name='toc46' href='#sect46'>.sst .ssm .ssi Marked Up Plain Text</a></li> +<li><a name='toc47' href='#sect47'>Sisu Text - Regular Files (.sst)</a></li> +<li><a name='toc48' href='#sect48'>Sisu Master Files (.ssm)</a></li> +<li><a name='toc49' href='#sect49'>Sisu Insert Files (.ssi)</a></li> +<li><a name='toc50' href='#sect50'>Sisupod, Zipped Binary Container (sisupod.zip, .ssp)</a></li> +<li><a name='toc51' href='#sect51'>Configuration</a></li> +<li><a name='toc52' href='#sect52'>Configuration Files</a></li> +<li><a name='toc53' href='#sect53'>Config.yml</a></li> +<li><a name='toc54' href='#sect54'>Sisu_document_make</a></li> +<li><a name='toc55' href='#sect55'>Css - Cascading Style Sheets (for Html, Xhtml and Xml)</a></li> +<li><a name='toc56' href='#sect56'>Organising Content - Directory Structure and Mapping</a></li> +<li><a name='toc57' href='#sect57'>Document Source Directory</a></li> +<li><a name='toc58' href='#sect58'>General Directories</a></li> +<li><a name='toc59' href='#sect59'>Document Output Directory Structures</a></li> +<li><a name='toc60' href='#sect60'>Output Directory Root</a></li> +<li><a name='toc61' href='#sect61'>Alternative Output Structures</a></li> +<li><a name='toc62' href='#sect62'>by Language</a></li> +<li><a name='toc63' href='#sect63'>by Filetype</a></li> +<li><a name='toc64' href='#sect64'>by Filename</a></li> +<li><a name='toc65' href='#sect65'>Remote Directories</a></li> +<li><a name='toc66' href='#sect66'>Sisupod</a></li> +<li><a name='toc67' href='#sect67'>Organising Content</a></li> +<li><a name='toc68' href='#sect68'>Homepages</a></li> +<li><a name='toc69' href='#sect69'>Home Page and Other Custom Built Pages in a Sub-directory</a></li> +<li><a name='toc70' href='#sect70'>Markup and Output Examples</a></li> +<li><a name='toc71' href='#sect71'>Markup Examples</a></li> +<li><a name='toc72' href='#sect72'>Sisu Markup Samples</a></li> +<li><a name='toc73' href='#sect73'>Sisu Search - Introduction</a></li> +<li><a name='toc74' href='#sect74'>Sql</a></li> +<li><a name='toc75' href='#sect75'>Populating Sql Type Databases</a></li> +<li><a name='toc76' href='#sect76'>Postgresql</a></li> +<li><a name='toc77' href='#sect77'>Name</a></li> +<li><a name='toc78' href='#sect78'>Description</a></li> +<li><a name='toc79' href='#sect79'>Synopsis</a></li> +<li><a name='toc80' href='#sect80'>Commands</a></li> +<li><a name='toc81' href='#sect81'>Create and Destroy Database</a></li> +<li><a name='toc82' href='#sect82'>Import and Remove Documents</a></li> +<li><a name='toc83' href='#sect83'>Sqlite</a></li> +<li><a name='toc84' href='#sect84'>Name</a></li> +<li><a name='toc85' href='#sect85'>Description</a></li> +<li><a name='toc86' href='#sect86'>Synopsis</a></li> +<li><a name='toc87' href='#sect87'>Commands</a></li> +<li><a name='toc88' href='#sect88'>Create and Destroy Database</a></li> +<li><a name='toc89' href='#sect89'>Import and Remove Documents</a></li> +<li><a name='toc90' href='#sect90'>Introduction</a></li> +<li><a name='toc91' href='#sect91'>Search - Database Frontend Sample, Utilising Database and Sisu Features,</a></li> +<li><a name='toc92' href='#sect92'>Search Form</a></li> +<li><a name='toc93' href='#sect93'>Sisu_webrick</a></li> +<li><a name='toc94' href='#sect94'>Name</a></li> +<li><a name='toc95' href='#sect95'>Synopsis</a></li> +<li><a name='toc96' href='#sect96'>Description</a></li> +<li><a name='toc97' href='#sect97'>Summary of Man Page</a></li> +<li><a name='toc98' href='#sect98'>Document Processing Command Flags</a></li> +<li><a name='toc99' href='#sect99'>Summary of Features</a></li> +<li><a name='toc100' href='#sect100'>See Also</a></li> +<li><a name='toc101' href='#sect101'>Homepage</a></li> +<li><a name='toc102' href='#sect102'>Source</a></li> +<li><a name='toc103' href='#sect103'>Author</a></li> +</ul> +</body> +</html> diff --git a/data/doc/sisu/html/sisu4.1.html b/data/doc/sisu/html/sisu4.1.html new file mode 100644 index 00000000..345e574b --- /dev/null +++ b/data/doc/sisu/html/sisu4.1.html @@ -0,0 +1,3693 @@ +<!-- manual page source format generated by PolyglotMan v3.2, --> +<!-- available at http://polyglotman.sourceforge.net/ --> + +<html> +<head> +<title>"sisu"("1") manual page</title> +</head> +<body bgcolor='white'> +<a href='#toc'>Table of Contents</a><p> +<br> + +<h2><a name='sect0' href='#toc0'>Name</a></h2> +<br> +sisu - documents: markup, structuring, publishing in multiple standard formats, +and search <br> + +<h2><a name='sect1' href='#toc1'>Synopsis</a></h2> +<br> +sisu [-short-options|--long-options] [filename/wildcard] +<p> <br> +sisu [-abCcDdeFGghIikLMmNnoPpQqRrSsTtUuVvWwXxYyZ_0-9] [filename/wildcard] + +<p> <br> +sisu --txt --html --epub --odt --pdf --wordmap --sqlite --manpage --texinfo --sisupod --source +--qrcode [filename/wildcard] +<p> <br> +sisu [-Ddcv] [instruction] [filename/wildcard] +<p> <br> +sisu --pg (--createdb|update [filename/wildcard]|--dropall) +<p> <br> +sisu [operations] +<p> <br> +sisu [-CcFLSVvW] +<p> <br> +sisu (--configure|--webrick|--sample-search-form) +<h2><a name='sect2' href='#toc2'>Sisu - Manual,</a></h2> +RALPH AMISSAH <br> + +<p> +<h2><a name='sect3' href='#toc3'>What is Sisu?</a></h2> +<br> + +<p> +<h2><a name='sect4' href='#toc4'>Introduction - What is Sisu?</a></h2> +<br> + +<p> <br> +<b>SiSU</b> is a framework for document structuring, publishing (in multiple open +standard formats) and search, comprising of: (a) a lightweight document +structure and presentation markup syntax; and (b) an accompanying engine +for generating standard document format outputs from documents prepared +in sisu markup syntax, which is able to produce multiple standard outputs +(including the population of sql databases) that (can) share a common numbering +system for the citation of text within a document. +<p> <br> +<b>SiSU</b> is developed under an open source, software libre license ( <i>GPLv3</i> +). Its use case for development is work with medium to large document sets +and cope with evolving document formats/ representation technologies. Documents +are prepared once, and generated as need be to update the technical presentation +or add additional output formats. Various output formats (including search +related output) share a common mechanism for cross-output-format citation. + +<p> <br> +<b>SiSU</b> both defines a markup syntax and provides an engine that produces +open standards format outputs from documents prepared with <b>SiSU</b> markup. +From a single lightly prepared document sisu custom builds several standard +output formats which share a common (text object) numbering system for +citation of content within a document (that also has implications for search). +The sisu engine works with an abstraction of the document’s structure and +content from which it is possible to generate different forms of representation +of the document. Significantly <b>SiSU</b> markup is more sparse than html and +outputs which include <i>HTML,</i> <i>EPUB,</i> <i>ODT</i> (Open Document Format text), <i>LaTeX,</i> +landscape and portrait <i>PDF,</i> all of which can be added to and updated. <b>SiSU</b> +is also able to populate <i>SQL</i> type databases at an object level, which means +that searches can be made with that degree of granularity. +<p> <br> +Source document preparation and output generation is a two step process: +(i) document source is prepared, that is, marked up in sisu markup syntax +and (ii) the desired output subsequently generated by running the sisu +engine against document source. Output representations if updated (in the +sisu engine) can be generated by re-running the engine against the prepared +source. Using <b>SiSU</b> markup applied to a document, <b>SiSU</b> custom builds (to +take advantage of the strengths of different ways of representing documents) +various standard open output formats including plain text, <i>HTML,</i> <i>XHTML,</i> +<i>XML,</i> <i>EPUB,</i> <i>ODT,</i> <i>LaTeX</i> or <i>PDF</i> files, and populate an <i>SQL</i> database with objects[^1] +(equating generally to paragraph-sized chunks) so searches may be performed +and matches returned with that degree of granularity ( e.g. your search criteria +is met by these documents and at these locations within each document). +Document output formats share a common object numbering system for locating +content. This is particularly suitable for "published" works (finalized +texts as opposed to works that are frequently changed or updated) for which +it provides a fixed means of reference of content. +<p> <br> +In preparing a <b>SiSU</b> document you optionally provide semantic information +related to the document in a document header, and in marking up the substantive +text provide information on the structure of the document, primarily indicating +heading levels and footnotes. You also provide information on basic text +attributes where used. The rest is automatic, sisu from this information +custom builds[^2] the different forms of output requested. +<p> <br> +<b>SiSU</b> works with an abstraction of the document based on its structure which +is comprised of its headings[^3] and objects[^4], which enables <b>SiSU</b> to represent +the document in many different ways, and to take advantage of the strengths +of different ways of presenting documents. The objects are numbered, and +these numbers can be used to provide a common basis for citing material +within a document across the different output format types. This is significant +as page numbers are not well suited to the digital age, in web publishing, +changing a browser’s default font or using a different browser can mean +that text will appear on a different page; and publishing in different +formats, html, landscape and portrait pdf etc. again page numbers are not +useful to cite text. Dealing with documents at an object level together +with object numbering also has implications for search that <b>SiSU</b> is able +to take advantage of. +<p> <br> +One of the challenges of maintaining documents is to keep them in a format +that allows use of them independently of proprietary platforms. Consider +issues related to dealing with legacy proprietary formats today and what +guarantee you have that old proprietary formats will remain (or can be +read without proprietary software/equipment) in 15 years time, or the way +the way in which html has evolved over its relatively short span of existence. +<b>SiSU</b> provides the flexibility of producing documents in multiple non-proprietary +open formats including <i>HTML,</i> <i>EPUB,</i> [^5] <i>ODT,</i> [^6] <i>PDF</i> [^7] <i>ODF,</i> [^8]. Whilst +<b>SiSU</b> relies on software, the markup is uncomplicated and minimalistic which +guarantees that future engines can be written to run against it. It is also +easily converted to other formats, which means documents prepared in <b>SiSU</b> +can be migrated to other document formats. Further security is provided +by the fact that the software itself, <b>SiSU</b> is available under <i>GPLv3</i> a licence +that guarantees that the source code will always be open, and free as in +libre, which means that that code base can be used, updated and further +developed as required under the terms of its license. Another challenge +is to keep up with a moving target. <b>SiSU</b> permits new forms of output to +be added as they become important, (Open Document Format text was added +in 2006 when it became an ISO standard for office applications and the +archival of documents), <i>EPUB</i> was introduced in 2009; and allows the technical +representations existing output to be updated ( <i>HTML</i> has evolved and the +related module has been updated repeatedly over the years, presumably when +the World Wide Web Consortium (w3c) finalises <i>HTML</i> 5 which is currently +under development, the <i>HTML</i> module will again be updated allowing all existing +documents to be regenerated as <i>HTML</i> 5). +<p> <br> +The document formats are written to the file-system and available for indexing +by independent indexing tools, whether off the web like Google and Yahoo +or on the site like Lucene and Hyperestraier. +<p> <br> +<b>SiSU</b> also provides other features such as concordance files and document +content certificates, and the working against an abstraction of document +structure has further possibilities for the research and development of +other document representations, the availability of objects is useful for +example for topic maps and thesauri, together with the flexibility of <b>SiSU</b> +offers great possibilities. +<p> <br> +<b>SiSU</b> is primarily for published works, which can take advantage of the +citation system to reliably reference its documents. <b>SiSU</b> works well in +a complementary manner with such collaborative technologies as Wikis, which +can take advantage of and be used to discuss the substance of content prepared +in <b>SiSU.</b> +<p> <br> +<<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> +<p> <br> +<<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> +> +<p> +<h2><a name='sect5' href='#toc5'>Commands Summary</a></h2> +<br> + +<p> +<h2><a name='sect6' href='#toc6'>Description</a></h2> + +<p> <br> +<b>SiSU</b> is a document publishing system, that from a simple single marked-up +document, produces multiple output formats including: <i>plaintext,</i> <i>HTML,</i> +<i>XHTML,</i> <i>XML,</i> <i>EPUB,</i> <i>ODT</i> ( <i>OpenDocument</i> ( <i>ODF</i> ) text), <i>LaTeX,</i> <i>PDF,</i> info, and +<i>SQL</i> ( <i>PostgreSQL</i> and <i>SQLite</i> ) , which share text object numbers ("object +citation numbering") and the same document structure information. For more +see: <<a href='http://sisudoc.org'>http://sisudoc.org</a> +> or <<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> +> +<p> +<h2><a name='sect7' href='#toc7'>Document Processing +Command Flags</a></h2> + +<p> +<dl> + +<dt><b>-a [filename/wildcard]</b> </dt> +<dd>produces <i>plaintext</i> with Unix linefeeds +and without markup, (object numbers are omitted), has footnotes at end +of each paragraph that contains them [ -A for output file] [see -e for endnotes]. +(Options include: --endnotes for endnotes --footnotes for footnotes at the +end of each paragraph --unix for unix linefeed (default) --msdos for msdos +linefeed) +<p> </dd> + +<dt><b>-b [filename/wildcard]</b> </dt> +<dd>see --xhtml +<p> </dd> + +<dt><b>--by-*</b> </dt> +<dd>see --output-by-* +<p> </dd> + +<dt><b>-C</b> </dt> +<dd>configure/initialise +shared output directory files initialize shared output directory (config +files such as css and dtd files are not updated if they already exist unless +modifier is used). -C --init-site configure/initialise site more extensive than +-C on its own, shared output directory files/force update, existing shared +output config files such as css and dtd files are updated if this modifier +is used. +<p> </dd> + +<dt><b>-CC</b> </dt> +<dd>see --configure +<p> </dd> + +<dt><b>-c [filename/wildcard]</b> </dt> +<dd>see --color-toggle +<p> </dd> + +<dt><b>--color-toggle +[filename/wildcard]</b> </dt> +<dd>screen toggle ansi screen colour on or off depending +on default set (unless -c flag is used: if sisurc colour default is set +to ’true’, output to screen will be with colour, if sisurc colour default +is set to ’false’ or is undefined screen output will be without colour). Alias + +<p>- +<p>c +<p> </dd> + +<dt><b>--configure</b> </dt> +<dd>configure/initialise shared output directory files initialize +shared output directory (config files such as css and dtd files are not +updated if they already exist unless modifier is used). The equivalent of: +-C --init-site configure/initialise site, more extensive than -C on its own, +shared output directory files/force update, existing shared output config +files such as css and dtd files are updated if -CC is used. +<p> </dd> + +<dt><b>--concordance +[filename/wildcard]</b> </dt> +<dd>produces concordance (wordmap) a rudimentary index +of all the words in a document. (Concordance files are not generated for +documents of over 260,000 words unless this limit is increased in the file +sisurc.yml). Alias -w +<p> </dd> + +<dt><b>-D [instruction] [filename]</b> </dt> +<dd>see --pg +<p> </dd> + +<dt><b>-d [--db-[database type + (sqlite|pg)]] --[instruction] [filename]</b> </dt> +<dd>see --sqlite +<p> </dd> + +<dt><b>--dal [filename/wildcard/url]</b> +</dt> +<dd>assumed for most other flags, creates new intermediate files for processing +(document abstraction) that is used in all subsequent processing of other +output. This step is assumed for most processing flags. To skip it see -n. + +<p>Alias -m +<p> </dd> + +<dt><b>--delete [filename/wildcard]</b> </dt> +<dd>see --zap +<p> </dd> + +<dt><b>--dump[=directory_path] [filename/wildcard]</b> +</dt> +<dd>places output in directory specified, if none is specified in the current +directory (pwd). Compare --redirect +<p> </dd> + +<dt><b>-e [filename/wildcard]</b> </dt> +<dd>see --epub +<p> </dd> + +<dt><b>--epub +[filename/wildcard]</b> </dt> +<dd>produces an epub document, [sisu version >=2 ] (filename.epub). + +<p>Alias -e +<p> </dd> + +<dt><b>--exc-*</b> </dt> +<dd>exclude output feature, overrides configuration settings +--exc- <i>ocn,</i> (exclude <i>object</i> citation numbering, (switches off <i>object</i> citation +numbering ) , affects html (seg, scroll), epub, xhtml, xml, pdf) ; --exc-toc, +(exclude table of contents, affects html (scroll), epub, pdf) ; --exc-links-to-manifest, +--exc-manifest-links, (exclude links to manifest, affects html (seg, scroll)); +--exc-search-form, (exclude search form, affects html (seg, scroll), manifest); +--exc-minitoc, (exclude mini table of contents, affects html (seg), concordance, +manifest); --exc-manifest-minitoc, (exclude mini table of contents, affects +manifest); --exc-html-minitoc, (exclude mini table of contents, affects html +(seg), concordance); --exc-html-navigation, (exclude navigation, affects html +(seg)); --exc-html-navigation-bar, (exclude navigation bar, affects html (seg)); +--exc-html-search-form, (exclude search form, affects html (seg, scroll)); --exc-html-right-pane, +(exclude right pane/column, affects html (seg, scroll)); --exc-html-top-band, +(exclude top band, affects html (seg, scroll), concordance (minitoc forced +on to provide seg navigation)); --exc-segsubtoc (exclude sub table of contents, +affects html (seg), epub) ; see also --inc-* +<p> </dd> + +<dt><b>-F [--webserv=webrick]</b> </dt> +<dd>see --sample-search-form + +<p> </dd> + +<dt><b>-f [optional string part of filename]</b> </dt> +<dd>see --find +<p> </dd> + +<dt><b>--find [optional string part + of filename]</b> </dt> +<dd>without match string, glob all .sst .ssm files in directory +(including language subdirectories). With match string, find files that +match given string in directory (including language subdirectories). Alias +-f, --glob, -G +<p> </dd> + +<dt><b>-G [optional string part of filename]</b> </dt> +<dd>see --find +<p> </dd> + +<dt><b>-g [filename/wildcard]</b> +</dt> +<dd> +<p>see --git +<p> </dd> + +<dt><b>--git [filename/wildcard]</b> </dt> +<dd>produces or updates markup source file +structure in a git repo (experimental and subject to change). Alias -g +<p> </dd> + +<dt><b>--glob +[optional string part of filename]</b> </dt> +<dd>see --find +<p> </dd> + +<dt><b>-h [filename/wildcard]</b> </dt> +<dd>see + +<p>- +<p>- +<p>html +<p> </dd> + +<dt><b>--harvest *.ss[tm]</b> </dt> +<dd>makes two lists of sisu output based on the sisu +markup documents in a directory: list of author and authors works (year +and titles), and; list by topic with titles and author. Makes use of header +metadata fields (author, title, date, topic_register). Can be used with +maintenance (-M) and remote placement (-R) flags. +<p> </dd> + +<dt><b>--help [topic]</b> </dt> +<dd>provides help +on the selected topic, where topics (keywords) include: list, (com)mands, +short(cuts), (mod)ifiers, (env)ironment, markup, syntax, headers, headings, +endnotes, tables, example, customise, skin, (dir)ectories, path, (lang)uage, +db, install, setup, (conf)igure, convert, termsheet, search, sql, features, +license. +<p> </dd> + +<dt><b>--html [filename/wildcard]</b> </dt> +<dd>produces html output, segmented text +with table of contents (toc.html and index.html) and the document in a single +file (scroll.html). Alias -h +<p> </dd> + +<dt><b>-I [filename/wildcard]</b> </dt> +<dd>see --texinfo +<p> </dd> + +<dt><b>-i [filename/wildcard]</b> +</dt> +<dd> +<p>see --manpage +<p> </dd> + +<dt><b>--inc-*</b> </dt> +<dd>include output feature, overrides configuration settings, +(usually the default if none set), has precedence over --exc-* (exclude output +feature). Some detail provided under --exc-*, see --exc-* +<p> </dd> + +<dt><b>-j [filename/wildcard]</b> +</dt> +<dd>copies images associated with a file for use by html, xhtml & xml outputs +(automatically invoked by --dump & redirect). +<p> </dd> + +<dt><b>--keep-processing-files [filename/wildcard/url]</b> +</dt> +<dd> +<p>see --maintenance +<p> </dd> + +<dt><b>-L</b> </dt> +<dd>prints license information. +<p> </dd> + +<dt><b>-M [filename/wildcard/url]</b> +</dt> +<dd> +<p>see --maintenance +<p> </dd> + +<dt><b>-m [filename/wildcard/url]</b> </dt> +<dd>see --dal (document abstraction +level/layer) +<p> </dd> + +<dt><b>--machine [filename/wildcard/url]</b> </dt> +<dd>see --dal (document abstraction +level/layer) +<p> </dd> + +<dt><b>--maintenance [filename/wildcard/url]</b> </dt> +<dd>maintenance mode, interim +processing files are preserved and their locations indicated. (also see +-V). Aliases -M and --keep-processing-files. +<p> </dd> + +<dt><b>--manpage [filename/wildcard]</b> </dt> +<dd>produces +man page of file, not suitable for all outputs. Alias -i +<p> </dd> + +<dt><b>-N [filename/wildcard/url]</b> +</dt> +<dd>document digest or document content certificate ( DCC ) as md5 digest tree +of the document: the digest for the document, and digests for each object +contained within the document (together with information on software versions +that produced it) (digest.txt). -NV for verbose digest output to screen. +<p> </dd> + +<dt><b>-n +[filename/wildcard/url]</b> </dt> +<dd>skip the creation of intermediate processing files +(document abstraction) if they already exist, this skips the equivalent +of -m which is otherwise assumed by most processing flags. +<p> </dd> + +<dt><b>--no-*</b> </dt> +<dd>see --exc-* + +<p> </dd> + +<dt><b>-o [filename/wildcard/url]</b> </dt> +<dd>see --odt +<p> </dd> + +<dt><b>--odf [filename/wildcard/url]</b> </dt> +<dd>see --odt + +<p> </dd> + +<dt><b>--odt [filename/wildcard/url]</b> </dt> +<dd>output basic document in opendocument file +format (opendocument.odt). Alias -o +<p> </dd> + +<dt><b>--output-by-*</b> </dt> +<dd>select output directory structure +from 3 alternatives: --output-by-language, (language directory (based on language +code) with filetype (html, epub, pdf etc.) subdirectories); --output-by-filetype, +(filetype directories with language code as part of filename); --output-by-filename, +(filename directories with language code as part of filename). This is configurable. +Alias --by-* +<p> </dd> + +<dt><b>-P [language_directory/filename language_directory]</b> </dt> +<dd>see --po4a + +<p> </dd> + +<dt><b>-p [filename/wildcard]</b> </dt> +<dd>see --pdf +<p> </dd> + +<dt><b>--pdf [filename/wildcard]</b> </dt> +<dd>produces <i>LaTeX</i> +pdf (portrait.pdf & landscape.pdf). Default paper size is set in config file, +or document header, or provided with additional command line parameter, +e.g. --papersize-a4 preset sizes include: ’A4’, U.S. ’letter’ and ’legal’ and book sizes +’A5’ and ’B5’ (system defaults to A4). Alias -p +<p> </dd> + +<dt><b>--pg [instruction] [filename]</b> +</dt> +<dd>database <i>PostgreSQL</i> ( --pgsql may be used instead) possible instructions, +include: --createdb; --create; --dropall; --import [filename]; --update [filename]; +--remove [filename]; see database section below. Alias -D +<p> </dd> + +<dt><b>--po [language_directory/filename + language_directory]</b> </dt> +<dd>see --po4a +<p> </dd> + +<dt><b>--po4a [language_directory/filename language_directory]</b> +</dt> +<dd>produces .pot and po files for the file in the languages specified by the +language directory. <b>SiSU</b> markup is placed in subdirectories named with the +language code, e.g. en/ fr/ es/. The sisu config file must set the output +directory structure to multilingual. v3, experimental +<p> </dd> + +<dt><b>-Q [filename/wildcard]</b> +</dt> +<dd> +<p>see --qrcode +<p> </dd> + +<dt><b>-q [filename/wildcard]</b> </dt> +<dd>see --quiet +<p> </dd> + +<dt><b>--qrcode [filename/wildcard]</b> +</dt> +<dd>generate QR code image of metadata (used in manifest). v3 only. +<p> </dd> + +<dt><b>--quiet [filename/wildcard]</b> +</dt> +<dd>quiet less output to screen. +<p> </dd> + +<dt><b>-R [filename/wildcard]</b> </dt> +<dd>see --rsync +<p> </dd> + +<dt><b>-r [filename/wildcard]</b> +</dt> +<dd> +<p>see --scp +<p> </dd> + +<dt><b>--redirect[=directory_path] [filename/wildcard]</b> </dt> +<dd>places output in +subdirectory under specified directory, subdirectory uses the filename +(without the suffix). If no output directory is specified places the subdirectory +under the current directory (pwd). Compare --dump +<p> </dd> + +<dt><b>--rsync [filename/wildcard]</b> +</dt> +<dd>copies sisu output files to remote host using rsync. This requires that +sisurc.yml has been provided with information on hostname and username, +and that you have your "keys" and ssh agent in place. Note the behavior +of rsync different if -R is used with other flags from if used alone. Alone +the rsync --delete parameter is sent, useful for cleaning the remote directory +(when -R is used together with other flags, it is not). Also see --scp. Alias + +<p>- +<p>R +<p> </dd> + +<dt><b>-S</b> </dt> +<dd>see --sisupod +<p> </dd> + +<dt><b>-S [filename/wildcard]</b> </dt> +<dd>see --sisupod +<p> </dd> + +<dt><b>-s [filename/wildcard]</b> +</dt> +<dd> +<p>see --source +<p> </dd> + +<dt><b>--sample-search-form [--webserv=webrick]</b> </dt> +<dd>generate examples of (naive) +cgi search form for <i>SQLite</i> and PgSQL depends on your already having used +sisu to populate an <i>SQLite</i> and/or PgSQL database, (the <i>SQLite</i> version scans +the output directories for existing sisu_sqlite databases, so it is first +necessary to create them, before generating the search form) see -d -D and +the database section below. If the optional parameter --webserv=webrick is +passed, the cgi examples created will be set up to use the default port +set for use by the webrick server, (otherwise the port is left blank and +the system setting used, usually 80). The samples are dumped in the present +work directory which must be writable, (with screen instructions given +that they be copied to the cgi-bin directory). Alias -F +<p> </dd> + +<dt><b>--scp [filename/wildcard]</b> +</dt> +<dd>copies sisu output files to remote host using scp. This requires that sisurc.yml +has been provided with information on hostname and username, and that you +have your "keys" and ssh agent in place. Also see --rsync. Alias -r +<p> </dd> + +<dt><b>--sqlite +--[instruction] [filename]</b> </dt> +<dd>database type set to <i>SQLite,</i> this produces one +of two possible databases, without additional database related instructions +it produces a discreet <i>SQLite</i> file for the document processed; with additional +instructions it produces a common <i>SQLite</i> database of all processed documents +that (come from the same document preparation directory and as a result) +share the same output directory base path (possible instructions include: +--createdb; --create; --dropall; --import [filename]; --update [filename]; --remove +[filename]); see database section below. Alias -d +<p> </dd> + +<dt><b>--sisupod</b> </dt> +<dd>produces a sisupod +a zipped sisu directory of markup files including sisu markup source files +and the directories local configuration file, images and skins. Note: this +only includes the configuration files or skins contained in ./_sisu not +those in ~/.sisu -S [filename/wildcard] option. Note: (this<br> + option is tested only with zsh). Alias -S +<p> </dd> + +<dt><b>--sisupod [filename/wildcard]</b> </dt> +<dd>produces +a zipped file of the prepared document specified along with associated +images, by default named sisupod.zip they may alternatively be named with +the filename extension .ssp This provides a quick way of gathering the relevant +parts of a sisu document which can then for example be emailed. A sisupod +includes sisu markup source file, (along with associated documents if a +master file, or available in multilingual versions), together with related +images and skin. <b>SiSU</b> commands can be run directly against a sisupod contained +in a local directory, or provided as a url on a remote site. As there is +a security issue with skins provided by other users, they are not applied +unless the flag --trust or --trusted is added to the command instruction, it +is recommended that file that are not your own are treated as untrusted. +The directory structure of the unzipped file is understood by sisu, and +sisu commands can be run within it. Note: if you wish to send multiple files, +it quickly becomes more space efficient to zip the sisu markup directory, +rather than the individual files for sending). See the -S option without +[filename/wildcard]. Alias -S +<p> </dd> + +<dt><b>--source [filename/wildcard]</b> </dt> +<dd>copies sisu markup +file to output directory. Alias -s +<p> </dd> + +<dt><b>-T [filename/wildcard (*.termsheet.rb)]</b> +</dt> +<dd>standard form document builder, preprocessing feature +<p> </dd> + +<dt><b>-t [filename/wildcard]</b> +</dt> +<dd> +<p>see --txt +<p> </dd> + +<dt><b>--texinfo [filename/wildcard]</b> </dt> +<dd>produces texinfo and info file, (view +with pinfo). Alias -I +<p> </dd> + +<dt><b>--txt [filename/wildcard]</b> </dt> +<dd>produces <i>plaintext</i> with Unix +linefeeds and without markup, (object numbers are omitted), has footnotes +at end of each paragraph that contains them [ -A for output file] [see -e + for endnotes]. (Options include: --endnotes for endnotes --footnotes for footnotes +at the end of each paragraph --unix for unix linefeed (default) --msdos for +msdos linefeed). Alias -t +<p> </dd> + +<dt><b>-U [filename/wildcard]</b> </dt> +<dd>see --urls +<p> </dd> + +<dt><b>-u [filename/wildcard]</b> +</dt> +<dd>provides url mapping of output files for the flags requested for processing, + +<p>also see -U +<p> </dd> + +<dt><b>--urls [filename/wildcard]</b> </dt> +<dd>prints url output list/map for the +available processing flags options and resulting files that could be requested, +(can be used to get a list of processing options in relation to a file, +together with information on the output that would be produced), -u provides +url output mapping for those flags requested for processing. The default +assumes sisu_webrick is running and provides webrick url mappings where +appropriate, but these can be switched to file system paths in sisurc.yml. + +<p>Alias -U +<p> </dd> + +<dt><b>-V</b> </dt> +<dd>on its own, provides <b>SiSU</b> version and environment information +(sisu --help env) +<p> </dd> + +<dt><b>-V [filename/wildcard]</b> </dt> +<dd>even more verbose than the -v flag. + +<p> </dd> + +<dt><b>-v</b> </dt> +<dd>on its own, provides <b>SiSU</b> version information +<p> </dd> + +<dt><b>-v [filename/wildcard]</b> +</dt> +<dd> +<p>see --verbose +<p> </dd> + +<dt><b>--v3 [filename/wildcard]</b> </dt> +<dd>invokes the sisu v3 document parser/generator. +You may run sisu3 instead. +<p> </dd> + +<dt><b>--v4 [filename/wildcard]</b> </dt> +<dd>invokes the sisu v4 document +parser/generator. This is the default and is normally omitted. +<p> </dd> + +<dt><b>--verbose [filename/wildcard]</b> +</dt> +<dd>provides verbose output of what is being generated, where output is placed +(and error messages if any), as with -u flag provides a url mapping of files +created for each of the processing flag requests. Alias -v +<p> </dd> + +<dt><b>-W</b> </dt> +<dd>see --webrick + +<p> </dd> + +<dt><b>-w [filename/wildcard]</b> </dt> +<dd>see --concordance +<p> </dd> + +<dt><b>--webrick</b> </dt> +<dd>starts ruby’ s webrick webserver +points at sisu output directories, the default port is set to 8081 and +can be changed in the resource configuration files. [tip: the webrick server + requires link suffixes, so html output should be created using the -h option + rather than also, note -F webrick ]. Alias -W +<p> </dd> + +<dt><b>--wordmap [filename/wildcard]</b> +</dt> +<dd> +<p>see --concordance +<p> </dd> + +<dt><b>--xhtml [filename/wildcard]</b> </dt> +<dd>produces xhtml/ <i>XML</i> output for +browser viewing (sax parsing). Alias -b +<p> </dd> + +<dt><b>--xml-dom [filename/wildcard]</b> </dt> +<dd>produces +<i>XML</i> output with deep document structure, in the nature of dom. Alias -X +<p> +</dd> + +<dt><b>--xml-sax [filename/wildcard]</b> </dt> +<dd>produces <i>XML</i> output shallow structure (sax parsing). + +<p>Alias -x +<p> </dd> + +<dt><b>-X [filename/wildcard]</b> </dt> +<dd>see --xml-dom +<p> </dd> + +<dt><b>-x [filename/wildcard]</b> </dt> +<dd>see --xml-sax + +<p> </dd> + +<dt><b>-Y [filename/wildcard]</b> </dt> +<dd>produces a short sitemap entry for the document, +based on html output and the sisu_manifest. --sitemaps generates/updates the +sitemap index of existing sitemaps. (Experimental, [g,y,m announcement this + week]) +<p> </dd> + +<dt><b>-y [filename/wildcard]</b> </dt> +<dd>produces an html summary of output generated +(hyperlinked to content) and document specific metadata (sisu_manifest.html). +This step is assumed for most processing flags. +<p> </dd> + +<dt><b>-Z [filename/wildcard]</b> </dt> +<dd>see + +<p>- +<p>- +<p>zap +<p> </dd> + +<dt><b>--zap [filename/wildcard]</b> </dt> +<dd>Zap, if used with other processing flags deletes +output files of the type about to be processed, prior to processing. If +-Z is used as the lone processing related flag (or in conjunction with a +combination of -[mMvVq]), will remove the related document output directory. + +<p>Alias -Z +<p> </dd> +</dl> + +<h2><a name='sect8' href='#toc8'>Command Line Modifiers</a></h2> +<br> + +<p> +<dl> + +<dt><b>--no-</b> </dt> +<dd><i>ocn</i> [with --html --pdf or --epub] switches off <i>object</i> citation numbering. +Produce output without identifying numbers in margins of html or <i>LaTeX</i> +/pdf output. +<p> </dd> + +<dt><b>--no-annotate</b> </dt> +<dd>strips output text of editor endnotes[^*1] denoted + +<p>by asterisk or dagger/plus sign +<p> </dd> + +<dt><b>--no-asterisk</b> </dt> +<dd>strips output text of editor +endnotes[^*2] denoted by asterisk sign +<p> </dd> + +<dt><b>--no-dagger</b> </dt> +<dd>strips output text of editor +endnotes[^+1] denoted by dagger/plus sign +<p> </dd> +</dl> + +<h2><a name='sect9' href='#toc9'>Database Commands</a></h2> +<br> + +<p> <br> +<b>dbi - database interface</b> +<p> <br> +<b>-D or --pgsql</b> set for <i>PostgreSQL</i> <b>-d or --sqlite</b> default set for <i>SQLite</i> -d is modifiable +with --db=[database type (PgSQL or .I SQLite ) ] +<p> +<dl> + +<dt><b>--pg -v --createall</b> </dt> +<dd>initial step, +creates required relations (tables, indexes) in existing <i>PostgreSQL</i> database +(a database should be created manually and given the same name as working +directory, as requested) (rb.dbi) [ -dv --createall .I SQLite equivalent] it +may be necessary to run sisu -Dv --createdb initially NOTE: at the present +time for <i>PostgreSQL</i> it may be necessary to manually create the database. +The command would be working directory name (without path)]. Please use +only alphanumerics and underscores. +<p> </dd> + +<dt><b>--pg -v --import</b> </dt> +<dd>[filename/wildcard] imports +data specified to <i>PostgreSQL</i> db (rb.dbi) [ -dv --import .I SQLite equivalent] + +<p> </dd> + +<dt><b>--pg -v --update</b> </dt> +<dd>[filename/wildcard] updates/imports specified data to <i>PostgreSQL</i> +db (rb.dbi) [ -dv --update .I SQLite equivalent] +<p> </dd> + +<dt><b>--pg --remove</b> </dt> +<dd>[filename/wildcard] +removes specified data to <i>PostgreSQL</i> db (rb.dbi) [ -d --remove .I SQLite equivalent] + +<p> </dd> + +<dt><b>--pg --dropall</b> </dt> +<dd>kills data" and drops ( <i>PostgreSQL</i> or <i>SQLite</i> ) db, tables & +indexes [ -d --dropall .I SQLite equivalent] +<p> <br> +The -v is for verbose output. +<p> </dd> +</dl> + +<h2><a name='sect10' href='#toc10'>Shortcuts, Shorthand for Multiple Flags</a></h2> +<br> + +<p> +<dl> + +<dt><b>--update [filename/wildcard]</b> </dt> +<dd>Checks existing file output and runs the flags +required to update this output. This means that if only html and pdf output +was requested on previous runs, only the -hp files will be applied, and +only these will be generated this time, together with the summary. This +can be very convenient, if you offer different outputs of different files, +and just want to do the same again. +<p> </dd> + +<dt><b>-0 to -5 [filename or wildcard]</b> </dt> +<dd>Default +shorthand mappings (for v3, note that the defaults can be changed/configured +in the sisurc.yml file): +<p> </dd> + +<dt><b>-0</b> </dt> +<dd>-NQhewpotbxXyYv [this is the default action run + when no options are give, i.e. on ’sisu [filename]’] +<p> </dd> + +<dt><b>-1</b> </dt> +<dd>-Qhewpoty +<p> </dd> + +<dt><b>-2</b> </dt> +<dd>-NQhewpotbxXy + +<p> </dd> + +<dt><b>-3</b> </dt> +<dd>-NQhewpotbxXyY +<p> </dd> + +<dt><b>-4</b> </dt> +<dd>-NQhewpotbxXDyY --update +<p> </dd> + +<dt><b>-5</b> </dt> +<dd>-NQhewpotbxXDyYv --update +<p> <br> +add -v for verbose mode and -c to toggle color state, e.g. sisu -2vc [filename + or wildcard] +<p> <br> + +<p>consider -u for appended url info or -v for verbose output +<p> </dd> +</dl> + +<h2><a name='sect11' href='#toc11'>Command Line +with Flags - Batch Processing</a></h2> + +<p> <br> +In the data directory run sisu -mh filename or wildcard eg. "sisu -h cisg.sst" +or "sisu -h *.{sst,ssm}" to produce html version of all documents. +<p> <br> +Running sisu (alone without any flags, filenames or wildcards) brings up +the interactive help, as does any sisu command that is not recognised. Enter +to escape. +<p> +<h2><a name='sect12' href='#toc12'>Help</a></h2> +<br> + +<p> +<h2><a name='sect13' href='#toc13'>Sisu Manual</a></h2> + +<p> <br> +The most up to date information on sisu should be contained in the sisu_manual, +available at: +<p> <br> + <<a href='http://sisudoc.org/sisu/sisu_manual/'>http://sisudoc.org/sisu/sisu_manual/</a> +><br> + +<p> <br> +The manual can be generated from source, found respectively, either within +the <b>SiSU</b> tarball or installed locally at: +<p> <br> + ./data/doc/sisu/markup-samples/sisu_manual<br> + +<p> <br> + /usr/share/doc/sisu/markup-samples/sisu_manual<br> + +<p> <br> +move to the respective directory and type e.g.: +<p> <br> + sisu sisu_manual.ssm<br> + +<p> +<h2><a name='sect14' href='#toc14'>Sisu Man Pages</a></h2> + +<p> <br> +If <b>SiSU</b> is installed on your system usual man commands should be available, +try: +<p> <br> + man sisu<br> + +<p> <br> +Most <b>SiSU</b> man pages are generated directly from sisu documents that are +used to prepare the sisu manual, the sources files for which are located +within the <b>SiSU</b> tarball at: +<p> <br> + ./data/doc/sisu/markup-samples/sisu_manual<br> + +<p> <br> +Once installed, directory equivalent to: +<p> <br> + /usr/share/doc/sisu/markup-samples/sisu_manual<br> + +<p> <br> +Available man pages are converted back to html using man2html: +<p> <br> + /usr/share/doc/sisu/html/<br> + +<p> <br> + ./data/doc/sisu/html<br> + +<p> <br> +An online version of the sisu man page is available here: +<p> <br> +* various sisu man pages <<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a> +> [^9] +<p> <br> +* sisu.1 <<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a> +> [^10] +<p> +<h2><a name='sect15' href='#toc15'>Sisu Built-in Interactive +Help</a></h2> + +<p> <br> +This is particularly useful for getting the current sisu setup/environment +information: +<p> <br> + sisu --help<br> + +<p> <br> + sisu --help [subject]<br> + +<p> <br> + sisu --help commands<br> + +<p> <br> + sisu --help markup<br> + +<p> <br> + sisu --help env [for feedback on the way your system is <br> + setup with regard to sisu ]<br> + +<p> <br> + sisu -V [environment information, same as above command]<br> + +<p> <br> + sisu (on its own provides version and some help information)<br> + +<p> <br> +Apart from real-time information on your current configuration the <b>SiSU</b> +manual and man pages are likely to contain more up-to-date information than +the sisu interactive help (for example on commands and markup). +<p> <br> +NOTE: Running the command sisu (alone without any flags, filenames or wildcards) +brings up the interactive help, as does any sisu command that is not recognised. +Enter to escape. +<p> +<h2><a name='sect16' href='#toc16'>Introduction to Sisu Markup[^11]</a></h2> +<br> + +<p> +<h2><a name='sect17' href='#toc17'>Summary</a></h2> + +<p> <br> +<b>SiSU</b> source documents are <i>plaintext</i> ( <i>UTF-8</i> )[^12] files +<p> <br> +All paragraphs are separated by an empty line. +<p> <br> +Markup is comprised of: +<p> <br> +* at the top of a document, the document header made up of semantic meta-data +about the document and if desired additional processing instructions (such +an instruction to automatically number headings from a particular level +down) +<p> <br> +* followed by the prepared substantive text of which the most important +single characteristic is the markup of different heading levels, which +define the primary outline of the document structure. Markup of substantive +text includes: +<p> <br> + * heading levels defines document structure<br> + +<p> <br> + * text basic attributes, italics, bold etc.<br> + +<p> <br> + * grouped text (objects), which are to be treated differently, such as +code<br> + blocks or poems.<br> + +<p> <br> + * footnotes/endnotes<br> + +<p> <br> + * linked text and images<br> + +<p> <br> + * paragraph actions, such as indent, bulleted, numbered-lists, etc.<br> + +<p> <br> +Some interactive help on markup is available, by typing sisu and selecting + +<p>markup or sisu --help markup +<p> <br> +To check the markup in a file: +<p> <br> + sisu --identify [filename].sst<br> + +<p> <br> + +<p>For brief descriptive summary of markup history +<p> <br> + sisu --query-history<br> + +<p> <br> +or if for a particular version: +<p> <br> + sisu --query-0.38<br> + +<p> +<h2><a name='sect18' href='#toc18'>Markup Examples</a></h2> + +<p> +<h2><a name='sect19' href='#toc19'>Online</a></h2> + +<p> <br> +Online markup examples are available together with the respective outputs +produced from <<a href='http://www.jus.uio.no/sisu/SiSU/examples.html'>http://www.jus.uio.no/sisu/SiSU/examples.html</a> +> or from <<a href='http://www.jus.uio.no/sisu/sisu_examples/'>http://www.jus.uio.no/sisu/sisu_examples/</a> +> + +<p> <br> +There is of course this document, which provides a cursory overview of +sisu markup and the respective output produced: <<a href='http://www.jus.uio.no/sisu/sisu_markup/'>http://www.jus.uio.no/sisu/sisu_markup/</a> +> + +<p> <br> +an alternative presentation of markup syntax: /usr/share/doc/sisu/on_markup.txt.gz + +<p> +<h2><a name='sect20' href='#toc20'>Installed</a></h2> + +<p> <br> +With <b>SiSU</b> installed sample skins may be found in: /usr/share/doc/sisu/markup-samples +(or equivalent directory) and if sisu -markup-samples is installed also under: + +<p>/usr/share/doc/sisu/markup-samples-non-free +<p> +<h2><a name='sect21' href='#toc21'>Markup of Headers</a></h2> +<br> + +<p> <br> +Headers contain either: semantic meta-data about a document, which can be +used by any output module of the program, or; processing instructions. +<p> +<br> +Note: the first line of a document may include information on the markup +version used in the form of a comment. Comments are a percentage mark at +the start of a paragraph (and as the first character in a line of text) +followed by a space and the comment: +<p> <br> +<pre>% this would be a comment +</pre> +<p> +<h2><a name='sect22' href='#toc22'>Sample Header</a></h2> + +<p> <br> +This current document is loaded by a master document that has a header +similar to this one: +<p> <br> +<pre>% SiSU master 2.0 +@title: SiSU +:subtitle: Manual +@creator: +:author: Amissah, Ralph +@publisher: [publisher name] +@rights: Copyright (C) Ralph Amissah 2007, part of SiSU documentation, +License GPL 3 +@classify: +:type: information +:topic_register: SiSU:manual;electronic documents:SiSU:manual +:subject: ebook, epublishing, electronic book, electronic publishing, + electronic document, electronic citation, data structure, + citation systems, search +% used_by: manual +@date: +:published: 2008-05-22 +:created: 2002-08-28 +:issued: 2002-08-28 +:available: 2002-08-28 +:modified: 2010-03-03 +@make: +:num_top: 1 +:breaks: new=C; break=1 +:bold: /Gnu|Debian|Ruby|SiSU/ +:home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org +:footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org +:manpage: name=sisu - documents: markup, structuring, publishing in multiple +standard formats, and search; + synopsis=sisu [-abcDdeFhIiMmNnopqRrSsTtUuVvwXxYyZz0-9] [filename/wildcard + ] + . sisu [-Ddcv] [instruction] + . sisu [-CcFLSVvW] + . sisu --v4 [operations] + . sisu --v3 [operations] +@links: +{ SiSU Homepage }http://www.sisudoc.org/ +{ SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ +{ Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html +{ SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html +{ SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html +{ SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary +{ SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ +{ SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html +{ SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org +{ SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU +</pre> +<p> +<h2><a name='sect23' href='#toc23'>Available Headers</a></h2> + +<p> <br> +Header tags appear at the beginning of a document and provide meta information +on the document (such as the <i>Dublin</i> Core ) , or information as to how the +document as a whole is to be processed. All header instructions take the +form @headername: or on the next line and indented by once space :subheadername: + +<p>All <i>Dublin</i> Core meta tags are available +<p> <br> +<b>@indentifier:</b> information or instructions +<p> <br> +where the "identifier" is a tag recognised by the program, and the "information" +or "instructions" belong to the tag/indentifier specified +<p> <br> +Note: a header where used should only be used once; all headers apart from +@title: are optional; the @structure: header is used to describe document +structure, and can be useful to know. +<p> <br> + +<p>This is a sample header +<p> <br> +<pre>% SiSU 2.0 [declared file-type identifier with markup version] +</pre> +<p> <br> +<pre>@title: [title text] [this header is the only one that is mandatory] + :subtitle: [subtitle if any] + :language: English +</pre> +<p> <br> +<pre>@creator: +:author: [Lastname, First names] +:illustrator: [Lastname, First names] +:translator: [Lastname, First names] +:prepared_by: [Lastname, First names] +</pre> +<p> <br> +<pre>@date: +:published: [year or yyyy-mm-dd] +:created: [year or yyyy-mm-dd] +:issued: [year or yyyy-mm-dd] +:available: [year or yyyy-mm-dd] +:modified: [year or yyyy-mm-dd] +:valid: [year or yyyy-mm-dd] +:added_to_site: [year or yyyy-mm-dd] +:translated: [year or yyyy-mm-dd] +</pre> +<p> <br> +<pre>@rights: +:copyright: Copyright (C) [Year and Holder] +:license: [Use License granted] +:text: [Year and Holder] +:translation: [Name, Year] +:illustrations: [Name, Year] +</pre> +<p> <br> +<pre>@classify: +:topic_register: SiSU:markup sample:book;book:novel:fantasy +:type: +:subject: +:description: +:keywords: +:abstract: +:loc: [Library of Congress classification] +:dewey: Dewey classification +</pre> +<p> <br> +<pre>@identify: +:isbn: [ISBN] +:oclc: +</pre> +<p> <br> +<pre>@links: { SiSU }http://www.sisudoc.org + { FSF }http://www.fsf.org +</pre> +<p> <br> +<pre>@make: +:num_top: 1 +:headings: [text to match for each level (e.g. PART; Chapter; Section; + Article; or another: none; BOOK|FIRST|SECOND; none; CHAPTER;) :breaks: new=:C; + break=1 :promo: sisu, ruby, sisu_search_libre, open_society :bold: [regular + expression of words/phrases to be made bold] +:italics: [regular expression of words/phrases to italicise] +:home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org +:footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org +</pre> +<p> <br> +<pre>@original: +:language: [language] +</pre> +<p> <br> +<pre>@notes: +:comment: +:prefix: [prefix is placed just after table of contents] +</pre> +<p> +<h2><a name='sect24' href='#toc24'>Markup of Substantive Text</a></h2> +<br> + +<p> +<h2><a name='sect25' href='#toc25'>Heading Levels</a></h2> + +<p> <br> +Heading levels are :A~ ,:B~ ,:C~ ,1~ ,2~ ,3~ ... :A - :C being part / section +headings, followed by other heading levels, and 1 -6 being headings followed +by substantive text or sub-headings. :A~ usually the title :A~? conditional +level 1 heading (used where a stand-alone document may be imported into +another) +<p> <br> +<b>:A~ [heading text]</b> Top level heading [this usually has similar content + to the title @title: ] NOTE: the heading levels described here are in 0.38 +notation, see heading +<p> <br> +<b>:B~ [heading text]</b> Second level heading [this is a heading level divider] + +<p> <br> +<b>:C~ [heading text]</b> Third level heading [this is a heading level divider] + +<p> <br> +<b>1~ [heading text]</b> Top level heading preceding substantive text of document +or sub-heading 2, the heading level that would normally be marked 1. or 2. +or 3. etc. in a document, and the level on which sisu by default would break +html output into named segments, names are provided automatically if none +are given (a number), otherwise takes the form 1~my_filename_for_this_segment + +<p> <br> +<b>2~ [heading text]</b> Second level heading preceding substantive text of document +or sub-heading 3 , the heading level that would normally be marked 1.1 or +1.2 or 1.3 or 2.1 etc. in a document. +<p> <br> +<b>3~ [heading text]</b> Third level heading preceding substantive text of document, +that would normally be marked 1.1.1 or 1.1.2 or 1.2.1 or 2.1.1 etc. in a document + +<p> <br> +<pre>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) +</pre> +<p> +<h2><a name='sect26' href='#toc26'>Font Attributes</a></h2> + +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>normal text, *{emphasis}*, !{bold text}!, /{italics}/, _{underscore}_, +"{citation}", +^{superscript}^, ,{subscript},, +{inserted text}+, -{strikethrough}-, #{monospace}# +normal text +*{emphasis}* [note: can be configured to be represented by bold, italics + or underscore] +!{bold text}! +/{italics}/ +_{underscore}_ +"{citation}" +^{superscript}^ +,{subscript}, ++{inserted text}+ +-{strikethrough}- +#{monospace}# +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +normal text, <b>emphasis,</b> <b>bold text</b> , <i>italics,</i> <i>underscore,</i> "citation", ^superscript^, +[subscript], ++inserted text++, --strikethrough--, monospace +<p> <br> + +<p>normal text +<p> <br> +<b>emphasis</b> [note: can be configured to be represented by bold, italics italics + or underscore] or underscore] +<p> <br> + +<p><b>bold text</b> +<p> <br> + +<p><i>italics</i> +<p> <br> + +<p><i>underscore</i> +<p> <br> +"citation" +<p> <br> +^superscript^ +<p> <br> +[subscript] +<p> <br> +++inserted text++ +<p> <br> +--strikethrough-- +<p> <br> + +<p>monospace +<p> +<h2><a name='sect27' href='#toc27'>Indentation and Bullets</a></h2> + +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>ordinary paragraph +_1 indent paragraph one step +_2 indent paragraph two steps +_9 indent paragraph nine steps +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> + +<p>ordinary paragraph +<p> <br> + indent paragraph one step<br> + +<p> <br> + indent paragraph two steps<br> + +<p> <br> + indent paragraph nine steps<br> + +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>_* bullet text +_1* bullet text, first indent +_2* bullet text, two step indent +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +* bullet text +<p> <br> + * bullet text, first indent<br> + +<p> <br> + * bullet text, two step indent<br> + +<p> <br> +Numbered List (not to be confused with headings/titles, (document structure)) + +<p> <br> +<b>markup example:</b> +<p> <br> +<pre># numbered list numbered list 1., 2., 3, etc. +_# numbered list numbered list indented a., b., c., d., etc. +</pre> +<p> +<h2><a name='sect28' href='#toc28'>Hanging Indents</a></h2> + +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>_0_1 first line no indent, +rest of paragraph indented one step +_1_0 first line indented, +rest of paragraph no indent +in each case level may be 0-9 +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> + first line no indent, rest of paragraph indented one step<br> + +<p> <br> +first line indented, rest of paragraph no indent +<p> <br> + +<p>in each case level may be 0-9 +<p> +<h2><a name='sect29' href='#toc29'>Footnotes / Endnotes</a></h2> + +<p> <br> +Footnotes and endnotes are marked up at the location where they would be +indicated within a text. They are automatically numbered. The output type + +<p>determines whether footnotes or endnotes will be produced +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>~{ a footnote or endnote }~ +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +[^13] +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>normal text~{ self contained endnote marker & endnote in one }~ continues +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +normal text[^14] continues +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks +if required }~ continues +normal text ~{** another unnumbered asterisk footnote/endnote }~ continues +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +normal text [^*] continues +<p> <br> +normal text [^**] continues +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>normal text ~[* editors notes, numbered asterisk footnote/endnote series + ]~ continues +normal text ~[+ editors notes, numbered asterisk footnote/endnote series + ]~ continues +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +normal text [^*3] continues +<p> <br> +normal text [^+2] continues +<p> <br> +<b>Alternative endnote pair notation for footnotes/endnotes:</b> +<p> <br> +<pre>% note the endnote marker "~^" +normal text~^ continues +^~ endnote text following the paragraph in which the marker occurs +</pre> +<p> <br> + +<p>the standard and pair notation cannot be mixed in the same document +<p> +<h2><a name='sect30' href='#toc30'>Links</a></h2> + +<p> + +<h2><a name='sect31' href='#toc31'>Naked Urls Within Text, Dealing with Urls</a></h2> + +<p> <br> +urls found within text are marked up automatically. A url within text is +automatically hyperlinked to itself and by default decorated with angled +braces, unless they are contained within a code block (in which case they +are passed as normal text), or escaped by a preceding underscore (in which +case the decoration is omitted). +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>normal text http://www.sisudoc.org/ continues +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +normal text <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> continues +<p> <br> + +<p>An escaped url without decoration +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>normal text _http://www.sisudoc.org/ continues +deb _http://www.jus.uio.no/sisu/archive unstable main non-free +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +normal text <_<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> continues +<p> <br> +deb <_<a href='http://www.jus.uio.no/sisu/archive'>http://www.jus.uio.no/sisu/archive</a> +> unstable main non-free +<p> <br> +where a code block is used there is neither decoration nor hyperlinking, + +<p>code blocks are discussed later in this document +<p> <br> +<b>resulting output:</b> +<p> <br> +<pre>deb http://www.jus.uio.no/sisu/archive unstable main non-free +deb-src http://www.jus.uio.no/sisu/archive unstable main non-free +</pre> +<p> +<h2><a name='sect32' href='#toc32'>Linking Text</a></h2> + +<p> <br> + +<p>To link text or an image to a url the markup is as follows +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>about { SiSU }http://url.org markup +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +aboutSiSU <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> markup +<p> <br> + +<p>A shortcut notation is available so the url link may also be provided automatically + +<p>as a footnote +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>about {~^ SiSU }http://url.org markup +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +aboutSiSU <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> [^15] markup +<p> <br> +Internal document links to a tagged location, including an <i>ocn</i> +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>about { text links }#link_text +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +about ⌠text links⌡⌈link_text⌋ +<p> <br> + +<p>Shared document collection link +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>about { SiSU book markup examples }:SiSU/examples.html +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +about ⌠ <b>SiSU</b> book markup examples⌡⌈:SiSU/examples.html⌋ +<p> +<h2><a name='sect33' href='#toc33'>Linking +Images</a></h2> + +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>{ tux.png 64x80 }image +% various url linked images +{tux.png 64x80 "a better way" }http://www.sisudoc.org/ +{GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian +and Ruby" }http://www.sisudoc.org/ +{~^ ruby_logo.png "Ruby" }http://www.ruby-lang.org/en/ +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +[ tux.png ] +<p> <br> +tux.png 64x80 "Gnu/Linux - a better way" <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> +<p> <br> +GnuDebianLinuxRubyBetterWay.png 100x101 "Way Better - with Gnu/Linux, Debian +and Ruby" <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> +<p> <br> +ruby_logo.png 70x90 "Ruby" <<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a> +> [^16] +<p> <br> + +<p><b>linked url footnote shortcut</b> +<p> <br> +<pre>{~^ [text to link] }http://url.org +% maps to: { [text to link] }http://url.org ~{ http://url.org }~ +% which produces hyper-linked text within a document/paragraph, with an +endnote providing the url for the text location used in the hyperlink +</pre> +<p> <br> +<pre>text marker *~name +</pre> +<p> <br> +note at a heading level the same is automatically achieved by providing +names to headings 1, 2 and 3 i.e. 2~[name] and 3~[name] or in the case of +auto-heading numbering, without further intervention. +<p> +<h2><a name='sect34' href='#toc34'>Link Shortcut for +Multiple Versions of a Sisu Document in the Same Directory</a></h2> +TREE +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>!_ /{"Viral Spiral"}/, David Bollier +{ "Viral Spiral", David Bollier [3sS]}viral_spiral.david_bollier.sst +</pre> +<p> <br> +<b></b> <i>Viral Spiral</i>, David Bollier +<p> "Viral Spiral", David Bollier <<a href='http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html'>http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html</a> +> + document manifest <<a href='http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html'>http://corundum/sisu_manual/en/manifest/viral_spiral.david_bollier.html</a> +><br> + ⌠html, segmented text⌡「<a href='http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」'>http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」</a> +<br> + ⌠html, scroll, document in one⌡「<a href='http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」'>http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」</a> +<br> + ⌠epub⌡「<a href='http://corundum/sisu_manual/en/epub/viral_spiral.david_bollier.epub」'>http://corundum/sisu_manual/en/epub/viral_spiral.david_bollier.epub」</a> +<br> + ⌠pdf, landscape⌡「<a href='http://corundum/sisu_manual/en/pdf/viral_spiral.david_bollier.pdf」'>http://corundum/sisu_manual/en/pdf/viral_spiral.david_bollier.pdf」</a> +<br> + ⌠pdf, portrait⌡「<a href='http://corundum/sisu_manual/en/pdf/viral_spiral.david_bollier.pdf」'>http://corundum/sisu_manual/en/pdf/viral_spiral.david_bollier.pdf」</a> +<br> + ⌠odf: odt, open document text⌡「<a href='http://corundum/sisu_manual/en/odt/viral_spiral.david_bollier.odt」'>http://corundum/sisu_manual/en/odt/viral_spiral.david_bollier.odt」</a> +<br> + ⌠xhtml scroll⌡「<a href='http://corundum/sisu_manual/en/xhtml/viral_spiral.david_bollier.xhtml」'>http://corundum/sisu_manual/en/xhtml/viral_spiral.david_bollier.xhtml」</a> +<br> + ⌠xml, sax⌡「<a href='http://corundum/sisu_manual/en/xml/viral_spiral.david_bollier.xml」'>http://corundum/sisu_manual/en/xml/viral_spiral.david_bollier.xml」</a> +<br> + ⌠xml, dom⌡「<a href='http://corundum/sisu_manual/en/xml/viral_spiral.david_bollier.xml」'>http://corundum/sisu_manual/en/xml/viral_spiral.david_bollier.xml」</a> +<br> + ⌠concordance⌡「<a href='http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」'>http://corundum/sisu_manual/en/html/viral_spiral.david_bollier.html」</a> +<br> + ⌠dcc, document content certificate (digests)⌡「<a href='http://corundum/sisu_manual/en/digest/viral_spiral.david_bollier.txt」'>http://corundum/sisu_manual/en/digest/viral_spiral.david_bollier.txt」</a> +<br> + ⌠markup source text⌡「<a href='http://corundum/sisu_manual/en/src/viral_spiral.david_bollier.sst」'>http://corundum/sisu_manual/en/src/viral_spiral.david_bollier.sst」</a> +<br> + ⌠markup source (zipped) pod⌡「<a href='http://corundum/sisu_manual/en/pod/viral_spiral.david_bollier.sst.zip」'>http://corundum/sisu_manual/en/pod/viral_spiral.david_bollier.sst.zip」</a> +<br> + +<p> +<h2><a name='sect35' href='#toc35'>Grouped Text</a></h2> + +<p> +<h2><a name='sect36' href='#toc36'>Tables</a></h2> + +<p> <br> + +<p>Tables may be prepared in two either of two forms +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>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 +</pre> +<p> <br> +<b>resulting output:</b> +<p> This is a table|this would become column two of row one|column +three of row one is here』And here begins another row|column two of row +two|column three of row two, and so on』 +<p> <br> + +<p>a second form may be easier to work with in cases where there is not much + +<p>information in each column +<p> <br> +<b>markup example:</b> [^18] +<p> <br> +<pre>!_ Table 3.1: Contributors to Wikipedia, January 2001 - June 2005 +{table~h 24; 12; 12; 12; 12; 12; 12;} + |Jan. 2001|Jan. 2002|Jan. 2003|Jan. 2004|July 2004|June +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. +</pre> +<p> <br> +<b>resulting output:</b> +<p> <br> +<b>Table 3.1: Contributors to Wikipedia, January 2001 - June 2005</b> +<p> |Jan. 2001|Jan. +2002|Jan. 2003|Jan. 2004|July 2004|June 2006』Contributors*|10|472|2,188|9,653|25,011|48,721』Active +contributors**|9|212|846|3,228|8,442|16,945』Very active contributors***|0|31|190|692|1,639|3,016』No. +of English language articles|25|16,000|101,000|190,000|320,000|630,000』No. of +articles, all languages|25|19,000|138,000|490,000|862,000|1,600,000』 +<p> <br> +* Contributed at least ten times; ** at least 5 times in last month; *** +more than 100 times in last month. +<p> +<h2><a name='sect37' href='#toc37'>Poem</a></h2> + +<p> <br> +<b>basic markup:</b> +<p> <br> +<pre>poem{ + Your poem here +}poem +Each verse in a poem is given an object number. +</pre> +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>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 +</pre> +<p> <br> +<b>resulting output:</b> +<p> ‘Fury said to a<br> + mouse, That he<br> + met in the<br> + house,<br> + "Let us<br> + both go to<br> + law: I will<br> + prosecute<br> + YOU. --Come,<br> + I’ll take no<br> + denial; We<br> + must have a<br> + trial: For<br> + really this<br> + morning I’ve<br> + nothing<br> + to do."<br> + Said the<br> + mouse to the<br> + cur, "Such<br> + a trial,<br> + dear Sir,<br> + With<br> + no jury<br> + or judge,<br> + would be<br> + wasting<br> + our<br> + breath."<br> + "I’ll be<br> + judge, I’ll<br> + be jury,"<br> + Said<br> + cunning<br> + old Fury:<br> + "I’ll<br> + try the<br> + whole<br> + cause,<br> + and<br> + condemn<br> + you<br> + to<br> + death."’<br> + +<p> +<h2><a name='sect38' href='#toc38'>Group</a></h2> + +<p> <br> +<b>basic markup:</b> +<p> <br> +<pre>group{ + Your grouped text here +}group +A group is treated as an object and given a single object number. +</pre> +<p> <br> +<b>markup example:</b> +<p> <br> +<pre>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 +</pre> +<p> <br> +<b>resulting output:</b> +<p> ‘Fury said to a<br> + mouse, That he<br> + met in the<br> + house,<br> + "Let us<br> + both go to<br> + law: I will<br> + prosecute<br> + YOU. --Come,<br> + I’ll take no<br> + denial; We<br> + must have a<br> + trial: For<br> + really this<br> + morning I’ve<br> + nothing<br> + to do."<br> + Said the<br> + mouse to the<br> + cur, "Such<br> + a trial,<br> + dear Sir,<br> + With<br> + no jury<br> + or judge,<br> + would be<br> + wasting<br> + our<br> + breath."<br> + "I’ll be<br> + judge, I’ll<br> + be jury,"<br> + Said<br> + cunning<br> + old Fury:<br> + "I’ll<br> + try the<br> + whole<br> + cause,<br> + and<br> + condemn<br> + you<br> + to<br> + death."’<br> + +<p> +<h2><a name='sect39' href='#toc39'>Code</a></h2> + +<p> <br> +Code tags code{ ... }code (used as with other group tags described above) +are used to escape regular sisu markup, and have been used extensively +within this document to provide examples of <b>SiSU</b> markup. You cannot however +use code tags to escape code tags. They are however used in the same way +as group or poem tags. +<p> <br> +A code-block is treated as an object and given a single object number. [an +option to number each line of code may be considered at some later time] + +<p> <br> +<b>use of code tags instead of poem compared, resulting output:</b> +<p> <br> +<pre> ‘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."’ +</pre> +<p> <br> +From <b>SiSU</b> 2.7.7 on you can number codeblocks by placing a hash after the +opening code tag code{# as demonstrated here: +<p> <br> +<pre>1 | ‘Fury said to a +2 | mouse, That he +3 | met in the +4 | house, +5 | "Let us +6 | both go to +7 | law: I will +8 | prosecute +9 | YOU. --Come, +10 | I’ll take no +11 | denial; We +12 | must have a +13 | trial: For +14 | really this +15 | morning I’ve +16 | nothing +17 | to do." +18 | Said the +19 | mouse to the +20 | cur, "Such +21 | a trial, +22 | dear Sir, +23 | With +24 | no jury +25 | or judge, +26 | would be +27 | wasting +28 | our +29 | breath." +30 | "I’ll be +31 | judge, I’ll +32 | be jury," +33 | Said +34 | cunning +35 | old Fury: +36 | "I’ll +37 | try the +38 | whole +39 | cause, +40 | and +41 | condemn +42 | you +43 | to +44 | death."’ +</pre> +<p> +<h2><a name='sect40' href='#toc40'>Additional Breaks - Linebreaks Within Objects, Column and Page-breaks</a></h2> + +<p> +<h2><a name='sect41' href='#toc41'>Line-breaks</a></h2> + +<p> +<br> +To break a line within a "paragraph object", two backslashes \\ with a space +before and a space or newline after them may be used. +<p> <br> +<pre>To break a line within a "paragraph object", +two backslashes \\ with a space before +and a space or newline after them \\ +may be used. +</pre> +<p> <br> +The html break br enclosed in angle brackets (though undocumented) is available +in versions prior to 3.0.13 and 2.9.7 (it remains available for the time being, +but is depreciated). +<p> +<h2><a name='sect42' href='#toc42'>Page Breaks</a></h2> + +<p> <br> +Page breaks are only relevant and honored in some output formats. A page +break or a new page may be inserted manually using the following markup +on a line on its own: +<p> <br> +page new =\= or breaks the page, starts a new page. +<p> <br> +page break -\- or breaks a column, starts a new column, if using columns, +else breaks the page, starts a new page. +<p> <br> +<pre>-\\- +or +<:pb> +</pre> +<p> <br> + +<p>or +<p> <br> +<pre>=\\= +or +<:pn> +</pre> +<p> +<h2><a name='sect43' href='#toc43'>Book Index</a></h2> + +<p> <br> +To make an index append to paragraph the book index term relates to it, +using an equal sign and curly braces. +<p> <br> +Currently two levels are provided, a main term and if needed a sub-term. +Sub-terms are separated from the main term by a colon. +<p> <br> +<pre> Paragraph containing main term and sub-term. + ={Main term:sub-term} +</pre> +<p> <br> +The index syntax starts on a new line, but there should not be an empty +line between paragraph and index markup. +<p> <br> +The structure of the resulting index would be: +<p> <br> +<pre> Main term, 1 + sub-term, 1 +</pre> +<p> <br> +Several terms may relate to a paragraph, they are separated by a semicolon. +If the term refers to more than one paragraph, indicate the number of paragraphs. + +<p> <br> +<pre> Paragraph containing main term, second term and sub-term. + ={first term; second term: sub-term} +</pre> +<p> <br> +The structure of the resulting index would be: +<p> <br> +<pre> First term, 1, + Second term, 1, + sub-term, 1 +</pre> +<p> <br> +If multiple sub-terms appear under one paragraph, they are separated under +the main term heading from each other by a pipe symbol. +<p> <br> +<pre> Paragraph containing main term, second term and sub-term. + ={Main term:sub-term+1|second sub-term} + A paragraph that continues discussion of the first sub-term +</pre> +<p> <br> +The plus one in the example provided indicates the first sub-term spans +one additional paragraph. The logical structure of the resulting index would +be: +<p> <br> +<pre> Main term, 1, + sub-term, 1-3, + second sub-term, 1, +</pre> +<p> +<h2><a name='sect44' href='#toc44'>Composite Documents Markup</a></h2> +<br> + +<p> <br> +It is possible to build a document by creating a master document that requires +other documents. The documents required may be complete documents that could +be generated independently, or they could be markup snippets, prepared +so as to be easily available to be placed within another text. If the calling +document is a master document (built from other documents), it should be +named with the suffix <b>.ssm</b> Within this document you would provide information +on the other documents that should be included within the text. These may +be other documents that would be processed in a regular way, or markup +bits prepared only for inclusion within a master document <b>.sst</b> regular markup +file, or <b>.ssi</b> (insert/information) A secondary file of the composite document + +<p>is built prior to processing with the same prefix and the suffix <b>._sst</b> +<p> +<br> + +<p>basic markup for importing a document into a master document +<p> <br> +<pre><< filename1.sst +<< filename2.ssi +</pre> +<p> <br> +The form described above should be relied on. Within the <i>Vim</i> editor it results +in the text thus linked becoming hyperlinked to the document it is calling +in which is convenient for editing. +<p> +<h2><a name='sect45' href='#toc45'>Sisu Filetypes</a></h2> +<br> + +<p> <br> +<b>SiSU</b> has <i>plaintext</i> and binary filetypes, and can process either type of +document. +<p> +<h2><a name='sect46' href='#toc46'>.sst .ssm .ssi Marked Up Plain Text</a></h2> + +<p> +<dl> + +<dt><b>SiSU¤b〕 documents are prepared +as plain-text (utf-8) files with</b> </dt> +<dd><b>SiSU</b> markup. They may make reference to and +contain images (for example), which are stored in the directory beneath +them _sisu/image. 〔b¤SiSU <i>plaintext</i> markup files are of three types that +may be distinguished by the file extension used: regular text .sst; master +documents, composite documents that incorporate other text, which can be +any regular text or text insert; and inserts the contents of which are +like regular text except these are marked .ssi and are not processed.<br> + +<p> <br> +<b>SiSU</b> processing can be done directly against a sisu documents; which may +be located locally or on a remote server for which a url is provided. +<p> <br> +<b>SiSU</b> source markup can be shared with the command: +<p> <br> + sisu -s [filename]<br> + +<p> </dd> +</dl> + +<h2><a name='sect47' href='#toc47'>Sisu Text - Regular Files (.sst)</a></h2> + +<p> <br> +The most common form of document in <b>SiSU,</b> see the section on <b>SiSU</b> markup. + +<p> +<h2><a name='sect48' href='#toc48'>Sisu Master Files (.ssm)</a></h2> + +<p> <br> +Composite documents which incorporate other <b>SiSU</b> documents which may be +either regular <b>SiSU</b> text .sst which may be generated independently, or inserts +prepared solely for the purpose of being incorporated into one or more +master documents. +<p> <br> +The mechanism by which master files incorporate other documents is described +as one of the headings under under <b>SiSU</b> markup in the <b>SiSU</b> manual. +<p> <br> +Note: Master documents may be prepared in a similar way to regular documents, +and processing will occur normally if a .sst file is renamed .ssm without +requiring any other documents; the .ssm marker flags that the document may +contain other documents. +<p> <br> +Note: a secondary file of the composite document is built prior to processing +with the same prefix and the suffix ._sst [^19] +<p> +<h2><a name='sect49' href='#toc49'>Sisu Insert Files (.ssi)</a></h2> + +<p> +<br> +Inserts are documents prepared solely for the purpose of being incorporated +into one or more master documents. They resemble regular <b>SiSU</b> text files +except they are ignored by the <b>SiSU</b> processor. Making a file a .ssi file +is a quick and convenient way of flagging that it is not intended that +the file should be processed on its own. +<p> +<h2><a name='sect50' href='#toc50'>Sisupod, Zipped Binary Container +(sisupod.zip, .ssp)</a></h2> + +<p> <br> +A sisupod is a zipped <b>SiSU</b> text file or set of <b>SiSU</b> text files and any +associated images that they contain (this will be extended to include sound +and multimedia-files) +<p> +<dl> + +<dt><b>SiSU</b> </dt> +<dd><i>plaintext</i> files rely on a recognised directory +structure to find contents such as images associated with documents, but +all images for example for all documents contained in a directory are located +in the sub-directory _sisu/image. Without the ability to create a sisupod +it can be inconvenient to manually identify all other files associated +with a document. A sisupod automatically bundles all associated files with +the document that is turned into a pod. +<p> <br> +The structure of the sisupod is such that it may for example contain a +single document and its associated images; a master document and its associated +documents and anything else; or the zipped contents of a whole directory +of prepared <b>SiSU</b> documents. +<p> <br> +The command to create a sisupod is: +<p> <br> + sisu -S [filename]<br> + +<p> <br> +Alternatively, make a pod of the contents of a whole directory: +<p> <br> + sisu -S<br> + +<p> <br> +<b>SiSU</b> processing can be done directly against a sisupod; which may be located +locally or on a remote server for which a url is provided. +<p> <br> +<<a href='http://www.sisudoc.org/sisu/sisu_commands'>http://www.sisudoc.org/sisu/sisu_commands</a> +> +<p> <br> +<<a href='http://www.sisudoc.org/sisu/sisu_manual'>http://www.sisudoc.org/sisu/sisu_manual</a> +> +<p> </dd> +</dl> + +<h2><a name='sect51' href='#toc51'>Configuration</a></h2> +<br> + +<p> +<h2><a name='sect52' href='#toc52'>Configuration Files</a></h2> + +<p> +<h2><a name='sect53' href='#toc53'>Config.yml</a></h2> + +<p> <br> +<b>SiSU</b> configration parameters are adjusted in the configuration file, which +can be used to override the defaults set. This includes such things as which +directory interim processing should be done in and where the generated +output should be placed. +<p> <br> +The <b>SiSU</b> configuration file is a yaml file, which means indentation is +significant. +<p> <br> +<b>SiSU</b> resource configuration is determined by looking at the following files +if they exist: +<p> <br> + ./_sisu/v4/sisurc.yml<br> + +<p> <br> + ./_sisu/sisurc.yml<br> + +<p> <br> + ~/.sisu/v4/sisurc.yml<br> + +<p> <br> + ~/.sisu/sisurc.yml<br> + +<p> <br> + /etc/sisu/v4/sisurc.yml<br> + +<p> <br> + /etc/sisu/sisurc.yml<br> + +<p> <br> +The search is in the order listed, and the first one found is used. +<p> <br> +In the absence of instructions in any of these it falls back to the internal +program defaults. +<p> <br> +Configuration determines the output and processing directories and the +database access details. +<p> <br> + +<p>If <b>SiSU</b> is installed a sample sisurc.yml may be found in /etc/sisu/sisurc.yml + +<p> +<h2><a name='sect54' href='#toc54'>Sisu_document_make</a></h2> + +<p> <br> +Most sisu document headers relate to metadata, the exception is the @make: +header which provides processing related information. The default contents +of the @make header may be set by placing them in a file sisu_document_make. + +<p> <br> +The search order is as for resource configuration: +<p> <br> + ./_sisu/v4/sisu_document_make<br> + +<p> <br> + ./_sisu/sisu_document_make<br> + +<p> <br> + ~/.sisu/v4/sisu_document_make<br> + +<p> <br> + ~/.sisu/sisu_document_make<br> + +<p> <br> + /etc/sisu/v4/sisu_document_make<br> + +<p> <br> + /etc/sisu/sisu_document_make<br> + +<p> <br> +A sample sisu_document_make can be found in the _sisu/ directory under +along with the provided sisu markup samples. +<p> +<h2><a name='sect55' href='#toc55'>Css - Cascading Style Sheets +(for Html, Xhtml and Xml)</a></h2> +<br> + +<p> <br> +CSS files to modify the appearance of <b>SiSU</b> html, <i>XHTML</i> or <i>XML</i> may be placed +in the configuration directory: ./_sisu/css ; ~/.sisu/css or; /etc/sisu/css +and these will be copied to the output directories with the command sisu +-CC. +<p> <br> +The basic CSS file for html output is html. css, placing a file of that +name in directory _sisu/css or equivalent will result in the default file +of that name being overwritten. +<p> <br> +<i>HTML:</i> html. css +<p> <br> +<i>XML</i> DOM: dom.css +<p> <br> +<i>XML</i> SAX: sax.css +<p> <br> +<i>XHTML:</i> xhtml. css +<p> <br> +The default homepage may use homepage.css or html. css +<p> <br> +Under consideration is to permit the placement of a CSS file with a different +name in directory _sisu/css directory or equivalent.[^20] +<p> +<h2><a name='sect56' href='#toc56'>Organising Content +- Directory Structure and Mapping</a></h2> +<br> + +<p> <br> +<b>SiSU</b> v3 has new options for the source directory tree, and output directory +structures of which there are 3 alternatives. +<p> +<h2><a name='sect57' href='#toc57'>Document Source Directory</a></h2> + +<p> +<br> +The document source directory is the directory in which sisu processing +commands are given. It contains the sisu source files (.sst .ssm .ssi), or +(for sisu v3 may contain) subdirectories with language codes which contain +the sisu source files, so all English files would go in subdirectory en/, +French in fr/, Spanish in es/ and so on. ISO 639-1 codes are used (as varied +by po4a). A list of available languages (and possible sub-directory names) +can be obtained with the command "sisu --help lang" The list of languages +is limited to langagues supported by XeTeX polyglosia. +<p> +<h2><a name='sect58' href='#toc58'>General Directories</a></h2> + +<p> +<br> +<pre>% files stored at this level e.g. sisu_manual.sst or +% for sisu v3 may be under language sub-directories +% e.g. + ./subject_name/en + ./subject_name/fr + ./subject_name/es + ./subject_name/_sisu + ./subject_name/_sisu/css + ./subject_name/_sisu/image +</pre> +<p> +<h2><a name='sect59' href='#toc59'>Document Output Directory Structures</a></h2> + +<p> +<h2><a name='sect60' href='#toc60'>Output Directory Root</a></h2> + +<p> <br> +The output directory root can be set in the sisurc.yml file. Under the root, +subdirectories are made for each directory in which a document set resides. +If you have a directory named poems or conventions, that directory will +be created under the output directory root and the output for all documents +contained in the directory of a particular name will be generated to subdirectories +beneath that directory (poem or conventions). A document will be placed +in a subdirectory of the same name as the document with the filetype identifier +stripped (.sst .ssm) +<p> <br> +The last part of a directory path, representing the sub-directory in which +a document set resides, is the directory name that will be used for the +output directory. This has implications for the organisation of document +collections as it could make sense to place documents of a particular subject, +or type within a directory identifying them. This grouping as suggested +could be by subject (sales_law, english_literature); or just as conveniently +by some other classification (X University). The mapping means it is also +possible to place in the same output directory documents that are for organisational +purposes kept separately, for example documents on a given subject of two +different institutions may be kept in two different directories of the +same name, under a directory named after each institution, and these would +be output to the same output directory. Skins could be associated with each +institution on a directory basis and resulting documents will take on the +appropriate different appearance. +<p> +<h2><a name='sect61' href='#toc61'>Alternative Output Structures</a></h2> + +<p> <br> +There are 3 possibile output structures described as being, by language, +by filetype or by filename, the selection is made in sisurc.yml +<p> <br> +<pre>#% output_dir_structure_by: language; filetype; or filename +output_dir_structure_by: language #(language & filetype, preferred?) +#output_dir_structure_by: filetype +#output_dir_structure_by: filename #(default, closest to original v1 & +v2) +</pre> +<p> +<h2><a name='sect62' href='#toc62'>by Language</a></h2> + +<p> <br> + +<p>The by language directory structure places output files +<p> <br> +The by language directory structure separates output files by language +code (all files of a given language), and within the language directory +by filetype. +<p> <br> + +<p>Its selection is configured in sisurc.yml +<p> <br> +output_dir_structure_by: language +<p> <br> +<pre> |-- en + |-- epub + |-- hashes + |-- html + | |-- viral_spiral.david_bollier + | |-- manifest + | |-- qrcode + | |-- odt + | |-- pdf + | |-- sitemaps + | |-- txt + | |-- xhtml + | ‘-- xml + |-- po4a + | ‘-- live-manual + | |-- po + | |-- fr + | ‘-- pot + ‘-- _sisu + |-- css + |-- image + |-- image_sys -> ../../_sisu/image_sys + ‘-- xml + |-- rnc + |-- rng + ‘-- xsd +</pre> +<p> <br> +#by: language subject_dir/en/manifest/filename.html +<p> +<h2><a name='sect63' href='#toc63'>by Filetype</a></h2> + +<p> <br> +The by filetype directory structure separates output files by filetype, +all html files in one directory pdfs in another and so on. Filenames are +given a language extension. +<p> <br> + +<p>Its selection is configured in sisurc.yml +<p> <br> +output_dir_structure_by: filetype +<p> <br> +<pre> |-- epub + |-- hashes + |-- html + |-- viral_spiral.david_bollier + |-- manifest + |-- qrcode + |-- odt + |-- pdf + |-- po4a + |-- live-manual + | |-- po + | |-- fr + | ‘-- pot + |-- _sisu + | |-- css + | |-- image + | |-- image_sys -> ../../_sisu/image_sys + | ‘-- xml + | |-- rnc + | |-- rng + | ‘-- xsd + |-- sitemaps + |-- txt + |-- xhtml + ‘-- xml +</pre> +<p> <br> +#by: filetype subject_dir/html/filename/manifest.en.html +<p> +<h2><a name='sect64' href='#toc64'>by Filename</a></h2> + +<p> <br> +The by filename directory structure places most output of a particular +file (the different filetypes) in a common directory. +<p> <br> + +<p>Its selection is configured in sisurc.yml +<p> <br> +output_dir_structure_by: filename +<p> <br> +<pre> |-- epub + |-- po4a + |-- live-manual + | |-- po + | |-- fr + | ‘-- pot + |-- _sisu + | |-- css + | |-- image + | |-- image_sys -> ../../_sisu/image_sys + | ‘-- xml + | |-- rnc + | |-- rng + | ‘-- xsd + |-- sitemaps + |-- src + |-- pod + ‘-- viral_spiral.david_bollier +</pre> +<p> <br> +#by: filename subject_dir/filename/manifest.en.html +<p> +<h2><a name='sect65' href='#toc65'>Remote Directories</a></h2> + +<p> <br> +<pre>% containing sub_directories named after the generated files from which +they are made + ./subject_name/src +% contains shared source files text and binary e.g. sisu_manual.sst and sisu_manual.sst.zip + ./subject_name/_sisu +% configuration file e.g. sisurc.yml + ./subject_name/_sisu/skin +% skins in various skin directories doc, dir, site, yml + ./subject_name/_sisu/css + ./subject_name/_sisu/image +% images for documents contained in this directory + ./subject_name/_sisu/mm +</pre> +<p> +<h2><a name='sect66' href='#toc66'>Sisupod</a></h2> + +<p> <br> +<pre>% files stored at this level e.g. sisu_manual.sst + ./sisupod/_sisu +% configuration file e.g. sisurc.yml + ./sisupod/_sisu/skin +% skins in various skin directories doc, dir, site, yml + ./sisupod/_sisu/css + ./sisupod/_sisu/image +% images for documents contained in this directory + ./sisupod/_sisu/mm +</pre> +<p> +<h2><a name='sect67' href='#toc67'>Organising Content</a></h2> + +<p> +<h2><a name='sect68' href='#toc68'>Homepages</a></h2> +<br> + +<p> <br> +<b>SiSU</b> is about the ability to auto-generate documents. Home pages are regarded +as custom built items, and are not created by <b>SiSU.</b> More accurately, <b>SiSU</b> +has a default home page, which will not be appropriate for use with other +sites, and the means to provide your own home page instead in one of two +ways as part of a site’s configuration, these being: +<p> <br> +1. through placing your home page and other custom built documents in the +subdirectory _sisu/home/ (this probably being the easier and more convenient +option) +<p> <br> +2. through providing what you want as the home page in a skin, +<p> <br> +Document sets are contained in directories, usually organised by site or +subject. Each directory can/should have its own homepage. See the section +on directory structure and organisation of content. +<p> +<h2><a name='sect69' href='#toc69'>Home Page and Other +Custom Built Pages in a Sub-directory</a></h2> + +<p> <br> +Custom built pages, including the home page index.html may be placed within +the configuration directory _sisu/home/ in any of the locations that is +searched for the configuration directory, namely ./_sisu ; ~/_sisu ; /etc/sisu +From there they are copied to the root of the output directory with the +command: +<p> <br> + sisu -CC<br> + +<p> +<h2><a name='sect70' href='#toc70'>Markup and Output Examples</a></h2> +<br> + +<p> +<h2><a name='sect71' href='#toc71'>Markup Examples</a></h2> + +<p> <br> +Current markup examples and document output samples are provided off <<a href='http://sisudoc.org'>http://sisudoc.org</a> +> +or <<a href='http://www.jus.uio.no/sisu'>http://www.jus.uio.no/sisu</a> +> and in the sisu -markup-sample package available +off <<a href='http://sources.sisudoc.org'>http://sources.sisudoc.org</a> +> +<p> <br> +For some documents hardly any markup at all is required at all, other than +a header, and an indication that the levels to be taken into account by +the program in generating its output are. +<p> +<h2><a name='sect72' href='#toc72'>Sisu Markup Samples</a></h2> + +<p> <br> +A few additional sample books prepared as sisu markup samples, output formats +to be generated using <b>SiSU</b> are contained in a separate package sisu -markup-samples. +sisu -markup-samples contains books (prepared using sisu markup), that were +released by their authors various licenses mostly different Creative Commons +licences that do not permit inclusion in the <b>Debian</b> Project as they have +requirements that do not meet the <b>Debian</b> Free Software Guidelines for various +reasons, most commonly that they require that the original substantive +text remain unchanged, and sometimes that the works be used only non-commercially. + +<p> <br> +<i>Accelerando,</i> Charles Stross (2005) accelerando.charles_stross.sst +<p> <br> +<i>Alice’s</i> Adventures in Wonderland, Lewis Carroll (1865) alices_adventures_in_wonderland.lewis_carroll.sst + +<p> <br> +<i>CONTENT,</i> Cory Doctorow (2008) content.cory_doctorow.sst +<p> <br> +<i>Democratizing</i> Innovation, Eric von Hippel (2005) democratizing_innovation.eric_von_hippel.sst + +<p> <br> +<i>Down</i> and Out in the Magic Kingdom, Cory Doctorow (2003) down_and_out_in_the_magic_kingdom.cory_doctorow.sst + +<p> <br> +<i>For</i> the Win, Cory Doctorow (2010) for_the_win.cory_doctorow.sst +<p> <br> +<i>Free</i> as in Freedom - Richard Stallman’s Crusade for Free Software, Sam Williams +(2002) free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst + +<p> <br> +<i>Free</i> as in Freedom 2.0 - Richard Stallman and the Free Software Revolution, +Sam Williams (2002), Richard M. Stallman (2010) free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst + +<p> <br> +<i>Free</i> Culture - How Big Media Uses Technology and the Law to Lock Down Culture +and Control Creativity, Lawrence Lessig (2004) free_culture.lawrence_lessig.sst + +<p> <br> +<i>Free</i> For All - How Linux and the Free Software Movement Undercut the High +Tech Titans, Peter Wayner (2002) free_for_all.peter_wayner.sst +<p> <br> +<i>GNU</i> GENERAL PUBLIC LICENSE v2, Free Software Foundation (1991) gpl2.fsf.sst + +<p> <br> +<i>GNU</i> GENERAL PUBLIC LICENSE v3, Free Software Foundation (2007) gpl3.fsf.sst + +<p> <br> +<i>Gulliver’s</i> Travels, Jonathan Swift (1726 / 1735) gullivers_travels.jonathan_swift.sst + +<p> <br> +<i>Little</i> Brother, Cory Doctorow (2008) little_brother.cory_doctorow.sst +<p> <br> +<i>The</i> Cathederal and the Bazaar, Eric Raymond (2000) the_cathedral_and_the_bazaar.eric_s_raymond.sst + +<p> <br> +<i>The</i> Public Domain - Enclosing the Commons of the Mind, James Boyle (2008) + +<p>the_public_domain.james_boyle.sst +<p> <br> +<i>The</i> Wealth of Networks - How Social Production Transforms Markets and Freedom, +Yochai Benkler (2006) the_wealth_of_networks.yochai_benkler.sst +<p> <br> +<i>Through</i> the Looking Glass, Lewis Carroll (1871) through_the_looking_glass.lewis_carroll.sst + +<p> <br> +<i>Two</i> Bits - The Cultural Significance of Free Software, Christopher Kelty +(2008) two_bits.christopher_kelty.sst +<p> <br> +<i>UN</i> Contracts for International Sale of Goods, UN (1980) un_contracts_international_sale_of_goods_convention_1980.sst + +<p> <br> +<i>Viral</i> Spiral, David Bollier (2008) viral_spiral.david_bollier.sst +<p> +<h2><a name='sect73' href='#toc73'>Sisu Search +- Introduction</a></h2> +<br> + +<p> <br> +<b>SiSU</b> output can easily and conveniently be indexed by a number of standalone +indexing tools, such as Lucene, Hyperestraier. +<p> <br> +Because the document structure of sites created is clearly defined, and +the text <i>object</i> citation system is available hypothetically at least, for +all forms of output, it is possible to search the sql database, and either +read results from that database, or just as simply map the results to the +html output, which has richer text markup. +<p> <br> +In addition to this <b>SiSU</b> has the ability to populate a relational sql type +database with documents at an object level, with objects numbers that are +shared across different output types, which make them searchable with that +degree of granularity. Basically, your match criteria is met by these documents +and at these locations within each document, which can be viewed within +the database directly or in various output formats. +<p> +<h2><a name='sect74' href='#toc74'>Sql</a></h2> +<br> + +<p> +<h2><a name='sect75' href='#toc75'>Populating Sql Type Databases</a></h2> + +<p> <br> +<b>SiSU</b> feeds sisu markupd documents into sql type databases <i>PostgreSQL</i> [^21] +and/or <i>SQLite</i> [^22] database together with information related to document +structure. +<p> <br> +This is one of the more interesting output forms, as all the structural +data of the documents are retained (though can be ignored by the user of +the database should they so choose). All site texts/documents are (currently) +streamed to four tables: +<p> <br> + * one containing semantic (and other) headers, including, title, author,<br> + subject, (the<br> + .I Dublin Core.<br> + ..);<br> + +<p> <br> + * another the substantive texts by individual "paragraph" (or object) +-<br> + along with structural information, each paragraph being identifiable +by its<br> + paragraph number (if it has one which almost all of them do), and the<br> + substantive text of each paragraph quite naturally being searchable +(both in<br> + formatted and clean text versions for searching); and<br> + +<p> <br> + * a third containing endnotes cross-referenced back to the paragraph from<br> + which they are referenced (both in formatted and clean text versions +for<br> + searching).<br> + +<p> <br> + * a fourth table with a one to one relation with the headers table contains<br> + full text versions of output, eg. pdf, html, xml, and<br> + .I ascii.<br> + +<p> <br> +There is of course the possibility to add further structures. +<p> <br> +At this level <b>SiSU</b> loads a relational database with documents chunked into +objects, their smallest logical structurally constituent parts, as text +objects, with their object citation number and all other structural information +needed to construct the document. Text is stored (at this text object level) +with and without elementary markup tagging, the stripped version being +so as to facilitate ease of searching. +<p> <br> +Being able to search a relational database at an object level with the +<b>SiSU</b> citation system is an effective way of locating content generated +by <b>SiSU.</b> As individual text objects of a document stored (and indexed) together +with object numbers, and all versions of the document have the same numbering, +complex searches can be tailored to return just the locations of the search +results relevant for all available output formats, with live links to the +precise locations in the database or in html/xml documents; or, the structural +information provided makes it possible to search the full contents of the +database and have headings in which search content appears, or to search +only headings etc. (as the <i>Dublin</i> Core is incorporated it is easy to make +use of that as well). +<p> +<h2><a name='sect76' href='#toc76'>Postgresql</a></h2> +<br> + +<p> +<h2><a name='sect77' href='#toc77'>Name</a></h2> + +<p> <br> +<b>SiSU</b> - Structured information, Serialized Units - a document publishing system, + +<p>postgresql dependency package +<p> +<h2><a name='sect78' href='#toc78'>Description</a></h2> + +<p> <br> +Information related to using postgresql with sisu (and related to the sisu_postgresql +dependency package, which is a dummy package to install dependencies needed +for <b>SiSU</b> to populate a postgresql database, this being part of <b>SiSU</b> - man +sisu) . +<p> +<h2><a name='sect79' href='#toc79'>Synopsis</a></h2> + +<p> <br> + sisu -D [instruction] [filename/wildcard if required]<br> + +<p> <br> + sisu -D --pg --[instruction] [filename/wildcard if required]<br> + +<p> +<h2><a name='sect80' href='#toc80'>Commands</a></h2> + +<p> <br> +Mappings to two databases are provided by default, postgresql and sqlite, +the same commands are used within sisu to construct and populate databases +however -d (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, + +<p>alternatively --sqlite or --pgsql may be used +<p> <br> +<b>-D or --pgsql</b> may be used interchangeably. +<p> +<h2><a name='sect81' href='#toc81'>Create and Destroy Database</a></h2> + +<p> +<dl> + +<dt><b>--pgsql +--createall</b> </dt> +<dd>initial step, creates required relations (tables, indexes) in +existing (postgresql) database (a database should be created manually and +given the same name as working directory, as requested) (rb.dbi) +<p> </dd> + +<dt><b>sisu -D +--createdb</b> </dt> +<dd>creates database where no database existed before +<p> </dd> + +<dt><b>sisu -D --create</b> +</dt> +<dd> +<p>creates database tables where no database tables existed before +<p> </dd> + +<dt><b>sisu -D +--Dropall</b> </dt> +<dd>destroys database (including all its content)! kills data and drops +tables, indexes and database associated with a given directory (and directories +of the same name). +<p> </dd> + +<dt><b>sisu -D --recreate</b> </dt> +<dd>destroys existing database and builds + +<p>a new empty database structure +<p> </dd> +</dl> + +<h2><a name='sect82' href='#toc82'>Import and Remove Documents</a></h2> + +<p> +<dl> + +<dt><b>sisu -D --import +-v [filename/wildcard]</b> </dt> +<dd>populates database with the contents of the file. +Imports documents(s) specified to a postgresql database (at an object level). + +<p> </dd> + +<dt><b>sisu -D --update -v [filename/wildcard]</b> </dt> +<dd>updates file contents in database + +<p> </dd> + +<dt><b>sisu -D --remove -v [filename/wildcard]</b> </dt> +<dd>removes specified document from postgresql +database. +<p> </dd> +</dl> + +<h2><a name='sect83' href='#toc83'>Sqlite</a></h2> +<br> + +<p> +<h2><a name='sect84' href='#toc84'>Name</a></h2> + +<p> <br> +<b>SiSU</b> - Structured information, Serialized Units - a document publishing system. + +<p> +<h2><a name='sect85' href='#toc85'>Description</a></h2> + +<p> <br> +Information related to using sqlite with sisu (and related to the sisu_sqlite +dependency package, which is a dummy package to install dependencies needed +for <b>SiSU</b> to populate an sqlite database, this being part of <b>SiSU</b> - man sisu) +. +<p> +<h2><a name='sect86' href='#toc86'>Synopsis</a></h2> + +<p> <br> + sisu -d [instruction] [filename/wildcard if required]<br> + +<p> <br> + sisu -d --(sqlite|pg) --[instruction] [filename/wildcard if <br> + required]<br> + +<p> +<h2><a name='sect87' href='#toc87'>Commands</a></h2> + +<p> <br> +Mappings to two databases are provided by default, postgresql and sqlite, +the same commands are used within sisu to construct and populate databases +however -d (lowercase) denotes sqlite and -D (uppercase) denotes postgresql, + +<p>alternatively --sqlite or --pgsql may be used +<p> <br> +<b>-d or --sqlite</b> may be used interchangeably. +<p> +<h2><a name='sect88' href='#toc88'>Create and Destroy Database</a></h2> + +<p> +<dl> + +<dt><b>--sqlite +--createall</b> </dt> +<dd>initial step, creates required relations (tables, indexes) in +existing (sqlite) database (a database should be created manually and given +the same name as working directory, as requested) (rb.dbi) +<p> </dd> + +<dt><b>sisu -d --createdb</b> +</dt> +<dd> +<p>creates database where no database existed before +<p> </dd> + +<dt><b>sisu -d --create</b> </dt> +<dd>creates + +<p>database tables where no database tables existed before +<p> </dd> + +<dt><b>sisu -d --dropall</b> +</dt> +<dd>destroys database (including all its content)! kills data and drops tables, +indexes and database associated with a given directory (and directories +of the same name). +<p> </dd> + +<dt><b>sisu -d --recreate</b> </dt> +<dd>destroys existing database and builds + +<p>a new empty database structure +<p> </dd> +</dl> + +<h2><a name='sect89' href='#toc89'>Import and Remove Documents</a></h2> + +<p> +<dl> + +<dt><b>sisu -d --import +-v [filename/wildcard]</b> </dt> +<dd>populates database with the contents of the file. +Imports documents(s) specified to an sqlite database (at an object level). + +<p> </dd> + +<dt><b>sisu -d --update -v [filename/wildcard]</b> </dt> +<dd>updates file contents in database + +<p> </dd> + +<dt><b>sisu -d --remove -v [filename/wildcard]</b> </dt> +<dd>removes specified document from sqlite +database. +<p> </dd> +</dl> + +<h2><a name='sect90' href='#toc90'>Introduction</a></h2> +<br> + +<p> +<h2><a name='sect91' href='#toc91'>Search - Database Frontend Sample, Utilising Database and Sisu Features,</a></h2> +INCLUDING +OBJECT CITATION NUMBERING (BACKEND CURRENTLY POSTGRESQL) +<p> <br> +Sample search frontend <<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a> +> [^23] A small database and +sample query front-end (search from) that makes use of the citation system, +<i>object</i> citation numbering to demonstrates functionality.[^24] +<p> <br> +<b>SiSU</b> can provide information on which documents are matched and at what +locations within each document the matches are found. These results are +relevant across all outputs using <i>object</i> citation numbering, which includes +html, <i>XML,</i> <i>EPUB,</i> <i>LaTeX,</i> <i>PDF</i> and indeed the <i>SQL</i> database. You can then refer +to one of the other outputs or in the <i>SQL</i> database expand the text within +the matched objects (paragraphs) in the documents matched. +<p> <br> +Note you may set results either for documents matched and object number +locations within each matched document meeting the search criteria; or +display the names of the documents matched along with the objects (paragraphs) +that meet the search criteria.[^25] +<p> +<dl> + +<dt><b>sisu -F --webserv-webrick</b> </dt> +<dd>builds a cgi web + +<p>search frontend for the database created +<p> <br> +The following is feedback on the setup on a machine provided by the help +command: +<p> <br> + sisu --help sql<br> + +<p> <br> +<pre>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 +</pre> +<p> <br> + +<p>Note on databases built +<p> <br> +By default, [unless otherwise specified] databases are built on a directory +basis, from collections of documents within that directory. The name of +the directory you choose to work from is used as the database name, i.e. +if you are working in a directory called /home/ralph/ebook the database +SiSU_ebook is used. [otherwise a manual mapping for the collection is +<p> </dd> +</dl> + +<h2><a name='sect92' href='#toc92'>Search +Form</a></h2> + +<p> +<dl> + +<dt><b>sisu -F</b> </dt> +<dd>generates a sample search form, which must be copied to the + +<p>web-server cgi directory +<p> </dd> + +<dt><b>sisu -F --webserv-webrick</b> </dt> +<dd>generates a sample search +form for use with the webrick server, which must be copied to the web-server + +<p>cgi directory +<p> </dd> + +<dt><b>sisu -W</b> </dt> +<dd>starts the webrick server which should be available + +<p>wherever sisu is properly installed +<p> <br> + +<p>The generated search form must be copied manually to the webserver directory + +<p>as instructed +<p> </dd> +</dl> + +<h2><a name='sect93' href='#toc93'>Sisu_webrick</a></h2> +<br> + +<p> +<h2><a name='sect94' href='#toc94'>Name</a></h2> + +<p> <br> +<b>SiSU</b> - Structured information, Serialized Units - a document publishing system + +<p> +<h2><a name='sect95' href='#toc95'>Synopsis</a></h2> + +<p> <br> +sisu_webrick [port] +<p> <br> + +<p>or +<p> <br> +sisu -W [port] +<p> +<h2><a name='sect96' href='#toc96'>Description</a></h2> + +<p> <br> +sisu_webrick is part of <b>SiSU</b> (man sisu) sisu_webrick starts <b>Ruby</b> <b>SiSU</b> +output is written, providing a list of these directories (assuming <b>SiSU</b> +is in use and they exist). +<p> <br> +The default port for sisu_webrick is set to 8081, this may be modified +in the yaml file: ~/.sisu/sisurc.yml a sample of which is provided as /etc/sisu/sisurc.yml +(or in the equivalent directory on your system). +<p> +<h2><a name='sect97' href='#toc97'>Summary of Man Page</a></h2> + +<p> <br> +sisu_webrick, may be started on it’s own with the command: sisu_webrick +[port] or using the sisu command with the -W flag: sisu -W [port] +<p> <br> + +<p>where no port is given and settings are unchanged the default port is 8081 + +<p> +<h2><a name='sect98' href='#toc98'>Document Processing Command Flags</a></h2> + +<p> <br> +sisu -W [port] starts <b>Ruby</b> Webrick web-server, serving <b>SiSU</b> output directories, +on the port provided, or if no port is provided and the defaults have not + +<p>been changed in ~/.sisu/sisurc.yaml then on port 8081 +<p> +<h2><a name='sect99' href='#toc99'>Summary of Features</a></h2> +<br> + +<p> <br> +* sparse/minimal markup (clean utf-8 source texts). Documents are prepared +in a single <i>UTF-8</i> file using a minimalistic mnemonic syntax. Typical literature, +documents like "War and Peace" require almost no markup, and most of the +headers are optional. +<p> <br> +* markup is easily readable/parsable by the human eye, (basic markup is +simpler and more sparse than the most basic <i>HTML</i> ) , [this may also be + converted to .I XML representations of the same input/source document]. +<p> +<br> +* markup defines document structure (this may be done once in a header +pattern-match description, or for heading levels individually); basic text +attributes (bold, italics, underscore, strike-through etc.) as required; +and semantic information related to the document (header information, extended +beyond the Dublin core and easily further extended as required); the headers +may also contain processing instructions. <b>SiSU</b> markup is primarily an abstraction +of document structure and document metadata to permit taking advantage +of the basic strengths of existing alternative practical standard ways +of representing documents [be that browser viewing, paper publication, + sql search etc.] (html, epub, xml, odf, latex, pdf, sql) +<p> <br> +* for output produces reasonably elegant output of established industry +and institutionally accepted open standard formats.[3] takes advantage of +the different strengths of various standard formats for representing documents, +amongst the output formats currently supported are: +<p> <br> +* <i>HTML</i> - both as a single scrollable text and a segmented document +<p> <br> +* <i>XHTML</i> +<p> <br> +* <i>EPUB</i> +<p> <br> +* <i>XML</i> - both in sax and dom style xml structures for further development + +<p>as required +<p> <br> +* <i>ODT</i> - Open Document Format text, the iso standard for document storage + +<p> <br> +* <i>LaTeX</i> - used to generate pdf +<p> <br> +* <i>PDF</i> (via <i>LaTeX</i> ) +<p> <br> +* <i>SQL</i> - population of an sql database ( <i>PostgreSQL</i> or <i>SQLite</i> ) , (at the +same object level that is used to cite text within a document) +<p> <br> +Also produces: concordance files; document content certificates (md5 or +sha256 digests of headings, paragraphs, images etc.) and html manifests +(and sitemaps of content). (b) takes advantage of the strengths implicit +in these very different output types, (e.g. PDFs produced using typesetting +of <i>LaTeX,</i> databases populated with documents at an individual object/paragraph +level, making possible <i>granular</i> search (and related possibilities)) +<p> <br> +* ensuring content can be cited in a meaningful way regardless of selected +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, <i>HTML,</i> <i>EPUB,</i> xml, sqlite, postgresql) , this +numbering system can be used to reference content. +<p> <br> +* Granular search within documents. <i>SQL</i> databases are populated at an object +level (roughly headings, paragraphs, verse, tables) and become searchable +with that degree of granularity, the output information provides the object/paragraph +numbers which are relevant across all generated outputs; it is also possible +to look at just the matching paragraphs of the documents in the database; +[output indexing also work +<p> <br> +* long term maintainability of document collections in a world of changing +formats, having a very sparsely marked-up source document base. there is +a considerable degree of future-proofing, output representations are "upgradeable", +and new document formats may be added. e.g. addition of odf (open document +text) module in 2006, epub in 2009 and in future html5 output sometime +in future, without modification of existing prepared texts +<p> <br> +* <i>SQL</i> search aside, documents are generated as required and static once +generated. +<p> <br> +* documents produced are static files, and may be batch processed, this +needs to be done only once but may be repeated for various reasons as desired +(updated content, addition of new output formats, updated technology document +presentations/representations) +<p> <br> +* document source ( <i>plaintext</i> utf-8) if shared on the net may be used as + +<p>input and processed locally to produce the different document outputs +<p> +<br> +* document source may be bundled together (automatically) with associated +documents (multiple language versions or master document with inclusions) +and images and sent as a zip file called a sisupod, if shared on the net + +<p>these too may be processed locally to produce the desired document outputs + +<p> <br> +* generated document outputs may automatically be posted to remote sites. + +<p> <br> +* for basic document generation, the only software dependency is <b>Ruby,</b> +and a few standard Unix tools (this covers <i>plaintext,</i> <i>HTML,</i> <i>EPUB,</i> <i>XML,</i> +<i>ODF,</i> <i>LaTeX</i> ) . To use a database you of course need that, and to convert +the <i>LaTeX</i> generated to pdf, a latex processor like tetex or texlive. +<p> <br> +* as a developers tool it is flexible and extensible +<p> <br> +Syntax highlighting for <b>SiSU</b> markup is available for a number of text editors. + +<p> <br> +<b>SiSU</b> is less about document layout than about finding a way with little +markup to be able to construct an abstract representation of a document +that makes it possible to produce multiple representations of it which +may be rather different from each other and used for different purposes, +whether layout and publishing, or search of content +<p> <br> +i.e. to be able to take advantage from this minimal preparation starting +point of some of the strengths of rather different established ways of +representing documents for different purposes, whether for search (relational +database, or indexed flat files generated for that purpose whether of complete +documents, or say of files made up of objects), online viewing (e.g. html, +xml, pdf) , or paper publication (e.g. pdf) ... +<p> <br> +the solution arrived at is by extracting structural information about the +document (about headings within the document) and by tracking objects (which +are serialized and also given hash values) in the manner described. It makes +possible representations that are quite different from those offered at +present. For example objects could be saved individually and identified +by their hashes, with an index of how the objects relate to each other +to form a document. +<p> +<ol> +<b>.</b><li>objects include: headings, paragraphs, verse, tables, +images, but not footnotes/endnotes which are numbered separately and tied +to the object from which they are referenced. +<p> <br> +</li><b>.</b><li>i.e. the +<p> <br> +<i>HTML,</i> +<p> <br> +<i>PDF,</i> +<p> <br> +<i>EPUB,</i> +<p> <br> + +<p><i>ODT</i> +<p> <br> +outputs are each built individually and optimised for that form of presentation, +rather than for example the html being a saved version of the odf, or the +pdf being a saved version of the html. +<p> <br> +</li><b>.</b><li> +<p>the different heading levels +<p> <br> +</li><b>.</b><li>units of text, primarily paragraphs and headings, also any tables, poems, + +<p>code-blocks +<p> <br> +</li><b>.</b><li> +<p>An open standard format for e-books +<p> <br> +</li><b>.</b><li>Open Document Format ( +<p> <br> + +<p><i>ODF</i> +<p> <br> +) text +<p> <br> +</li><b>.</b><li> +<p>Specification submitted by Adobe to ISO to become a full open ISO specification + +<p> <br> +<<a href='http://www.linux-watch.com/news/NS7542722606.html'>http://www.linux-watch.com/news/NS7542722606.html</a> +> +<p> <br> +</li><b>.</b><li> +<p>ISO standard ISO/IEC 26300:2006 +<p> <br> +</dd> + +<dt><b>*1.</b> </dt> +<dd>square brackets +<p> <br> +</dd> + +<dt><b>*2.</b> </dt> +<dd>square brackets +<p> <br> +</dd> + +<dt><b>+1.</b> </dt> +<dd>square brackets +<p> <br> +</li><b>.</b><li><<a href='http://www.jus.uio.no/sisu/man/'>http://www.jus.uio.no/sisu/man/</a> +> +<p> <br> +</li><b>.</b><li><<a href='http://www.jus.uio.no/sisu/man/sisu.1.html'>http://www.jus.uio.no/sisu/man/sisu.1.html</a> +> +<p> <br> +</li><b>.</b><li>From sometime after SiSU 0.58 it should be possible to describe SiSU markup +using SiSU, which though not an original design goal is useful. +<p> <br> +</li><b>.</b><li> +<p>files should be prepared using +<p> <br> + +<p><i>UTF-8</i> +<p> <br> + +<p>character encoding +<p> <br> +</li><b>.</b><li> +<p>a footnote or endnote +<p> <br> +</li><b>.</b><li>self contained endnote marker & endnote in one +<p> <br> +</dd> + +<dt><b>*.</b> </dt> +<dd>unnumbered asterisk footnote/endnote, insert multiple asterisks if required + +<p> <br> +</dd> + +<dt><b>**.</b> </dt> +<dd>another unnumbered asterisk footnote/endnote +<p> <br> +</dd> + +<dt><b>*3.</b> </dt> +<dd>editors notes, numbered asterisk footnote/endnote series +<p> <br> +</dd> + +<dt><b>+2.</b> </dt> +<dd>editors notes, numbered asterisk footnote/endnote series +<p> <br> +</li><b>.</b><li><<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> +<p> <br> +</li><b>.</b><li><<a href='http://www.ruby-lang.org/en/'>http://www.ruby-lang.org/en/</a> +> +<p> <br> +</li><b>.</b><li> +<p>Table from the Wealth of Networks by Yochai Benkler +<p> <br> +<<a href='http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler'>http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler</a> +> +<p> <br> +</li><b>.</b><li>.ssc (for composite) is under consideration but ._sst makes clear that this +is not a regular file to be worked on, and thus less likely that people +will have "accidents", working on a .ssc file that is overwritten by subsequent +processing. It may be however that when the resulting file is shared .ssc +is an appropriate suffix to use. +<p> <br> +</li><b>.</b><li><<a href='http://www.postgresql.org/'>http://www.postgresql.org/</a> +> +<p> <br> +<<a href='http://advocacy.postgresql.org/'>http://advocacy.postgresql.org/</a> +> +<p> <br> +<<a href='http://en.wikipedia.org/wiki/Postgresql'>http://en.wikipedia.org/wiki/Postgresql</a> +> +<p> <br> +</li><b>.</b><li><<a href='http://www.hwaci.com/sw/sqlite/'>http://www.hwaci.com/sw/sqlite/</a> +> +<p> <br> +<<a href='http://en.wikipedia.org/wiki/Sqlite'>http://en.wikipedia.org/wiki/Sqlite</a> +> +<p> <br> +</li><b>.</b><li><<a href='http://search.sisudoc.org'>http://search.sisudoc.org</a> +> +<p> <br> +</li><b>.</b><li>(which could be extended further with current back-end). As regards scaling +of the database, it is as scalable as the database (here Postgresql) and +hardware allow. +<p> <br> +</li><b>.</b><li>of this feature when demonstrated to an IBM software innovations evaluator +in 2004 he said to paraphrase: this could be of interest to us. We have +large document management systems, you can search hundreds of thousands +of documents and we can tell you which documents meet your search criteria, +but there is no way we can tell you without opening each document where +within each your matches are found. +<p> <br> + +<p> </li> +</ol> + +<h2><a name='sect100' href='#toc100'>See Also</a></h2> + <a href='http:~/bin/man2html?sisu:1'>sisu(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-epub:1'>sisu-epub(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-harvest:1'>sisu-harvest(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-html:1'>sisu-html(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-odf:1'>sisu-odf(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-pdf:1'>sisu-pdf(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-pg:1'>sisu-pg(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-sqlite:1'>sisu-sqlite(1)</a> +,<br> + <a href='http:~/bin/man2html?sisu-txt:1'>sisu-txt(1)</a> +.<br> + <a href='http:~/bin/man2html?sisu_vim:7'>sisu_vim(7)</a> +<br> + +<h2><a name='sect101' href='#toc101'>Homepage</a></h2> + More information about SiSU can be found at <<a href='http://www.sisudoc.org/'>http://www.sisudoc.org/</a> +> +or <<a href='http://www.jus.uio.no/sisu/'>http://www.jus.uio.no/sisu/</a> +><br> + +<h2><a name='sect102' href='#toc102'>Source</a></h2> + <<a href='http://sources.sisudoc.org/'>http://sources.sisudoc.org/</a> +><br> + +<h2><a name='sect103' href='#toc103'>Author</a></h2> + SiSU is written by Ralph Amissah <ralph@amissah.com><br> + <p> + +<hr><p> +<a name='toc'><b>Table of Contents</b></a><p> +<ul> +<li><a name='toc0' href='#sect0'>Name</a></li> +<li><a name='toc1' href='#sect1'>Synopsis</a></li> +<li><a name='toc2' href='#sect2'>Sisu - Manual,</a></li> +<li><a name='toc3' href='#sect3'>What is Sisu?</a></li> +<li><a name='toc4' href='#sect4'>Introduction - What is Sisu?</a></li> +<li><a name='toc5' href='#sect5'>Commands Summary</a></li> +<li><a name='toc6' href='#sect6'>Description</a></li> +<li><a name='toc7' href='#sect7'>Document Processing Command Flags</a></li> +<li><a name='toc8' href='#sect8'>Command Line Modifiers</a></li> +<li><a name='toc9' href='#sect9'>Database Commands</a></li> +<li><a name='toc10' href='#sect10'>Shortcuts, Shorthand for Multiple Flags</a></li> +<li><a name='toc11' href='#sect11'>Command Line with Flags - Batch Processing</a></li> +<li><a name='toc12' href='#sect12'>Help</a></li> +<li><a name='toc13' href='#sect13'>Sisu Manual</a></li> +<li><a name='toc14' href='#sect14'>Sisu Man Pages</a></li> +<li><a name='toc15' href='#sect15'>Sisu Built-in Interactive Help</a></li> +<li><a name='toc16' href='#sect16'>Introduction to Sisu Markup[^11]</a></li> +<li><a name='toc17' href='#sect17'>Summary</a></li> +<li><a name='toc18' href='#sect18'>Markup Examples</a></li> +<li><a name='toc19' href='#sect19'>Online</a></li> +<li><a name='toc20' href='#sect20'>Installed</a></li> +<li><a name='toc21' href='#sect21'>Markup of Headers</a></li> +<li><a name='toc22' href='#sect22'>Sample Header</a></li> +<li><a name='toc23' href='#sect23'>Available Headers</a></li> +<li><a name='toc24' href='#sect24'>Markup of Substantive Text</a></li> +<li><a name='toc25' href='#sect25'>Heading Levels</a></li> +<li><a name='toc26' href='#sect26'>Font Attributes</a></li> +<li><a name='toc27' href='#sect27'>Indentation and Bullets</a></li> +<li><a name='toc28' href='#sect28'>Hanging Indents</a></li> +<li><a name='toc29' href='#sect29'>Footnotes / Endnotes</a></li> +<li><a name='toc30' href='#sect30'>Links</a></li> +<li><a name='toc31' href='#sect31'>Naked Urls Within Text, Dealing with Urls</a></li> +<li><a name='toc32' href='#sect32'>Linking Text</a></li> +<li><a name='toc33' href='#sect33'>Linking Images</a></li> +<li><a name='toc34' href='#sect34'>Link Shortcut for Multiple Versions of a Sisu Document in the Same Directory</a></li> +<li><a name='toc35' href='#sect35'>Grouped Text</a></li> +<li><a name='toc36' href='#sect36'>Tables</a></li> +<li><a name='toc37' href='#sect37'>Poem</a></li> +<li><a name='toc38' href='#sect38'>Group</a></li> +<li><a name='toc39' href='#sect39'>Code</a></li> +<li><a name='toc40' href='#sect40'>Additional Breaks - Linebreaks Within Objects, Column and Page-breaks</a></li> +<li><a name='toc41' href='#sect41'>Line-breaks</a></li> +<li><a name='toc42' href='#sect42'>Page Breaks</a></li> +<li><a name='toc43' href='#sect43'>Book Index</a></li> +<li><a name='toc44' href='#sect44'>Composite Documents Markup</a></li> +<li><a name='toc45' href='#sect45'>Sisu Filetypes</a></li> +<li><a name='toc46' href='#sect46'>.sst .ssm .ssi Marked Up Plain Text</a></li> +<li><a name='toc47' href='#sect47'>Sisu Text - Regular Files (.sst)</a></li> +<li><a name='toc48' href='#sect48'>Sisu Master Files (.ssm)</a></li> +<li><a name='toc49' href='#sect49'>Sisu Insert Files (.ssi)</a></li> +<li><a name='toc50' href='#sect50'>Sisupod, Zipped Binary Container (sisupod.zip, .ssp)</a></li> +<li><a name='toc51' href='#sect51'>Configuration</a></li> +<li><a name='toc52' href='#sect52'>Configuration Files</a></li> +<li><a name='toc53' href='#sect53'>Config.yml</a></li> +<li><a name='toc54' href='#sect54'>Sisu_document_make</a></li> +<li><a name='toc55' href='#sect55'>Css - Cascading Style Sheets (for Html, Xhtml and Xml)</a></li> +<li><a name='toc56' href='#sect56'>Organising Content - Directory Structure and Mapping</a></li> +<li><a name='toc57' href='#sect57'>Document Source Directory</a></li> +<li><a name='toc58' href='#sect58'>General Directories</a></li> +<li><a name='toc59' href='#sect59'>Document Output Directory Structures</a></li> +<li><a name='toc60' href='#sect60'>Output Directory Root</a></li> +<li><a name='toc61' href='#sect61'>Alternative Output Structures</a></li> +<li><a name='toc62' href='#sect62'>by Language</a></li> +<li><a name='toc63' href='#sect63'>by Filetype</a></li> +<li><a name='toc64' href='#sect64'>by Filename</a></li> +<li><a name='toc65' href='#sect65'>Remote Directories</a></li> +<li><a name='toc66' href='#sect66'>Sisupod</a></li> +<li><a name='toc67' href='#sect67'>Organising Content</a></li> +<li><a name='toc68' href='#sect68'>Homepages</a></li> +<li><a name='toc69' href='#sect69'>Home Page and Other Custom Built Pages in a Sub-directory</a></li> +<li><a name='toc70' href='#sect70'>Markup and Output Examples</a></li> +<li><a name='toc71' href='#sect71'>Markup Examples</a></li> +<li><a name='toc72' href='#sect72'>Sisu Markup Samples</a></li> +<li><a name='toc73' href='#sect73'>Sisu Search - Introduction</a></li> +<li><a name='toc74' href='#sect74'>Sql</a></li> +<li><a name='toc75' href='#sect75'>Populating Sql Type Databases</a></li> +<li><a name='toc76' href='#sect76'>Postgresql</a></li> +<li><a name='toc77' href='#sect77'>Name</a></li> +<li><a name='toc78' href='#sect78'>Description</a></li> +<li><a name='toc79' href='#sect79'>Synopsis</a></li> +<li><a name='toc80' href='#sect80'>Commands</a></li> +<li><a name='toc81' href='#sect81'>Create and Destroy Database</a></li> +<li><a name='toc82' href='#sect82'>Import and Remove Documents</a></li> +<li><a name='toc83' href='#sect83'>Sqlite</a></li> +<li><a name='toc84' href='#sect84'>Name</a></li> +<li><a name='toc85' href='#sect85'>Description</a></li> +<li><a name='toc86' href='#sect86'>Synopsis</a></li> +<li><a name='toc87' href='#sect87'>Commands</a></li> +<li><a name='toc88' href='#sect88'>Create and Destroy Database</a></li> +<li><a name='toc89' href='#sect89'>Import and Remove Documents</a></li> +<li><a name='toc90' href='#sect90'>Introduction</a></li> +<li><a name='toc91' href='#sect91'>Search - Database Frontend Sample, Utilising Database and Sisu Features,</a></li> +<li><a name='toc92' href='#sect92'>Search Form</a></li> +<li><a name='toc93' href='#sect93'>Sisu_webrick</a></li> +<li><a name='toc94' href='#sect94'>Name</a></li> +<li><a name='toc95' href='#sect95'>Synopsis</a></li> +<li><a name='toc96' href='#sect96'>Description</a></li> +<li><a name='toc97' href='#sect97'>Summary of Man Page</a></li> +<li><a name='toc98' href='#sect98'>Document Processing Command Flags</a></li> +<li><a name='toc99' href='#sect99'>Summary of Features</a></li> +<li><a name='toc100' href='#sect100'>See Also</a></li> +<li><a name='toc101' href='#sect101'>Homepage</a></li> +<li><a name='toc102' href='#sect102'>Source</a></li> +<li><a name='toc103' href='#sect103'>Author</a></li> +</ul> +</body> +</html> diff --git a/data/doc/sisu/markup-samples/README b/data/doc/sisu/markup-samples/README index ac71cc50..5e7b6944 100644 --- a/data/doc/sisu/markup-samples/README +++ b/data/doc/sisu/markup-samples/README @@ -1,5 +1,6 @@ The package sisu contains a few documents published under the GPL or that are -Debian Free Software Guideline license compatible, noteably: +Debian Free Software Guideline license compatible, in the v4 and legacy v3 +directories below, notably: Text: Free as in Freedom - Richard Stallman's Crusade for Free Software URL: <http://faifzilla.org/> @@ -152,6 +153,11 @@ remain unchanged, and sometimes that the works be used only non-commercially. License: Attribution-Noncommercial-Share Alike (CC-BY-NC-SA) 3.0 URL: <http://creativecommons.org/licenses/by-nc-sa/3.0/> Markup: little_brother.cory_doctorow.sst + Cover: cover_image_wordle_little_brother.png + URL: <http://craphound.com/littlebrother/2009/09/09/cool-free-cover-image-for-little-brother-from-wordle/> + Copyright: Wordle, Cory Doctorow, 2011 + License: Attribution United States (CC BY) 3.0 + URL: <http://creativecommons.org/licenses/by/3.0/us/> Illustration: little_brother_doctorow.png URL: <http://commons.wikimedia.org/wiki/File:Little_Brother_illustration_by_Richard_Wilkinson_04.jpg> Copyright: Richard Wilkinson diff --git a/data/doc/sisu/markup-samples/v3/samples/free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst b/data/doc/sisu/markup-samples/v3/samples/free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst index d19efafa..16de9266 100644 --- a/data/doc/sisu/markup-samples/v3/samples/free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst +++ b/data/doc/sisu/markup-samples/v3/samples/free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst @@ -14,21 +14,21 @@ :license: Published under the GNU Free Documentation License. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Document License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being no invariant sections, with the Front-Cover Texts being no invariant sections, and with the Back-Cover Texts being no invariant sections. A copy of the license is included in Appendix C, GNU Free Documentation License. All images are to be included verbatim when the document is copied, distributed, or modified under the terms of the GFDL. @classify: - :topic_register: SiSU:markup sample:book;copyright;GNU/Linux:GPL|copyleft|free software;free software;Software:Software Libré;GPL;Linux:GNU|Software Libré;book:biography;programming + :topic_register: SiSU markup sample:book:biography;book:biography;copyright;GNU/Linux:GPL|copyleft|free software;free software;Software:Software Libré;GPL;Linux:GNU|Software Libré;programming :oclc: 49044520 :isbn: 9780596002879 @links: - {Home and Source}http://faifzilla.org/ - {@ Wikipedia}http://en.wikipedia.org/wiki/Free_as_in_Freedom:_Richard_Stallman%27s_Crusade_for_Free_Software - {@ Amazon.com}http://www.amazon.com/gp/product/0596002874 - {@ Barnes & Noble}http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?isbn=0596002874 - {SiSU}http://sisudoc.org/ - {sources / git}http://sources.sisudoc.org/ + { Home and Source }http://faifzilla.org/ + { @ Wikipedia }http://en.wikipedia.org/wiki/Free_as_in_Freedom:_Richard_Stallman%27s_Crusade_for_Free_Software + { @ Amazon.com }http://www.amazon.com/gp/product/0596002874 + { @ Barnes & Noble }http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?isbn=0596002874 + { SiSU }http://sisudoc.org/ + { sources / git }http://sources.sisudoc.org/ @make: - :skin: skin_rms :breaks: new=:A,:B,:C,1 + :skin: skin_rms :A~ @title @author @@ -223,7 +223,7 @@ Once inside the auditorium, a visitor finds the person who has forced this tempo % extended range for Microsoft -The subject of Stallman's speech is the history and future of the free software movement. The location is significant. Less than a month before, Microsoft senior vice president Craig Mundie appeared at the nearby NYU Stern School of Business, delivering a speech blasting the General Public License, or GPL, a legal device originally conceived by Stallman 16 years before. Built to counteract the growing wave of software secrecy overtaking the computer industry-a wave first noticed by Stallman during his 1980 troubles with the Xerox laser printer-the GPL has evolved into a central tool of the free software community. In simplest terms, the GPL locks software programs into a form of communal ownership-what today's legal scholars now call the "digital commons"-through the legal weight of copyright. Once locked, programs remain unremovable. Derivative versions must carry the same copyright protection-even derivative versions that bear only a small snippet of the original source code. For this reason, some within the software industry have taken to calling the GPL a "viral" license, because it spreads itself to every software program it touches.~{ Actually, the GPL's powers are not quite that potent. According to section 10 of the GNU General Public License, Version 2 (1991), the viral nature of the license depends heavily on the Free Software Foundation's willingness to view a program as a derivative work, not to mention the existing license the GPL would replace.<br>If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software that is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.<br>"To compare something to a virus is very harsh," says Stallman. "A spider plant is a more accurate comparison; it goes to another place if you actively take a cutting."<br>For more information on the GNU General Public License, visit http://www.gnu.org/copyleft/gpl.html }~ +The subject of Stallman's speech is the history and future of the free software movement. The location is significant. Less than a month before, Microsoft senior vice president Craig Mundie appeared at the nearby NYU Stern School of Business, delivering a speech blasting the General Public License, or GPL, a legal device originally conceived by Stallman 16 years before. Built to counteract the growing wave of software secrecy overtaking the computer industry-a wave first noticed by Stallman during his 1980 troubles with the Xerox laser printer-the GPL has evolved into a central tool of the free software community. In simplest terms, the GPL locks software programs into a form of communal ownership-what today's legal scholars now call the "digital commons"-through the legal weight of copyright. Once locked, programs remain unremovable. Derivative versions must carry the same copyright protection-even derivative versions that bear only a small snippet of the original source code. For this reason, some within the software industry have taken to calling the GPL a "viral" license, because it spreads itself to every software program it touches.~{ Actually, the GPL's powers are not quite that potent. According to section 10 of the GNU General Public License, Version 2 (1991), the viral nature of the license depends heavily on the Free Software Foundation's willingness to view a program as a derivative work, not to mention the existing license the GPL would replace. \\ If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software that is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. \\ "To compare something to a virus is very harsh," says Stallman. "A spider plant is a more accurate comparison; it goes to another place if you actively take a cutting." \\ For more information on the GNU General Public License, visit http://www.gnu.org/copyleft/gpl.html }~ ={Mundie, Craig+2;NYU Stern School of Business;Stern School of Business (NYU)} In an information economy increasingly dependent on software and increasingly beholden to software standards, the GPL has become the proverbial "big stick." Even companies that once laughed it off as software socialism have come around to recognize the benefits. Linux, the Unix-like kernel developed by Finnish college student Linus Torvalds in 1991, is licensed under the GPL, as are many of the world's most popular programming tools: GNU Emacs, the GNU Debugger, the GNU C Compiler, etc. Together, these tools form the components of a free software operating system developed, nurtured, and owned by the worldwide hacker community. Instead of viewing this community as a threat, high-tech companies like IBM, Hewlett Packard, and Sun Microsystems have come to rely upon it, selling software applications and services built to ride atop the ever-growing free software infrastructure. @@ -235,12 +235,12 @@ They've also come to rely upon it as a strategic weapon in the hacker community' 20 years is a long time in the software industry. Consider this: in 1980, when Richard Stallman was cursing the AI Lab's Xerox laser printer, Microsoft, the company modern hackers view as the most powerful force in the worldwide software industry, was still a privately held startup. IBM, the company hackers used to regard as the most powerful force in the worldwide software industry, had yet to to introduce its first personal computer, thereby igniting the current low-cost PC market. Many of the technologies we now take for granted-the World Wide Web, satellite television, 32-bit video-game consoles-didn't even exist. The same goes for many of the companies that now fill the upper echelons of the corporate establishment, companies like AOL, Sun Microsystems, Amazon.com, Compaq, and Dell. The list goes on and on. ={Amazon.com;AOL (America OnLine);Compaq computers;Dell computers;PCs (personal computers);personal computers (PCs)} -The fact that the high-technology marketplace has come so far in such little time is fuel for both sides of the GPL debate. GPL-proponents point to the short lifespan of most computer hardware platforms. Facing the risk of buying an obsolete product, consumers tend to flock to companies with the best long-term survival. As a result, the software marketplace has become a winner-take-all arena.~{ See Shubha Ghosh, "Revealing the Microsoft Windows Source Code," Gigalaw.com (January, 2000).<br> http://www.gigalaw.com/articles/ghosh-2000-01-p1.html }~ The current, privately owned software environment, GPL-proponents say, leads to monopoly abuse and stagnation. Strong companies suck all the oxygen out of the marketplace for rival competitors and innovative startups. +The fact that the high-technology marketplace has come so far in such little time is fuel for both sides of the GPL debate. GPL-proponents point to the short lifespan of most computer hardware platforms. Facing the risk of buying an obsolete product, consumers tend to flock to companies with the best long-term survival. As a result, the software marketplace has become a winner-take-all arena.~{ See Shubha Ghosh, "Revealing the Microsoft Windows Source Code," Gigalaw.com (January, 2000). \\ http://www.gigalaw.com/articles/ghosh-2000-01-p1.html }~ The current, privately owned software environment, GPL-proponents say, leads to monopoly abuse and stagnation. Strong companies suck all the oxygen out of the marketplace for rival competitors and innovative startups. -GPL-opponents argue just the opposite. Selling software is just as risky, if not more risky, than buying software, they say. Without the legal guarantees provided by private software licenses, not to mention the economic prospects of a privately owned "killer app" (i.e., a breakthrough technology that launches an entirely new market),~{ Killer apps don't have to be proprietary. Witness, of course, the legendary Mosaic browser, a program whose copyright permits noncommercial derivatives with certain restrictions. Still, I think the reader gets the point: the software marketplace is like the lottery. The bigger the potential payoff, the more people want to participate. For a good summary of the killer-app phenomenon, see Philip Ben-David, "Whatever Happened to the `Killer App'?" e-Commerce News (December 7, 2000).<br> http://www.ecommercetimes.com/perl/story/5893.html }~ companies lose the incentive to participate. Once again, the market stagnates and innovation declines. As Mundie himself noted in his May 3 address on the same campus, the GPL's "viral" nature "poses a threat" to any company that relies on the uniqueness of its software as a competitive asset. Added Mundie: +GPL-opponents argue just the opposite. Selling software is just as risky, if not more risky, than buying software, they say. Without the legal guarantees provided by private software licenses, not to mention the economic prospects of a privately owned "killer app" (i.e., a breakthrough technology that launches an entirely new market),~{ Killer apps don't have to be proprietary. Witness, of course, the legendary Mosaic browser, a program whose copyright permits noncommercial derivatives with certain restrictions. Still, I think the reader gets the point: the software marketplace is like the lottery. The bigger the potential payoff, the more people want to participate. For a good summary of the killer-app phenomenon, see Philip Ben-David, "Whatever Happened to the `Killer App'?" e-Commerce News (December 7, 2000). \\ http://www.ecommercetimes.com/perl/story/5893.html }~ companies lose the incentive to participate. Once again, the market stagnates and innovation declines. As Mundie himself noted in his May 3 address on the same campus, the GPL's "viral" nature "poses a threat" to any company that relies on the uniqueness of its software as a competitive asset. Added Mundie: ={Mundie, Craig+2} -_1 It also fundamentally undermines the independent commercial software sector because it effectively makes it impossible to distribute software on a basis where recipients pay for the product rather than just the cost of distribution.~{ See Craig Mundie, "The Commercial Software Model," senior vice president, Microsoft Corp. Excerpted from an online transcript of Mundie's May 3, 2001, speech to the New York University Stern School of Business.<br> http://www.microsoft.com/presspass/exec/craig/05-03sharedsource.asp }~ +_1 It also fundamentally undermines the independent commercial software sector because it effectively makes it impossible to distribute software on a basis where recipients pay for the product rather than just the cost of distribution.~{ See Craig Mundie, "The Commercial Software Model," senior vice president, Microsoft Corp. Excerpted from an online transcript of Mundie's May 3, 2001, speech to the New York University Stern School of Business. \\ http://www.microsoft.com/presspass/exec/craig/05-03sharedsource.asp }~ The mutual success of GNU/Linux, the amalgamated operating system built around the GPL-protected Linux kernel, and Windows over the last 10 years reveals the wisdom of both perspectives. Nevertheless, the battle for momentum is an important one in the software industry. Even powerful vendors such as Microsoft rely on the support of third-party software developers whose tools, programs, and computer games make an underlying software platform such as Windows more attractive to the mainstream consumer. Citing the rapid evolution of the technology marketplace over the last 20 years, not to mention his own company's admirable track record during that period, Mundie advised listeners to not get too carried away by the free software movement's recent momentum: ={GNU Project:Linux and, mutual success of;Linux:GNU Project and;third-party software developers supporting Microsoft} @@ -299,7 +299,7 @@ Richard Matthew Stallman's rise from frustrated academic to political leader ove Most importantly, it speaks to the changing nature of political power in a world increasingly beholden to computer technology and the software programs that power that technology. -Maybe that's why, even at a time when most high-technology stars are on the wane, Stallman's star has grown. Since launching the GNU Project in 1984,~{ The acronym GNU stands for "GNU's not Unix." In another portion of the May 29, 2001, NYU speech, Stallman summed up the acronym's origin:<br>_1 We hackers always look for a funny or naughty name for a program, because naming a program is half the fun of writing the program. We also had a tradition of recursive acronyms, to say that the program that you're writing is similar to some existing program . . . I looked for a recursive acronym for Something Is Not UNIX. And I tried all 26 letters and discovered that none of them was a word. I decided to make it a contraction. That way I could have a three-letter acronym, for Something's Not UNIX. And I tried letters, and I came across the word "GNU." That was it.<br>_1 Although a fan of puns, Stallman recommends that software users pronounce the "g" at the beginning of the acronym (i.e., "gah-new"). Not only does this avoid confusion with the word "gnu," the name of the African antelope, Connochaetes gnou, it also avoids confusion with the adjective "new." "We've been working on it for 17 years now, so it is not exactly new any more," Stallman says.<br>Source: author notes and online transcript of "Free Software: Freedom and Cooperation," Richard Stallman's May 29, 2001, speech at New York University.<br> http://www.gnu.org/events/rms-nyu-2001-transcript.txt }~ Stallman has been at turns ignored, satirized, vilified, and attacked-both from within and without the free software movement. Through it all, the GNU Project has managed to meet its milestones, albeit with a few notorious delays, and stay relevant in a software marketplace several orders of magnitude more complex than the one it entered 18 years ago. So too has the free software ideology, an ideology meticulously groomed by Stallman himself. +Maybe that's why, even at a time when most high-technology stars are on the wane, Stallman's star has grown. Since launching the GNU Project in 1984,~{ The acronym GNU stands for "GNU's not Unix." In another portion of the May 29, 2001, NYU speech, Stallman summed up the acronym's origin: \\ _1 We hackers always look for a funny or naughty name for a program, because naming a program is half the fun of writing the program. We also had a tradition of recursive acronyms, to say that the program that you're writing is similar to some existing program . . . I looked for a recursive acronym for Something Is Not UNIX. And I tried all 26 letters and discovered that none of them was a word. I decided to make it a contraction. That way I could have a three-letter acronym, for Something's Not UNIX. And I tried letters, and I came across the word "GNU." That was it. \\ _1 Although a fan of puns, Stallman recommends that software users pronounce the "g" at the beginning of the acronym (i.e., "gah-new"). Not only does this avoid confusion with the word "gnu," the name of the African antelope, Connochaetes gnou, it also avoids confusion with the adjective "new." "We've been working on it for 17 years now, so it is not exactly new any more," Stallman says. \\ Source: author notes and online transcript of "Free Software: Freedom and Cooperation," Richard Stallman's May 29, 2001, speech at New York University. \\ http://www.gnu.org/events/rms-nyu-2001-transcript.txt }~ Stallman has been at turns ignored, satirized, vilified, and attacked-both from within and without the free software movement. Through it all, the GNU Project has managed to meet its milestones, albeit with a few notorious delays, and stay relevant in a software marketplace several orders of magnitude more complex than the one it entered 18 years ago. So too has the free software ideology, an ideology meticulously groomed by Stallman himself. To understand the reasons behind this currency, it helps to examine Richard Stallman both in his own words and in the words of the people who have collaborated and battled with him along the way. The Richard Stallman character sketch is not a complicated one. If any person exemplifies the old adage "what you see is what you get," it's Stallman. @@ -339,7 +339,7 @@ Thirty years after the fact, Lippman punctuates the memory with a laugh. "To tel Seated at the dining-room table of her second Manhattan apartment-the same spacious three-bedroom complex she and her son moved to following her 1967 marriage to Maurice Lippman, now deceased-Alice Lippman exudes a Jewish mother's mixture of pride and bemusement when recalling her son's early years. The nearby dining-room credenza offers an eight-by-ten photo of Stallman glowering in full beard and doctoral robes. The image dwarfs accompanying photos of Lippman's nieces and nephews, but before a visitor can make too much of it, Lippman makes sure to balance its prominent placement with an ironic wisecrack. ={Lippman, Maurice} -"Richard insisted I have it after he received his honorary doctorate at the University of Glasgow," says Lippman. "He said to me, `Guess what, mom? It's the first graduation I ever attended.'"~{ See Michael Gross, "Richard Stallman: High School Misfit, Symbol of Free Software, MacArthur-certified Genius" (1999). This interview is one of the most candid Stallman interviews on the record. I recommend it highly.<br> http://www.mgross.com/interviews/stallman1.html }~ +"Richard insisted I have it after he received his honorary doctorate at the University of Glasgow," says Lippman. "He said to me, `Guess what, mom? It's the first graduation I ever attended.'"~{ See Michael Gross, "Richard Stallman: High School Misfit, Symbol of Free Software, MacArthur-certified Genius" (1999). This interview is one of the most candid Stallman interviews on the record. I recommend it highly. \\ http://www.mgross.com/interviews/stallman1.html }~ ={University of Glasgow} Such comments reflect the sense of humor that comes with raising a child prodigy. Make no mistake, for every story Lippman hears and reads about her son's stubbornness and unusual behavior, she can deliver at least a dozen in return. @@ -382,10 +382,10 @@ Seth Breidbart, a fellow Columbia Science Honors Program alumnus, offers bolster "It's hard to describe," Breidbart says. "It wasn't like he was unapproachable. He was just very intense. [He was] very knowledgeable but also very hardheaded in some ways." -Such descriptions give rise to speculation: are judgment-laden adjectives like "intense" and "hardheaded" simply a way to describe traits that today might be categorized under juvenile behavioral disorder? A December, 2001, /{Wired}/ magazine article titled "The Geek Syndrome" paints the portrait of several scientifically gifted children diagnosed with high-functioning autism or Asperger Syndrome. In many ways, the parental recollections recorded in the Wired article are eerily similar to the ones offered by Lippman. Even Stallman has indulged in psychiatric revisionism from time to time. During a 2000 profile for the /{Toronto Star}/, Stallman described himself to an interviewer as "borderline autistic,"~{ See Judy Steed, /{Toronto Star}/, BUSINESS, (October 9, 2000): C03.<br>His vision of free software and social cooperation stands in stark contrast to the isolated nature of his private life. A Glenn Gould-like eccentric, the Canadian pianist was similarly brilliant, articulate, and lonely. Stallman considers himself afflicted, to some degree, by autism: a condition that, he says, makes it difficult for him to interact with people. }~ a description that goes a long way toward explaining a lifelong tendency toward social and emotional isolation and the equally lifelong effort to overcome it. +Such descriptions give rise to speculation: are judgment-laden adjectives like "intense" and "hardheaded" simply a way to describe traits that today might be categorized under juvenile behavioral disorder? A December, 2001, /{Wired}/ magazine article titled "The Geek Syndrome" paints the portrait of several scientifically gifted children diagnosed with high-functioning autism or Asperger Syndrome. In many ways, the parental recollections recorded in the Wired article are eerily similar to the ones offered by Lippman. Even Stallman has indulged in psychiatric revisionism from time to time. During a 2000 profile for the /{Toronto Star}/, Stallman described himself to an interviewer as "borderline autistic,"~{ See Judy Steed, /{Toronto Star}/, BUSINESS, (October 9, 2000): C03. \\ His vision of free software and social cooperation stands in stark contrast to the isolated nature of his private life. A Glenn Gould-like eccentric, the Canadian pianist was similarly brilliant, articulate, and lonely. Stallman considers himself afflicted, to some degree, by autism: a condition that, he says, makes it difficult for him to interact with people. }~ a description that goes a long way toward explaining a lifelong tendency toward social and emotional isolation and the equally lifelong effort to overcome it. ={Asperger Syndrome+1;autism+5;Geek Syndrome, The (Silberman)+1;Wired magazine;Toronto Star;Silberman, Steve+1;Stallman, Richard M.:behavioral disorders+1} -Such speculation benefits from the fast and loose nature of most so-called "behavioral disorders" nowadays, of course. As Steve Silberman, author of "The Geek Syndrome," notes, American psychiatrists have only recently come to accept Asperger Syndrome as a valid umbrella term covering a wide set of behavioral traits. The traits range from poor motor skills and poor socialization to high intelligence and an almost obsessive affinity for numbers, computers, and ordered systems.~{ See Steve Silberman, "The Geek Syndrome," Wired (December, 2001).<br> http://www.wired.com/wired/archive/9.12/aspergers_pr.html }~ Reflecting on the broad nature of this umbrella, Stallman says its possible that, if born 40 years later, he might have merited just such a diagnosis. Then again, so would many of his computer-world colleagues. +Such speculation benefits from the fast and loose nature of most so-called "behavioral disorders" nowadays, of course. As Steve Silberman, author of "The Geek Syndrome," notes, American psychiatrists have only recently come to accept Asperger Syndrome as a valid umbrella term covering a wide set of behavioral traits. The traits range from poor motor skills and poor socialization to high intelligence and an almost obsessive affinity for numbers, computers, and ordered systems.~{ See Steve Silberman, "The Geek Syndrome," Wired (December, 2001). \\ http://www.wired.com/wired/archive/9.12/aspergers_pr.html }~ Reflecting on the broad nature of this umbrella, Stallman says its possible that, if born 40 years later, he might have merited just such a diagnosis. Then again, so would many of his computer-world colleagues. ={Stallman, Richard M.:childhood, behavioral disorders} "It's possible I could have had something like that," he says. "On the other hand, one of the aspects of that syndrome is difficulty following rhythms. I can dance. In fact, I love following the most complicated rhythms. It's not clear cut enough to know." @@ -589,7 +589,7 @@ Looking back, Stallman sees nothing unusual in the AI Lab's willingness to accep To get a taste of "bureaucratic and stuffy," Stallman need only visit the computer labs at Harvard. There, access to the terminals was doled out according to academic rank. As an undergrad, Stallman usually had to sign up or wait until midnight, about the time most professors and grad students finished their daily work assignments. The waiting wasn't difficult, but it was frustrating. Waiting for a public terminal, knowing all the while that a half dozen equally usable machines were sitting idle inside professors' locked offices, seemed the height of illogic. Although Stallman paid the occasional visit to the Harvard computer labs, he preferred the more egalitarian policies of the AI Lab. "It was a breath of fresh air," he says. "At the AI Lab, people seemed more concerned about work than status." ={Harvard University:computer labs} -Stallman quickly learned that the AI Lab's first-come, first-served policy owed much to the efforts of a vigilant few. Many were holdovers from the days of Project MAC, the Department of Defense-funded research program that had given birth to the first time-share operating systems. A few were already legends in the computing world. There was Richard Greenblatt, the lab's in-house Lisp expert and author of MacHack, the computer chess program that had once humbled A.I. critic Hubert Dreyfus. There was Gerald Sussman, original author of the robotic block-stacking program HACKER. And there was Bill Gosper, the in-house math whiz already in the midst of an 18-month hacking bender triggered by the philosophical implications of the computer game LIFE.~{ See Steven Levy, Hackers (Penguin USA [paperback], 1984): 144.<br>Levy devotes about five pages to describing Gosper's fascination with LIFE, a math-based software game first created by British mathematician John Conway. I heartily recommend this book as a supplement, perhaps even a prerequisite, to this one. }~ +Stallman quickly learned that the AI Lab's first-come, first-served policy owed much to the efforts of a vigilant few. Many were holdovers from the days of Project MAC, the Department of Defense-funded research program that had given birth to the first time-share operating systems. A few were already legends in the computing world. There was Richard Greenblatt, the lab's in-house Lisp expert and author of MacHack, the computer chess program that had once humbled A.I. critic Hubert Dreyfus. There was Gerald Sussman, original author of the robotic block-stacking program HACKER. And there was Bill Gosper, the in-house math whiz already in the midst of an 18-month hacking bender triggered by the philosophical implications of the computer game LIFE.~{ See Steven Levy, Hackers (Penguin USA [paperback], 1984): 144. \\ Levy devotes about five pages to describing Gosper's fascination with LIFE, a math-based software game first created by British mathematician John Conway. I heartily recommend this book as a supplement, perhaps even a prerequisite, to this one. }~ ={Dreyfus, Hubert;Gosper, Bill;Greenblat, Richard;LIFE mathematical game;LISP programming language;MacHack;Project MAC;Sussman, Gerald+2} Members of the tight-knit group called themselves "hackers." Over time, they extended the "hacker" description to Stallman as well. In the process of doing so, they inculcated Stallman in the ethical traditions of the "hacker ethic ." To be a hacker meant more than just writing programs, Stallman learned. It meant writing the best possible programs. It meant sitting at a terminal for 36 hours straight if that's what it took to write the best possible programs. Most importantly, it meant having access to the best possible machines and the most useful information at all times. Hackers spoke openly about changing the world through software, and Stallman learned the instinctual hacker disdain for any obstacle that prevented a hacker from fulfilling this noble cause. Chief among these obstacles were poor software, academic bureaucracy, and selfish behavior. @@ -615,7 +615,7 @@ Using this feature, Stallman was able to watch how programs written by hackers p By the end of 1970, hacking at the AI Lab had become a regular part of Stallman's weekly schedule. From Monday to Thursday, Stallman devoted his waking hours to his Harvard classes. As soon as Friday afternoon arrived, however, he was on the T, heading down to MIT for the weekend. Stallman usually timed his arrival to coincide with the ritual food run. Joining five or six other hackers in their nightly quest for Chinese food, he would jump inside a beat-up car and head across the Harvard Bridge into nearby Boston. For the next two hours, he and his hacker colleagues would discuss everything from ITS to the internal logic of the Chinese language and pictograph system. Following dinner, the group would return to MIT and hack code until dawn. -For the geeky outcast who rarely associated with his high-school peers, it was a heady experience, suddenly hanging out with people who shared the same predilection for computers, science fiction, and Chinese food. "I remember many sunrises seen from a car coming back from Chinatown," Stallman would recall nostalgically, 15 years after the fact in a speech at the Swedish Royal Technical Institute. "It was actually a very beautiful thing to see a sunrise, 'cause that's such a calm time of day. It's a wonderful time of day to get ready to go to bed. It's so nice to walk home with the light just brightening and the birds starting to chirp; you can get a real feeling of gentle satisfaction, of tranquility about the work that you have done that night."~{ See Richard Stallman, "RMS lecture at KTH (Sweden)," (October 30, 1986).<br> http://www.gnu.org/philosophy/stallman-kth.html }~ +For the geeky outcast who rarely associated with his high-school peers, it was a heady experience, suddenly hanging out with people who shared the same predilection for computers, science fiction, and Chinese food. "I remember many sunrises seen from a car coming back from Chinatown," Stallman would recall nostalgically, 15 years after the fact in a speech at the Swedish Royal Technical Institute. "It was actually a very beautiful thing to see a sunrise, 'cause that's such a calm time of day. It's a wonderful time of day to get ready to go to bed. It's so nice to walk home with the light just brightening and the birds starting to chirp; you can get a real feeling of gentle satisfaction, of tranquility about the work that you have done that night."~{ See Richard Stallman, "RMS lecture at KTH (Sweden)," (October 30, 1986). \\ http://www.gnu.org/philosophy/stallman-kth.html }~ ={Swedish Royal Technical Institute} The more Stallman hung out with the hackers, the more he adopted the hacker worldview. Already committed to the notion of personal liberty, Stallman began to infuse his actions with a sense of communal responsibility. When others violated the communal code, Stallman was quick to speak out. Within a year of his first visit, Stallman was the one breaking into locked offices, trying to recover the sequestered terminals that belonged to the lab community as a whole. In true hacker fashion, Stallman also sought to make his own personal contribution to the art of lock hacking. One of the most artful door-opening tricks, commonly attributed to Greenblatt, involved bending a stiff wire into a cane and attaching a loop of tape to the long end. Sliding the wire under the door, a hacker could twist and rotate the wire so that the long end touched the door knob. Provided the adhesive on the tape held, a hacker could open the doorknob with a few sharp twists. @@ -685,7 +685,7 @@ Ask anyone who's spent more than a minute in Richard Stallman's presence, and yo To call the Stallman gaze intense is an understatement. Stallman's eyes don't just look at you; they look through you. Even when your own eyes momentarily shift away out of simple primate politeness, Stallman's eyes remain locked-in, sizzling away at the side of your head like twin photon beams. -Maybe that's why most writers, when describing Stallman, tend to go for the religious angle. In a 1998 Salon.com article titled "The Saint of Free Software," Andrew Leonard describes Stallman's green eyes as "radiating the power of an Old Testament prophet."~{ See Andrew Leonard, "The Saint of Free Software," Salon.com (August 1998).<br> http://www.salon.com/21st/feature/1998/08/cov_31feature.html }~ A 1999 /{Wired}/ magazine article describes the Stallman beard as "Rasputin-like,"~{ See Leander Kahney, "Linux's Forgotten Man," Wired News (March 5, 1999).<br> http://www.wired.com/news/print/0,1294,18291,00.html }~ while a /{London Guardian}/ profile describes the Stallman smile as the smile of "a disciple seeing Jesus."~{ See "Programmer on moral high ground; Free software is a moral issue for Richard Stallman believes in freedom and free software." London Guardian (November 6, 1999).<br>These are just a small sampling of the religious comparisons. To date, the most extreme comparison has to go to Linus Torvalds, who, in his autobiography-see Linus Torvalds and David Diamond, Just For Fun: The Story of an Accidentaly Revolutionary (HarperCollins Publishers, Inc., 2001): 58-writes "Richard Stallman is the God of Free Software."<br>Honorable mention goes to Larry Lessig, who, in a footnote description of Stallman in his book-see Larry Lessig, The Future of Ideas (Random House, 2001): 270-likens Stallman to Moses:<br>_1 ... as with Moses, it was another leader, Linus Torvalds, who finally carried the movement into the promised land by facilitating the development of the final part of the OS puzzle. Like Moses, too, Stallman is both respected and reviled by allies within the movement. He is [an] unforgiving, and hence for many inspiring, leader of a critically important aspect of modern culture. I have deep respect for the principle and commitment of this extraordinary individual, though I also have great respect for those who are courageous enough to question his thinking and then sustain his wrath.<br>In a final interview with Stallman, I asked him his thoughts about the religious comparisons. "Some people do compare me with an Old Testament prophent, and the reason is Old Testament prophets said certain social practices were wrong. They wouldn't compromise on moral issues. They couldn't be bought off, and they were usually treated with contempt." }~ +Maybe that's why most writers, when describing Stallman, tend to go for the religious angle. In a 1998 Salon.com article titled "The Saint of Free Software," Andrew Leonard describes Stallman's green eyes as "radiating the power of an Old Testament prophet."~{ See Andrew Leonard, "The Saint of Free Software," Salon.com (August 1998). \\ http://www.salon.com/21st/feature/1998/08/cov_31feature.html }~ A 1999 /{Wired}/ magazine article describes the Stallman beard as "Rasputin-like,"~{ See Leander Kahney, "Linux's Forgotten Man," Wired News (March 5, 1999). \\ http://www.wired.com/news/print/0,1294,18291,00.html }~ while a /{London Guardian}/ profile describes the Stallman smile as the smile of "a disciple seeing Jesus."~{ See "Programmer on moral high ground; Free software is a moral issue for Richard Stallman believes in freedom and free software." London Guardian (November 6, 1999). \\ These are just a small sampling of the religious comparisons. To date, the most extreme comparison has to go to Linus Torvalds, who, in his autobiography-see Linus Torvalds and David Diamond, Just For Fun: The Story of an Accidentaly Revolutionary (HarperCollins Publishers, Inc., 2001): 58-writes "Richard Stallman is the God of Free Software." \\ Honorable mention goes to Larry Lessig, who, in a footnote description of Stallman in his book-see Larry Lessig, The Future of Ideas (Random House, 2001): 270-likens Stallman to Moses: \\ _1 ... as with Moses, it was another leader, Linus Torvalds, who finally carried the movement into the promised land by facilitating the development of the final part of the OS puzzle. Like Moses, too, Stallman is both respected and reviled by allies within the movement. He is [an] unforgiving, and hence for many inspiring, leader of a critically important aspect of modern culture. I have deep respect for the principle and commitment of this extraordinary individual, though I also have great respect for those who are courageous enough to question his thinking and then sustain his wrath. \\ In a final interview with Stallman, I asked him his thoughts about the religious comparisons. "Some people do compare me with an Old Testament prophent, and the reason is Old Testament prophets said certain social practices were wrong. They wouldn't compromise on moral issues. They couldn't be bought off, and they were usually treated with contempt." }~ ={Wired magazine;Leonard, Andrew;London Guardian;Salon.com} Such analogies serve a purpose, but they ultimately fall short. That's because they fail to take into account the vulnerable side of the Stallman persona. Watch the Stallman gaze for an extended period of time, and you will begin to notice a subtle change. What appears at first to be an attempt to intimidate or hypnotize reveals itself upon second and third viewing as a frustrated attempt to build and maintain contact. If, as Stallman himself has suspected from time to time, his personality is the product of autism or Asperger Syndrome, his eyes certainly confirm the diagnosis. Even at their most high-beam level of intensity, they have a tendency to grow cloudy and distant, like the eyes of a wounded animal preparing to give up the ghost. @@ -747,7 +747,7 @@ Stallman's body bears witness to the tragedy. Lack of exercise has left Stallman The walk is further slowed by Stallman's willingness to stop and smell the roses, literally. Spotting a particularly beautiful blossom, he tickles the innermost petals with his prodigious nose, takes a deep sniff and steps back with a contented sigh. -"Mmm, rhinophytophilia,"~{ At the time, I thought Stallman was referring to the flower's scientific name. Months later, I would learn that rhinophytophilia was in fact a humorous reference to the activity, i.e., Stallman sticking his nose into a flower and enjoying the moment. For another humorous Stallman flower incident, visit:<br> http://www.stallman.org/texas.html }~ he says, rubbing his back. +"Mmm, rhinophytophilia,"~{ At the time, I thought Stallman was referring to the flower's scientific name. Months later, I would learn that rhinophytophilia was in fact a humorous reference to the activity, i.e., Stallman sticking his nose into a flower and enjoying the moment. For another humorous Stallman flower incident, visit: \\ http://www.stallman.org/texas.html }~ he says, rubbing his back. The drive to the restaurant takes less than three minutes. Upon recommendation from Tim Ney, former executive director of the Free Software Foundation, I have let Stallman choose the restaurant. While some reporters zero in on Stallman's monk-like lifestyle, the truth is, Stallman is a committed epicure when it comes to food. One of the fringe benefits of being a traveling missionary for the free software cause is the ability to sample delicious food from around the world. "Visit almost any major city in the world, and chances are Richard knows the best restaurant in town," says Ney. "Richard also takes great pride in knowing what's on the menu and ordering for the entire table." ={Ney, Tim} @@ -772,7 +772,7 @@ The conversation shifts to Napster, the San Mateo, California software company, Although based on proprietary software, the Napster system draws inspiration from the long-held Stallman contention that once a work enters the digital realm-in other words, once making a copy is less a matter of duplicating sounds or duplicating atoms and more a matter of duplicating information-the natural human impulse to share a work becomes harder to restrict. Rather than impose additional restrictions, Napster execs have decided to take advantage of the impulse. Giving music listeners a central place to trade music files, the company has gambled on its ability to steer the resulting user traffic toward other commercial opportunities. -The sudden success of the Napster model has put the fear in traditional record companies, with good reason. Just days before my Palo Alto meeting with Stallman, U.S. District Court Judge Marilyn Patel granted a request filed by the Recording Industry Association of America for an injunction against the file-sharing service. The injunction was subsequently suspended by the U.S. Ninth District Court of Appeals, but by early 2001, the Court of Appeals, too, would find the San Mateo-based company in breach of copyright law,~{ See Cecily Barnes and Scott Ard, "Court Grants Stay of Napster Injunction," News.com (July 28, 2000).<br> http://news.cnet.com/news/0-1005-200-2376465.html }~ a decision RIAA spokesperson Hillary Rosen would later proclaim proclaim a "clear victory for the creative content community and the legitimate online marketplace."~{ See "A Clear Victory for Recording Industry in Napster Case," RIAA press release (February 12, 2001).<br> http://www.riaa.com/PR_story.cfm?id=372 }~ +The sudden success of the Napster model has put the fear in traditional record companies, with good reason. Just days before my Palo Alto meeting with Stallman, U.S. District Court Judge Marilyn Patel granted a request filed by the Recording Industry Association of America for an injunction against the file-sharing service. The injunction was subsequently suspended by the U.S. Ninth District Court of Appeals, but by early 2001, the Court of Appeals, too, would find the San Mateo-based company in breach of copyright law,~{ See Cecily Barnes and Scott Ard, "Court Grants Stay of Napster Injunction," News.com (July 28, 2000). \\ http://news.cnet.com/news/0-1005-200-2376465.html }~ a decision RIAA spokesperson Hillary Rosen would later proclaim proclaim a "clear victory for the creative content community and the legitimate online marketplace."~{ See "A Clear Victory for Recording Industry in Napster Case," RIAA press release (February 12, 2001). \\ http://www.riaa.com/PR_story.cfm?id=372 }~ For hackers such as Stallman, the Napster business model is scary in different ways. The company's eagerness to appropriate time-worn hacker principles such as file sharing and communal information ownership, while at the same time selling a service based on proprietary software, sends a distressing mixed message. As a person who already has a hard enough time getting his own carefully articulated message into the media stream, Stallman is understandably reticent when it comes to speaking out about the company. Still, Stallman does admit to learning a thing or two from the social side of the Napster phenomenon. @@ -795,7 +795,7 @@ I turn to look, catching a glimpse of a woman's back. The woman is young, somewh "Oh, no," he says. "They're gone. And to think, I'll probably never even get to see her again." -After a brief sigh, Stallman recovers. The moment gives me a chance to discuss Stallman's reputation vis-ý-vis the fairer sex. The reputation is a bit contradictory at times. A number of hackers report Stallman's predilection for greeting females with a kiss on the back of the hand.~{ See Mae Ling Mak, "Mae Ling's Story" (December 17, 1998).<br> http://www.crackmonkey.org/pipermail/crackmonkey/1998q4/003006.htm <br>So far, Mak is the only person I've found willing to speak on the record in regard to this practice, although I've heard this from a few other female sources. Mak, despite expressing initial revulsion at it, later managed to put aside her misgivings and dance with Stallman at a 1999 LinuxWorld show.<br> http://www.linux.com/interact/potd.phtml?potd_id=44 }~ A May 26, 2000 Salon.com article, meanwhile, portrays Stallman as a bit of a hacker lothario. Documenting the free software-free love connection, reporter Annalee Newitz presents Stallman as rejecting traditional family values, telling her, "I believe in love, but not monogamy."~{ See Annalee Newitz, "If Code is Free Why Not Me?" Salon.com (May 26, 2000).<br> http://www.salon.com/tech/feature/2000/05/26/free_love/print.html }~ +After a brief sigh, Stallman recovers. The moment gives me a chance to discuss Stallman's reputation vis-ý-vis the fairer sex. The reputation is a bit contradictory at times. A number of hackers report Stallman's predilection for greeting females with a kiss on the back of the hand.~{ See Mae Ling Mak, "Mae Ling's Story" (December 17, 1998). \\ http://www.crackmonkey.org/pipermail/crackmonkey/1998q4/003006.htm \\ So far, Mak is the only person I've found willing to speak on the record in regard to this practice, although I've heard this from a few other female sources. Mak, despite expressing initial revulsion at it, later managed to put aside her misgivings and dance with Stallman at a 1999 LinuxWorld show. \\ http://www.linux.com/interact/potd.phtml?potd_id=44 }~ A May 26, 2000 Salon.com article, meanwhile, portrays Stallman as a bit of a hacker lothario. Documenting the free software-free love connection, reporter Annalee Newitz presents Stallman as rejecting traditional family values, telling her, "I believe in love, but not monogamy."~{ See Annalee Newitz, "If Code is Free Why Not Me?" Salon.com (May 26, 2000). \\ http://www.salon.com/tech/feature/2000/05/26/free_love/print.html }~ ={Newitz, Annalee;Salon.com} Stallman lets his menu drop a little when I bring this up. "Well, most men seem to want sex and seem to have a rather contemptuous attitude towards women," he says. "Even women they're involved with. I can't understand it at all." @@ -839,7 +839,7 @@ Stallman asks me if I would be interested in hearing the folk filk. As soon as I _1 How much wood could a woodchuck chuck,If a woodchuck could chuck wood? How many poles could a polak lock,If a polak could lock poles? How many knees could a negro grow, If a negro could grow knees? The answer, my dear, is stick it in your ear.The answer is to stick it in your ear. -The singing ends, and Stallman's lips curl into another child-like half smile. I glance around at the nearby tables. The Asian families enjoying their Sunday lunch pay little attention to the bearded alto in their midst.~{ For more Stallman filks, visit<br> http://www.stallman.org/doggerel.html. To hear Stallman singing "The Free Software Song," visit<br> http://www.gnu.org/music/free-software-song.html. }~ After a few moments of hesitation, I finally smile too. +The singing ends, and Stallman's lips curl into another child-like half smile. I glance around at the nearby tables. The Asian families enjoying their Sunday lunch pay little attention to the bearded alto in their midst.~{ For more Stallman filks, visit \\ http://www.stallman.org/doggerel.html. To hear Stallman singing "The Free Software Song," visit \\ http://www.gnu.org/music/free-software-song.html. }~ After a few moments of hesitation, I finally smile too. "Do you want that last cornball?" Stallman asks, eyes twinkling. Before I can screw up the punch line, Stallman grabs the corn-encrusted dumpling with his two chopsticks and lifts it proudly. "Maybe I'm the one who should get the cornball," he says. @@ -903,7 +903,7 @@ The waiter, uncomprehending or fooled by the look of the bill, smiles and scurri The AI Lab of the 1970s was by all accounts a special place. Cutting-edge projects and top-flight researchers gave it an esteemed position in the world of computer science. The internal hacker culture and its anarchic policies lent a rebellious mystique as well. Only later, when many of the lab's scientists and software superstars had departed, would hackers fully realize the unique and ephemeral world they had once inhabited. ={AI Lab (Artificial Intelligence Laboratory)+17} -"It was a bit like the Garden of Eden," says Stallman, summing up the lab and its software-sharing ethos in a 1998 Forbes article. "It hadn't occurred to us not to cooperate."~{ See Josh McHugh, "For the Love of Hacking," Forbes (August 10, 1998).<br> http://www.forbes.com/forbes/1998/0810/6203094a.html }~ +"It was a bit like the Garden of Eden," says Stallman, summing up the lab and its software-sharing ethos in a 1998 Forbes article. "It hadn't occurred to us not to cooperate."~{ See Josh McHugh, "For the Love of Hacking," Forbes (August 10, 1998). \\ http://www.forbes.com/forbes/1998/0810/6203094a.html }~ Such mythological descriptions, while extreme, underline an important fact. The ninth floor of 545 Tech Square was more than a workplace for many. For hackers such as Stallman, it was home. @@ -960,13 +960,13 @@ During the late 1960s, interface design made additional leaps. In a famous 1968 Such innovations would take another two decades to make their way into the commercial marketplace. Still, by the 1970s, video screens had started to replace teletypes as display terminals, creating the potential for full-screen-as opposed to line-by-line-editing capabilities. ={display terminals, replacing teletypes;video screens} -One of the first programs to take advantage of this full-screen capability was the MIT AI Lab's TECO. Short for Text Editor and COrrector, the program had been upgraded by hackers from an old teletype line editor for the lab's PDP-6 machine.~{ According to the Jargon File, TECO's name originally stood for Tape Editor and Corrector.<br> http://www.tuxedo.org/~esr/jargon/html/entry/TECO.html }~ +One of the first programs to take advantage of this full-screen capability was the MIT AI Lab's TECO. Short for Text Editor and COrrector, the program had been upgraded by hackers from an old teletype line editor for the lab's PDP-6 machine.~{ According to the Jargon File, TECO's name originally stood for Tape Editor and Corrector. \\ http://www.tuxedo.org/~esr/jargon/html/entry/TECO.html }~ -TECO was a substantial improvement over old editors, but it still had its drawbacks. To create and edit a document, a programmer had to enter a series of software commands specifying each edit. It was an abstract process. Unlike modern word processors, which update text with each keystroke, TECO demanded that the user enter an extended series of editing instructions followed by an "end of command" sequence just to change the text.Over time, a hacker grew proficient enough to write entire documents in edit mode, but as Stallman himself would later point out, the process required "a mental skill like that of blindfold chess."~{ See Richard Stallman, "EMACS: The Extensible, Customizable, Display Editor," AI Lab Memo (1979). An updated HTML version of this memo, from which I am quoting, is available at<br> http://www.gnu.org/software/emacs/emacs-paper.html }~ +TECO was a substantial improvement over old editors, but it still had its drawbacks. To create and edit a document, a programmer had to enter a series of software commands specifying each edit. It was an abstract process. Unlike modern word processors, which update text with each keystroke, TECO demanded that the user enter an extended series of editing instructions followed by an "end of command" sequence just to change the text.Over time, a hacker grew proficient enough to write entire documents in edit mode, but as Stallman himself would later point out, the process required "a mental skill like that of blindfold chess."~{ See Richard Stallman, "EMACS: The Extensible, Customizable, Display Editor," AI Lab Memo (1979). An updated HTML version of this memo, from which I am quoting, is available at \\ http://www.gnu.org/software/emacs/emacs-paper.html }~ To facilitate the process, AI Lab hackers had built a system that displayed both the "source" and "display" modes on a split screen. Despite this innovative hack, switching from mode to mode was still a nuisance. -TECO wasn't the only full-screen editor floating around the computer world at this time. During a visit to the Stanford Artificial Intelligence Lab in 1976, Stallman encountered an edit program named E. The program contained an internal feature, which allowed a user to update display text after each command keystroke. In the language of 1970s programming, E was one of the first rudimentary WYSIWYG editors. Short for "what you see is what you get," WYSIWYG meant that a user could manipulate the file by moving through the displayed text, as opposed to working through a back-end editor program."~{ See Richard Stallman, "Emacs the Full Screen Editor" (1987).<br> http://www.lysator.liu.se/history/garb/txt/87-1-emacs.txt }~ +TECO wasn't the only full-screen editor floating around the computer world at this time. During a visit to the Stanford Artificial Intelligence Lab in 1976, Stallman encountered an edit program named E. The program contained an internal feature, which allowed a user to update display text after each command keystroke. In the language of 1970s programming, E was one of the first rudimentary WYSIWYG editors. Short for "what you see is what you get," WYSIWYG meant that a user could manipulate the file by moving through the displayed text, as opposed to working through a back-end editor program."~{ See Richard Stallman, "Emacs the Full Screen Editor" (1987). \\ http://www.lysator.liu.se/history/garb/txt/87-1-emacs.txt }~ ={E edit program;Stanford Artificial Intelligence Laboratory} Impressed by the hack, Stallman looked for ways to expand TECO's functionality in similar fashion upon his return to MIT. He found a TECO feature called Control-R, written by Carl Mikkelson and named after the two-key combination that triggered it. Mikkelson's hack switched TECO from its usual abstract command-execution mode to a more intuitive keystroke-by-keystroke mode. Stallman revised the feature in a subtle but significant way. He made it possible to trigger other TECO command strings, or "macros," using other, two-key combinations. Where users had once entered command strings and discarded them after entering then, Stallman's hack made it possible to save macro tricks on file and call them up at will. Mikkelson's hack had raised TECO to the level of a WYSIWYG editor. Stallman's hack had raised it to the level of a user-programmable WYSIWYG editor. "That was the real breakthrough," says Guy Steele, a fellow AI Lab hacker at the time. ^39^ @@ -1005,7 +1005,7 @@ Stallman now faced another conundrum: if users made changes but didn't communica Not everybody accepted the contract. The explosive innovation continued throughout the decade, resulting in a host of Emacs-like programs with varying degrees of cross-compatibility. A few cited their relation to Stallman's original Emacs with humorously recursive names: Sine (Sine is not Emacs), Eine (Eine is not Emacs), and Zwei (Zwei was Eine initially). As a devoted exponent of the hacker ethic, Stallman saw no reason to halt this innovation through legal harassment. Still, the fact that some people would so eagerly take software from the community chest, alter it, and slap a new name on the resulting software displayed a stunning lack of courtesy. ={Eine (Eine is not Emacs) text editor;Zwei (Zwei was Eine initially) text editor;Sine (Sine is not Emacs) text editor} -Such rude behavior was reflected against other, unsettling developments in the hacker community. Brian Reid's 1979 decision to embed "time bombs" in Scribe, making it possible for Unilogic to limit unpaid user access to the software, was a dark omen to Stallman. "He considered it the most Nazi thing he ever saw in his life," recalls Reid. Despite going on to later Internet fame as the cocreator of the Usenet alt heirarchy, Reid says he still has yet to live down that 1979 decision, at least in Stallman's eyes. "He said that all software should be free and the prospect of charging money for software was a crime against humanity."~{ In a 1996 interview with online magazine MEME, Stallman cited Scribe's sale as irksome, but hesitated to mention Reid by name. "The problem was nobody censured or punished this student for what he did," Stallman said. "The result was other people got tempted to follow his example." See MEME 2.04.<br> http://memex.org/meme2-04.html }~ +Such rude behavior was reflected against other, unsettling developments in the hacker community. Brian Reid's 1979 decision to embed "time bombs" in Scribe, making it possible for Unilogic to limit unpaid user access to the software, was a dark omen to Stallman. "He considered it the most Nazi thing he ever saw in his life," recalls Reid. Despite going on to later Internet fame as the cocreator of the Usenet alt heirarchy, Reid says he still has yet to live down that 1979 decision, at least in Stallman's eyes. "He said that all software should be free and the prospect of charging money for software was a crime against humanity."~{ In a 1996 interview with online magazine MEME, Stallman cited Scribe's sale as irksome, but hesitated to mention Reid by name. "The problem was nobody censured or punished this student for what he did," Stallman said. "The result was other people got tempted to follow his example." See MEME 2.04. \\ http://memex.org/meme2-04.html }~ ={Reid, Brian+1;Unilogic software company;time bombs, in software;Scribe text-formatting program} % additional reference to Unilogic; also time bombs; also scribe text-formatting program @@ -1017,7 +1017,7 @@ Although Stallman had been powerless to head off Reid's sale, he did possess the Over time, Emacs became a sales tool for the hacker ethic. The flexibility Stallman and built into the software not only encouraged collaboration, it demanded it. Users who didn't keep abreast of the latest developments in Emacs evolution or didn't contribute their contributions back to Stallman ran the risk of missing out on the latest breakthroughs. And the breakthroughs were many. Twenty years later, users had modified Emacs for so many different uses-using it as a spreadsheet, calculator, database, and web browser-that later Emacs developers adopted an overflowing sink to represent its versatile functionality. "That's the idea that we wanted to convey," says Stallman. "The amount of stuff it has contained within it is both wonderful and awful at the same time." -Stallman's AI Lab contemporaries are more charitable. Hal Abelson, an MIT grad student who worked with Stallman during the 1970s and would later assist Stallman as a charter boardmember of the Free Software Foundation, describes Emacs as "an absolutely brilliant creation." In giving programmers a way to add new software libraries and features without messing up the system, Abelson says, Stallman paved the way for future large-scale collaborative software projects. "Its structure was robust enough that you'd have people all over the world who were loosely collaborating [and] contributing to it," Abelson says. "I don't know if that had been done before."~{ In writing this chapter, I've elected to focus more on the social significance of Emacs than the software significance. To read more about the software side, I recommend Stallman's 1979 memo. I particularly recommend the section titled "Research Through Development of Installed Tools" (#SEC27). Not only is it accessible to the nontechnical reader, it also sheds light on how closely intertwined Stallman's political philosophies are with his software-design philosophies. A sample excerpt follows:<br>_1 EMACS could not have been reached by a process of careful design, because such processes arrive only at goals which are visible at the outset, and whose desirability is established on the bottom line at the outset. Neither I nor anyone else visualized an extensible editor until I had made one, nor appreciated its value until he had experienced it. EMACS exists because I felt free to make individually useful small improvements on a path whose end was not in sight. }~ +Stallman's AI Lab contemporaries are more charitable. Hal Abelson, an MIT grad student who worked with Stallman during the 1970s and would later assist Stallman as a charter boardmember of the Free Software Foundation, describes Emacs as "an absolutely brilliant creation." In giving programmers a way to add new software libraries and features without messing up the system, Abelson says, Stallman paved the way for future large-scale collaborative software projects. "Its structure was robust enough that you'd have people all over the world who were loosely collaborating [and] contributing to it," Abelson says. "I don't know if that had been done before."~{ In writing this chapter, I've elected to focus more on the social significance of Emacs than the software significance. To read more about the software side, I recommend Stallman's 1979 memo. I particularly recommend the section titled "Research Through Development of Installed Tools" (#SEC27). Not only is it accessible to the nontechnical reader, it also sheds light on how closely intertwined Stallman's political philosophies are with his software-design philosophies. A sample excerpt follows: \\ EMACS could not have been reached by a process of careful design, because such processes arrive only at goals which are visible at the outset, and whose desirability is established on the bottom line at the outset. Neither I nor anyone else visualized an extensible editor until I had made one, nor appreciated its value until he had experienced it. EMACS exists because I felt free to make individually useful small improvements on a path whose end was not in sight. }~ ={Abelson, Hal} Guy Steele expresses similar admiration. Currently a research scientist for Sun Microsystems, he remembers Stallman primarily as a "brilliant programmer with the ability to generate large quantities of relatively bug-free code." Although their personalities didn't exactly mesh, Steele and Stallman collaborated long enough for Steele to get a glimpse of Stallman's intense coding style. He recalls a notable episode in the late 1970s when the two programmers banded together to write the editor's "pretty print" feature. Originally conceived by Steele, pretty print was another keystroke-triggerd feature that reformatted Emacs' source code so that it was both more readable and took up less space, further bolstering the program's WYSIWIG qualities. The feature was strategic enough to attract Stallman's active interest, and it wasn't long before Steele wrote that he and Stallman were planning an improved version. @@ -1035,7 +1035,7 @@ The length of the session revealed itself when Steele finally left the AI Lab. S On September 27, 1983, computer programmers logging on to the Usenet newsgroup net.unix-wizards encountered an unusual message. Posted in the small hours of the morning, 12:30 a.m. to be exact, and signed by rms@mit-oz, the message's subject line was terse but attention-grabbing. "New UNIX implementation," it read. Instead of introducing a newly released version of Unix, however, the message's opening paragraph issued a call to arms: ={GNU Project:new UNIX implementation;net.unix-wizards newsgroup} -_1 Starting this Thanksgiving I am going to write a complete Unix-compatible software system called GNU (for Gnu's Not Unix), and give it away free to everyone who can use it. Contributions of time, money, programs and equipment are greatly needed.~{ See Richard Stallman, "Initial GNU Announcement" (September 1983).<br> http://www.gnu.ai.mit.edu/gnu/initial-announcement.html }~ +_1 Starting this Thanksgiving I am going to write a complete Unix-compatible software system called GNU (for Gnu's Not Unix), and give it away free to everyone who can use it. Contributions of time, money, programs and equipment are greatly needed.~{ See Richard Stallman, "Initial GNU Announcement" (September 1983). \\ http://www.gnu.ai.mit.edu/gnu/initial-announcement.html }~ ={Unix operating system:GNU system and} To an experienced Unix developer, the message was a mixture of idealism and hubris. Not only did the author pledge to rebuild the already mature Unix operating system from the ground up, he also proposed to improve it in places. The new GNU system, the author predicted, would carry all the usual components-a text editor, a shell program to run Unix-compatible applications, a compiler, "and a few other things." ^44^ It would also contain many enticing features that other Unix systems didn't yet offer: a graphic user interface based on the Lisp programming language, a crash-proof file system, and networking protocols built according to MIT's internal networking system. @@ -1068,7 +1068,7 @@ The breaking point came in 1982. That was the year the lab's administration deci "Without hackers to maintain the system, [faculty members] said, `We're going to have a disaster; we must have commercial software,'" Stallman would recall a few years later. "They said, `We can expect the company to maintain it.' It proved that they were utterly wrong, but that's what they did."~{ See Richard Stallman (1986). }~ -At first, hackers viewed the Twenex system as yet another authoritarian symbol begging to be subverted. The system's name itself was a protest. Officially dubbed TOPS-20 by DEC, it was a successor to TOPS-10, a commercial operating system DEC marketed for the PDP-10. Bolt Beranek Newman had deveoped an improved version, dubbed Tenex, which TOPS-20 drew upon.~{ Multiple sources: see Richard Stallman interview, Gerald Sussman email, and Jargon File 3.0.0.<br> http://www.clueless.com/jargon3.0.0/TWENEX.html }~ Stallman, the hacker who coined the Twenex term, says he came up with the name as a way to avoid using the TOPS-20 name. "The system was far from tops, so there was no way I was going to call it that," Stallman recalls. "So I decided to insert a `w' in the Tenex name and call it Twenex." +At first, hackers viewed the Twenex system as yet another authoritarian symbol begging to be subverted. The system's name itself was a protest. Officially dubbed TOPS-20 by DEC, it was a successor to TOPS-10, a commercial operating system DEC marketed for the PDP-10. Bolt Beranek Newman had deveoped an improved version, dubbed Tenex, which TOPS-20 drew upon.~{ Multiple sources: see Richard Stallman interview, Gerald Sussman email, and Jargon File 3.0.0. \\ http://www.clueless.com/jargon3.0.0/TWENEX.html }~ Stallman, the hacker who coined the Twenex term, says he came up with the name as a way to avoid using the TOPS-20 name. "The system was far from tops, so there was no way I was going to call it that," Stallman recalls. "So I decided to insert a `w' in the Tenex name and call it Twenex." ={DEC (Digital Equipment Corporation);TOPS-20 operating system+1} % ={Bolt, Beranek & Newman engineering firm;Tenex} @@ -1088,7 +1088,7 @@ The disguise was a thin one at best. By 1982, Stallman's aversion to passwords a "I'm eternally grateful that MIT let me and many other people use their computers for free," says Hopkins. "It meant a lot to many people." -This so-called "tourist" policy, which had been openly tolerated by MIT management during the ITS years,~{ See "MIT AI Lab Tourist Policy."<br> http://catalog.com/hopkins/text/tourist-policy.html }~ fell by the wayside when Oz became the lab's primary link to the ARPAnet. At first, Stallman continued his policy of repeating his login ID as a password so outside users could follow in his footsteps. Over time, however, the Oz's fragility prompted administrators to bar outsiders who, through sheer accident or malicious intent, might bring down the system. When those same administrators eventually demanded that Stallman stop publishing his password, Stallman, citing personal ethics, refused to do so and ceased using the Oz system altogether. ^46^ +This so-called "tourist" policy, which had been openly tolerated by MIT management during the ITS years,~{ See "MIT AI Lab Tourist Policy." \\ http://catalog.com/hopkins/text/tourist-policy.html }~ fell by the wayside when Oz became the lab's primary link to the ARPAnet. At first, Stallman continued his policy of repeating his login ID as a password so outside users could follow in his footsteps. Over time, however, the Oz's fragility prompted administrators to bar outsiders who, through sheer accident or malicious intent, might bring down the system. When those same administrators eventually demanded that Stallman stop publishing his password, Stallman, citing personal ethics, refused to do so and ceased using the Oz system altogether. ^46^ "[When] passwords first appeared at the MIT AI Lab I [decided] to follow my belief that there should be no passwords," Stallman would later say. "Because I don't believe that it's really desirable to have security on a computer, I shouldn't be willing to help uphold the security regime." ^46^ @@ -1151,7 +1151,7 @@ Nowhere was this state of affairs more evident than in the realm of personal com One of the most notorious of these programmers was Bill Gates, a Harvard dropout two years Stallman's junior. Although Stallman didn't know it at the time, seven years before sending out his message to the net.unix-wizards newsgroup, Gates, a budding entrepreneur and general partner with the Albuquerque-based software firm Micro-Soft, later spelled as Microsoft, had sent out his own open letter to the software-developer community. Written in response to the PC users copying Micro-Soft's software programs, Gates' " Open Letter to Hobbyists" had excoriated the notion of communal software development. ={Gates, Bill+2;Micro-Soft;net.unix-wizards newsgroup;Open Letter to Hobbyists (Gates)+1} -"Who can afford to do professional work for nothing?" asked Gates. "What hobbyist can put three man-years into programming, finding all bugs, documenting his product, and distributing it for free?"~{ See Bill Gates, "An Open Letter to Hobbyists" (February 3, 1976).<br>To view an online copy of this letter, go to<br> http://www.blinkenlights.com/classiccmp/gateswhine.html. }~ +"Who can afford to do professional work for nothing?" asked Gates. "What hobbyist can put three man-years into programming, finding all bugs, documenting his product, and distributing it for free?"~{ See Bill Gates, "An Open Letter to Hobbyists" (February 3, 1976). \\ To view an online copy of this letter, go to \\ http://www.blinkenlights.com/classiccmp/gateswhine.html. }~ Although few hackers at the AI Lab saw the missive, Gates' 1976 letter nevertheless represented the changing attitude toward software both among commercial software companies and commercial software developers. Why treat software as a zero-cost commodity when the market said otherwise? As the 1970s gave way to the 1980s, selling software became more than a way to recoup costs; it became a political statement. At a time when the Reagan Administration was rushing to dismantle many of the federal regulations and spending programs that had been built up during the half century following the Great Depression, more than a few software programmers saw the hacker ethic as anticompetitive and, by extension, un-American. At best, it was a throwback to the anticorporate attitudes of the late 1960s and early 1970s. Like a Wall Street banker discovering an old tie-dyed shirt hiding between French-cuffed shirts and double-breasted suits, many computer programmers treated the hacker ethic as an embarrassing reminder of an idealistic age. @@ -1171,7 +1171,7 @@ group{ If not now, when? -}group ~{ See Richard Stallman, Open Sources (O'Reilly & Associates, Inc., 1999): 56.<br>Stallman adds his own footnote to this statement, writing, "As an atheist, I don't follow any religious leaders, but I sometimes find I admire something one of them has said." }~ +}group ~{ See Richard Stallman, Open Sources (O'Reilly & Associates, Inc., 1999): 56. \\ Stallman adds his own footnote to this statement, writing, "As an atheist, I don't follow any religious leaders, but I sometimes find I admire something one of them has said." }~ Speaking to audiences, Stallman avoids the religious route and expresses the decision in pragmatic terms. "I asked myself: what could I, an operating-system developer, do to improve the situation? It wasn't until I examined the question for a while that I realized an operating-system developer was exactly what was needed to solve the problem." @@ -1212,7 +1212,7 @@ In the course of reverse-engineering Gosling's interpreter, Stallman would creat Despite the stress it generated, the dispute over Gosling's innovations would assist both Stallman and the free software movement in the long term. It would force Stallman to address the weaknesses of the Emacs Commune and the informal trust system that had allowed problematic offshoots to emerge. It would also force Stallman to sharpen the free software movement's political objectives. Following the release of GNU Emacs in 1985, Stallman issued " The GNU Manifesto," an expansion of the original announcement posted in September, 1983. Stallman included within the document a lengthy section devoted to the many arguments used by commercial and academic programmers to justify the proliferation of proprietary software programs. One argument, "Don't programmers deserve a reward for their creativity," earned a response encapsulating Stallman's anger over the recent Gosling Emacs episode: ={Emacs Commune:proprietary software and;Emacs text editor;GNU Emacs;GNU Manifesto} -"If anything deserves a reward, it is social contribution," Stallman wrote. "Creativity can be a social contribution, but only in so far [sic] as society is free to use the results. If programmers deserve to be rewarded for creating innovative programs, by the same token they deserve to be punished if they restrict the use of these programs."~{ See Richard Stallman, "The GNU Manifesto" (1985).<br> http://www.gnu.org/manifesto.html }~ +"If anything deserves a reward, it is social contribution," Stallman wrote. "Creativity can be a social contribution, but only in so far [sic] as society is free to use the results. If programmers deserve to be rewarded for creating innovative programs, by the same token they deserve to be punished if they restrict the use of these programs."~{ See Richard Stallman, "The GNU Manifesto" (1985). \\ http://www.gnu.org/manifesto.html }~ With the release of GNU Emacs, the GNU Project finally had code to show. It also had the burdens of any software-based enterprise. As more and more Unix developers began playing with the software, money, gifts, and requests for tapes began to pour in. To address the business side of the GNU Project, Stallman drafted a few of his colleagues and formed the Free Software Foundation (FSF), a nonprofit organization dedicated to speeding the GNU Project towards its goal. With Stallman as president and various hacker allies as board members, the FSF helped provide a corporate face for the GNU Project. ={Free Software Foundation (FSF):GNU Project and;GNU Project:Emacs, release of} @@ -1252,9 +1252,9 @@ Needless to say, Stallman, who stands in front of the room dressed in plain blue As Stallman putters around the front of the room, a few audience members wearing T-shirts with the logo of the Maui FreeBSD Users Group (MFUG) race to set up camera and audio equipment. FreeBSD, a free software offshoot of the Berkeley Software Distribution, the venerable 1970s academic version of Unix, is technically a competitor to the GNU/Linux operating system. Still, in the hacking world, Stallman speeches are documented with a fervor reminiscent of the Grateful Dead and its legendary army of amateur archivists. As the local free software heads, it's up to the MFUG members to make sure fellow programmers in Hamburg, Mumbai, and Novosibirsk don't miss out on the latest pearls of RMS wisdom. ={Berkely Software Distribution (BSD);BSD (Berkely Software Distribution);Grateful Dead, The+1;Maui FreeBSD Users Group} -The analogy to the Grateful Dead is apt. Often, when describing the business opportunities inherent within the free software model, Stallman has held up the Grateful Dead as an example. In refusing to restrict fans' ability to record live concerts, the Grateful Dead became more than a rock group. They became the center of a tribal community dedicated to Grateful Dead music. Over time, that tribal community became so large and so devoted that the band shunned record contracts and supported itself solely through musical tours and live appearances. In 1994, the band's last year as a touring act, the Grateful Dead drew $52 million in gate receipts alone.~{ See "Grateful Dead Time Capsule: 1985-1995 North American Tour Grosses."<br> http://www.accessplace.com/gdtc/1197.htm }~ +The analogy to the Grateful Dead is apt. Often, when describing the business opportunities inherent within the free software model, Stallman has held up the Grateful Dead as an example. In refusing to restrict fans' ability to record live concerts, the Grateful Dead became more than a rock group. They became the center of a tribal community dedicated to Grateful Dead music. Over time, that tribal community became so large and so devoted that the band shunned record contracts and supported itself solely through musical tours and live appearances. In 1994, the band's last year as a touring act, the Grateful Dead drew $52 million in gate receipts alone.~{ See "Grateful Dead Time Capsule: 1985-1995 North American Tour Grosses." \\ http://www.accessplace.com/gdtc/1197.htm }~ -While few software companies have been able to match that success, the tribal aspect of the free software community is one reason many in the latter half of the 1990s started to accept the notion that publishing software source code might be a good thing. Hoping to build their own loyal followings, companies such as IBM, Sun Microsystems, and Hewlett Packard have come to accept the letter, if not the spirit, of the Stallman free software message. Describing the GPL as the information-technology industry's "Magna Carta," ZDNet software columnist Evan Leibovitch sees the growing affection for all things GNU as more than just a trend. "This societal shift is letting users take back control of their futures," Leibovitch writes. "Just as the Magna Carta gave rights to British subjects, the GPL enforces consumer rights and freedoms on behalf of the users of computer software."~{ See Evan Leibovitch, "Who's Afraid of Big Bad Wolves," ZDNet Tech Update (December 15, 2000).<br> http://techupdate.zdnet.com/techupdate/stories/main/0,14179,2664992,00.html }~ +While few software companies have been able to match that success, the tribal aspect of the free software community is one reason many in the latter half of the 1990s started to accept the notion that publishing software source code might be a good thing. Hoping to build their own loyal followings, companies such as IBM, Sun Microsystems, and Hewlett Packard have come to accept the letter, if not the spirit, of the Stallman free software message. Describing the GPL as the information-technology industry's "Magna Carta," ZDNet software columnist Evan Leibovitch sees the growing affection for all things GNU as more than just a trend. "This societal shift is letting users take back control of their futures," Leibovitch writes. "Just as the Magna Carta gave rights to British subjects, the GPL enforces consumer rights and freedoms on behalf of the users of computer software."~{ See Evan Leibovitch, "Who's Afraid of Big Bad Wolves," ZDNet Tech Update (December 15, 2000). \\ http://techupdate.zdnet.com/techupdate/stories/main/0,14179,2664992,00.html }~ ={Hewlett Packard;IBM;Sun Microsystems} The tribal aspect of the free software community also helps explain why 40-odd programmers, who might otherwise be working on physics projects or surfing the Web for windsurfing buoy reports, have packed into a conference room to hear Stallman speak. @@ -1266,7 +1266,7 @@ Unlike the New York speech, Stallman gets no introduction. He also offers no sel Once again, Stallman quickly segues into the parable of the Xerox laser printer, taking a moment to deliver the same dramatic finger-pointing gestures to the crowd. He also devotes a minute or two to the GNU/Linux name. -"Some people say to me, `Why make such a fuss about getting credit for this system? After all, the important thing is the job is done, not whether you get recognition for it.' Well, this would be wise advice if it were true. But the job wasn't to build an operating system; the job is to spread freedom to the users of computers. And to do that we have to make it possible to do everything with computers in freedom."~{ For narrative purposes, I have hesitated to go in-depth when describing Stallman's full definition of software "freedom." The GNU Project web site lists four fundamental components:<br>The freedom to run a program, for any purpose (freedom 0).<br>The freedom to study how a program works, and adapt it to your needs (freedom 1).<br>The freedom to redistribute copies of a program so you can help your neighbor (freedom 2).<br>The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3).<br>For more information, please visit "The Free Software Definition" at http://www.gnu.org/philosophy/free-sw.html }~ +"Some people say to me, `Why make such a fuss about getting credit for this system? After all, the important thing is the job is done, not whether you get recognition for it.' Well, this would be wise advice if it were true. But the job wasn't to build an operating system; the job is to spread freedom to the users of computers. And to do that we have to make it possible to do everything with computers in freedom."~{ For narrative purposes, I have hesitated to go in-depth when describing Stallman's full definition of software "freedom." The GNU Project web site lists four fundamental components: \\ The freedom to run a program, for any purpose (freedom 0). \\ The freedom to study how a program works, and adapt it to your needs (freedom 1). \\ The freedom to redistribute copies of a program so you can help your neighbor (freedom 2). \\ The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). \\ For more information, please visit "The Free Software Definition" at http://www.gnu.org/philosophy/free-sw.html }~ Adds Stallman, "There's a lot more work to do." @@ -1320,7 +1320,7 @@ The skit is a lighthearted moment of self-pardoy, a humorous return-jab at the m Discussing the St. Ignucius persona afterward, Stallman says he first came up with it in 1996, long after the creation of Emacs but well before the emergence of the "open source" term and the struggle for hacker-community leadership that precipitated it. At the time, Stallman says, he wanted a way to "poke fun at himself," to remind listeners that, though stubborn, Stallman was not the fanatic some made him out to be. It was only later, Stallman adds, that others seized the persona as a convenient way to play up his reputation as software ideologue, as Eric Raymond did in an 1999 interview with the linux.com web site: ={linux.com;Raymond, Eric:St. Ignucius and+2} -_1 When I say RMS calibrates what he does, I'm not belittling or accusing him of insincerity. I'm saying that like all good communicators he's got a theatrical streak. Sometimes it's conscious-have you ever seen him in his St. Ignucius drag, blessing software with a disk platter on his head? Mostly it's unconscious; he's just learned the degree of irritating stimulus that works, that holds attention without (usually) freaking people out.~{ See "Guest Interview: Eric S. Raymond," Linux.com (May 18, 1999).<br> http://www.linux.com/interviews/19990518/8/ }~ +_1 When I say RMS calibrates what he does, I'm not belittling or accusing him of insincerity. I'm saying that like all good communicators he's got a theatrical streak. Sometimes it's conscious-have you ever seen him in his St. Ignucius drag, blessing software with a disk platter on his head? Mostly it's unconscious; he's just learned the degree of irritating stimulus that works, that holds attention without (usually) freaking people out.~{ See "Guest Interview: Eric S. Raymond," Linux.com (May 18, 1999). \\ http://www.linux.com/interviews/19990518/8/ }~ Stallman takes issue with the Raymond analysis. "It's simply my way of making fun of myself," he says. "The fact that others see it as anything more than that is a reflection of their agenda, not mine." @@ -1370,7 +1370,7 @@ By the spring of 1985, Richard Stallman had settled on the GNU Project's first m The dispute with UniPress had highlighted a flaw in the Emacs Commune social contract. Where users relied on Stallman's expert insight, the Commune's rules held. In areas where Stallman no longer held the position of alpha hacker-pre-1984 Unix systems, for example-individuals and companies were free to make their own rules. ={UniPress software company} -The tension between the freedom to modify and the freedom to exert authorial privilege had been building before GOSMACS. The Copyright Act of 1976 had overhauled U.S. copyright law, extending the legal protection of copyright to software programs. According to Section 102(b) of the Act, individuals and companies now possessed the ability to copyright the "expression" of a software program but not the "actual processes or methods embodied in the program."~{ See Hal Abelson, Mike Fischer, and Joanne Costello, "Software and Copyright Law," updated version (1998).<br> http://www.swiss.ai.mit.edu/6805/articles/int-prop/software-copyright.html }~ Translated, programmers and companies had the ability to treat software programs like a story or song. Other programmers could take inspiration from the work, but to make a direct copy or nonsatirical derivative, they first had to secure permission from the original creator. Although the new law guaranteed that even programs without copyright notices carried copyright protection, programmers quickly asserted their rights, attaching coypright notices to their software programs. +The tension between the freedom to modify and the freedom to exert authorial privilege had been building before GOSMACS. The Copyright Act of 1976 had overhauled U.S. copyright law, extending the legal protection of copyright to software programs. According to Section 102(b) of the Act, individuals and companies now possessed the ability to copyright the "expression" of a software program but not the "actual processes or methods embodied in the program."~{ See Hal Abelson, Mike Fischer, and Joanne Costello, "Software and Copyright Law," updated version (1998). \\ http://www.swiss.ai.mit.edu/6805/articles/int-prop/software-copyright.html }~ Translated, programmers and companies had the ability to treat software programs like a story or song. Other programmers could take inspiration from the work, but to make a direct copy or nonsatirical derivative, they first had to secure permission from the original creator. Although the new law guaranteed that even programs without copyright notices carried copyright protection, programmers quickly asserted their rights, attaching coypright notices to their software programs. ={Copyright Act of 1976;copyright laws;GOSMACS (Gosling Emacs);software:copyright laws on} At first, Stallman viewed these notices with alarm. Rare was the software program that didn't borrow source code from past programs, and yet, with a single stroke of the president's pen, Congress had given programmers and companies the power to assert individual authorship over communally built programs. It also injected a dose of formality into what had otherwise been an informal system. Even if hackers could demonstrate how a given program's source-code bloodlines stretched back years, if not decades, the resources and money that went into battling each copyright notice were beyond most hackers' means. Simply put, disputes that had once been settled hacker-to-hacker were now settled lawyer-to-lawyer. In such a system, companies, not hackers, held the automatic advantage. @@ -1402,9 +1402,8 @@ As an example of this informality, Gilmore cites a copyright notice for trn, a U % previous markup as 'poem' with footnote not satisfactory -Copyright (c) 1985, Larry Wall<br> -You may copy the trn kit in whole or in part as long as you don't try -to make money off it, or pretend that you wrote it.~{ See Trn Kit README.<br> http://www.za.debian.org/doc/trn/trn-readme }~ +Copyright (c) 1985, Larry Wall \\ +You may copy the trn kit in whole or in part as long as you don't try to make money off it, or pretend that you wrote it.~{ See Trn Kit README. \\ http://www.za.debian.org/doc/trn/trn-readme }~ Such statements, while reflective of the hacker ethic, also reflected the difficulty of translating the loose, informal nature of that ethic into the rigid, legal language of copyright. In writing the GNU Emacs License, Stallman had done more than close up the escape hatch that permitted proprietary offshoots. He had expressed the hacker ethic in a manner understandable to both lawyer and hacker alike. @@ -1430,7 +1429,7 @@ anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. -}poem ~{ See Richard Stallman, et al., "GNU General Public License: Version 1," (February, 1989).<br> http://www.gnu.org/copyleft/copying-1.0.html }~ +}poem ~{ See Richard Stallman, et al., "GNU General Public License: Version 1," (February, 1989). \\ http://www.gnu.org/copyleft/copying-1.0.html }~ In fashioning the GPL, Stallman had been forced to make an additional adjustment to the informal tenets of the old Emacs Commune. Where he had once demanded that Commune members publish any and all changes, Stallman now demanded publication only in instances when programmers circulated their derivative versions in the same public manner as Stallman. In other words, programmers who simply modified Emacs for private use no longer needed to send the source-code changes back to Stallman. In what would become a rare compromise of free software doctrine, Stallman slashed the price tag for free software. Users could innovate without Stallman looking over their shoulders just so long as they didn't bar Stallman and the rest of the hacker community from future exchanges of the same program. ={Emacs Commune+1} @@ -1445,7 +1444,7 @@ As hacks go, the GPL stands as one of Stallman's best. It created a system of co "The GPL developed much like any piece of free software with a large community discussing its structure, its respect or the opposite in their observation, needs for tweaking and even to compromise it mildly for greater acceptance," says Jerry Cohen, another attorney who helped Stallman with the creation of the license. "The process worked very well and GPL in its several versions has gone from widespread skeptical and at times hostile response to widespread acceptance." -In a 1986 interview with Byte magazine, Stallman summed up the GPL in colorful terms. In addition to proclaiming hacker values, Stallman said, readers should also "see it as a form of intellectual jujitsu, using the legal system that software hoarders have set up against them."~{ See David Betz and Jon Edwards, "Richard Stallman discusses his public-domain [sic] Unix-compatible software system with BYTE editors," BYTE (July, 1996). (Reprinted on the GNU Project web site: http://www.gnu.org/gnu/byte-interview.html )<br>This interview offers an interesting, not to mention candid, glimpse at Stallman's political attitudes during the earliest days of the GNU Project. It is also helpful in tracing the evolution of Stallman's rhetoric.<br>Describing the purpose of the GPL, Stallman says, "I'm trying to change the way people approach knowledge and information in general. I think that to try to own knowledge, to try to control whether people are allowed to use it, or to try to stop other people from sharing it, is sabotage."<br>Contrast this with a statement to the author in August 2000: "I urge you not to use the term `intellectual property' in your thinking. It will lead you to misunderstand things, because that term generalizes about copyrights, patents, and trademarks. And those things are so different in their effects that it is entirely foolish to try to talk about them at once. If you hear somebody saying something about intellectual property, without quotes, then he's not thinking very clearly and you shouldn't join." }~ Years later, Stallman would describe the GPL's creation in less hostile terms. "I was thinking about issues that were in a sense ethical and in a sense political and in a sense legal," he says. "I had to try to do what could be sustained by the legal system that we're in. In spirit the job was that of legislating the basis for a new society, but since I wasn't a government, I couldn't actually change any laws. I had to try to do this by building on top of the existing legal system, which had not been designed for anything like this." +In a 1986 interview with Byte magazine, Stallman summed up the GPL in colorful terms. In addition to proclaiming hacker values, Stallman said, readers should also "see it as a form of intellectual jujitsu, using the legal system that software hoarders have set up against them."~{ See David Betz and Jon Edwards, "Richard Stallman discusses his public-domain [sic] Unix-compatible software system with BYTE editors," BYTE (July, 1996). (Reprinted on the GNU Project web site: http://www.gnu.org/gnu/byte-interview.html ) \\ This interview offers an interesting, not to mention candid, glimpse at Stallman's political attitudes during the earliest days of the GNU Project. It is also helpful in tracing the evolution of Stallman's rhetoric. \\ Describing the purpose of the GPL, Stallman says, "I'm trying to change the way people approach knowledge and information in general. I think that to try to own knowledge, to try to control whether people are allowed to use it, or to try to stop other people from sharing it, is sabotage." \\ Contrast this with a statement to the author in August 2000: "I urge you not to use the term `intellectual property' in your thinking. It will lead you to misunderstand things, because that term generalizes about copyrights, patents, and trademarks. And those things are so different in their effects that it is entirely foolish to try to talk about them at once. If you hear somebody saying something about intellectual property, without quotes, then he's not thinking very clearly and you shouldn't join." }~ Years later, Stallman would describe the GPL's creation in less hostile terms. "I was thinking about issues that were in a sense ethical and in a sense political and in a sense legal," he says. "I had to try to do what could be sustained by the legal system that we're in. In spirit the job was that of legislating the basis for a new society, but since I wasn't a government, I couldn't actually change any laws. I had to try to do this by building on top of the existing legal system, which had not been designed for anything like this." ={Byte magazine} About the time Stallman was pondering the ethical, political, and legal issues associated with free software, a California hacker named Don Hopkins mailed him a manual for the 68000 microprocessor. Hopkins, a Unix hacker and fellow science-fiction buff, had borrowed the manual from Stallman a while earlier. As a display of gratitude, Hopkins decorated the return envelope with a number of stickers obtained at a local science-fiction convention. One sticker in particular caught Stallman's eye. It read, "Copyleft (L), All Rights Reversed." Following the release of the first version of GPL, Stallman paid tribute to the sticker, nicknaming the free software license "Copyleft." Over time, the nickname and its shorthand symbol, a backwards "C," would become an official Free Software Foundation synonym for the GPL. @@ -1469,7 +1468,7 @@ Hired in 1986, Bostic had taken on the personal project of porting BSD over to t % CSRG abbreviated to SRG above? -The arguments eventually took hold, although not in the way Stallman would have liked. In June, 1989, Berkeley separated its networking code from the rest of the AT&T-owned operating system and distributed it under a University of California license. The contract terms were liberal. All a licensee had to do was give credit to the university in advertisements touting derivative programs.~{ The University of California's "obnoxious advertising clause" would later prove to be a problem. Looking for a less restrictive alternative to the GPL, some hackers used the University of California, replacing "University of California" with the name of their own instution. The result: free software programs that borrowed from dozens of other programs would have to cite dozens of institutions in advertisements. In 1999, after a decade of lobbying on Stallman's part, the University of California agreed to drop this clause.<br>See "The BSD License Problem" at http://www.gnu.org/philosophy/bsd.html. }~ In contrast to the GPL, proprietary offshoots were permissible. Only one problem hampered the license's rapid adoption: the BSD Networking release wasn't a complete operating system. People could study the code, but it could only be run in conjunction with other proprietary-licensed code. +The arguments eventually took hold, although not in the way Stallman would have liked. In June, 1989, Berkeley separated its networking code from the rest of the AT&T-owned operating system and distributed it under a University of California license. The contract terms were liberal. All a licensee had to do was give credit to the university in advertisements touting derivative programs.~{ The University of California's "obnoxious advertising clause" would later prove to be a problem. Looking for a less restrictive alternative to the GPL, some hackers used the University of California, replacing "University of California" with the name of their own instution. The result: free software programs that borrowed from dozens of other programs would have to cite dozens of institutions in advertisements. In 1999, after a decade of lobbying on Stallman's part, the University of California agreed to drop this clause. \\ See "The BSD License Problem" at http://www.gnu.org/philosophy/bsd.html. }~ In contrast to the GPL, proprietary offshoots were permissible. Only one problem hampered the license's rapid adoption: the BSD Networking release wasn't a complete operating system. People could study the code, but it could only be run in conjunction with other proprietary-licensed code. ={AT&T+1} Over the next few years, Bostic and other University of California employees worked to replace the missing components and turn BSD into a complete, freely redistributable operating system. Although delayed by a legal challenge from Unix Systems Laboratories-the AT&T spin-off that retained ownership of the Unix brand name-the effort would finally bear fruit in the early 1990s. Even before then, however, many of the Berkeley utilities would make their way into Stallman's GNU Project. @@ -1538,14 +1537,14 @@ Jeremy Allison, a Sun user during the late 1980s and programmer destined to run Stallman's growing stature as a software programmer, however, was balanced by his struggles as a project manager. Although the GNU Project moved from success to success in creation of developer-oriented tools, its inability to generate a working kernel-the central "traffic cop" program in all Unix systems that determines which devices and applications get access to the microprocessor and when-was starting to elicit grumbles as the 1980s came to a close. As with most GNU Project efforts, Stallman had started kernel development by looking for an existing program to modify. According to a January 1987 "Gnusletter," Stallman was already working to overhaul TRIX, a Unix kernel developed at MIT. -A review of GNU Project "GNUsletters" of the late 1980s reflects the management tension. In January, 1987, Stallman announced to the world that the GNU Project was working to overhaul TRIX, a Unix kernel developed at MIT. A year later, in February of 1988, the GNU Project announced that it had shifted its attentions to Mach, a lightweight "micro-kernel" developed at Carnegie Mellon. All told, however, official GNU Project kernel development wouldn't commence until 1990.~{ See "HURD History."<br> http://www.gnu.org/software/hurd/history.html }~ +A review of GNU Project "GNUsletters" of the late 1980s reflects the management tension. In January, 1987, Stallman announced to the world that the GNU Project was working to overhaul TRIX, a Unix kernel developed at MIT. A year later, in February of 1988, the GNU Project announced that it had shifted its attentions to Mach, a lightweight "micro-kernel" developed at Carnegie Mellon. All told, however, official GNU Project kernel development wouldn't commence until 1990.~{ See "HURD History." \\ http://www.gnu.org/software/hurd/history.html }~ % ={Carnegie Mellon University} The delays in kernel development were just one of many concerns weighing on Stallman during this period. In 1989, Lotus Development Corporation filed suit against rival software company, Paperback Software International, for copying menu commands in Lotus' popular 1-2-3 Spreadsheet program. Lotus' suit, coupled with the Apple-Microsoft "look and feel" battle, provided a troublesome backdrop for the GNU Project. Although both suits fell outside the scope of the GNU Project, both revolved around operating systems and software applications developed for the personal computer, not Unix-compatible hardware systems-they threatened to impose a chilling effect on the entire culture of software development. Determined to do something, Stallman recruited a few programmer friends and composed a magazine ad blasting the lawsuits. He then followed up the ad by helping to organize a group to protest the corporations filing the suit. Calling itself the League of Programming Freedom, the group held protests outside the offices of Lotus, Inc. and the Boston courtroom hosting the Lotus trial. ={Apple Computers;Lotus Development Corp.;Microsoft Corporation:Apple Computer lawsuit;Paperback Software International} -The protests were notable.~{ According to a League of Programming Freedom Press, the protests were notable for featuring the first hexadecimal protest chant:<br>1-2-3-4, toss the lawyers out the door;<br>5-6-7-8, innovate don't litigate;<br>9-A-B-C, 1-2-3 is not for me;<br>D-E-F-O, look and feel have got to go<br> http://lpf.ai.mit.edu/Links/prep.ai.mit.edu/demo.final.release }~ They document the evolving nature of software industry. Applications had quietly replaced operating systems as the primary corporate battleground. In its unfulfilled quest to build a free software operating system, the GNU Project seemed hopelessly behind the times. Indeed, the very fact that Stallman had felt it necessary to put together an entirely new group dedicated to battling the "look and feel" lawsuits reinforced that obsolescence in the eyes of some observers. +The protests were notable.~{ According to a League of Programming Freedom Press, the protests were notable for featuring the first hexadecimal protest chant: \\ 1-2-3-4, toss the lawyers out the door; \\ 5-6-7-8, innovate don't litigate; \\ 9-A-B-C, 1-2-3 is not for me; \\ D-E-F-O, look and feel have got to go \\ http://lpf.ai.mit.edu/Links/prep.ai.mit.edu/demo.final.release }~ They document the evolving nature of software industry. Applications had quietly replaced operating systems as the primary corporate battleground. In its unfulfilled quest to build a free software operating system, the GNU Project seemed hopelessly behind the times. Indeed, the very fact that Stallman had felt it necessary to put together an entirely new group dedicated to battling the "look and feel" lawsuits reinforced that obsolescence in the eyes of some observers. In 1990, the John D. and Catherine T. MacArthur Foundation cerified Stallman's genius status when it granted Stallman a MacArthur fellowship, therefore making him a recipient for the organization's so-called "genius grant." The grant, a $240,000 reward for launching the GNU Project and giving voice to the free software philosophy, relieved a number of short-term concerns. First and foremost, it gave Stallman, a nonsalaried employee of the FSF who had been supporting himself through consulting contracts, the ability to devote more time to writing GNU code.~{ I use the term "writing" here loosely. About the time of the MacArthur award, Stallman began suffering chronic pain in his hands and was dictating his work to FSF-employed typists. Although some have speculated that the hand pain was the result of repetitive stress injury, or RSI, an injury common among software programmers, Stallman is not 100% sure. "It was NOT carpal tunnel syndrome," he writes. "My hand problem was in the hands themselves, not in the wrists." Stallman has since learned to work without typists after switching to a keyboard with a lighter touch. }~ @@ -1582,7 +1581,7 @@ things people like/dislike in minix, as my OS resembles it somewhat (same physical layout of the file-system (due to practical reasons) among other things). -}poem~{ See "Linux 10th Anniversary."<br> http://www.linux10.org/history/ }~ +}poem~{ See "Linux 10th Anniversary." \\ http://www.linux10.org/history/ }~ The posting drew a smattering of responses and within a month, Torvalds had posted a 0.01 version of the operating system-i.e., the earliest possible version fit for outside review-on an Internet FTP site. In the course of doing so, Torvalds had to come up with a name for the new system. On his own PC hard drive, Torvalds had saved the program as Linux, a name that paid its respects to the software convention of giving each Unix variant a name that ended with the letter X. Deeming the name too "egotistical," Torvalds changed it to Freax, only to have the FTP site manager change it back. ={Freax} @@ -1596,7 +1595,7 @@ _1 You put six months of your life into this thing and you want to make it avail When it was time to release the 0.12 version of Linux, the first to include a fully integrated version of GCC, Torvalds decided to voice his allegiance with the free software movement. He discarded the old kernel license and replaced it with the GPL. The decision triggered a porting spree, as Torvalds and his collaborators looked to other GNU programs to fold into the growing Linux stew. Within three years, Linux developers were offering their first production release, Linux 1.0, including fully modified versions of GCC, GDB, and a host of BSD tools. -By 1994, the amalgamated operating system had earned enough respect in the hacker world to make some observers wonder if Torvalds hadn't given away the farm by switching to the GPL in the project's initial months. In the first issue of Linux Journal, publisher Robert Young sat down with Torvalds for an interview. When Young asked the Finnish programmer if he felt regret at giving up private ownership of the Linux source code, Torvalds said no. "Even with 20/20 hindsight," Torvalds said, he considered the GPL "one of the very best design decisions" made during the early stages of the Linux project.~{ See Robert Young, "Interview with Linus, the Author of Linux," Linux Journal (March 1, 1994).<br> http://www.linuxjournal.com/article.php?sid=2736 }~ +By 1994, the amalgamated operating system had earned enough respect in the hacker world to make some observers wonder if Torvalds hadn't given away the farm by switching to the GPL in the project's initial months. In the first issue of Linux Journal, publisher Robert Young sat down with Torvalds for an interview. When Young asked the Finnish programmer if he felt regret at giving up private ownership of the Linux source code, Torvalds said no. "Even with 20/20 hindsight," Torvalds said, he considered the GPL "one of the very best design decisions" made during the early stages of the Linux project.~{ See Robert Young, "Interview with Linus, the Author of Linux," Linux Journal (March 1, 1994). \\ http://www.linuxjournal.com/article.php?sid=2736 }~ ={Young, Robert} % robert young entry added @@ -1628,7 +1627,7 @@ Or were they? To the pessimistically inclined, each sign of acceptance carried i % Intel index ref added -Finally, there was the curious nature of Linux itself. Unrestricted by design bugs (like GNU) and legal disputes (like BSD), Linux' high-speed evolution had been so unplanned, its success so accidental, that programmers closest to the software code itself didn't know what to make of it. More compilation album than operating system, it was comprised of a hacker medley of greatest hits: everything from GCC, GDB, and glibc (the GNU Project's newly developed C Library) to X (a Unix-based graphic user interface developed by MIT's Laboratory for Computer Science) to BSD-developed tools such as BIND (the Berkeley Internet Naming Daemon, which lets users substitute easy-to-remember Internet domain names for numeric IP addresses) and TCP/IP. The arch's capstone, of course, was the Linux kernel-itself a bored-out, super-charged version of Minix. Rather than building their operating system from scratch, Torvalds and his rapidly expanding Linux development team had followed the old Picasso adage, "good artists borrow; great artists steal." Or as Torvalds himself would later translate it when describing the secret of his success: "I'm basically a very lazy person who likes to take credit for things other people actually do."~{ Torvalds has offered this quote in many different settings. To date, however, the quote's most notable appearance is in the Eric Raymond essay, "The Cathedral and the Bazaar" (May, 1997).<br> http://www.tuxedo.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/index.html }~ +Finally, there was the curious nature of Linux itself. Unrestricted by design bugs (like GNU) and legal disputes (like BSD), Linux' high-speed evolution had been so unplanned, its success so accidental, that programmers closest to the software code itself didn't know what to make of it. More compilation album than operating system, it was comprised of a hacker medley of greatest hits: everything from GCC, GDB, and glibc (the GNU Project's newly developed C Library) to X (a Unix-based graphic user interface developed by MIT's Laboratory for Computer Science) to BSD-developed tools such as BIND (the Berkeley Internet Naming Daemon, which lets users substitute easy-to-remember Internet domain names for numeric IP addresses) and TCP/IP. The arch's capstone, of course, was the Linux kernel-itself a bored-out, super-charged version of Minix. Rather than building their operating system from scratch, Torvalds and his rapidly expanding Linux development team had followed the old Picasso adage, "good artists borrow; great artists steal." Or as Torvalds himself would later translate it when describing the secret of his success: "I'm basically a very lazy person who likes to take credit for things other people actually do."~{ Torvalds has offered this quote in many different settings. To date, however, the quote's most notable appearance is in the Eric Raymond essay, "The Cathedral and the Bazaar" (May, 1997). \\ http://www.tuxedo.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/index.html }~ ={BIND (Berkely Internet Naming Daemon);Berkely Internet Naming Daemon (BIND);C programming language:glibc;GNU Debugger (GDB):Linux and;GDB (GNU Debugger): Linux and;glibc (GNU C Library);GNU C Library (glibc);kernel (Linux);X graphic user interface;Laboratory for Computer Science:X, developing;Minix operating system:kernel, used for Linux;TCP/IP;Torvalds, Linus:Minix, reworking for Linux+2} Such laziness, while admirable from an efficiency perspective, was troubling from a political perspective. For one thing, it underlined the lack of an ideological agenda on Torvalds' part. Unlike the GNU developers, Torvalds hadn't built an operating system out of a desire to give his fellow hackers something to work with; he'd built it to have something he himself could play with. Like Tom Sawyer whitewashing a fence, Torvalds' genius lay less in the overall vision and more in his ability to recruit other hackers to speed the process. @@ -1657,7 +1656,7 @@ The message represented a dramatic about-face on Stallman's part. Until 1993, St The friend's report was correct. Built to run on 386-based machines, Linux was firmly rooted to its low-cost hardware platform. What the friend failed to report, however, was the sizable advantage Linux enjoyed as the only freely modifiable operating system in the marketplace. In other words, while Stallman spent the next three years listening to bug reports from his HURD team, Torvalds was winning over the programmers who would later uproot and replant the operating system onto new platforms. -By 1993, the GNU Project's inability to deliver a working kernel was leading to problems both within the GNU Project and within the free software movement at large. A March, 1993, a Wired magazine article by Simson Garfinkel described the GNU Project as "bogged down" despite the success of the project's many tools.~{ See Simson Garfinkel, "Is Stallman Stalled?" Wired (March, 1993). }~ Those within the project and its nonprofit adjunct, the Free Software Foundation, remember the mood as being even worse than Garfinkel's article let on. "It was very clear, at least to me at the time, that there was a window of opportunity to introduce a new operating system," says Chassell. "And once that window was closed, people would become less interested. Which is in fact exactly what happened."~{ Chassel's concern about there being a 36-month "window" for a new operating system is not unique to the GNU Project. During the early 1990s, free software versions of the Berkeley Software Distribution were held up by Unix System Laboratories' lawsuit restricting the release of BSD-derived software. While many users consider BSD offshoots such as FreeBSD and OpenBSD to be demonstrably superior to GNU/Linux both in terms of performance and security, the number of FreeBSD and OpenBSD users remains a fraction of the total GNU/Linux user population.<br>To view a sample analysis of the relative success of GNU/Linux in relation to other free software operating systems, see the essay by New Zealand hacker, Liam Greenwood, "Why is Linux Successful" (1999). }~ +By 1993, the GNU Project's inability to deliver a working kernel was leading to problems both within the GNU Project and within the free software movement at large. A March, 1993, a Wired magazine article by Simson Garfinkel described the GNU Project as "bogged down" despite the success of the project's many tools.~{ See Simson Garfinkel, "Is Stallman Stalled?" Wired (March, 1993). }~ Those within the project and its nonprofit adjunct, the Free Software Foundation, remember the mood as being even worse than Garfinkel's article let on. "It was very clear, at least to me at the time, that there was a window of opportunity to introduce a new operating system," says Chassell. "And once that window was closed, people would become less interested. Which is in fact exactly what happened."~{ Chassel's concern about there being a 36-month "window" for a new operating system is not unique to the GNU Project. During the early 1990s, free software versions of the Berkeley Software Distribution were held up by Unix System Laboratories' lawsuit restricting the release of BSD-derived software. While many users consider BSD offshoots such as FreeBSD and OpenBSD to be demonstrably superior to GNU/Linux both in terms of performance and security, the number of FreeBSD and OpenBSD users remains a fraction of the total GNU/Linux user population. \\ To view a sample analysis of the relative success of GNU/Linux in relation to other free software operating systems, see the essay by New Zealand hacker, Liam Greenwood, "Why is Linux Successful" (1999). }~ ={Garfinkel, Simson;GNU Project:kernel;Wired magazine:GNU Project and} % ={Chassell, Robert} @@ -1673,7 +1672,7 @@ Stallman cites a number of issues when explaining the delay. The Lotus and Apple "I figured, OK, the [Mach] part that has to talk to the machine has already been debugged," Stallman says, recalling the HURD team's troubles in a 2000 speech. "With that head start, we should be able to get it done faster. But instead, it turned out that debugging these asynchronous multithreaded programs was really hard. There were timing books that would clobber the files, and that's no fun. The end result was that it took many, many years to produce a test version."~{ See Maui High Performance Computing Center Speech. }~ -Whatever the excuse, or excuses, the concurrent success of the Linux-kernel team created a tense situation. Sure, the Linux kernel had been licensed under the GPL, but as Murdock himself had noted, the desire to treat Linux as a purely free software operating system was far from uniform. By late 1993, the total Linux user population had grown from a dozen or so Minix enthusiasts to somewhere between 20,000 and 100,000.~{ GNU/Linux user-population numbers are sketchy at best, which is why I've provided such a broad range. The 100,000 total comes from the Red Hat "Milestones" site,<br> http://www.redhat.com/about/corporate/milestones.html }~ What had once been a hobby was now a marketplace ripe for exploitation. Like Winston Churchill watching Soviet troops sweep into Berlin, Stallman felt an understandable set of mixed emotions when it came time to celebrate the Linux "victory."~{ I wrote this Winston Churchill analogy before Stallman himself sent me his own unsolicited comment on Churchill:<br>_1 World War II and the determination needed to win it was a very strong memory as I was growing up. Statements such as Churchill's, "We will fight them in the landing zones, we will fight them on the beaches . . . we will never surrender," have always resonated for me. }~ +Whatever the excuse, or excuses, the concurrent success of the Linux-kernel team created a tense situation. Sure, the Linux kernel had been licensed under the GPL, but as Murdock himself had noted, the desire to treat Linux as a purely free software operating system was far from uniform. By late 1993, the total Linux user population had grown from a dozen or so Minix enthusiasts to somewhere between 20,000 and 100,000.~{ GNU/Linux user-population numbers are sketchy at best, which is why I've provided such a broad range. The 100,000 total comes from the Red Hat "Milestones" site, \\ http://www.redhat.com/about/corporate/milestones.html }~ What had once been a hobby was now a marketplace ripe for exploitation. Like Winston Churchill watching Soviet troops sweep into Berlin, Stallman felt an understandable set of mixed emotions when it came time to celebrate the Linux "victory."~{ I wrote this Winston Churchill analogy before Stallman himself sent me his own unsolicited comment on Churchill: \\ _1 World War II and the determination needed to win it was a very strong memory as I was growing up. Statements such as Churchill's, "We will fight them in the landing zones, we will fight them on the beaches . . . we will never surrender," have always resonated for me. }~ Although late to the party, Stallman still had clout. As soon as the FSF announced that it would lend its money and moral support to Murdock's software project, other offers of support began rolling in. Murdock dubbed the new project Debian-a compression of his and his wife, Deborah's, names-and within a few weeks was rolling out the first distribution. "[Richard's support] catapulted Debian almost overnight from this interesting little project to something people within the community had to pay attention to," Murdock says. ={Debian+19} @@ -1685,7 +1684,7 @@ In January of 1994, Murdock issued the " Debian Manifesto." Written in the spiri _1 The Free Software Foundation plays an extremely important role in the future of Debian. By the simple fact that they will be distributing it, a message is sent to the world that Linux is not a commercial product and that it never should be, but that this does not mean that Linux will never be able to compete commercially. For those of you who disagree, I challenge you to rationalize the success of GNU Emacs and GCC, which are not commercial software but which have had quite an impact on the commercial market regardless of that fact. -_1 The time has come to concentrate on the future of Linux rather than on the destructive goal of enriching oneself at the expense of the entire Linux community and its future. The development and distribution of Debian may not be the answer to the problems that I have outlined in the Manifesto, but I hope that it will at least attract enough attention to these problems to allow them to be solved.~{ See Ian Murdock, "A Brief History of Debian," (January 6, 1994): Appendix A, "The Debian Manifesto."<br> http://www.debian.org/doc/manuals/project-history/apA.html }~ +_1 The time has come to concentrate on the future of Linux rather than on the destructive goal of enriching oneself at the expense of the entire Linux community and its future. The development and distribution of Debian may not be the answer to the problems that I have outlined in the Manifesto, but I hope that it will at least attract enough attention to these problems to allow them to be solved.~{ See Ian Murdock, "A Brief History of Debian," (January 6, 1994): Appendix A, "The Debian Manifesto." \\ http://www.debian.org/doc/manuals/project-history/apA.html }~ Shortly after the Manifesto's release, the Free Software Foundation made its first major request. Stallman wanted Murdock to call its distribution "GNU/Linux." At first, Murdock says, Stallman had wanted to use the term " Lignux"-"as in Linux with GNU at the heart of it"-but a sample testing of the term on Usenet and in various impromptu hacker focus groups had merited enough catcalls to convince Stallman to go with the less awkward GNU/Linux. ={Lignux (Linux with GNU)} @@ -1698,7 +1697,7 @@ The deepest split, Murdock says, was over glibc. Short for GNU C Library, glibc In the hacker world, forks are an interesting phenomenon. Although the hacker ethic permits a programmer to do anything he wants with a given program's source code, most hackers prefer to pour their innovations into a central source-code file or "tree" to ensure compatibility with other people's programs. To fork glibc this early in the development of Linux would have meant losing the potential input of hundreds, even thousands, of Linux developers. It would also mean growing incompatibility between Linux and the GNU system that Stallman and the GNU team still hoped to develop. ={forks (code)+3;tree (source code)} -As leader of the GNU Project, Stallman had already experienced the negative effects of a software fork in 1991. A group of Emacs developers working for a software company named Lucid had a falling out over Stallman's unwillingness to fold changes back into the GNU Emacs code base. The fork had given birth to a parallel version, Lucid Emacs, and hard feelings all around.~{ Jamie Zawinski, a former Lucid programmer who would go on to head the Mozilla development team, has a web site that documents the Lucid/GNU Emacs fork, titled, "The Lemacs/FSFmacs Schism."<br> http://www.jwz.org/doc/lemacs.html }~ +As leader of the GNU Project, Stallman had already experienced the negative effects of a software fork in 1991. A group of Emacs developers working for a software company named Lucid had a falling out over Stallman's unwillingness to fold changes back into the GNU Emacs code base. The fork had given birth to a parallel version, Lucid Emacs, and hard feelings all around.~{ Jamie Zawinski, a former Lucid programmer who would go on to head the Mozilla development team, has a web site that documents the Lucid/GNU Emacs fork, titled, "The Lemacs/FSFmacs Schism." \\ http://www.jwz.org/doc/lemacs.html }~ ={Emacs text editor:Lucid software company and;GNU Emacs:Lucid software company and;Lucid software company} Murdock says Debian was mounting work on a similar fork in glibc source code that motivated Stallman to insist on adding the GNU prefix when Debian rolled out its software distribution. "The fork has since converged. Still, at the time, there was a concern that if the Linux community saw itself as a different thing as the GNU community, it might be a force for disunity." @@ -1749,7 +1748,7 @@ Ready or not. In November , 1995, Peter Salus, a member of the Free Software Foundation and author of the 1994 book, A Quarter Century of Unix, issued a call for papers to members of the GNU Project's "system-discuss" mailing list. Salus, the conference's scheduled chairman, wanted to tip off fellow hackers about the upcoming Conference on Freely Redistributable Software in Cambridge, Massachusetts. Slated for February, 1996 and sponsored by the Free Software Foundation, the event promised to be the first engineering conference solely dedicated to free software and, in a show of unity with other free software programmers, welcomed papers on "any aspect of GNU, Linux, NetBSD, 386BSD, FreeBSD, Perl, Tcl/tk, and other tools for which the code is accessible and redistributable." Salus wrote: ={Free Software Foundation (FSF);FSF (Free Software Foundation);FreeBSD;Conference on Freely Redistributable Software+1;Linux;NetBSD;Perl programming language;386BSD;Salus, Peter+4} -_1 Over the past 15 years, free and low-cost software has become ubiquitous. This conference will bring together implementers of several different types of freely redistributable software and publishers of such software (on various media). There will be tutorials and refereed papers, as well as keynotes by Linus Torvalds and Richard Stallman.~{ See Peter Salus, "FYI-Conference on Freely Redistributable Software, 2/2, Cambridge" (1995) (archived by Terry Winograd).<br> http://hci.stanford.edu/pcd-archives/pcd-fyi/1995/0078.html }~ +_1 Over the past 15 years, free and low-cost software has become ubiquitous. This conference will bring together implementers of several different types of freely redistributable software and publishers of such software (on various media). There will be tutorials and refereed papers, as well as keynotes by Linus Torvalds and Richard Stallman.~{ See Peter Salus, "FYI-Conference on Freely Redistributable Software, 2/2, Cambridge" (1995) (archived by Terry Winograd). \\ http://hci.stanford.edu/pcd-archives/pcd-fyi/1995/0078.html }~ One of the first people to receive Salus' email was conference committee member Eric S. Raymond. Although not the leader of a project or company like the various other members of the list, Raymond had built a tidy reputation within the hacker community as a major contributor to GNU Emacs and as editor of /{The New Hacker Dictionary}/, a book version of the hacking community's decade-old Jargon File. ={New Hacker Dictionary, The;Raymond, Eric:open source and+56} @@ -1758,7 +1757,7 @@ For Raymond, the 1996 conference was a welcome event. Active in the GNU Project Despite the falling out, Raymond remained active in the free software community. So much so that when Salus suggested a conference pairing Stallman and Torvalds as keynote speakers, Raymond eagerly seconded the idea. With Stallman representing the older, wiser contingent of ITS/Unix hackers and Torvalds representing the younger, more energetic crop of Linux hackers, the pairing indicated a symbolic show of unity that could only be beneficial, especially to ambitious younger (i.e., below 40) hackers such as Raymond. "I sort of had a foot in both camps," Raymond says. -By the time of the conference, the tension between those two camps had become palpable. Both groups had one thing in common, though: the conference was their first chance to meet the Finnish wunderkind in the flesh. Surprisingly, Torvalds proved himself to be a charming, affable speaker. Possessing only a slight Swedish accent, Torvalds surprised audience members with his quick, self-effacing wit.~{ Although Linus Torvalds is Finnish, his mother tongue is Swedish. "The Rampantly Unofficial Linus FAQ" offers a brief explanation:<br>_1 Finland has a significant (about 6%) Swedish-speaking minority population. They call themselves "finlandssvensk" or "finlandssvenskar" and consider themselves Finns; many of their families have lived in Finland for centuries. Swedish is one of Finland's two official languages.<br> http://tuxedo.org/~esr/faqs/linus/ }~ Even more surprising, says Raymond, was Torvalds' equal willingness to take potshots at other prominent hackers, including the most prominent hacker of all, Richard Stallman. By the end of the conference, Torvalds' half-hacker, half-slacker manner was winning over older and younger conference-goers alike. +By the time of the conference, the tension between those two camps had become palpable. Both groups had one thing in common, though: the conference was their first chance to meet the Finnish wunderkind in the flesh. Surprisingly, Torvalds proved himself to be a charming, affable speaker. Possessing only a slight Swedish accent, Torvalds surprised audience members with his quick, self-effacing wit.~{ Although Linus Torvalds is Finnish, his mother tongue is Swedish. "The Rampantly Unofficial Linus FAQ" offers a brief explanation: \\ _1 Finland has a significant (about 6%) Swedish-speaking minority population. They call themselves "finlandssvensk" or "finlandssvenskar" and consider themselves Finns; many of their families have lived in Finland for centuries. Swedish is one of Finland's two official languages. \\ http://tuxedo.org/~esr/faqs/linus/ }~ Even more surprising, says Raymond, was Torvalds' equal willingness to take potshots at other prominent hackers, including the most prominent hacker of all, Richard Stallman. By the end of the conference, Torvalds' half-hacker, half-slacker manner was winning over older and younger conference-goers alike. "It was a pivotal moment," recalls Raymond. "Before 1996, Richard was the only credible claimant to being the ideological leader of the entire culture. People who dissented didn't do so in public. The person who broke that taboo was Torvalds." @@ -1776,7 +1775,7 @@ As a former GNU Project member, Raymond sensed an added dynamic to the tension b For Raymond, the defection merely confirmed a growing suspicion: recent delays such as the HURD and recent troubles such as the Lucid-Emacs schism reflected problems normally associated with software project management, not software code development. Shortly after the Freely Redistributable Software Conference, Raymond began working on his own pet software project, a popmail utility called "fetchmail." Taking a cue from Torvalds, Raymond issued his program with a tacked-on promise to update the source code as early and as often as possible. When users began sending in bug reports and feature suggestions, Raymond, at first anticipating a tangled mess, found the resulting software surprisingly sturdy. Analyzing the success of the Torvalds approach, Raymond issued a quick analysis: using the Internet as his "petri dish" and the harsh scrutiny of the hacker community as a form of natural selection, Torvalds had created an evolutionary model free of central planning. ={fetchmail;FreeBSD;Conference on Freely Redistributable Software;Internet} -What's more, Raymond decided, Torvalds had found a way around Brooks' Law. First articulated by Fred P. Brooks, manager of IBM's OS/360 project and author of the 1975 book, The Mythical Man-Month, Brooks' Law held that adding developers to a project only resulted in further project delays. Believing as most hackers that software, like soup, benefits from a limited number of cooks, Raymond sensed something revolutionary at work. In inviting more and more cooks into the kitchen, Torvalds had actually found away to make the resulting software better.~{ Brooks' Law is the shorthand summary of the following quote taken from Brooks' book:<br>_1 Since software construction is inherently a systems effort-an exercise in complex interrelationships-communication effort is great, and it quickly dominates the decrease in individual task time brought about by partitioning. Adding more men then lengthens, not shortens, the schedule.<br>See Fred P. Brooks, The Mythical Man-Month (Addison Wesley Publishing, 1995) }~ +What's more, Raymond decided, Torvalds had found a way around Brooks' Law. First articulated by Fred P. Brooks, manager of IBM's OS/360 project and author of the 1975 book, The Mythical Man-Month, Brooks' Law held that adding developers to a project only resulted in further project delays. Believing as most hackers that software, like soup, benefits from a limited number of cooks, Raymond sensed something revolutionary at work. In inviting more and more cooks into the kitchen, Torvalds had actually found away to make the resulting software better.~{ Brooks' Law is the shorthand summary of the following quote taken from Brooks' book: \\ _1 Since software construction is inherently a systems effort-an exercise in complex interrelationships-communication effort is great, and it quickly dominates the decrease in individual task time brought about by partitioning. Adding more men then lengthens, not shortens, the schedule. \\ See Fred P. Brooks, The Mythical Man-Month (Addison Wesley Publishing, 1995) }~ ={Brooks, Fred P.;Mythical Man-Month, The (Brooks)} Raymond put his observations on paper. He crafted them into a speech, which he promptly delivered before a group of friends and neighbors in Chester County, Pennsylvania. Dubbed " The Cathedral and the Bazaar," the speech contrasted the management styles of the GNU Project with the management style of Torvalds and the kernel hackers. Raymond says the response was enthusiastic, but not nearly as enthusiastic as the one he received during the 1997 Linux Kongress, a gathering of Linux users in Germany the next spring. @@ -1814,7 +1813,7 @@ While in California, Raymond also managed to squeeze in a visit to VA Research, Peterson, whose organization had taken an active interest in advancing the free software cause, offered an alternative: open source. -Looking back, Peterson says she came up with the open source term while discussing Netscape's decision with a friend in the public relations industry. She doesn't remember where she came upon the term or if she borrowed it from another field, but she does remember her friend disliking the term.~{ See Malcolm Maclachlan, "Profit Motive Splits Open Source Movement," TechWeb News (August 26, 1998).<br> http://content.techweb.com/wire/story/TWB19980824S0012 }~ +Looking back, Peterson says she came up with the open source term while discussing Netscape's decision with a friend in the public relations industry. She doesn't remember where she came upon the term or if she borrowed it from another field, but she does remember her friend disliking the term.~{ See Malcolm Maclachlan, "Profit Motive Splits Open Source Movement," TechWeb News (August 26, 1998). \\ http://content.techweb.com/wire/story/TWB19980824S0012 }~ At the meeting, Peterson says, the response was dramatically different. "I was hesitant about suggesting it," Peterson recalls. "I had no standing with the group, so started using it casually, not highlighting it as a new term." To Peterson's surprise, the term caught on. By the end of the meeting, most of the attendees, including Raymond, seemed pleased by it. @@ -1871,7 +1870,7 @@ http://www.opensource.org/docs/definition.html }~ Perens would later resign from the OSI, expressing regret that the organization had set itself up in opposition to Stallman and the FSF. Still, looking back on the need for a free software definition outside the Free Software Foundation's auspices, Perens understands why other hackers might still feel the need for distance. "I really like and admire Richard," says Perens. "I do think Richard would do his job better if Richard had more balance. That includes going away from free software for a couple of months." -Stallman's monomaniacal energies would do little to counteract the public-relations momentum of open source proponents. In August of 1998, when chip-maker Intel purchased a stake in GNU/Linux vendor Red Hat, an accompanying New York Times article described the company as the product of a movement "known alternatively as free software and open source."~{ See Amy Harmon, "For Sale: Free Operating System," New York Times (September 28, 1998).<br> http://www.nytimes.com/library/tech/98/09/biztech/articles/28linux.html }~ Six months later, a John Markoff article on Apple Computer was proclaiming the company's adoption of the "open source" Apache server in the article headline.~{ See John Markoff, "Apple Adopts `Open Source' for its Server Computers," New York Times (March 17, 1999).<br> http://www.nytimes.com/library/tech/99/03/biztech/articles/17apple.html }~ +Stallman's monomaniacal energies would do little to counteract the public-relations momentum of open source proponents. In August of 1998, when chip-maker Intel purchased a stake in GNU/Linux vendor Red Hat, an accompanying New York Times article described the company as the product of a movement "known alternatively as free software and open source."~{ See Amy Harmon, "For Sale: Free Operating System," New York Times (September 28, 1998). \\ http://www.nytimes.com/library/tech/98/09/biztech/articles/28linux.html }~ Six months later, a John Markoff article on Apple Computer was proclaiming the company's adoption of the "open source" Apache server in the article headline.~{ See John Markoff, "Apple Adopts `Open Source' for its Server Computers," New York Times (March 17, 1999). \\ http://www.nytimes.com/library/tech/99/03/biztech/articles/17apple.html }~ ={Apache web server;Apple Computers:open source software and;Intel;Markoff, John;Red Hat Inc.:success of+1} Such momentum would coincide with the growing momentum of companies that actively embraced the "open source" term. By August of 1999, Red Hat, a company that now eagerly billed itself as "open source," was selling shares on Nasdaq. In December, VA Linux-formerly VA Research-was floating its own IPO to historical effect. Opening at $30 per share, the company's stock price exploded past the $300 mark in initial trading only to settle back down to the $239 level. Shareholders lucky enough to get in at the bottom and stay until the end experienced a 698% increase in paper wealth, a Nasdaq record. @@ -1881,7 +1880,7 @@ Such momentum would coincide with the growing momentum of companies that activel Among those lucky shareholders was Eric Raymond, who, as a company board member since the Mozilla launch, had received 150,000 shares of VA Linux stock. Stunned by the realization that his essay contrasting the Stallman-Torvalds managerial styles had netted him $36 million in potential wealth, Raymond penned a follow-up essay. In it, Raymond mused on the relationship between the hacker ethic and monetary wealth: -_1 Reporters often ask me these days if I think the open-source community will be corrupted by the influx of big money. I tell them what I believe, which is this: commercial demand for programmers has been so intense for so long that anyone who can be seriously distracted by money is already gone. Our community has been self-selected for caring about other things-accomplishment, pride, artistic passion, and each other.~{ See Eric Raymond, "Surprised by Wealth," Linux Today (December 10, 1999).<br> http://linuxtoday.com/news_story.php3?ltsn=1999-12-10-001-05-NW-LF }~ +_1 Reporters often ask me these days if I think the open-source community will be corrupted by the influx of big money. I tell them what I believe, which is this: commercial demand for programmers has been so intense for so long that anyone who can be seriously distracted by money is already gone. Our community has been self-selected for caring about other things-accomplishment, pride, artistic passion, and each other.~{ See Eric Raymond, "Surprised by Wealth," Linux Today (December 10, 1999). \\ http://linuxtoday.com/news_story.php3?ltsn=1999-12-10-001-05-NW-LF }~ Whether or not such comments allayed suspicions that Raymond and other open source proponents had simply been in it for the money, they drove home the open source community's ultimate message: all you needed to sell the free software concept is a friendly face and a sensible message. Instead of fighting the marketplace head-on as Stallman had done, Raymond, Torvalds, and other new leaders of the hacker community had adopted a more relaxed approach-ignoring the marketplace in some areas, leveraging it in others. Instead of playing the role of high-school outcasts, they had played the game of celebrity, magnifying their power in the process. @@ -2118,7 +2117,7 @@ During my research, I came across an essay titled "Freedom-Or Copyright?" Writte % additional reference to the Digital Millenium Copyright Act -_1 We still have the same old freedoms in using paper books. But if e-books replace printed books, that exception will do little good. With "electronic ink," which makes it possible to download new text onto an apparently printed piece of paper, even newspapers could become ephemeral. Imagine: no more used book stores; no more lending a book to your friend; no more borrowing one from the public library-no more "leaks" that might give someone a chance to read without paying. (And judging from the ads for Microsoft Reader, no more anonymous purchasing of books either.) This is the world publishers have in mind for us.~{ See "Safari Tech Books Online; Subscriber Agreement: Terms of Service."<br> http://safari.oreilly.com/mainhlp.asp?help=service }~ +_1 We still have the same old freedoms in using paper books. But if e-books replace printed books, that exception will do little good. With "electronic ink," which makes it possible to download new text onto an apparently printed piece of paper, even newspapers could become ephemeral. Imagine: no more used book stores; no more lending a book to your friend; no more borrowing one from the public library-no more "leaks" that might give someone a chance to read without paying. (And judging from the ads for Microsoft Reader, no more anonymous purchasing of books either.) This is the world publishers have in mind for us.~{ See "Safari Tech Books Online; Subscriber Agreement: Terms of Service." \\ http://safari.oreilly.com/mainhlp.asp?help=service }~ Needless to say, the essay caused some concern. Neither Tracy nor I had discussed the software her company would use nor had we discussed the type of copyright that would govern the e-book's usage. I mentioned the Technology Review article and asked if she could give me information on her company's e-book policies. Tracy promised to get back to me. @@ -2209,9 +2208,9 @@ In July, a full year after the original email from Tracy, I got a call from Henn Sure enough, the issue did come up. I learned through Henning that O'Reilly intended to publish the biography both as a book and as part of its new Safari Tech Books Online subscription service. The Safari user license would involve special restrictions,1 Henning warned, but O'Reilly was willing to allow for a copyright that permitted users to copy and share and the book's text regardless of medium. Basically, as author, I had the choice between two licenses: the Open Publication License or the GNU Free Documentation License. ={Open Publication License (OPL)+8;OPL (Open Publication License)+8;Safari Tech Books Online subscription service} -I checked out the contents and background of each license. The Open Publication License (OPL)~{ See "The Open Publication License: Draft v1.0" (June 8, 1999).<br> http://opencontent.org/openpub/ }~ gives readers the right to reproduce and distribute a work, in whole or in part, in any medium "physical or electronic," provided the copied work retains the Open Publication License. It also permits modification of a work, provided certain conditions are met. Finally, the Open Publication License includes a number of options, which, if selected by the author, can limit the creation of "substantively modified" versions or book-form derivatives without prior author approval. +I checked out the contents and background of each license. The Open Publication License (OPL)~{ See "The Open Publication License: Draft v1.0" (June 8, 1999). \\ http://opencontent.org/openpub/ }~ gives readers the right to reproduce and distribute a work, in whole or in part, in any medium "physical or electronic," provided the copied work retains the Open Publication License. It also permits modification of a work, provided certain conditions are met. Finally, the Open Publication License includes a number of options, which, if selected by the author, can limit the creation of "substantively modified" versions or book-form derivatives without prior author approval. -The GNU Free Documentation License (GFDL),~{ See "The GNU Free Documentation License: Version 1.1" (March, 2000).<br> http://www.gnu.org/copyleft/fdl.html }~ meanwhile, permits the copying and distribution of a document in any medium, provided the resulting work carries the same license. It also permits the modification of a document provided certain conditions. Unlike the OPL, however, it does not give authors the option to restrict certain modifications. It also does not give authors the right to reject modifications that might result in a competitive book product. It does require certain forms of front- and back-cover information if a party other than the copyright holder wishes to publish more than 100 copies of a protected work, however. +The GNU Free Documentation License (GFDL),~{ See "The GNU Free Documentation License: Version 1.1" (March, 2000). \\ http://www.gnu.org/copyleft/fdl.html }~ meanwhile, permits the copying and distribution of a document in any medium, provided the resulting work carries the same license. It also permits the modification of a document provided certain conditions. Unlike the OPL, however, it does not give authors the option to restrict certain modifications. It also does not give authors the right to reject modifications that might result in a competitive book product. It does require certain forms of front- and back-cover information if a party other than the copyright holder wishes to publish more than 100 copies of a protected work, however. ={GFDL (GNU Free Documentation License)+1;GNU Free Documentation License (GFDL)+1} In the course of researching the licenses, I also made sure to visit the GNU Project web page titled "Various Licenses and Comments About Them."~{ See http://www.gnu.org/philosophy/license-list.html }~ On that page, I found a Stallman critique of the Open Publication License. Stallman's critique related to the creation of modified works and the ability of an author to select either one of the OPL's options to restrict modification. If an author didn't want to select either option, it was better to use the GFDL instead, Stallman noted, since it minimized the risk of the nonselected options popping up in modified versions of a document. diff --git a/data/doc/sisu/markup-samples/v3/samples/free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst b/data/doc/sisu/markup-samples/v3/samples/free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst index 43d64ab4..4b040a75 100644 --- a/data/doc/sisu/markup-samples/v3/samples/free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst +++ b/data/doc/sisu/markup-samples/v3/samples/free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst @@ -14,19 +14,19 @@ :license: Published under the GNU Free Documentation License. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License." @classify: - :topic_register: SiSU:markup sample:book;copyright;GNU/Linux:GPL|copyleft|free software;free software;Software:Software Libré;GPL;Linux:GNU|Software Libré;book:biography;programming + :topic_register: SiSU markup sample:book:biography;book:biography;copyright;GNU/Linux:GPL|copyleft|free software;free software;Software:Software Libré;GPL;Linux:GNU|Software Libré;programming @links: - {Home and Source}http://faifzilla.org/ - {@ Wikipedia}http://en.wikipedia.org/wiki/Free_as_in_Freedom:_Richard_Stallman%27s_Crusade_for_Free_Software - {@ Amazon.com}http://www.amazon.com/gp/product/0596002874 - {@ Barnes & Noble}http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?isbn=0596002874 - {SiSU}http://sisudoc.org/ - {sources / git}http://sources.sisudoc.org/ + { Home and Source }http://faifzilla.org/ + { @ Wikipedia }http://en.wikipedia.org/wiki/Free_as_in_Freedom:_Richard_Stallman%27s_Crusade_for_Free_Software + { @ Amazon.com }http://www.amazon.com/gp/product/0596002874 + { @ Barnes & Noble }http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?isbn=0596002874 + { SiSU }http://sisudoc.org/ + { sources / git }http://sources.sisudoc.org/ @make: - :skin: skin_rms2 :breaks: new=:A,:B,:C,1 + :skin: skin_rms2 % http://static.fsf.org/nosvn/faif-2.0.pdf % http://www.scribd.com/doc/55232810/Free-as-in-Freedom-Richard-Stallman diff --git a/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_description.sst b/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_description.sst index 9060160a..ec16f4f6 100644 --- a/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_description.sst +++ b/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_description.sst @@ -39,7 +39,7 @@ :breaks: new=C; break=1 :skin: skin_sisu :bold: /Debian|Ruby|SiSU|ocn|object citation numbering|granular search|rant|utf-?8|WARNING/ - :italics: /Linux|FreeBSD|Dragonfly|Perl|LaTeX|Postgresql|PostgreSQL|Postgres|sqlite|SQL|PHP|xml|XML|Ion|g?vim|ascii|pdf|xhtml|pdflatex|pgsql|Postscript|texinfo|metadata|metatags|metaverse|rant|rake|YAML|object citation system|ocn|object citation numbering|granular search|Dublin Core|Lex Mercatoria|Project Gutenberg|Slashdot/i + :italics: /Linux|FreeBSD|Dragonfly|Perl|LaTeX|Postgresql|PostgreSQL|Postgres|sqlite|SQL|PHP|xml|XML|Ion|g?vim|ascii|pdf|xhtml|pdflatex|pgsql|Postscript|texinfo|metadata|metatags|metaverse|rant|rake|YAML|object citation system|ocn|object citation numbering|granular search|Dublin Core|Lex Mercatoria/i :A~? @title @creator diff --git a/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_markup.sst b/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_markup.sst index ddc0a3d4..e3fbb226 100644 --- a/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_markup.sst +++ b/data/doc/sisu/markup-samples/v3/sisu_manual/sisu_markup.sst @@ -247,7 +247,6 @@ code{ :isbn: [ISBN] :loc: [Library of Congress classification] :dewey: [Dewey classification - :pg: [Project Gutenberg text number] }code diff --git a/data/doc/sisu/markup-samples/v4/samples/_sisu/sisu_document_make b/data/doc/sisu/markup-samples/v4/samples/_sisu/sisu_document_make new file mode 100644 index 00000000..85e583e1 --- /dev/null +++ b/data/doc/sisu/markup-samples/v4/samples/_sisu/sisu_document_make @@ -0,0 +1,9 @@ +@make: + :breaks: break=1 + :home_button_text: {SiSU}http://sisudoc.org; {sources / git}http://sources.sisudoc.org/ +% :footer: {SiSU}http://sisudoc.org; {sources / git}http://sources.sisudoc.org/ +% :home_button_image: {sisu.png }http://sisudoc.org + +@links:+ + {SiSU}http://sisudoc.org + {sources / git}http://sources.sisudoc.org/ diff --git a/data/doc/sisu/markup-samples/v4/samples/free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst b/data/doc/sisu/markup-samples/v4/samples/free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst index 97bc59c0..2d38902a 100644 --- a/data/doc/sisu/markup-samples/v4/samples/free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst +++ b/data/doc/sisu/markup-samples/v4/samples/free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst @@ -25,11 +25,12 @@ { @ Wikipedia }http://en.wikipedia.org/wiki/Free_as_in_Freedom:_Richard_Stallman%27s_Crusade_for_Free_Software { @ Amazon.com }http://www.amazon.com/gp/product/0596002874 { @ Barnes & Noble }http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?isbn=0596002874 - { SiSU }http://sisudoc.org/ - { sources / git }http://sources.sisudoc.org/ @make: :breaks: new=:A,:B,:C,1 + :home_button_image: {free_as_in_freedom.png }http://stallman.org/ + :home_button_text: {Free as in Freedom}http://stallman.org/; {Free Software Foundation}http://www.fsf.org + :footer: {Free as in Freedom}http://stallman.org/; {Free Software Foundation}http://www.fsf.org :A~ @title @author diff --git a/data/doc/sisu/markup-samples/v4/samples/free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst b/data/doc/sisu/markup-samples/v4/samples/free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst index f071971e..c99cb10e 100644 --- a/data/doc/sisu/markup-samples/v4/samples/free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst +++ b/data/doc/sisu/markup-samples/v4/samples/free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst @@ -17,15 +17,15 @@ :topic_register: SiSU markup sample:book:biography;book:biography;copyright;GNU/Linux:GPL|copyleft|free software;free software;Software:Software Libré;GPL;Linux:GNU|Software Libré;programming @links: - {Home and Source}http://faifzilla.org/ - {@ Wikipedia}http://en.wikipedia.org/wiki/Free_as_in_Freedom:_Richard_Stallman%27s_Crusade_for_Free_Software - {@ Amazon.com}http://www.amazon.com/gp/product/0596002874 - {@ Barnes & Noble}http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?isbn=0596002874 - {CONTENT, Cory Doctorow @ SiSU}http://www.jus.uio.no/sisu/content.cory_doctorow - {Little Brother, Cory Doctorow @ SiSU}http://www.jus.uio.no/sisu/little_brother.cory_doctorow + { Home and Source }http://faifzilla.org/ + { @ Wikipedia }http://en.wikipedia.org/wiki/Free_as_in_Freedom:_Richard_Stallman%27s_Crusade_for_Free_Software + { @ Amazon.com }http://www.amazon.com/gp/product/0596002874 + { @ Barnes & Noble }http://search.barnesandnoble.com/booksearch/isbnInquiry.asp?isbn=0596002874 @make: :breaks: new=:A,:B,:C,1 + :home_button_text: {Free as in Freedom 2.0}http://stallman.org/; {Free Software Foundation}http://www.fsf.org + :footer: {Free as in Freedom 2.0}http://stallman.org/; {Free Software Foundation}http://www.fsf.org % http://static.fsf.org/nosvn/faif-2.0.pdf % http://www.scribd.com/doc/55232810/Free-as-in-Freedom-Richard-Stallman diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/_sisu/sisu_document_make b/data/doc/sisu/markup-samples/v4/sisu_manual/_sisu/sisu_document_make new file mode 100644 index 00000000..17c6bbf8 --- /dev/null +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/_sisu/sisu_document_make @@ -0,0 +1,20 @@ +@make: + :num_top: 1 + :breaks: new=C; break=1 + :bold: /Debian|Ruby|SiSU/ + :italics: /Linux|GPL|GPLv3|LaTeX|PostgreSQL|SQLite|SQL|Vim|ascii|plaintext|UTF-?8|HTML|XHTML|XML|EPUB|OpenDocument|ODF|ODT|PDF|pgSQL|TeXinfo|YAML|YML|ocn|object citation system|object citation numbering|granular search|Dublin Core/ + :substitute: /${debian_stable}/,'*{Wheezy}*' /${debian_testing}/,'*{Jessie}*' + :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org + :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org + +@links: + { SiSU Homepage }http://www.sisudoc.org/ + { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ + { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html + { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html + { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html + { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary + { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ + { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html + { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org + { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu.ssm b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu.ssm index b3b3ae58..79703fef 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu.ssm +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu.ssm @@ -21,23 +21,8 @@ :topic_register: SiSU:manual;electronic documents:SiSU:manual :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - @make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :manpage: name=sisu - documents: markup, structuring, publishing in multiple standard formats, and search; synopsis=sisu [-abCcDdeFGghIikLMmNnoPpQqRrSsTtUuVvWwXxYyZ_0-9] [filename/wildcard] . sisu [-Ddcv] [instruction] [filename/wildcard] . sisu [-CcFLSVvW] . sisu [operations] . sisu --v4 [operations] . sisu --v3 [operations] . sisu2 [operations] + :manpage: name=sisu - documents: markup, structuring, publishing in multiple standard formats, and search; synopsis=sisu [-short-options|--long-options] [filename/wildcard] . sisu [-abCcDdeFGghIikLMmNnoPpQqRrSsTtUuVvWwXxYyZ_0-9] [filename/wildcard] . sisu --txt --html --epub --odt --pdf --wordmap --sqlite --manpage --texinfo --sisupod --source --qrcode [filename/wildcard] . sisu [-Ddcv] [instruction] [filename/wildcard] . sisu --pg (--createdb|update [filename/wildcard]|--dropall) . sisu [operations] . sisu [-CcFLSVvW] . sisu (--configure|--webrick|--sample-search-form) :A~ @title @creator @@ -85,14 +70,4 @@ << sisu_webrick.sst -<< sisu_remote.sst - -<< sisu_quickstart.sst - -<< sisu_syntax_highlighting.sst - -<< sisu_how.ssi - << sisu_short_feature_summary.ssi - -<< sisu_help_sources.sst diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_commands.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_commands.sst index 068942b5..0f3c0b8e 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_commands.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_commands.sst @@ -21,23 +21,6 @@ :topic_register: electronic documents:SiSU:document:commands;SiSU:manual:commands;electronic documents:SiSU:manual:commands;SiSU:document:commands;SiSU:document:commands :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator :B~? SiSU Commands @@ -377,9 +360,12 @@ strips output text of editor endnotes~[+ square brackets ]~ denoted by dagger/pl 1~commands_database database commands -dbi - database interface +!_ dbi - database interface --D or --pgsql set for PostgreSQL -d or --sqlite default set for SQLite -d is modifiable with --db=[database type (PgSQL or SQLite)] +!_ -D or --pgsql +set for PostgreSQL +!_ -d or --sqlite +default set for SQLite -d is modifiable with --db=[database type (PgSQL or SQLite)] !_ --pg -v --createall \\ initial step, creates required relations (tables, indexes) in existing PostgreSQL database (a database should be created manually and given the same name as working directory, as requested) (rb.dbi) [ -dv --createall SQLite equivalent] it may be necessary to run sisu -Dv --createdb initially NOTE: at the present time for PostgreSQL it may be necessary to manually create the database. The command would be 'createdb [database name]' where database name would be SiSU_[present working directory name (without path)]. Please use only alphanumerics and underscores. diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_config.ssi b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_config.ssi index 853580b3..3c29f995 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_config.ssi +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_config.ssi @@ -11,7 +11,7 @@ :created: 2002-08-28 :issued: 2002-08-28 :available: 2002-08-28 - :modified: 2011-02-07 + :modified: 2011-12-12 @rights: :copyright: Copyright (C) Ralph Amissah 2007 @@ -23,19 +23,9 @@ 1~config Configuration -2~ Determining the Current Configuration +2~ Configuration files -Information on the current configuration of SiSU should be available with the help command: - -_1 sisu -v - -which is an alias for: - -_1 sisu --help env - -Either of these should be executed from within a directory that contains sisu markup source documents. - -2~ Configuration files (config.yml) +3~ config.yml SiSU configration parameters are adjusted in the configuration file, which can be used to override the defaults set. This includes such things as which directory interim processing should be done in and where the generated output should be placed. @@ -43,10 +33,16 @@ The SiSU configuration file is a yaml file, which means indentation is significa SiSU resource configuration is determined by looking at the following files if they exist: +_1 ./_sisu/v4/sisurc.yml + _1 ./_sisu/sisurc.yml +_1 ~/.sisu/v4/sisurc.yml + _1 ~/.sisu/sisurc.yml +_1 /etc/sisu/v4/sisurc.yml + _1 /etc/sisu/sisurc.yml The search is in the order listed, and the first one found is used. @@ -57,3 +53,23 @@ Configuration determines the output and processing directories and the database If SiSU is installed a sample sisurc.yml may be found in /etc/sisu/sisurc.yml +3~ sisu_document_make + +Most sisu document headers relate to metadata, the exception is the @make: header which provides processing related information. The default contents of the @make header may be set by placing them in a file sisu_document_make. + +The search order is as for resource configuration: + +_1 ./_sisu/v4/sisu_document_make + +_1 ./_sisu/sisu_document_make + +_1 ~/.sisu/v4/sisu_document_make + +_1 ~/.sisu/sisu_document_make + +_1 /etc/sisu/v4/sisu_document_make + +_1 /etc/sisu/sisu_document_make + +A sample sisu_document_make can be found in the _sisu/ directory under along with the provided sisu markup samples. + diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_description.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_description.sst index 06a630e8..9f8fdcd8 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_description.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_description.sst @@ -21,24 +21,6 @@ :topic_register: electronic documents;SiSU:document:description;sisu:document:description :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Debian|Ruby|SiSU|ocn|object citation numbering|granular search|rant|utf-?8|WARNING/ - :italics: /Linux|FreeBSD|Dragonfly|Perl|LaTeX|Postgresql|PostgreSQL|Postgres|sqlite|SQL|Reiserfs|PHP|xml|XML|Ion|g?vim|ascii|pdf|xhtml|pdflatex|pgsql|Postscript|texinfo|metadata|metatags|metaverse|rant|rake|YAML|object citation system|ocn|object citation numbering|granular search|Dublin Core|Lex Mercatoria|Project Gutenberg|Slashdot/i - :A~? @title @creator :B~? SiSU an attempt to describe diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_examples.ssi b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_examples.ssi index ebe4c1ea..cf9df9d5 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_examples.ssi +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_examples.ssi @@ -17,9 +17,9 @@ :copyright: Copyright (C) Ralph Amissah 2007 :license: GPL 3 (part of SiSU documentation) -:A~? @title @creator +A~? @title @creator -:B~? SiSU Markup and Output Examples +B~? SiSU Markup and Output Examples 1~examples Markup and Output Examples @@ -28,3 +28,70 @@ Current markup examples and document output samples are provided off http://sisudoc.org or http://www.jus.uio.no/sisu and in the sisu-markup-sample package available off http://sources.sisudoc.org For some documents hardly any markup at all is required at all, other than a header, and an indication that the levels to be taken into account by the program in generating its output are. + +2~sisu-markup-samples SiSU Markup Samples + +A few additional sample books prepared as sisu markup samples, output formats to be generated using SiSU are contained in a separate package sisu-markup-samples. sisu-markup-samples contains books (prepared using sisu markup), that were released by their authors various licenses mostly different Creative Commons licences that do not permit inclusion in the Debian Project as they have requirements that do not meet the Debian Free Software Guidelines for various reasons, most commonly that they require that the original substantive text remain unchanged, and sometimes that the works be used only non-commercially. + +/{Accelerando}/, Charles Stross (2005) \\ +accelerando.charles_stross.sst + +/{Alice's Adventures in Wonderland}/, Lewis Carroll (1865) \\ +alices_adventures_in_wonderland.lewis_carroll.sst + +/{CONTENT}/, Cory Doctorow (2008) \\ +content.cory_doctorow.sst + +/{Democratizing Innovation}/, Eric von Hippel (2005) \\ +democratizing_innovation.eric_von_hippel.sst + +/{Down and Out in the Magic Kingdom}/, Cory Doctorow (2003) \\ +down_and_out_in_the_magic_kingdom.cory_doctorow.sst + +/{For the Win}/, Cory Doctorow (2010) \\ +for_the_win.cory_doctorow.sst + +/{Free as in Freedom - Richard Stallman's Crusade for Free Software}/, Sam Williams (2002) \\ +free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst + +/{Free as in Freedom 2.0 - Richard Stallman and the Free Software Revolution}/, Sam Williams (2002), Richard M. Stallman (2010) \\ +free_as_in_freedom_2.richard_stallman_and_the_free_software_revolution.sam_williams.richard_stallman.sst + +/{Free Culture - How Big Media Uses Technology and the Law to Lock Down Culture and Control Creativity}/, Lawrence Lessig (2004) \\ +free_culture.lawrence_lessig.sst + +/{Free For All - How Linux and the Free Software Movement Undercut the High Tech Titans}/, Peter Wayner (2002) \\ +free_for_all.peter_wayner.sst + +/{GNU GENERAL PUBLIC LICENSE v2}/, Free Software Foundation (1991) \\ +gpl2.fsf.sst + +/{GNU GENERAL PUBLIC LICENSE v3}/, Free Software Foundation (2007) \\ +gpl3.fsf.sst + +/{Gulliver's Travels}/, Jonathan Swift (1726 / 1735) \\ +gullivers_travels.jonathan_swift.sst + +/{Little Brother}/, Cory Doctorow (2008) \\ +little_brother.cory_doctorow.sst + +/{The Cathederal and the Bazaar}/, Eric Raymond (2000) \\ +the_cathedral_and_the_bazaar.eric_s_raymond.sst + +/{The Public Domain - Enclosing the Commons of the Mind}/, James Boyle (2008) \\ +the_public_domain.james_boyle.sst + +/{The Wealth of Networks - How Social Production Transforms Markets and Freedom}/, Yochai Benkler (2006) \\ +the_wealth_of_networks.yochai_benkler.sst + +/{Through the Looking Glass}/, Lewis Carroll (1871) \\ +through_the_looking_glass.lewis_carroll.sst + +/{Two Bits - The Cultural Significance of Free Software}/, Christopher Kelty (2008) \\ +two_bits.christopher_kelty.sst + +/{UN Contracts for International Sale of Goods}/, UN (1980) \\ +un_contracts_international_sale_of_goods_convention_1980.sst + +/{Viral Spiral}/, David Bollier (2008) \\ +viral_spiral.david_bollier.sst diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_faq.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_faq.sst index 333023eb..966cea5f 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_faq.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_faq.sst @@ -21,23 +21,6 @@ :topic_register: electronic documents;SiSU:document:FAQ;sisu:document:FAQ;SiSU:manual:FAQ;electronic documents:SiSU:manual:FAQ :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator 1~faq FAQ - Frequently Asked/Answered Questions diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_filetypes.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_filetypes.sst index e53c96f8..d36acac0 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_filetypes.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_filetypes.sst @@ -21,23 +21,6 @@ :topic_register: SiSU:manual:filetypes;electronic documents:SiSU:manual:filetypes :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator 1~filetypes SiSU filetypes @@ -58,10 +41,6 @@ _1 sisu -s [filename] The most common form of document in SiSU, see the section on SiSU markup. -http://www.sisudoc.org/sisu/sisu_markup - -http://www.sisudoc.org/sisu/sisu_manual - 3~ sisu master files (.ssm) Composite documents which incorporate other SiSU documents which may be either regular SiSU text .sst which may be generated independently, or inserts prepared solely for the purpose of being incorporated into one or more master documents. @@ -72,10 +51,6 @@ Note: Master documents may be prepared in a similar way to regular documents, an Note: a secondary file of the composite document is built prior to processing with the same prefix and the suffix ._sst ~{ .ssc (for composite) is under consideration but ._sst makes clear that this is not a regular file to be worked on, and thus less likely that people will have "accidents", working on a .ssc file that is overwritten by subsequent processing. It may be however that when the resulting file is shared .ssc is an appropriate suffix to use. }~ -http://www.sisudoc.org/sisu/sisu_markup - -http://www.sisudoc.org/sisu/sisu_manual - 3~ sisu insert files (.ssi) Inserts are documents prepared solely for the purpose of being incorporated into one or more master documents. They resemble regular SiSU text files except they are ignored by the SiSU processor. Making a file a .ssi file is a quick and convenient way of flagging that it is not intended that the file should be processed on its own. @@ -102,67 +77,67 @@ http://www.sisudoc.org/sisu/sisu_commands http://www.sisudoc.org/sisu/sisu_manual -1~alt Experimental Alternative Input Representations - -2~ Alternative XML - -SiSU offers alternative XML input representations of documents as a proof of concept, experimental feature. They are however not strictly maintained, and incomplete and should be handled with care. - -!_ convert from sst to simple xml representations (sax, dom and node): - -_1 sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard] - -_1 sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard] - -_1 sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard] - -!_ convert to sst from any sisu xml representation (sax, dom and node): - -_1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] - -or the same: - -_1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] - -3~ XML SAX representation - -To convert from sst to simple xml (sax) representation: - -_1 sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard] - -To convert from any sisu xml representation back to sst - -_1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] - -or the same: - -_1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] - -3~ XML DOM representation - -To convert from sst to simple xml (dom) representation: - -_1 sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard] - -To convert from any sisu xml representation back to sst - -_1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] - -or the same: - -_1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] - -3~ XML Node representation - -To convert from sst to simple xml (node) representation: - -_1 sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard] - -To convert from any sisu xml representation back to sst - -_1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] - -or the same: - -_1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] +% 1~alt Experimental Alternative Input Representations +% +% 2~ Alternative XML +% +% SiSU offers alternative XML input representations of documents as a proof of concept, experimental feature. They are however not strictly maintained, and incomplete and should be handled with care. +% +% !_ convert from sst to simple xml representations (sax, dom and node): +% +% _1 sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard] +% +% _1 sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard] +% +% _1 sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard] +% +% !_ convert to sst from any sisu xml representation (sax, dom and node): +% +% _1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] +% +% or the same: +% +% _1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] +% +% 3~ XML SAX representation +% +% To convert from sst to simple xml (sax) representation: +% +% _1 sisu --to-sax [filename/wildcard] or sisu --to-sxs [filename/wildcard] +% +% To convert from any sisu xml representation back to sst +% +% _1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] +% +% or the same: +% +% _1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] +% +% 3~ XML DOM representation +% +% To convert from sst to simple xml (dom) representation: +% +% _1 sisu --to-dom [filename/wildcard] or sisu --to-sxd [filename/wildcard] +% +% To convert from any sisu xml representation back to sst +% +% _1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] +% +% or the same: +% +% _1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] +% +% 3~ XML Node representation +% +% To convert from sst to simple xml (node) representation: +% +% _1 sisu --to-node [filename/wildcard] or sisu --to-sxn [filename/wildcard] +% +% To convert from any sisu xml representation back to sst +% +% _1 sisu --from-xml2sst [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] +% +% or the same: +% +% _1 sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_help.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_help.sst index 99c0922a..ce6627b7 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_help.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_help.sst @@ -21,23 +21,6 @@ :topic_register: SiSU:manual:help;electronic documents:manual:SiSU:help :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator :B~? SiSU Help diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_help_sources.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_help_sources.sst index a96e09cf..bee5ed78 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_help_sources.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_help_sources.sst @@ -21,23 +21,6 @@ :topic_register: SiSU:manual:help sources;electronic documents:SiSU:manual:help sources :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator :B~? SiSU Help Sources diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_howto.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_howto.sst index 5e137eb4..dab3e8a4 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_howto.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_howto.sst @@ -21,23 +21,6 @@ :topic_register: SiSU:manual:howto;electronic documents:SiSU:manual:howto;SiSU:document:howto;sisu:document:howto :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator :B~? SiSU some technical information diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_introduction.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_introduction.sst index 08b1578d..8978ace6 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_introduction.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_introduction.sst @@ -20,23 +20,6 @@ @classify: :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator :B~? What is SiSU? diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_manual.ssm b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_manual.ssm index 312e9286..90e8a323 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_manual.ssm +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_manual.ssm @@ -21,23 +21,6 @@ :topic_register: SiSU:manual;electronic documents:SiSU:manual :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~ @title @creator :B~ What is SiSU? diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup.sst index 7a10bb94..9027817a 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup.sst @@ -21,23 +21,6 @@ :topic_register: electronic documents:SiSU:document:markup;SiSU:document:markup;SiSU:document:markup;SiSU:manual:markup;electronic documents:SiSU:manual:markup :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/i - :A~? @title @creator :B~? SiSU Markup @@ -146,6 +129,8 @@ code{ :num_top: 1 :breaks: new=C; break=1 :bold: /Gnu|Debian|Ruby|SiSU/ + :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org + :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org :manpage: name=sisu - documents: markup, structuring, publishing in multiple standard formats, and search; synopsis=sisu [-abcDdeFhIiMmNnopqRrSsTtUuVvwXxYyZz0-9] [filename/wildcard ] . sisu [-Ddcv] [instruction] @@ -241,15 +226,22 @@ code{ :description: :keywords: :abstract: - :isbn: [ISBN] :loc: [Library of Congress classification] :dewey: [Dewey classification - :pg: [Project Gutenberg text number] }code code{ +@identify: + :isbn: [ISBN] + :oclc: + +}code + + +code{ + @links: { SiSU }http://www.sisudoc.org { FSF }http://www.fsf.org @@ -265,6 +257,8 @@ code{ :promo: sisu, ruby, sisu_search_libre, open_society :bold: [regular expression of words/phrases to be made bold] :italics: [regular expression of words/phrases to italicise] + :home_button_text: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org + :footer: {SiSU}http://sisudoc.org; {git}http://git.sisudoc.org }code @@ -1271,232 +1265,4 @@ code{ }code -The form described above should be relied on. Within the Vim editor it results in the text thus linked becoming hyperlinked to the document it is calling in which is convenient for editing. Alternative markup for importation of documents under consideration, and occasionally supported have been. - -code{ - -<< filename.ssi - -<<{filename.ssi} - -% using textlink alternatives - -<< |filename.ssi|@|^| - -}code - -1~syntax_history Markup Syntax History - -2~ Notes related to Files-types and Markup Syntax - -3.0 very minor additions to markup added, substantially the same as version 2.0 - -2.0 introduced new headers and is therefore incompatible with 1.0 though otherwise the same with the addition of a couple of tags (i.e. a superset) - -0.38 is substantially current for version 1.0 - -depreciated 0.16 supported, though file names were changed at 0.37 - -_* sisu --query=[sisu version [0.38] or 'history] - -provides a short history of changes to SiSU markup - -!_ SiSU 2.0 -(2010-03-06:09/6) -same as 1.0, apart from the changing of headers and the addition of a monospace tag related headers now grouped, e.g. - -code{ - -@title: - :subtitle: - -@creator: - :author: - :translator: - :illustrator: - -@rights: - :text: - :illustrations: - -}code - -see document markup samples, and sisu --help headers - -the monospace tag takes the form of a hash '#' - -code{ - -#{ this enclosed text would be monospaced }# - -}code - -!_ 1.0 -(2009-12-19:50/6) -same as 0.69 - -!_ 0.69 -(2008-09-16:37/2) -(same as 1.0) and as previous (0.57) with the addition of book index tags - -code{ - -/^={.+?}$/ - -}code - -e.g. appended to a paragraph, on a new-line (without a blank line in between) logical structure produced assuming this is the first text "object" - -code{ - - ={GNU/Linux community distribution:Debian+2|Fedora|Gentoo;Free Software Foundation+5} - -}code - -code{ - -Free Software Foundation, 1-6 -GNU/Linux community distribution, 1 - Debian, 1-3 - Fedora, 1 - Gentoo, - -}code - -!_ 0.66 -(2008-02-24:07/7) -same as previous, adds semantic tags, [experimental and not-used] - -code{ - -/[:;]{.+?}[:;][a-z+]/ - -}code - -!_ 0.57 -(2007w34/4) -SiSU 0.57 is the same as 0.42 with the introduction of some a shortcut to use the headers @title and @creator in the first heading [expanded using the contents of the headers @title: and @author:] - -code{ - -:A~ @title by @author - -}code - -!_ 0.52 -(2007w14/6) -declared document type identifier at start of text/document: - -_1 SiSU 0.52 - -or, backward compatible using the comment marker: - -_1 % SiSU 0.38 - -variations include 'SiSU (text|master|insert) [version]' and 'sisu-[version]' - -!_ 0.51 -(2007w13/6) -skins changed (simplified), markup unchanged - -!_ 0.42 -(2006w27/4) -* (asterisk) type endnotes, used e.g. in relation to author - -SiSU 0.42 is the same as 0.38 with the introduction of some additional endnote types, - -Introduces some variations on endnotes, in particular the use of the asterisk - -code{ - -~{* for example for describing an author }~ and ~{** for describing a second author }~ - -}code - -* for example for describing an author - -** for describing a second author - -and - -code{ - -~[* my note ]~ or ~[+ another note ]~ - -}code - -which numerically increments an asterisk and plus respectively - -*1 my note -+1 another note - -!_ 0.38 -(2006w15/7) -introduced new/alternative notation for headers, e.g. @title: (instead of 0\~title), and accompanying document structure markup, :A,:B,:C,1,2,3 (maps to previous 1,2,3,4,5,6) - -SiSU 0.38 introduced alternative experimental header and heading/structure markers, - -code{ - -@headername: and headers :A~ :B~ :C~ 1~ 2~ 3~ - -}code - -as the equivalent of: - -code{ - -0~headername and headers 1~ 2~ 3~ 4~ 5~ 6~ - -}code - -The internal document markup of SiSU 0.16 remains valid and standard Though note that SiSU 0.37 introduced a new file naming convention - -SiSU has in effect two sets of levels to be considered, using 0.38 notation A-C headings/levels, pre-ordinary paragraphs /pre-substantive text, and 1-3 headings/levels, levels which are followed by ordinary text. This may be conceptualised as levels A,B,C, 1,2,3, and using such letter number notation, in effect: A must exist, optional B and C may follow in sequence (not strict) 1 must exist, optional 2 and 3 may follow in sequence i.e. there are two independent heading level sequences A,B,C and 1,2,3 (using the 0.16 standard notation 1,2,3 and 4,5,6) on the positive side: the 0.38 A,B,C,1,2,3 alternative makes explicit an aspect of structuring documents in SiSU that is not otherwise obvious to the newcomer (though it appears more complicated, is more in your face and likely to be understood fairly quickly); the substantive text follows levels 1,2,3 and it is 'nice' to do most work in those levels - -!_ 0.37 -(2006w09/7) -introduced new file naming convention, .sst (text), .ssm (master), .ssi (insert), markup syntax unchanged - -SiSU 0.37 introduced new file naming convention, using the file extensions .sst .ssm and .ssi to replace .s1 .s2 .s3 .r1 .r2 .r3 and .si - -this is captured by the following file 'rename' instruction: - -code{ - -rename 's/\.s[123]$/\.sst/' *.s{1,2,3} -rename 's/\.r[123]$/\.ssm/' *.r{1,2,3} -rename 's/\.si$/\.ssi/' *.si - -}code - -The internal document markup remains unchanged, from SiSU 0.16 - -!_ 0.35 -(2005w52/3) -sisupod, zipped content file introduced - -!_ 0.23 -(2005w36/2) -utf-8 for markup file - -!_ 0.22 -(2005w35/3) -image dimensions may be omitted if rmagick is available to be relied upon - -!_ 0.20.4 -(2005w33/4) -header 0~links - -!_ 0.16 -(2005w25/2) -substantial changes introduced to make markup cleaner, header 0\~title type, and headings [1-6]\~ introduced, also percentage sign (%) at start of a text line as comment marker - -SiSU 0.16 (0.15 development branch) introduced the use of - -the header 0~ and headings/structure 1~ 2~ 3~ 4~ 5~ 6~ - -in place of the 0.1 header, heading/structure notation - -SiSU 0.1 headers and headings structure represented by -header 0{~ and headings/structure 1{ 2{ 3{ 4{~ 5{ 6{ +The form described above should be relied on. Within the Vim editor it results in the text thus linked becoming hyperlinked to the document it is calling in which is convenient for editing. diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup_syntax_history.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup_syntax_history.sst new file mode 100644 index 00000000..a5b56f1f --- /dev/null +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_markup_syntax_history.sst @@ -0,0 +1,260 @@ +% SiSU 4.0 + +@title: SiSU + :subtitle: Markup + +@creator: + :author: Amissah, Ralph + +@date: + :created: 2002-08-28 + :issued: 2002-08-28 + :available: 2002-08-28 + :published: 2008-05-22 + :modified: 2012-10-03 + +@rights: + :copyright: Copyright (C) Ralph Amissah 2007 + :license: GPL 3 (part of SiSU documentation) + +@classify: + :topic_register: electronic documents:SiSU:document:markup;SiSU:document:markup;SiSU:document:markup;SiSU:manual:markup;electronic documents:SiSU:manual:markup + :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search + +:A~? @title @creator + +:B~? SiSU Markup Syntax History + +1~ Composite documents markup + +It is possible to build a document by creating a master document that requires other documents. The documents required may be complete documents that could be generated independently, or they could be markup snippets, prepared so as to be easily available to be placed within another text. If the calling document is a master document (built from other documents), it should be named with the suffix *{.ssm}* Within this document you would provide information on the other documents that should be included within the text. These may be other documents that would be processed in a regular way, or markup bits prepared only for inclusion within a master document *{.sst}* regular markup file, or *{.ssi}* (insert/information) A secondary file of the composite document is built prior to processing with the same prefix and the suffix *{._sst}* + +basic markup for importing a document into a master document + +code{ + +<< filename1.sst + +<< filename2.ssi + +}code + +The form described above should be relied on. Within the Vim editor it results in the text thus linked becoming hyperlinked to the document it is calling in which is convenient for editing. + +1~syntax_history Markup Syntax History + +2~ Notes related to Files-types and Markup Syntax + +4.0 introduced additional headers and drops the use of skins replacing them with additions to the @make: header, and having a common _sisu/sisu_document_make file that uses @make: header syntax to provide a default @make: (it will parse 2.0 but igore skins, markup is otherwise the same as version 2.0 with version 3.0's minor additions) + +3.0 very minor additions to markup added, substantially the same as version 2.0 + +2.0 introduced new headers and is therefore incompatible with 1.0 though otherwise the same with the addition of a couple of tags (i.e. a superset) + +0.38 is substantially current for version 1.0 + +depreciated 0.16 supported, though file names were changed at 0.37 + +_* sisu --query=[sisu version [0.38] or 'history] + +provides a short history of changes to SiSU markup + +!_ SiSU 2.0 +(2010-03-06:09/6) +same as 1.0, apart from the changing of headers and the addition of a monospace tag related headers now grouped, e.g. + +code{ + +@title: + :subtitle: + +@creator: + :author: + :translator: + :illustrator: + +@rights: + :text: + :illustrations: + +}code + +see document markup samples, and sisu --help headers + +the monospace tag takes the form of a hash '#' + +code{ + +#{ this enclosed text would be monospaced }# + +}code + +!_ 1.0 +(2009-12-19:50/6) +same as 0.69 + +!_ 0.69 +(2008-09-16:37/2) +(same as 1.0) and as previous (0.57) with the addition of book index tags + +code{ + +/^={.+?}$/ + +}code + +e.g. appended to a paragraph, on a new-line (without a blank line in between) logical structure produced assuming this is the first text "object" + +code{ + + ={GNU/Linux community distribution:Debian+2|Fedora|Gentoo;Free Software Foundation+5} + +}code + +code{ + +Free Software Foundation, 1-6 +GNU/Linux community distribution, 1 + Debian, 1-3 + Fedora, 1 + Gentoo, + +}code + +!_ 0.66 +(2008-02-24:07/7) +same as previous, adds semantic tags, [experimental and not-used] + +code{ + +/[:;]{.+?}[:;][a-z+]/ + +}code + +!_ 0.57 +(2007w34/4) +SiSU 0.57 is the same as 0.42 with the introduction of some a shortcut to use the headers @title and @creator in the first heading [expanded using the contents of the headers @title: and @author:] + +code{ + +:A~ @title by @author + +}code + +!_ 0.52 +(2007w14/6) +declared document type identifier at start of text/document: + +_1 SiSU 0.52 + +or, backward compatible using the comment marker: + +_1 % SiSU 0.38 + +variations include 'SiSU (text|master|insert) [version]' and 'sisu-[version]' + +!_ 0.51 +(2007w13/6) +skins changed (simplified), markup unchanged + +!_ 0.42 +(2006w27/4) +* (asterisk) type endnotes, used e.g. in relation to author + +SiSU 0.42 is the same as 0.38 with the introduction of some additional endnote types, + +Introduces some variations on endnotes, in particular the use of the asterisk + +code{ + +~{* for example for describing an author }~ and ~{** for describing a second author }~ + +}code + +* for example for describing an author + +** for describing a second author + +and + +code{ + +~[* my note ]~ or ~[+ another note ]~ + +}code + +which numerically increments an asterisk and plus respectively + +*1 my note ++1 another note + +!_ 0.38 +(2006w15/7) +introduced new/alternative notation for headers, e.g. @title: (instead of 0\~title), and accompanying document structure markup, :A,:B,:C,1,2,3 (maps to previous 1,2,3,4,5,6) + +SiSU 0.38 introduced alternative experimental header and heading/structure markers, + +code{ + +@headername: and headers :A~ :B~ :C~ 1~ 2~ 3~ + +}code + +as the equivalent of: + +code{ + +0~headername and headers 1~ 2~ 3~ 4~ 5~ 6~ + +}code + +The internal document markup of SiSU 0.16 remains valid and standard Though note that SiSU 0.37 introduced a new file naming convention + +SiSU has in effect two sets of levels to be considered, using 0.38 notation A-C headings/levels, pre-ordinary paragraphs /pre-substantive text, and 1-3 headings/levels, levels which are followed by ordinary text. This may be conceptualised as levels A,B,C, 1,2,3, and using such letter number notation, in effect: A must exist, optional B and C may follow in sequence (not strict) 1 must exist, optional 2 and 3 may follow in sequence i.e. there are two independent heading level sequences A,B,C and 1,2,3 (using the 0.16 standard notation 1,2,3 and 4,5,6) on the positive side: the 0.38 A,B,C,1,2,3 alternative makes explicit an aspect of structuring documents in SiSU that is not otherwise obvious to the newcomer (though it appears more complicated, is more in your face and likely to be understood fairly quickly); the substantive text follows levels 1,2,3 and it is 'nice' to do most work in those levels + +!_ 0.37 +(2006w09/7) +introduced new file naming convention, .sst (text), .ssm (master), .ssi (insert), markup syntax unchanged + +SiSU 0.37 introduced new file naming convention, using the file extensions .sst .ssm and .ssi to replace .s1 .s2 .s3 .r1 .r2 .r3 and .si + +this is captured by the following file 'rename' instruction: + +code{ + +rename 's/\.s[123]$/\.sst/' *.s{1,2,3} +rename 's/\.r[123]$/\.ssm/' *.r{1,2,3} +rename 's/\.si$/\.ssi/' *.si + +}code + +The internal document markup remains unchanged, from SiSU 0.16 + +!_ 0.35 +(2005w52/3) +sisupod, zipped content file introduced + +!_ 0.23 +(2005w36/2) +utf-8 for markup file + +!_ 0.22 +(2005w35/3) +image dimensions may be omitted if rmagick is available to be relied upon + +!_ 0.20.4 +(2005w33/4) +header 0~links + +!_ 0.16 +(2005w25/2) +substantial changes introduced to make markup cleaner, header 0\~title type, and headings [1-6]\~ introduced, also percentage sign (%) at start of a text line as comment marker + +SiSU 0.16 (0.15 development branch) introduced the use of + +the header 0~ and headings/structure 1~ 2~ 3~ 4~ 5~ 6~ + +in place of the 0.1 header, heading/structure notation + +SiSU 0.1 headers and headings structure represented by +header 0{~ and headings/structure 1{ 2{ 3{ 4{~ 5{ 6{ diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_output_overview.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_output_overview.sst index 7abe9f25..332f4aae 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_output_overview.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_output_overview.sst @@ -21,23 +21,6 @@ :topic_register: electronic documents:SiSU:document:markup table;SiSU:manual:output overview;electronic documents:SiSU:manual:output overview;SiSU:document:output overview;SiSU:document:output overview :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 -% :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator :B~? SiSU overview of status of features available in various outputs diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_postgresql.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_postgresql.sst index 2bfc8c65..574e307c 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_postgresql.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_postgresql.sst @@ -21,22 +21,7 @@ :topic_register: electronic documents:SiSU:document:postgresql;SiSU:manual:postgresql;electronic documents:SiSU:manual:postgresql;SiSU:document:postgresql;SiSU:document:postgresql; :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - @make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ :manpage: section=7; name=sisu - package to install what sisu needs to to populate a postgresql database (postgresql dependency component); synopsis=sisu -Dv [filename/wildcard ]\n sisu -Dv [instruction] :A~? @title @creator diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_quickstart.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_quickstart.sst index f62237e1..ae95f528 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_quickstart.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_quickstart.sst @@ -21,23 +21,6 @@ :topic_register: electronic documents:SiSU:document:quickstart;SiSU:manual:quickstart;electronic documents:SiSU:manual:quickstart;SiSU:document:quickstart;SiSU:document:quickstart :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator :B~? Quickstart - SiSU installation and use diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_remote.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_remote.sst index ca2d4028..959fbcf6 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_remote.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_remote.sst @@ -21,23 +21,6 @@ :topic_register: electronic documents:SiSU:document:remote;SiSU:manual:remote;electronic documents:SiSU:manual:remote;SiSU:document:remote;SiSU:document:remote :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator :B~? SiSU Remote Operations diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_search.ssm b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_search.ssm index 5cfa539d..9c40a8bf 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_search.ssm +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_search.ssm @@ -20,23 +20,6 @@ @classify: :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator :B~? SiSU Search diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_search_intro.ssi b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_search_intro.ssi index 22563bcd..d5da379f 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_search_intro.ssi +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_search_intro.ssi @@ -17,11 +17,6 @@ :copyright: Copyright (C) Ralph Amissah 2007 :license: GPL 3 (part of SiSU documentation) -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator :B~? SiSU Search diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_short_feature_summary.ssi b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_short_feature_summary.ssi index c8099fb0..294644af 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_short_feature_summary.ssi +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_short_feature_summary.ssi @@ -33,21 +33,21 @@ _* markup defines document structure (this may be done once in a header pattern- _* for output produces reasonably elegant output of established industry and institutionally accepted open standard formats.[3] takes advantage of the different strengths of various standard formats for representing documents, amongst the output formats currently supported are: -_1* html - both as a single scrollable text and a segmented document +_* HTML - both as a single scrollable text and a segmented document -_1* xhtml +_* XHTML -_1* epub +_* EPUB -_1* XML - both in sax and dom style xml structures for further development as required +_* XML - both in sax and dom style xml structures for further development as required -_1* ODF - open document format, the iso standard for document storage +_* ODT - Open Document Format text, the iso standard for document storage -_1* LaTeX - used to generate pdf +_* LaTeX - used to generate pdf -_1* pdf (via LaTeX) +_* PDF (via LaTeX) -_1* sql - population of an sql database, (at the same object level that is used to cite text within a document) +_* SQL - population of an sql database (PostgreSQL or SQLite), (at the same object level that is used to cite text within a document) Also produces: concordance files; document content certificates (md5 or sha256 digests of headings, paragraphs, images etc.) and html manifests (and sitemaps of content). (b) takes advantage of the strengths implicit in these very different output types, (e.g. PDFs produced using typesetting of LaTeX, databases populated with documents at an individual object/paragraph level, making possible granular search (and related possibilities)) diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_sqlite.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_sqlite.sst index 3e462cc1..a73ae16c 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_sqlite.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_sqlite.sst @@ -21,22 +21,7 @@ :topic_register: electronic documents:SiSU:document:sqlite;SiSU:manual:sqlite;electronic documents:SiSU:manual:sqlite;SiSU:document:sqlite;SiSU:document:sqlite :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - @make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ :manpage: section=7; name=sisu - package to install what sisu needs to to populate a postgresql database (postgresql dependency component); synopsis=sisu -dv [filename/wildcard ]\n sisu -dv [instruction] :A~? @title @creator diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_syntax_highlighting.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_syntax_highlighting.sst index 21879106..12a70fb8 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_syntax_highlighting.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_syntax_highlighting.sst @@ -21,23 +21,6 @@ :topic_register: electronic documents:SiSU:document:syntax highlighting;SiSU:manual:syntax highlighting;electronic documents:SiSU:manual:syntax highlighting;SiSU:document:syntax highlighting;SiSU:document:syntax highlighting :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - -@make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ - :A~? @title @creator :B~? SiSU Syntax Highlighting diff --git a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_webrick.sst b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_webrick.sst index b229ea9c..6e56e53a 100644 --- a/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_webrick.sst +++ b/data/doc/sisu/markup-samples/v4/sisu_manual/sisu_webrick.sst @@ -21,22 +21,7 @@ :topic_register: electronic documents:SiSU:document:webrick;SiSU:manual:webrick;electronic documents:SiSU:manual:webrick;SiSU:document:webrick;SiSU:document:webrick :subject: ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search -@links: - { SiSU Homepage }http://www.sisudoc.org/ - { SiSU Manual }http://www.sisudoc.org/sisu/sisu_manual/ - { Book Samples & Markup Examples }http://www.jus.uio.no/sisu/SiSU/examples.html - { SiSU Download }http://www.jus.uio.no/sisu/SiSU/download.html - { SiSU Changelog }http://www.jus.uio.no/sisu/SiSU/changelog.html - { SiSU Git repo }http://git.sisudoc.org/?p=code/sisu.git;a=summary - { SiSU List Archives }http://lists.sisudoc.org/pipermail/sisu/ - { SiSU @ Debian }http://packages.qa.debian.org/s/sisu.html - { SiSU Project @ Debian }http://qa.debian.org/developer.php?login=sisu@lists.sisudoc.org - { SiSU @ Wikipedia }http://en.wikipedia.org/wiki/SiSU - @make: - :num_top: 1 - :breaks: new=C; break=1 - :bold: /Gnu|Debian|Ruby|SiSU/ :manpage: section=7; name=sisu - documents: structuring, publishing in multiple formats, and search; synopsis=sisu -W :A~? @title @creator @@ -72,20 +57,3 @@ where no port is given and settings are unchanged the default port is 8081 2~ Document processing command flags sisu -W [port] starts Ruby Webrick web-server, serving SiSU output directories, on the port provided, or if no port is provided and the defaults have not been changed in ~/.sisu/sisurc.yaml then on port 8081 - -2~ Further information - -For more information on SiSU see: http://www.sisudoc.org/ or http://www.jus.uio.no/sisu - -or man sisu - -2~ Author - -Ralph Amissah ralph@amissah.com or ralph.amissah@gmail.com - -2~ SEE ALSO - -_1 sisu(1) - -_1 sisu_vim(7) - |