- From: Chris Lilley <chris@w3.org>
- Date: Mon, 14 Feb 2000 15:36:38 +0100
- To: "Pawson, David" <DPawson@rnib.org.uk>
- CC: "'www-svg@w3.org'" <www-svg@w3.org>
"Pawson, David" wrote: > > Chris Lilley wrote: > > >> >One reason > >> >is that XHTML/CSS/XSL do word wrap > >> <snip/> > > >CSS1 and CSS2 and XSL all use a nested box, flow layout model. > > My only issue here is that I can't... sorry I don't think I can, > use CSS with the available SVG viewers today. Well you are using CSS, but not using the default nested box, flow layout model for rendering what CSS produces. Instead you are using the SVG rendering. But you are, at present, using the CSS selectors and cascading of UA, author and reader stylesheets, etc. The problem is that there is not a standardised way yet to switch renderer on an element by element basis. So all text-oriented (eg, HTML browser) implementations of XML plus CSS use the NBFL rendering model and all graphics-oriented (SVG viewer) implementations of SVG plus CSS use the SVG rendering model. > (I am seeking visual output, since I now have html, braille versions) You want graphical visual output of the SVG graphics, and you want some other textual information displayed as flowed text, is that it? What is needed is a viewer that has both NBFL and SVG models, and can nest them; plus the new property that allows the stylesheet author to switch between these two renderers. That could be implemented either by adding a NBFL renderer to an SVG viewer, or adding an SVG renderer to an XML browser. -- Chris
Received on Monday, 14 February 2000 09:36:43 UTC