diff options
| author | Ralph Amissah <ralph@amissah.com> | 2013-09-21 00:13:03 -0400 |
|---|---|---|
| committer | Ralph Amissah <ralph@amissah.com> | 2013-09-21 00:13:03 -0400 |
| commit | 1b89f377f4bab1080310c859fd4edbf2c9a5cafe (patch) | |
| tree | 2c96cb94b92c1e1546f7d2ca7a1bcbd3872cb5d4 /data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi | |
| parent | v4 v5: i18n CJK: zh ja ko, add languages Chinese, Japanese, Korean (diff) | |
sisu_manual, move to en/ sub-dir (permitting translations)
* use of language sub-dir for source sisu markup suited to permitting
translation management by po4a
Diffstat (limited to 'data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi')
| -rw-r--r-- | data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi | 26 |
1 files changed, 0 insertions, 26 deletions
diff --git a/data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi b/data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi deleted file mode 100644 index 3372bcd4..00000000 --- a/data/doc/sisu/markup-samples/sisu_manual/sisu_how.ssi +++ /dev/null @@ -1,26 +0,0 @@ -% SiSU 2.0 - -@title: SiSU - :subtitle: How Does SiSU Work? - -@creator: - :author: Amissah, Ralph - -@date: - :published: 2007-09-16 - :created: 2002-08-28 - :issued: 2002-08-28 - :available: 2002-08-28 - :modified: 2011-02-07 - -@rights: - :copyright: Copyright (C) Ralph Amissah 2007 - :license: GPL 3 (part of SiSU documentation) - -:A~? @title @creator - -:B~? Description - -1~sisu_how How does sisu work? - -SiSU markup is fairly minimalistic, it consists of: a (largely optional) document header, made up of information about the document (such as when it was published, who authored it, and granting what rights) and any processing instructions; and markup within the substantive text of the document, which is related to document structure and typeface. SiSU must be able to discern the structure of a document, (text headings and their levels in relation to each other), either from information provided in the document header or from markup within the text (or from a combination of both). Processing is done against an abstraction of the document comprising of information on the document's structure and its objects,[2] which the program serializes (providing the object numbers) and which are assigned hash sum values based on their content. This abstraction of information about document structure, objects, (and hash sums), provides considerable flexibility in representing documents different ways and for different purposes (e.g. search, document layout, publishing, content certification, concordance etc.), and makes it possible to take advantage of some of the strengths of established ways of representing documents, (or indeed to create new ones). |