SiSU -->
TOC linked  toc  Full Text  scroll  PDF portrait   pdf  PDF landscape   pdf  ODF/ODT  odt    A-Z  Document Manifest  @
<< previous TOC next >>
< ^ >

SiSU - Manual,
Ralph Amissah

What is SiSU?

1. Introduction - What is SiSU?

2. How does sisu work?

3. Summary of features

4. Help

4.1 SiSU Manual
4.2 SiSU man pages
4.3 SiSU built-in interactive help
4.4 Help Sources

5. Commands Summary

5.1 Synopsis
5.2 Description
5.3 Document Processing Command Flags

6. command line modifiers

7. database commands

8. Shortcuts, Shorthand for multiple flags

8.1 Command Line with Flags - Batch Processing

9. Introduction to SiSU Markup

9.1 Summary
9.2 Markup Examples
9.2.1 Online
9.2.2 Installed

10. Markup of Headers

10.1 Sample Header
10.2 Available Headers

11. Markup of Substantive Text

11.1 Heading Levels
11.2 Font Attributes
11.3 Indentation and bullets
11.4 Footnotes / Endnotes
11.5 Links
11.5.1 Naked URLs within text, dealing with urls
11.5.2 Linking Text
11.5.3 Linking Images
11.6 Grouped Text
11.6.1 Tables
11.6.2 Poem
11.6.3 Group
11.6.4 Code
11.7 Book index

12. Composite documents markup

Markup Syntax History

13. Notes related to Files-types and Markup Syntax

14. SiSU filetypes

14.1 .sst .ssm .ssi marked up plain text
14.1.1 sisu text - regular files (.sst)
14.1.2 sisu master files (.ssm)
14.1.3 sisu insert files (.ssi)
14.2 sisupod, zipped binary container (sisupod.zip, .ssp)

15. Experimental Alternative Input Representations

15.1 Alternative XML
15.1.1 XML SAX representation
15.1.2 XML DOM representation
15.1.3 XML Node representation

16. Configuration

16.1 Determining the Current Configuration
16.2 Configuration files (config.yml)

17. Skins

17.1 Document Skin
17.2 Directory Skin
17.3 Site Skin
17.4 Sample Skins

18. CSS - Cascading Style Sheets (for html, XHTML and XML)

19. Organising Content

19.1 Directory Structure and Mapping
19.1.1 General Directories
19.1.2 Remote Directories
19.1.3 Sisupod
19.2 Organising Content

20. Homepages

20.1 Home page and other custom built pages in a sub-directory
20.2 Home page within a skin

21. Markup and Output Examples

21.1 Markup examples
21.2 A few book (and other) examples
"The Wealth of Networks", Yochai Benkler
"Two Bits", Christopher Kelty
"Free Culture", Lawrence Lessig
"Free as in Freedom: Richard Stallman's Crusade for Free Software", by Sam Williams
"Free For All: How Linux and the Free Software Movement Undercut the High Tech Titans", by Peter Wayner
"The Cathedral and the Bazaar", by Eric S. Raymond
"Accelerando", Charles Stross
"Tainaron", Leena Krohn
"Sphinx or Robot", Leena Krohn
"War and Peace", Leo Tolstoy, PG Etext 2600
"Don Quixote", Miguel de Cervantes [Saavedra], translated by John Ormsby, PG Etext 996
"Gulliver's Travels", Jonathan Swift, transcribed from the 1892 George Bell and Sons edition by David Price, PG Etext 829
"Alice's Adventures in Wonderland", Lewis Carroll, PG Etext 11
"Through The Looking-Glass", Lewis Carroll, PG Etext 12
"Alice's Adventures in Wonderland" and "Through The Looking-Glass", Lewis Carroll, PG Etexts 11 and 12
"Gnu Public License 2", (GPL 2) Free Software Foundation
"Gnu Public License v3 - Third discussion draft", (GPLv3) Free Software Foundation
"Debian Social Contract"
"Debian Constitution v1.3", (simple/default markup)
"Debian Constitution v1.3", (markup adjusted for output to more closely match the original)
"Debian Constitution v1.2", (simple/default markup)
"Debian Constitution v1.2", (markup adjusted for output to more closely match the original)
"A Uniform Sales Terminology", Vikki Rogers and Albert Kritzer
"The Autonomous Contract" 1997 - markup sample
"The Autonomous Contract Revisited" - markup sample
"United Nations Convention on Contracts for the International Sale of Goods"
PECL the "Principles of European Contract Law"
21.3 SQL - PostgreSQL, SQLite
21.4 Lex Mercatoria as an example
21.5 For good measure the markup for a document with lots of (simple) tables
21.6 And a link to the output of a reported case

