Re: (dsssl) [help wanted] OpenJade

[Sebastian Rahtz <sebastian.rahtz@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

Adam Di Carlo writes:
 > So -- C++ and DSSSL hackers and documenters!  Let them say XSL is the
 > future -- maybe they are right and maybe not.  Who knows.  Who cares?
 > We have single sourced documentation with XML and SGML today, with
 > high-quality printing, and a stable spec, *today*!  Can the XSL-FO
 > toolchain say that?   I don't think so.

*If* you regard the jadetex component as part of the "DSSSL Solution",
then I would make a comment or two

 a) jadetex is NOT doing a perfect job. it really needs someone to
 lift it from its present hibernation (twitching occasionally in its
 sleep), and fix up all the problems.

 b) if I make an XSL FO file, I can run it through 2 free and 2
 commercial processors today on this computer (FOP, PassiveTeX,
 Antenna House, XEP); none of them perfect, but between them I'd claim
 they (easily) cover more than jadetex

what I do not know (from lack of trying) is whether the PDF and MIF
backends to Jade do as good a job. To my mind, the OpenJade project
should really be pushing the direct PDF backend.

 > programming symantics with their schema systems, and that seems to be
 > breaking apart (TREX, Relax, XML Schema).  Is it just me or is it all
 > trying to recapture (badly) computer science features that lisp (and
 > others) had 50 years ago?]

of course it is. thats life... was it ever fair?

sebastian


 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist