- From: Lars Marius Garshol <larsga@ifi.uio.no>
- Date: 04 Nov 1997 23:44:43 +0100
- To: www-style@w3.org
* Chris Lilley | | Thanks. Detailed comments, criticisms, change requests, etc are | welcome, in this mailing list. The document asked for comments on the speak-* properties, and they sounded sane to me. I can see many cases in which they would be useful. cue-before/-after sounds very important. I'm thinking of cases like <P CLASS=warning> Don't do this at home! </P> or <CODE CLASS=scheme> (define ! (lambda(n) ; interesting Scheme code here )) </CODE> However, making audio samples of things like somebody saying warning or Scheme code ahead requires a bit of resources and know-how. Also, the sample may be unavailable/in the wrong format/whatever. IMHO it would be a good thing to allow string values as well as URLs. That way one could write CODE.scheme { speak-punctuation: code; speech-rate: slow; cue-before: "Scheme example"; pause-before: 100ms; pause-after: 100ms } Similarly, the ability to insert text and/or attribute values would be a good thing. Some XML applications are probably going to require the insertion of text at certain points and they will be that much harder to display with CSS if CSS cannot insert text. I assume we'll have to wait for XSL/DSSSL specifications and implementations. | Tell us about what parts you like, too. I liked that the specification was much more thorough and exact. The CSS1 spec left room for interpretation, which probably wasn't a good thing, so I for one am glad there is less room now. Other than that I can only say that I wish this entire effort the best of luck. May we see better implementations of CSS2 than we've seen of CSS1... -- "These are, as I began, cumbersome ways / to kill a man. Simpler, direct, and much more neat / is to see that he is living somewhere in the middle / of the twentieth century, and leave him there." -- Edwin Brock http://www.ifi.uio.no/~larsga/ http://birk105.studby.uio.no/
Received on Tuesday, 4 November 1997 17:45:36 UTC