Altova Mailing List Archives

Re: [xsl] XHTML html validation

From: Owen Rees <owen.rees@------>
Date: 2/16/2007 4:14:00 PM
--On Friday, February 16, 2007 13:51:15 +0000 John Steel wrote:

Owen Rees wrote:

[...] Your top
level element should start with something like this:

<html xmlns="" xml:lang="en" lang="en">

Oh man, well even though this is like pulling teeth I'm hoping others wo
do the same will benefit :-)
When I make the change you suggest, all my xml tags appear in the source
of the page literally as though my stylesheet wasn't used.

Perhaps it was not clear but I was referring to the output from the 
transform when I referred to the top level element. In order to be XHTML, 
the elements must be in the correct namespace, and your transform must put 
them in that namespace if they are not already in that namespace in the 

I think it would help to separate the problems of generating correct XHTML 
and delivering it to the browser. Small but complete sample input XML and 
simplified but complete stylesheet would be useful for the generating 
correct XHTML part.

Owen Rees
Hewlett Packard Laboratories, Bristol, UK


These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.