22. A Checklist of Output Features

23. SiSU Search - Introduction

24. SQL

24.1 populating SQL type databases

25. Postgresql

25.1 Name
25.2 Description
25.3 Synopsis
25.4 Commands
25.4.1 create and destroy database
25.4.2 import and remove documents

26. Sqlite

26.1 Name
26.2 Description
26.3 Synopsis
26.4 Commands
26.4.1 create and destroy database
26.4.2 import and remove documents

27. Introduction

27.1 Search - database frontend sample, utilising database and SiSU features, including object citation numbering (backend currently PostgreSQL)
27.2 Search Form

28. Hyperestraier

29. sisu_webrick

29.1 Name
29.2 Synopsis
29.3 Description
29.4 Summary of man page
29.5 Document processing command flags
29.6 Further information
29.7 Author
29.8 SEE ALSO

30. Remote Source Documents

Remote Document Output

31. Remote Output

31.1 commands
31.2 configuration

32. Remote Servers

Download information

33. Download SiSU - Linux/Unix

SiSU Current Version - Linux/Unix
Source (tarball tar.gz)
Git (source control management)
Debian
RPM

Installation

34. Installation

34.1 Debian
34.2 Other Unix / Linux
34.2.1 source tarball

35. SiSU Components, Dependencies and Notes

35.1 sisu
35.2 sisu-complete
35.3 sisu-examples
35.4 sisu-pdf
35.5 sisu-postgresql
35.6 sisu-remote
35.7 sisu-sqlite

36. Quickstart - Getting Started Howto

36.1 Installation
36.1.1 Debian Installation
36.1.2 RPM Installation
36.1.3 Installation from source
36.2 Testing SiSU, generating output
36.2.1 basic text, plaintext, html, XML, ODF
36.2.2 LaTeX / pdf
36.2.3 relational database - postgresql, sqlite
36.3 Getting Help
36.3.1 The man pages
36.3.2 Built in help
36.3.3 The home page
36.4 Markup Samples

HowTo

37. Getting Help

37.1 SiSU "man" pages
37.2 SiSU built-in help
37.3 Command Line with Flags - Batch Processing

38. Setup, initialisation

38.1 initialise output directory
38.1.1 Use of search functionality, an example using sqlite
38.2 misc
38.2.1 url for output files -u -U
38.2.2 toggle screen color
38.2.3 verbose mode
38.2.4 quiet mode
38.2.5 maintenance mode intermediate files kept -M
38.2.6 start the webrick server
38.3 remote placement of output

39. Configuration Files

40. Markup

40.1 Headers
40.2 Font Face
40.2.1 Bold
40.2.2 Italics
40.2.3 Underscore
40.2.4 Strikethrough
40.3 Endnotes
40.4 Links
40.5 Number Titles
40.6 Line operations
40.7 Tables
40.8 Grouped Text
40.9 Composite Document

41. Change Appearance

41.1 Skins
41.2 CSS

Extracts from the README

42. README

42.1 Online Information, places to look
42.2 Installation
42.2.1 Debian
42.2.2 RPM
42.2.3 Source package .tgz
42.2.4 to use setup.rb
42.2.5 to use install (prapared with "Rake")
42.2.6 to use install (prapared with "Rant")
42.3 Dependencies
42.4 Quick start
42.5 Configuration files
42.6 Use General Overview
42.7 Help
42.8 Directory Structure
42.9 Configuration File
42.10 Markup
42.11 Additional Things
42.12 License
42.13 SiSU Standard

