Fw: About the style processing instruction
Hi Didier, Thanks for the explanation. It all makes perfect sense when considering the PI as intended for automating the selection of which stylesheet to use. The end user specifies somehow which back-end(s) he wants - which includes both the physical media (paper, screen, ...) and the ultimate render engine (TeX, OpenGL, ...); the style engine then selects the "best" stylesheet according to this PI. If this is the case, don't we have to define a clear algorithm which stylesheet is the "best" match? This would be trivial if the user specifies a single back end. However if the user to specifies several alternatives (say with a priority for each) then it becomes much less simple. Another issue is standard names such as "TeX", "OpenGL", "Glasses". While the set of names was small - "screen", "print" this wasn't a problem. But if this is to be extended to use to specify back-end programs and their parameters, we'd need Iana-like namespace management. Is there a reasonable way to make use of the existing Iana name space somehow (e.g., "screen,application/tex")? Share & Enjoy, Oren. XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format