- From: David Carlisle <davidc@nag.co.uk>
- Date: Sun, 4 Feb 2001 22:55:51 GMT
- To: Arved_37@chebucto.ns.ca
- CC: www-xsl-fo@w3.org
> That being said, I agree that the _XSL WG_ intends FO to be something that > could be rendered into any format. Not _any_ format, but formats, yes. If XSLFO are not (like dssl before them) intended to be cross format style description, what's the point? In xmltex for example you can either pass your TEI file straight to TeX or you can first munge it into FO and then pass that to TeX. Currently the trip through FO makes it harder rather than easier to achieve many things that one might want to achieve. Far less control over floats, running heads etc, no (standardised) control over pdf features such as bookmarks andacrobat's initial state. However the benefits of FO are (hopefully) that one may express the desired style rules using XSLT/FO which is far more documentatble as a language than "random tex hacks" as used to write a normal tex package, and secondly that that same style specification might be used by a completely different engine formatting to some unknown format. > With reference to my GIF diagram, I'll get Dave to tell you about the disadvantages of using diagrams:-) (actually I only have vt100 telnet access to work at present, will look at it later) > I think HTML+CSS is eminently reasonable as a browser input - I just > don't see FO processing as a reasonable waypoint to arrive at that. If that's all you want, true just write the html directly. But why can't I specify a general layout scheme for my online doc in xsl/FO then produce pdf, dvi, html+css, or some new hypertext system all from the same spec? David _____________________________________________________________________ This message has been checked for all known viruses by Star Internet delivered through the MessageLabs Virus Control Centre. For further information visit http://www.star.net.uk/stats.asp
Received on Sunday, 4 February 2001 17:56:05 UTC