Projects / SiSU
SiSU
SiSU (Structured information, Serialized Units) is a lightweight markup based, text structuring and publishing framework (that features granular search). With minimal markup of a plaintext file, it produces: plain-text, HTML, XHTML, XML, ODF, LaTeX, PDF, and populates an SQL database at an object/paragraph level for granular searches. Prepare documents using your text editor of choice, then use SiSU to generate the desired output formats. SiSU is controlled from the command line.
| Tags | Text Processing Markup XML TeX/LaTeX Information Management Database HTML/XHTML General Document Repositories |
|---|---|
| Operating Systems | POSIX Linux |
| Implementation | Ruby |
Recent releases
- 19 Jan 2009 05:01
No changes have been submitted for this release.
- 31 Dec 2008 10:03
No changes have been submitted for this release.
- 24 Dec 2008 13:40
No changes have been submitted for this release.
- 16 Dec 2008 06:56
No changes have been submitted for this release.
- 14 Dec 2008 15:09
No changes have been submitted for this release.
- All comments
Recent commentsdiffs and releases
On reflection I withdraw the "diff" suggestion as justification of a release, (unless you know what you are looking at).
Fixes important enough to justify a release may (on occasion) be a code line or even a character in length.
did not realise the 'marketing' thing was not a brand new comment
still ...
Changelog
For future reference the project changelog may be found at:
http://www.jus.uio.no/sisu/SiSU/changelog.html
http://www.jus.uio.no/sisu/SiSU/changelog.html#current
RA
Re: Marketing gimmick
> One of the many who do not give changes
> information while releasing new version.
> Do they just give new version number and
> resubmit to remain on the front page of
> freshmeat ?
>
> This kind of marketing gimmick is
> adopted by lot others who resubmit
> without any considerable change in their
> versions. This kind of manipulation of
> platform like freshmeat must be plugged
> by freshmeat administration.
A url to the changelog is submitted with each release
(the most recent being):
http://www.jus.uio.no/sisu/SiSU/changelog.html#0.53.0
[changes are a bit more significant than reported in the
changelog as there are bugfixes and this starts to work
with ruby1.9 (as currently found in Debian
[ruby 1.9.0 (2007-05-26 patchlevel 0)] though working
with ruby 1.9 is not an immediate goal by any means.
So far each version released has been submitted to
freshmeat (I plan to continue to do so, unless freshmeat
policy is somehow that this should not be the case).
Incidentally I use freshmeat as an additional/external
record of version releases - rather than as a 'marketing
tool'.
If you (or anyone) need verification of change, do diffs
against versions (the last two you will find at):
http://www.jus.uio.no/sisu/pkg/src/sisu_0.52.7.orig.tar.gz
http://www.jus.uio.no/sisu/pkg/src/sisu_0.53.0.orig.tar.gz
(and compare lib/sisu/52.7 with lib/sisu/v0)
enjoy :)
RA
Marketing gimmick
One of the many who do not give changes information while releasing new version. Do they just give new version number and resubmit to remain on the front page of freshmeat ?
This kind of marketing gimmick is adopted by lot others who resubmit without any considerable change in their versions. This kind of manipulation of platform like freshmeat must be plugged by freshmeat administration.