Your message dated Thu, 1 Aug 2013 23:35:02 -0400
with message-id <[email protected]>
and subject line Re: Bug#627629: short justification why 'foo' can not
substitute 'sisu'
has caused the Debian Bug report #627629,
regarding short justification why 'foo' can not substitute 'sisu'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
627629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627629
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sisu
Severity: wishlist
may be i did not search well enough, but i did not find a justification
why 'foo' can not substitute 'sisu'. Even on irc #sisu i could not get
the answer.
*) With foo i mean the whole farm of markup languages with their
corresponding converters like REST, Docbook and so on.
I would be nice to find a short hint like "sisu can do x and y while
others can only do x or y"
This might be a important part of the package description.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.38-2-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--- End Message ---
--- Begin Message ---
Package: sisu
Severity: wishlist
Here in closing this bug which has lived here long enough, are some
short comments on sisu, and some more general comments.
I don't think any justification is required & sorry I cannot provide a
meaningful short answer or comparison with the many text markups and
processors out there. However, as a general rule I prefer choice. I like
that there are many editors (I use vim), programming languages of a
particular genre (I use ruby primarily), window managers, tiling ones
even (I use subtle or awesome), web browsers (I have discovered dwb but
also use Iceweasel & chromium), shells (I use zsh), terms (I use urxvt),
terminal multiplexors (tmux) ... and so on and on the list is endless,
and more power to this; I love LaTeX, I like that Lout exists too.
Text markup, and its parsing along with the generation of different text
output formats is an area fertile for experimentation and innovation.
SiSU is described extensively both on the home page (which is dated) and
in its manpages.
Within Debian the short description of sisu is "structuring, publishing
in multiple formats and search" which is sufficient to indicate its
directions.
A number of choices made in sisu markup are related to document
structure, heading relations and sisu defined objects. sisu attempts to
provide an output agnostic / universal object numbering (paragraph
identifying) system, that is able to identify/locate text/objects within
it regardless of the selected output type produced, whether html
latex/pdf epub or sql etc... and it uses these universal numbers
extensively, e.g. in concordance files, book indexes, search results
(and comparing multilingual documents). Some choices in the markup are
to make this possible. For some texts it is also possible with almost no
markup to get meaningful output, see for example the sisu preparation
for Tolstoy's "War and Peace" which is available online. Sisu also
assumes there are a number of documents and provides (configurable
alternative) directory structure to the output it produces, which also
has implications for search and making use of document metadata.
Beyond this short comparisons with other document formats and outputs
are not so helpful.
As I recall you come from a LaTeX and paper based output background ...
and you provided a demonstration of the magnificent possibilities of
LaTeX pdf output, which are impressive and I am aware of. Indeed for pdf
output sisu depends on LaTeX and uses a very small subset of its
capabilities.
Docbook is a lot more verbose than sisu, and has a different focus and
feature set.
The most most widely used (plain) text markup (for generation of
multiple outputs) these days appears to be markdown, which has the
advantage of being more like a prepared pretty plain text file; it
appears there are a couple of extended forms of markdown. One of the
most impressive extended markdown processors appears to be pandoc
("appears" only because I have not yet used it personally). For those
not needing what sisu seeks to do; or indeed for people needing another
focus and feature set (including an even wider range of document output
formats), I recommend looking at pandoc. Indeed REST which you mention
and appears to be similar to markdown & someday I will need to look up
(Wikipedia possibly) how it is different from from markdown.
> May be I did not search well enough, but I did not find a
> justification why 'foo' can not substitute 'sisu'.
Why so many computer languages (or object oriented or functional
programming languages), when each of them is Turing complete? Why so
many text editors? Why so many web browsers?
But seriously it may be useful if you find it but do open source e.g.
text editors, or web browsers, or programming languages need to spend
more time explaining indeed "justifying" why they are different than
describing what they do? & that is rhetorical, I do not expect an
answer, or want this particular discussion, thanks.
> Even on irc #sisu i could not get the answer.
I don't recall the question, or discussion if there was one, though I
can imagine being tempted to ignore it then as now ... it is too broad,
a bother, unintended humbug. One would have to attempt to address each
other markup, (that I do not use) something I again avoid here on
closing this wishlist bug. Ideas for sisu existed by or before 1996,
and work on it started in 1997, nothing like it existed then and as
described it remains different in scope, focus and approach from the
other fish out there.
Thanks,
ralph
* Jonas Stein <[email protected]>
[Sun, 22 May 2011 23:37:48 +0200], wrote:
> Package: sisu
> Severity: wishlist
>
> may be i did not search well enough, but i did not find a justification
> why 'foo' can not substitute 'sisu'. Even on irc #sisu i could not get
> the answer.
>
> *) With foo i mean the whole farm of markup languages with their
> corresponding converters like REST, Docbook and so on.
>
> I would be nice to find a short hint like "sisu can do x and y while
> others can only do x or y"
>
> This might be a important part of the package description.
>
>
>
> -- System Information:
> Debian Release: wheezy/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: i386 (i686)
>
> Kernel: Linux 2.6.38-2-686 (SMP w/1 CPU core)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
>
>
signature.asc
Description: Digital signature
--- End Message ---
