From a72e66db913de3a2e508080c8b1fc8d1342a899b Mon Sep 17 00:00:00 2001 From: Ralph Amissah Date: Tue, 25 Sep 2007 23:23:03 +0100 Subject: remove generated output from main package --- .../sisu_manual/sisu_filetypes/scroll.xhtml | 529 --------------------- 1 file changed, 529 deletions(-) delete mode 100644 data/doc/manuals_generated/sisu_manual/sisu_filetypes/scroll.xhtml (limited to 'data/doc/manuals_generated/sisu_manual/sisu_filetypes/scroll.xhtml') diff --git a/data/doc/manuals_generated/sisu_manual/sisu_filetypes/scroll.xhtml b/data/doc/manuals_generated/sisu_manual/sisu_filetypes/scroll.xhtml deleted file mode 100644 index 10d37c04..00000000 --- a/data/doc/manuals_generated/sisu_manual/sisu_filetypes/scroll.xhtml +++ /dev/null @@ -1,529 +0,0 @@ - - - - - - - - Title: - - SiSU - Filetypes - -
- Creator: - - Ralph Amissah - -
- Rights: - - Copyright (C) Ralph Amissah 2007, part of SiSU documentation, License GPL 3 - -
- Type: - - information - -
- Subject: - - ebook, epublishing, electronic book, electronic publishing, electronic document, electronic citation, data structure, citation systems, search - -
- Date created: - - 2002-08-28 - -
- Date issued: - - 2002-08-28 - -
- Date available: - - 2002-08-28 - -
- Date modified: - - 2007-09-16 - -
- Date: - - 2007-09-16 - -
- - - - - SiSU - Filetypes,
Ralph Amissah - - 1 - - - - 1. SiSU filetypes - - 2 - - - - SiSU has plaintext and binary filetypes, and can process either -type of document. - - 3 - - - - 1.1 .sst .ssm .ssi marked up plain text - - 4 - - - - 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. - - 5 - - - - 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. - - 6 - - - - SiSU source markup can be shared with the command: - - 7 - - - - sisu -s [filename] - - 8 - - - - 1.1.1 sisu text - regular files (.sst) - - 9 - - - - The most common form of document in SiSU, see the section on -SiSU markup. - - 10 - - - - <http://www.jus.uio.no/sisu/sisu_markup> - - 11 - - - - <http://www.jus.uio.no/sisu/sisu_manual> - - 12 - - - - 1.1.2 sisu master files (.ssm) - - 13 - - - - 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. - - 14 - - - - The mechanism by which master files incorporate other documents is -described as one of the headings under under SiSU markup in the -SiSU manual. - - 15 - - - - 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. - - 16 - - - - Note: a secondary file of the composite document is built prior to -processing with the same prefix and the suffix ._sst 1 - - - 1. .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. - - 17 - - - - <http://www.jus.uio.no/sisu/sisu_markup> - - 18 - - - - <http://www.jus.uio.no/sisu/sisu_manual> - - 19 - - - - 1.1.3 sisu insert files (.ssi) - - 20 - - - - 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. - - 21 - - - - 1.2 sisupod, zipped binary container (sisupod.zip, .ssp) - - 22 - - - - 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) - - 23 - - - - 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. - - 24 - - - - 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. - - 25 - - - - The command to create a sisupod is: - - 26 - - - - sisu -S [filename] - - 27 - - - - Alternatively, make a pod of the contents of a whole directory: - - 28 - - - - sisu -S - - 29 - - - - 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. - - 30 - - - - <http://www.jus.uio.no/sisu/sisu_commands> - - 31 - - - - <http://www.jus.uio.no/sisu/sisu_manual> - - 32 - - - - 2. Experimental Alternative Input Representations - - 33 - - - - 2.1 Alternative XML - - 34 - - - - 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. - - 35 - - - - convert from sst to simple xml representations (sax, dom and -node): - - 36 - - - - sisu --to-sax [filename/wildcard] or sisu --to-sxs -[filename/wildcard] - - 37 - - - - sisu --to-dom [filename/wildcard] or sisu --to-sxd -[filename/wildcard] - - 38 - - - - sisu --to-node [filename/wildcard] or sisu --to-sxn -[filename/wildcard] - - 39 - - - - convert to sst from any sisu xml representation (sax, dom and -node): - - 40 - - - - sisu --from-xml2sst [filename/wildcard -[.sxs.xml,.sxd.xml,sxn.xml]] - - 41 - - - - or the same: - - 42 - - - - sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] - - 43 - - - - 2.1.1 XML SAX representation - - 44 - - - - To convert from sst to simple xml (sax) representation: - - 45 - - - - sisu --to-sax [filename/wildcard] or sisu --to-sxs -[filename/wildcard] - - 46 - - - - To convert from any sisu xml representation back to sst - - 47 - - - - sisu --from-xml2sst [filename/wildcard -[.sxs.xml,.sxd.xml,sxn.xml]] - - 48 - - - - or the same: - - 49 - - - - sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] - - 50 - - - - 2.1.2 XML DOM representation - - 51 - - - - To convert from sst to simple xml (dom) representation: - - 52 - - - - sisu --to-dom [filename/wildcard] or sisu --to-sxd -[filename/wildcard] - - 53 - - - - To convert from any sisu xml representation back to sst - - 54 - - - - sisu --from-xml2sst [filename/wildcard -[.sxs.xml,.sxd.xml,sxn.xml]] - - 55 - - - - or the same: - - 56 - - - - sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] - - 57 - - - - 2.1.3 XML Node representation - - 58 - - - - To convert from sst to simple xml (node) representation: - - 59 - - - - sisu --to-node [filename/wildcard] or sisu --to-sxn -[filename/wildcard] - - 60 - - - - To convert from any sisu xml representation back to sst - - 61 - - - - sisu --from-xml2sst [filename/wildcard -[.sxs.xml,.sxd.xml,sxn.xml]] - - 62 - - - - or the same: - - 63 - - - - sisu --from-sxml [filename/wildcard [.sxs.xml,.sxd.xml,sxn.xml]] - - 64 - - - - Endnotes - - 0 - - - -- cgit v1.2.3