Are you sure that having the browser use its own XSL engine to transform the XML to HTML is really a good idea? You will be limiting your readership (as not everyone uses such a browser), and opening yourself up to possible incompatibilities in how such browsers perform the transform (not all XSL-powered browsers use the same XSL processor). Server-side transformation "on-the-fly" avoids both these issues, and may be achieved by two basic methods. 1) use a servlet (Saxon can be so used); 2. write a web-scripting language page (such as PHP, or ASP) and pull the XML and XSL files together, such a page can be a three or four line affair.
Since you are having no problems transforming DC on the client ,I presume that the processing instruction (<?xml:stylesheet href="http://path_to_stylesheet" type="text/xsl"?>) in those files is good. I would hazard a guess that your Saxon stylesheet is in some way incompatible with the Microsoft MSXML parser.
Yale University Library::Manuscripts and Archives
At 12:20 PM 11/15/2002 +0200, you wrote:
>I wonder if anyone knows how to solve this problem
>I have many EAD files which when I run them through SAXON render very nicely into HTML files and are then posted on the web. However I have had a directive to render these files directly on the browser in xml - i.e. the stylesheet reference is included in the EAD file and the address in the internet bar shows Blah.xml instead of Blah.html.
>I have tried many things but am unable to get this to happen - it seems that the links to the individual files just will not render. Is this something to do with MSXML and SAXON differences. I have done the same thing with TEI Lite and Dublin Core files and have had no problem.
>Any assistance would be gratefully received
>University of Natal
>[log in to unmask]