RE: Jade/DSSSL future

Subject: RE: Jade/DSSSL future
From: "Didier PH Martin" <martind@xxxxxxxxxxxxx>
Date: Sun, 30 May 1999 08:17:38 -0400
Hi James,

There are some elements in XSLFo that are hard to translate into the
existing Mozilla object bank. To implement the full spec we need:

a) a first set of FO stabilized
b) to create new FO to the current existing set.

James, I didn't say it is technically impossible. The problems are more with
schedule and delivery (we're so late). And we have to first find a way to
integrate transformation languages (we're working on this actually). Thus,
we have first to create an architecture for transformation languages. Then,
we'll have to create the notion of FO independent of HTML.

Didier PH Martin

-----Original Message-----
From: owner-dssslist@xxxxxxxxxxxxxxxx
[mailto:owner-dssslist@xxxxxxxxxxxxxxxx]On Behalf Of James Tauber
Sent: Saturday, May 29, 1999 10:39 PM
To: dssslist@xxxxxxxxxxxxxxxx
Subject: Re: Jade/DSSSL future

> The probability to have XSLFO is very very low. We are not working on
> it. This is too much work to reconcile CSS objects and XSLFO objects.

I don't see why it would be. Most of the XSL flow objects in the current
draft are very similar to their CSS counterparts. I would have imagined that
the harder parts of rendering CSS objects would be those parts relating to
formatting in general, independent of whether CSS or XSL flow objects are
being used, so it would be relatively easy to drive the rendering engine
with XSL FOs as well as CSS FOs.

Admittedly, the functionality of XSL FOs will exceed CSS FOs in later
drafts, but I don't see there being any great reconciliation effort needed
by implementors. The XSL WG is doing that work for you.


 DSSSList info and archive:

 DSSSList info and archive:

Current Thread