Subject: Error correction From: "Didier PH Martin" <martind@xxxxxxxxxxxxx> Date: Thu, 28 Jan 1999 23:50:33 -0500 |
Hi Chris, I made an error the style specs says that the href property is a URI and therefore can be a URN (RFC 2141) thus a style sheet can be location independant if a URN is used instead of a URL. Also: Maybe I should use the media property which is already extensible. here a spec extract: 6.13 Media descriptors The following is a list of recognized media descriptors ( %MediaDesc in the DTD). screen Intended for non-paged computer screens. tty Intended for media using a fixed-pitch character grid, such as teletypes, terminals, or portable devices with limited display capabilities. tv Intended for television-type devices (low resolution, color, limited scrollability). projection Intended for projectors. handheld Intended for handheld devices (small screen, monochrome, bitmapped graphics, limited bandwidth). print Intended for paged, opaque material and for documents viewed on screen in print preview mode. braille Intended for braille tactile feedback devices. aural Intended for speech synthesizers. all Suitable for all devices. Future versions of HTML may introduce new values and may allow parameterized values. To facilitate the introduction of these extensions, conforming user agents must be able to parse the media attribute value as follows: The value is a comma-separated list of entries. For example, media="screen, 3d-glasses, print and resolution > 90dpi" is mapped to: "screen" "3d-glasses" "print and resolution > 90dpi Each entry is truncated just before the first character that isn't a US ASCII letter [a-zA-Z] (Unicode decimal 65-90, 97-122), digit [0-9] (Unicode hex 30-39), or hyphen (45). In the example, this gives: "screen" "3d-glasses" "print" A case-sensitive match is then made with the set of media types defined above. User agents may ignore entries that don't match. In the example we are left with screen and print ------------------------- So maybe I should use media="screen, rtf" or media="screen, CGM" this way I would be compliant with the specs :-) Is it OK now? So I would get instead: <?xml-stylesheet href="urn:tns:myscript" type="text/xsl" media="screen, CGM" ?> the URN gives me location independence and the media give mr freedom of choice for my rendering. If the browser cannot assure me Qality of rendering it could degrade to what it is capable of. At least my style specification would indicate my level of rendering service quality. I guess now we have common ground :-) thanx for the challenge, I get a better processing instruction. By the way I like the media property example it illustrates very well what quality of service for rendering means. It means that if the client's browser has 3d-glasses it will be rendered better. Same thing for my CGM renderer, as a producer I know that my work will be better rendered with a CGM compliant device (again, this is an example) Cheers Didier PH Martin mailto:martind@xxxxxxxxxxxxx http://www.netfolder.com XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Getting MSIE5b2 "Using XSL to Gener, TK | Thread | RE: Error correction (Was also Anno, Heikki Toivonen |
RE: Announcement, Didier PH Martin | Date | RTF specs, Didier PH Martin |
Month |