From: Greg Faron <gfaron@xxxxxxxxxxxxxxxxxx>
Date: Thu, 07 Nov 2002 11:27:11 -0700
At 03:55 AM 11/7/2002, you wrote:
This also didn't work:
Up to this point, everybody has been assuming that the end-result-HTML
was coming out improperly because many XSLT engines will create the empty tag
<script ... />
rather than what the browser requires:
<script ... ></script>
For this reason, they've found creative ways of forcing individual
beginning and ending tags.
First, take a look at the transformed result and see which is being
produced. If it is the latter, it is not the XSLT conversion that is the
produced HTML file. That would not be an XSL question, but I'll help you
solve it off-list if you mail me the generated HTML and produce for me a
listing of the directory so I can see the exact file hierarchy.
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Integre Technical Publishing Co.