aboutsummaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorRalph Amissah <ralph@amissah.com>2010-02-04 17:45:16 -0500
committerRalph Amissah <ralph@amissah.com>2010-02-04 17:45:16 -0500
commitff555f6a7459ca2e925aefe0821d7057cec76e51 (patch)
treeeed591b2fad690a3f0a0ec73d9dd6b2f922d2f7a
parent blob update, odt.zip fixes heading bug in odt representations (diff)
CHANGELOG & README ...
-rw-r--r--CHANGELOG10
-rw-r--r--README36
-rw-r--r--data/doc/sisu/README36
-rw-r--r--data/doc/sisu/v1/CHANGELOG10
4 files changed, 58 insertions, 34 deletions
diff --git a/CHANGELOG b/CHANGELOG
index cb745568..0ccbf3ba 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -10,11 +10,21 @@ Reverse Chronological:
%% STABLE MANIFEST
+%% 1.0.1.orig.tar.gz (2009-12-19:50/6)
+http://www.jus.uio.no/sisu/pkg/src/sisu_1.0.1.orig.tar.gz
+ sisu_1.0.1.orig.tar.gz
+ sisu_1.0.1-1.dsc
+ sisu_1.0.1-1.diff.gz
+
+ * odf:odt odt.zip fix addressing issue with presentation of headings in
+ produced open document text
+
%% 1.0.0.orig.tar.gz (2009-12-19:50/6)
http://www.jus.uio.no/sisu/pkg/src/sisu_1.0.0.orig.tar.gz
7bec7f47f6ad5b816226af0489bc2ae81d4c9092b8870ba939e9f58800245dfd 1554276 sisu_1.0.0.orig.tar.gz
b64f406766c6289edabf97d225bf9eedbba26c8c413091c9bdc7cca9ec7912e5 1145 sisu_1.0.0-1.dsc
002051ea41e5584d463719f9ac560fad3d0de985916b76e403c060f1bda8e21c 152286 sisu_1.0.0-1.diff.gz
+
* open v1 branch, bump series vesion number to 1
* with the introduction of sisu version 2 (a new middle layer engine)
imminent, that will be maintained in parallel with this version, it is
diff --git a/README b/README
index a3f29f7d..d1bd6870 100644
--- a/README
+++ b/README
@@ -13,22 +13,23 @@ Homepage: <http://www.jus.uio.no/sisu>
With minimal preparation of a plain-text (UTF-8) file using its native
markup-syntax, SiSU produces: plain-text, HTML, XHTML, XML, ODF:ODT
(Opendocument), LaTeX, PDF, and populates an SQL database (PostgreSQL or
- SQLite) in paragraph sized chunks so that document searches are done at this
- "atomic" level of granularity.
+ SQLite) with text objects, roughly, paragraph sized chunks so that document
+ searches are done at this level of granularity.
- Outputs share a common citation numbering system, and any semantic meta-data
- provided about the document.
+ Outputs share a common citation numbering system, associated with text
+ objects and any semantic meta-data provided about the document.
SiSU also provides concordance files, document content certificates and
- manifests of generated output.
+ manifests of generated output. Book indexes may be made.
SiSU takes advantage of well established open standard ways of representing
text, and provides a bridge to take advantage of the strengths of each,
- while remaining simple. SiSU implements across document formats a "useful
- common feature set" [coming from a humanities, law, and possibly social
- sciences perspective, rather than technical or scientific writing] ...
- focus is primarily on content and data integrity rather than appearance,
- (though outputs in the various formats are respectable).
+ while retaining minimal markup requirement. SiSU implements a "useful
+ common feature set" across document formats [coming from a humanities, law,
+ and possibly social sciences perspective, rather than technical or
+ scientific writing] ... focus is primarily on content and data integrity
+ rather than appearance, (though outputs in the various formats are
+ respectable).
Syntax highlighting files for a number of editors are provided.
A vim syntax highlighting file and an ftplugin with folds for sisu markup is
@@ -56,22 +57,23 @@ SiSU can be used for Internet, Intranet, local filesystem or cd publishing.
SiSU can be used directly off the filesystem, or from a database.
-SiSU's scalability, is be dependent on your hardware, and filesystem (in my
-case Reiserfs), and/or database Postgresql.
+SiSU's scalability, is be dependent on your hardware, and filesystem and/or
+database Postgresql.
Amongst it's characteristics are:
* simple mnemonoic markup style,
-* the ability to produce multiple output formats, including
-html, structured XML, LaTeX, pdf (via LaTeX), stream to a relational database
-whilst retaining document structure - Postgresql and Sqlite,
+* the ability to produce multiple output formats, including html, XML, LaTeX,
+pdf (via LaTeX), stream to a relational database whilst retaining document
+structure - Postgresql and Sqlite,
* that all share a common citation system (a simple idea from which much good),
possibly most exciting, the following: if fed into a relational database (as it
can be automatically), the document set is searchable, with results displayed
-at a paragraph level, or the possibility of an indexed display of documents in
-which the match is found together with a hyperlinked listing for each of each
+at a paragraph level, or the possibility of an indexed display of documents
+identifying the paragraph in which the match is found (using the object
+citation numbering system) together with a hyperlinked listing for each of each
paragraph in which the match is found. In any event citations using this system
(with or without the relational database) are relevant for all output formats.
diff --git a/data/doc/sisu/README b/data/doc/sisu/README
index a3f29f7d..d1bd6870 100644
--- a/data/doc/sisu/README
+++ b/data/doc/sisu/README
@@ -13,22 +13,23 @@ Homepage: <http://www.jus.uio.no/sisu>
With minimal preparation of a plain-text (UTF-8) file using its native
markup-syntax, SiSU produces: plain-text, HTML, XHTML, XML, ODF:ODT
(Opendocument), LaTeX, PDF, and populates an SQL database (PostgreSQL or
- SQLite) in paragraph sized chunks so that document searches are done at this
- "atomic" level of granularity.
+ SQLite) with text objects, roughly, paragraph sized chunks so that document
+ searches are done at this level of granularity.
- Outputs share a common citation numbering system, and any semantic meta-data
- provided about the document.
+ Outputs share a common citation numbering system, associated with text
+ objects and any semantic meta-data provided about the document.
SiSU also provides concordance files, document content certificates and
- manifests of generated output.
+ manifests of generated output. Book indexes may be made.
SiSU takes advantage of well established open standard ways of representing
text, and provides a bridge to take advantage of the strengths of each,
- while remaining simple. SiSU implements across document formats a "useful
- common feature set" [coming from a humanities, law, and possibly social
- sciences perspective, rather than technical or scientific writing] ...
- focus is primarily on content and data integrity rather than appearance,
- (though outputs in the various formats are respectable).
+ while retaining minimal markup requirement. SiSU implements a "useful
+ common feature set" across document formats [coming from a humanities, law,
+ and possibly social sciences perspective, rather than technical or
+ scientific writing] ... focus is primarily on content and data integrity
+ rather than appearance, (though outputs in the various formats are
+ respectable).
Syntax highlighting files for a number of editors are provided.
A vim syntax highlighting file and an ftplugin with folds for sisu markup is
@@ -56,22 +57,23 @@ SiSU can be used for Internet, Intranet, local filesystem or cd publishing.
SiSU can be used directly off the filesystem, or from a database.
-SiSU's scalability, is be dependent on your hardware, and filesystem (in my
-case Reiserfs), and/or database Postgresql.
+SiSU's scalability, is be dependent on your hardware, and filesystem and/or
+database Postgresql.
Amongst it's characteristics are:
* simple mnemonoic markup style,
-* the ability to produce multiple output formats, including
-html, structured XML, LaTeX, pdf (via LaTeX), stream to a relational database
-whilst retaining document structure - Postgresql and Sqlite,
+* the ability to produce multiple output formats, including html, XML, LaTeX,
+pdf (via LaTeX), stream to a relational database whilst retaining document
+structure - Postgresql and Sqlite,
* that all share a common citation system (a simple idea from which much good),
possibly most exciting, the following: if fed into a relational database (as it
can be automatically), the document set is searchable, with results displayed
-at a paragraph level, or the possibility of an indexed display of documents in
-which the match is found together with a hyperlinked listing for each of each
+at a paragraph level, or the possibility of an indexed display of documents
+identifying the paragraph in which the match is found (using the object
+citation numbering system) together with a hyperlinked listing for each of each
paragraph in which the match is found. In any event citations using this system
(with or without the relational database) are relevant for all output formats.
diff --git a/data/doc/sisu/v1/CHANGELOG b/data/doc/sisu/v1/CHANGELOG
index cb745568..0ccbf3ba 100644
--- a/data/doc/sisu/v1/CHANGELOG
+++ b/data/doc/sisu/v1/CHANGELOG
@@ -10,11 +10,21 @@ Reverse Chronological:
%% STABLE MANIFEST
+%% 1.0.1.orig.tar.gz (2009-12-19:50/6)
+http://www.jus.uio.no/sisu/pkg/src/sisu_1.0.1.orig.tar.gz
+ sisu_1.0.1.orig.tar.gz
+ sisu_1.0.1-1.dsc
+ sisu_1.0.1-1.diff.gz
+
+ * odf:odt odt.zip fix addressing issue with presentation of headings in
+ produced open document text
+
%% 1.0.0.orig.tar.gz (2009-12-19:50/6)
http://www.jus.uio.no/sisu/pkg/src/sisu_1.0.0.orig.tar.gz
7bec7f47f6ad5b816226af0489bc2ae81d4c9092b8870ba939e9f58800245dfd 1554276 sisu_1.0.0.orig.tar.gz
b64f406766c6289edabf97d225bf9eedbba26c8c413091c9bdc7cca9ec7912e5 1145 sisu_1.0.0-1.dsc
002051ea41e5584d463719f9ac560fad3d0de985916b76e403c060f1bda8e21c 152286 sisu_1.0.0-1.diff.gz
+
* open v1 branch, bump series vesion number to 1
* with the introduction of sisu version 2 (a new middle layer engine)
imminent, that will be maintained in parallel with this version, it is