>> The page that illustrates the problem best is this one:

I don't think you've said what differences you see (a quick look they
looked the similar in FF and IE) so it's hard to give specific advice,
but just a general observation

You said the problem was in output generated a template that had:

 >>            name="span">
> >>            <xsl:attribute
> >>                name="class">c</xsl:attribute>

(which could more easily have been written <span class="c"> you only
need   xsl:element and xsl:attribute if the element names are
constructed dynamically) however the example page you quote doesnt have
a class="c" anywhere?.

The page is a mixture of xhtml and elements with local names of html
elements but in no namespace. If it was served with an xml mime tye
FF would not render the no-namespace elements, and IE doesn't understand
xhtml at all. You just get rendered result as the file is served as
text/html so the (no)namespace declarations (and xml syntax such as <br/.) are
ignored, however it may be easier to get cross platform behaviour if you
generate either xhtml (in the xhtml namespace) or html (necessarily in
no namespace)

David

________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.

This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs. 
________________________________________________________________________