Extracts from man 8 sisu

43. Post Installation Setup

43.1 Post Installation Setup - Quick start
43.2 Document markup directory
43.2.1 Configuration files
43.2.2 Debian INSTALLATION Note
43.2.3 Document Resource Configuration
43.2.4 Skins

44. FAQ - Frequently Asked/Answered Questions

44.1 Why are urls produced with the -v (and -u) flag that point to a web server on port 8081?
44.2 I cannot find my output, where is it?
44.3 I do not get any pdf output, why?
44.4 Where is the latex (or some other interim) output?
44.5 Why isn't SiSU markup XML
44.6 LaTeX claims to be a document preparation system for high-quality typesetting. Can the same be said about SiSU?
44.7 Can the SiSU markup be used to prepare for a LaTex automatic building of an index to the work?
44.8 Can the conversion from SiSU to LaTeX be modified if we have special needs for the LaTeX, or do we need to modify the LaTeX manually?
44.9 How do I create GIN or GiST index in Postgresql for use in SiSU
44.10 Are there some examples of using Ferret Search with a SiSU repository?
44.11 Have you had any reports of building SiSU from tar on Mac OS 10.4?
44.12 Where is version 1.0?

45. Who might be interested in the SiSU feature set?

46. Work Needed

47. Wishlist

48. Editor Files, Syntax Highlighting

49. Help Sources

49.1 man pages
49.1.1 man
49.2 sisu generated output - links to html
49.2.1 www.sisudoc.org
49.3 man2html
49.3.1 locally installed
49.3.2 www.jus.uio.no/sisu

Endnotes

Concordance (wordlist)

Manifest (alternative outputs)

Metadata

SiSU

Manual

Ralph Amissah

copy @ SiSU

SiSU - Manual,
Ralph Amissah

What is SiSU?

11. Markup of Substantive Text

11.1 Heading Levels
11.2 Font Attributes
11.3 Indentation and bullets
11.4 Footnotes / Endnotes
11.5 Links
11.5.1 Naked URLs within text, dealing with urls
11.5.2 Linking Text
11.5.3 Linking Images
11.6 Grouped Text
11.6.1 Tables
11.6.2 Poem
11.6.3 Group
11.6.4 Code
11.7 Book index

11.1 Heading Levels

Heading levels are :A~ ,:B~ ,:C~ ,1~ ,2~ ,3~ ... :A - :C being part / section headings, followed by other heading levels, and 1 -6 being headings followed by substantive text or sub-headings. :A~ usually the title :A~? conditional level 1 heading (used where a stand-alone document may be imported into another)

:A~ [heading text] Top level heading [this usually has similar content to the title @title: ] NOTE: the heading levels described here are in 0.38 notation, see heading

:B~ [heading text] Second level heading [this is a heading level divider]

:C~ [heading text] Third level heading [this is a heading level divider]

1~ [heading text] Top level heading preceding substantive text of document or sub-heading 2, the heading level that would normally be marked 1. or 2. or 3. etc. in a document, and the level on which sisu by default would break html output into named segments, names are provided automatically if none are given (a number), otherwise takes the form 1~my_filename_for_this_segment

2~ [heading text] Second level heading preceding substantive text of document or sub-heading 3, the heading level that would normally be marked 1.1 or 1.2 or 1.3 or 2.1 etc. in a document.

3~ [heading text] Third level heading preceding substantive text of document, that would normally be marked 1.1.1 or 1.1.2 or 1.2.1 or 2.1.1 etc. in a document

  1~filename level 1 heading,

  % the primary division such as Chapter that is followed by substantive text, and may be further subdivided (this is the level on which by default html segments are made)

11.2 Font Attributes

markup example:

  normal text !{emphasis}! *{bold text}* _{underscore}_ /{italics}/ "{citation}" ^{superscript}^ ,{subscript}, +{inserted text}+

  normal text

  !{emphasis}!

  *{bold text}*

  _{underscore}_

  /{italics}/

  "{citation}"

  ^{superscript}^

  ,{subscript},

  +{inserted text}+

  -{strikethrough}-

