Thanks to Jon for the informative overview, and to Lee for the
csszengarden link. Both were very helpful. But I'm still puzzled about a
few things. Please bear with me. I'm just trying to understand the Lenya
approach.
Is it fair to say that xml/xsl/xslt/xsl-fo was conceived as a sort of
"grand solution" to the problem of separation of content, logic and
presentation, with xml for content, xsl for stylesheets, xslt for
transformations and xsl-fo for presentation? If so, it appears to be a
very good solution. XML is touted as probably the best overall format
for content, and is used extensively. XSLT would transform that content
to html/xhtml. That leaves XSL and XSL-FO. So I'm left wondering why
isn't xsl (eXtensionable Stylesheet Language, it even has stylesheet
language in its name!) used for stylesheets instead of CSS? Then I read
that browsers aren't able to handle xsl-fo. Is that the crux of the
problem? That xml/xsl/xslt/xsl-fo is the optimal solution, but browsers
just aren't ready for it?
And CSS's are used instead because browsers do understand CSS?
And finally, if tomorrow all major browsers were able to understand
xml/xsl/xslt/xsl-fo would there be a need for Cocoon, and would Lenya
(without Cocoon) become almost like a front-end for xml/xsl/xslt/xsl-fo?
glhowze
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
