[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: About the style processing instruction
Hi Matthieu <Comment> Don't you think that the best situation you discribe here would be possible if each different backend could be define externally. I explain: I suppose that we could consider a FO document as a XML document. If it is possible to write a XSL ss like "FO document to TeX ocument" which translate all FO to a specific backend, thus, any new backend could be added to any browser. This need two XSL process "work" (one for PI given by the XSL ss author, and one another for the PI about the FO translation). Perhaps I've made a mistake by considering a FO document like a XML document, or perhaps this already exist and in this case excuse me. In the contrary, this could be a solution. <Reply> Tell me if I get it right. Your suggestion is that a style sheet may contain instructions telling which back end to use or at least require that rendering level of quality (the browser provide a rendering in accordance to this format rendering model). So, we don't specify in the content XML document the media output but in the style sheet document. Am I right? Is it what you are saying? Regards Didier PH Martin mailto:martind@xxxxxxxxxxxxx http://www.netfolder.com 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
|