[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Guidelines for client-side XSLT (WAS Re: XSL 2.0
On 30/06/07, M. David Peterson <m.david@xxxxxxxxxxxxx> wrote:
On Fri, 29 Jun 2007 14:16:16 -0600, Jirka Kosek <jirka@xxxxxxxx> wrote:Agreed. > Moreover, if you invoke XSLT by using <?xml-stylesheet?> PI then there > is a known problem of IE which strips all whitespace nodes from input > document. You can overcome this problem by invoking transformation from > JavaScript, but there is no cross-platform Javascript API for XSLT, so > you have to use some bridging library like Sarissa. And there are still > user agents that doesn't do XSLT -- search engines and some minor, but > still used browsers. So it is not that simple, and producing HTML on > server means that you don't have to cope with many annoying browser > quirks. Agreed again. However, AFAIK we have no repository or Wiki, where Jirka and others can lookup reliably how to do it. Instead, rumors are used as a base for design decisions (see above). To give you an example: whether or not that client supports XSLT. In the case of Google, I would send them a prerendered (or potentially dynamically rendered) HTML file. Google is perfectly happy with XML, it uses the text for indexing and the anchor elements to find other pages, maybe XML again. Same with Yahoo, only MSN does not spider XML, but this will come soon I think. If you could propose a place for such a factual base about client-side XSLT, I would be happy to contribute. Regards, Manfred
|
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
|