SiSU - Manual,
Ralph Amissah

  1

What is SiSU?

  2

Markup Syntax History

  392

14. SiSU filetypes

14. SiSU filetypes

  409

SiSU has plaintext and binary filetypes, and can process either type of document.

  410

14.1 .sst .ssm .ssi marked up plain text

  411

SiSU documents are prepared as plain-text (utf-8) files with SiSU markup. They may make reference to and contain images (for example), which are stored in the directory beneath them _sisu/image. SiSU plaintext markup files are of three types that may be distinguished by the file extension used: regular text .sst; master documents, composite documents that incorporate other text, which can be any regular text or text insert; and inserts the contents of which are like regular text except these are marked .ssi and are not processed.

  412

SiSU processing can be done directly against a sisu documents; which may be located locally or on a remote server for which a url is provided.

  413

SiSU source markup can be shared with the command:

  414

sisu -s [filename]

  415

14.1.1 sisu text - regular files (.sst)

  416

The most common form of document in SiSU, see the section on SiSU markup.

  417

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

  418

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

  419

14.1.2 sisu master files (.ssm)

  420

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.

  421

The mechanism by which master files incorporate other documents is described as one of the headings under under SiSU markup in the SiSU manual.

  422

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.

  423

Note: a secondary file of the composite document is built prior to processing with the same prefix and the suffix ._sst   ²² 

  424

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

  425

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

  426

14.1.3 sisu insert files (.ssi)

  427

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.

  428

14.2 sisupod, zipped binary container (sisupod.zip, .ssp)

  429

A sisupod is a zipped SiSU text file or set of SiSU text files and any associated images that they contain (this will be extended to include sound and multimedia-files)

  430

SiSU plaintext files rely on a recognised directory structure to find contents such as images associated with documents, but all images for example for all documents contained in a directory are located in the sub-directory _sisu/image. Without the ability to create a sisupod it can be inconvenient to manually identify all other files associated with a document. A sisupod automatically bundles all associated files with the document that is turned into a pod.

  431

The structure of the sisupod is such that it may for example contain a single document and its associated images; a master document and its associated documents and anything else; or the zipped contents of a whole directory of prepared SiSU documents.

  432

The command to create a sisupod is:

  433

sisu -S [filename]

  434

Alternatively, make a pod of the contents of a whole directory:

  435

sisu -S

  436

SiSU processing can be done directly against a sisupod; which may be located locally or on a remote server for which a url is provided.

  437

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

  438

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

  439

 ^22. .ssc (for composite) is under consideration but ._sst makes clear that this is not a regular file to be worked on, and thus less likely that people will have "accidents", working on a .ssc file that is overwritten by subsequent processing. It may be however that when the resulting file is shared .ssc is an appropriate suffix to use.

Output generated by SiSU 0.59.0 2007-09-23 (2007w38/0)
SiSU Copyright ^© Ralph Amissah 1997, current 2007. 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 2007. All Rights Reserved.

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 libre.
Get With the Future Way Better!