resulting output:

normal text emphasis bold text underscore italics citation superscript subscript inserted text strikethrough

normal text

emphasis

bold text

underscore

italics

citation

superscript

subscript

inserted text

strikethrough

11.3 Indentation and bullets

markup example:

  ordinary paragraph

  _1 indent paragraph one step

  _2 indent paragraph two steps

  _9 indent paragraph nine steps

resulting output:

ordinary paragraph

indent paragraph one step

indent paragraph two steps

indent paragraph nine steps

markup example:

  _* bullet text

  _1* bullet text, first indent

  _2* bullet text, two step indent

resulting output:

  • bullet text
  • bullet text, first indent
  • bullet text, two step indent
  • Numbered List (not to be confused with headings/titles, (document structure))

    markup example:

      # numbered list                numbered list 1., 2., 3, etc.

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

    11.4 Footnotes / Endnotes

    Footnotes and endnotes not distinguished in markup. They are automatically numbered. Depending on the output file format (html, odf, pdf etc.), the document output selected will have either footnotes or endnotes.

    markup example:

      ~{ a footnote or endnote }~

    resulting output:

    markup example:

      normal text~{ self contained endnote marker & endnote in one }~ continues

    resulting output:

    normal text  12  continues

    markup example:

      normal text ~{* unnumbered asterisk footnote/endnote, insert multiple asterisks if required }~ continues

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

    resulting output:

    normal text   *  continues

    normal text   **  continues

    markup example:

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

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

    resulting output:

    normal text   *3  continues

    normal text   +2  continues

    Alternative endnote pair notation for footnotes/endnotes:

      % note the endnote marker "~^"

      normal text~^ continues

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

    the standard and pair notation cannot be mixed in the same document

    11.5 Links

    11.5.1 Naked URLs within text, dealing with urls

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

    markup example:

      normal text http://www.jus.uio.no/sisu continues

    resulting output:

    normal text <http://www.jus.uio.no/sisu> continues

    An escaped url without decoration

    markup example:

      normal text _http://www.jus.uio.no/sisu continues

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

    resulting output:

    normal text http://www.jus.uio.no/sisu continues

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

    where a code block is used there is neither decoration nor hyperlinking, code blocks are discussed later in this document

    resulting output:

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

    To link text or an image to a url the markup is as follows

    markup example:

      about { SiSU }http://url.org markup

    11.5.2 Linking Text

    resulting output:

    about SiSU markup

    A shortcut notation is available so the url link may also be provided automatically as a footnote

    markup example:

      about {~^ SiSU }http://url.org markup

    resulting output:

    about SiSU   13  markup

    11.5.3 Linking Images

    markup example:

      { tux.png 64x80 }image

      % various url linked images

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

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

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

    resulting output:


    Gnu/Linux - a better way


    Ruby

      14 


    Way Better - with Gnu/Linux, Debian and Ruby

    linked url footnote shortcut

      {~^ [text to link] }http://url.org

      % maps to: { [text to link] }http://url.org ~{ http://url.org }~

      % which produces hyper-linked text within a document/paragraph, with an endnote providing the url for the text location used in the hyperlink

      text marker *~name

    note at a heading level the same is automatically achieved by providing names to headings 1, 2 and 3 i.e. 2~[name] and 3~[name] or in the case of auto-heading numbering, without further intervention.

    11.6 Grouped Text

    11.6.1 Tables

    Tables may be prepared in two either of two forms

    markup example:

      table{ c3; 40; 30; 30;

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

      And here begins another row
      column two of row two
      column three of row two, and so on

      }table

    resulting output:

    This is a table

    this would become column two of row one

    column three of row one is here

    And here begins another row

    column two of row two

    column three of row two, and so on

    a second form may be easier to work with in cases where there is not much information in each column

    markup example:  15 

      !_ Table 3.1: Contributors to Wikipedia, January 2001 - June 2005

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

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

    resulting output:

    Table 3.1: Contributors to Wikipedia, January 2001 - June 2005

    Jan. 2001

    Jan. 2002

    Jan. 2003

    Jan. 2004

    July 2004

    June 2006

    Contributors*

    10

    472

    2,188

    9,653

    25,011

    48,721

    Active contributors**

    9

    212

    846

    3,228

    8,442

    16,945

    Very active contributors***

    0

    31

    190

    692

    1,639

    3,016

    No. of English language articles

    25

    16,000

    101,000

    190,000

    320,000

    630,000

    No. of articles, all languages

    25

    19,000

    138,000

    490,000

    862,000

    1,600,000

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

    11.6.2 Poem

    basic markup:

      poem{

        Your poem here

      }poem

      Each verse in a poem is given a separate object number.

    markup example:

      poem{

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

      }poem

    resulting output:

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

    11.6.3 Group

    basic markup:

      group{

        Your grouped text here

      }group

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

    markup example:

      group{

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

      }group

    resulting output:

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

    11.6.4 Code

    Code tags are used to escape regular sisu markup, and have been used extensively within this document to provide examples of SiSU markup. You cannot however use code tags to escape code tags. They are however used in the same way as group or poem tags.

    A code-block is treated as an object and given a single object number. [an option to number each line of code may be considered at some later time]

    use of code tags instead of poem compared, resulting output:

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

    11.7 Book index

    To make an index append to paragraph the book index term relates to it, using an equal sign and curly braces.

    Currently two levels are provided, a main term and if needed a sub-term. Sub-terms are separated from the main term by a colon.

        Paragraph containing main term and sub-term.
        ={Main term:sub-term}

    The index syntax starts on a new line, but there should not be an empty line between paragraph and index markup.

    The structure of the resulting index would be:

        Main term, 1
          sub-term, 1

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

        Paragraph containing main term, second term and sub-term.
        ={first term; second term: sub-term}

    The structure of the resulting index would be:

        First term, 1,
        Second term, 1,
          sub-term, 1

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

        Paragraph containing main term, second term and sub-term.
        ={Main term:sub-term+1|second sub-term

        A paragraph that continues discussion of the first sub-term

    The plus one in the example provided indicates the first sub-term spans one additional paragraph. The logical structure of the resulting index would be:

        Main term, 1,
          sub-term, 1-3,
          second sub-term, 1,


     11. a footnote or endnote

     12. self contained endnote marker & endnote in one

     * unnumbered asterisk footnote/endnote, insert multiple asterisks if required

     ** another unnumbered asterisk footnote/endnote

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

     +2. editors notes, numbered asterisk footnote/endnote series

     13. <http://www.jus.uio.no/sisu/>

     14. <http://www.ruby-lang.org/en/>

     15. Table from the Wealth of Networks by Yochai Benkler

    <http://www.jus.uio.no/sisu/the_wealth_of_networks.yochai_benkler>

    TOC linked  toc  Full Text  scroll  PDF portrait   pdf  PDF landscape   pdf  ODF/ODT  odt    A-Z  Document Manifest  @
    << previous TOC next >>
    < ^ >

    SiSU

    Output generated by SiSU 0.70.0 2008-12-03 (2008w48/3)
    SiSU Copyright © Ralph Amissah 1997, current 2008. All Rights Reserved.
    SiSU is software for document structuring, publishing and search,
    www.jus.uio.no/sisu and www.sisudoc.org
    w3 since October 3 1993 ralph@amissah.com

    SiSU using:
    Standard SiSU markup syntax,
    Standard SiSU meta-markup syntax, and the
    Standard SiSU object citation numbering and system, (object/text positioning system)
    Copyright © Ralph Amissah 1997, current 2008. All Rights Reserved.

    GPLv3

    SiSU is released under GPLv3 or later, <http://www.gnu.org/licenses/gpl.html>

    SiSU, developed using Ruby on Debian/Gnu/Linux software infrastructure, with the usual GPL (or OSS) suspects.
    Better - "performance, reliability, scalability, security & total cost of ownership" [not to mention flexibility & choice] use of and adherence to open standards (where practical and fair) and it is software libré.
    Get With the Future Way Better!



    idx txt


    SiSU manual


    SiSU