W3C home > Mailing lists > Public > www-style@w3.org > September 2002

RE: XSL-FO's

From: Ian Tindale <ian_tindale@yahoo.co.uk>
Date: Thu, 5 Sep 2002 23:44:47 +0100
To: <www-style@w3.org>
Message-ID: <000201c2552d$db49a080$fc00a8c0@solstice>


> -----Original Message-----
> From: www-style-request@w3.org [mailto:www-style-request@w3.org] On Behalf
> Of HÃ¥kon Wium Lie
> Sent: 05 September 2002 22:59
> 
>  > If you need to know, you're looking in the wrong place - you've
>  > gone too far, turn back. Return to the source.
> 
> I'm a speech browser on the web. I've been sent an XSL-FO "document".
> How do I return to the source?

Oops, sorry, you've received the wrong information. Can't think how that might have happened, unless it has something to do with the extremely illogical carry-over of aural properties into XSL-FO from CSS2, which was pretty bloody daft if you ask me. :)

I'd have thought it would be more logical to sort out what kind of UA you are - HTML browser, XML 'browser', television, WAP device, speaky thing, Braille terminal, synthesizer, teapot etc, and send you precisely the kind of stuff you'll be happy with. Aural properties to my mind belong in a stylesheet model of their own, rather than being tucked away in the corner of a visual spec, where they've more chance of being ignored than used. Thus, if you're a speech browser, you'll be sent a differently transformed set of objects, and hopefully a different 'style' sheet also. Neither of which would be applicable to a visual device, but that eventuality would never happen would it.

Rather than letting accessibility in a little bit, like giving a concession 'oh, here, have this dusty corner of the style sheet spec', why not have entire style sheet modes for different sensory environments, and deliver appropriately?

Ian Tindale
Received on Thursday, 5 September 2002 18:45:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:16 GMT