RE: html to dsssl ?

["Didier PH Martin" <martind@xxxxxxxxxxxxx>]

Hi Sebastian,

Sebastian said:
Surely the existing XSL processors separate out the parser engine, and
do not care what it is so long as it delivers a document tree? the XSL
parser and applicator itself, of course, will remain untouched. I
really don't think its that unlikely that someone would fit an SGML
parser to an XSL engine during the course of the next year

Didier says:
I was sure you would say that :-))
OK let's now take it differently: I really don't think that its unlikely
that someone would add a XSL type of functionality to OpenJade. What such
thing would this bring? RTF, HTML, MIF, Tex (and PDF) output for both SGML
and XML. In fact, it is more probable that this happens than having the XML
world going toward the SGML world :-))


Sabastian said:
Actually, I suspect that what we'll see is people who need to stay in
SGML archivally and for special applications will add an SGML->XML
process in their filter chain, and start to use XML tools....


Didier says:
And then add a new layer, more complexity, more work, hummmm not necessarily
the best.

Actually, here is what is happening in the XSL world. Most of the
implementations are made in Java except Keith Moore which is working on a
C++ one (and off course the microsoft implementation).
Don't you think that the OpenJade world could improve the actual product to
add new features like templates, new script languages? Let's supose for a
minute that it would be the case. We then have a chance to have a better
tool than what's actually available.



regards
Didier PH Martin
mailto:martind@xxxxxxxxxxxxx
http://www.netfolder.com


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